dbcve.org
Service ManagerApplication · Easyvista

CVE-2022-38492

HIGH · 8.8 CVSS v3.1 Published 2023-01-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An issue was discovered in EasyVista 2020.2.125.3 and 2022.1.109.0.03. One parameter allows SQL injection. Version 2022.1.110.1.02 fixes the vulnerability.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A SQL injection vulnerability exists in EasyVista versions 2020.2.125.3 and 2022.1.109.0.03 where an unspecified parameter allows SQL injection attacks. The vulnerability was patched in version 2022.1.110.1.02.

MitigationApply EasyVista version 2022.1.110.1.02 or later to remediate this SQL injection vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Service ManagerApplication
Affected:= 2020.2.125.3= 2022.1.109.0.03

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify EasyVista Service Manager version
    Access the EasyVista admin portal and navigate to the About or System Information section, or check the installation configuration files for the version number
    Affected if Unable to retrieve version information from the system
  2. Compare against affected version 2020.2.125.3
    Check if the installed version is exactly 2020.2.125.3
    Affected if Version is exactly 2020.2.125.3
  3. Compare against affected version 2022.1.109.0.03
    Check if the installed version is exactly 2022.1.109.0.03
    Affected if Version is exactly 2022.1.109.0.03
  4. Verify current version against fixed release
    If running a 2022.1.x release, confirm the full version string to determine if it predates the patched version 2022.1.110.1.02
    Affected if Version is earlier than 2022.1.110.1.02 and matches the affected release pattern

Environment is affected only if the installed EasyVista Service Manager version is exactly 2020.2.125.3 or exactly 2022.1.109.0.03

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply EasyVista version 2022.1.110.1.02 or later to remediate this SQL injection vulnerability.

Recommended fix High confidence

EasyVista Service Manager 2022.1.110.1.02

  1. Obtain the upgrade package for EasyVista Service Manager version 2022.1.110.1.02 from the official vendor
  2. Review the EasyVista upgrade documentation before proceeding
  3. Create a full backup of the current database and configuration
  4. Test the upgrade in a non-production environment first
  5. Execute the upgrade following vendor-provided installation procedures
  6. Verify the SQL injection vulnerability is resolved by testing the previously vulnerable parameter
  7. Confirm all other system functionalities work correctly after upgrade
Caveat Review release notes for any feature changes between 2020.2.125.3/2022.1.109.0.03 and 2022.1.110.1.02 that may affect existing configurations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Service Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-38492 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-38492 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data