dbcve.org
LemminxApplication · Eclipse

CVE-2022-0672

MEDIUM · 5.5 CVSS v3.1 Published 2022-02-18
Fix available
A fix is available. Upgrade to 0.19.0 or later.
See remediation →
57/100
Remediation priority · Elevated
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
A flaw was found in LemMinX in versions prior to 0.19.0. Insecure redirect could allow unauthorized access to sensitive information locally if LemMinX is run under a privileged user.

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 · moderate confidence

LemMinX XML validator prior to version 0.19.0 contains an insecure redirect vulnerability that could allow unauthorized local file access when the software runs under a privileged user context. The specific mechanics of the redirect are not detailed in the available advisory.

MitigationUpgrade LemMinX to version 0.19.0 or later. Additionally, ensure the application runs with minimal necessary privileges to limit potential impact of local file access.

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
LemminxApplication
Affected:< 0.19.0

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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. Locate the LemMinX installation or JAR file
    Search for files named lemminx, lemminx-*.jar, or org.eclipse.lemminX in common installation directories, project dependencies, or the application's classpath
    Affected if LemMinX files or JARs are found on the system
  2. Identify the installed LemMinX version
    Inspect the JAR manifest, run 'java -jar lemminx.jar --version', or check the version string in the application's metadata or dependency declaration
    Affected if The version is lower than 0.19.0 or cannot be determined
  3. Confirm the application runs with elevated privileges
    Review the user context or service account under which LemMinX or the hosting application executes; check if it runs as root, Administrator, or a privileged service account
    Affected if LemMinX runs under a privileged user context (root, Administrator, or equivalent)
  4. Check if XML validation features are actively used
    Inspect application logs, configuration files, or usage patterns to determine whether XML schema validation via LemMinX is enabled and processing untrusted XML input
    Affected if XML validation is enabled and processes external or untrusted XML documents

A system is affected if it runs any version of Eclipse LemMinX prior to 0.19.0, particularly in a privileged context where local file access could be exploited via the insecure redirect.

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
Upgrade available Upgrade to 0.19.0 or later
Fixed in 0.19.0
Interim mitigation

Upgrade LemMinX to version 0.19.0 or later. Additionally, ensure the application runs with minimal necessary privileges to limit potential impact of local file access.

Recommended fix High confidence

0.19.0

  1. Check current LemMinX version by running: lemminx --version or checking your dependency manifest
  2. For package manager installations: Update via your package manager (e.g., npm install lemminx@latest, brew upgrade lemminx, or apt-get upgrade lemminx)
  3. If using as a dependency in a project: Update the dependency version in your package.json or build configuration to ^0.19.0
  4. Verify the upgrade was successful by running: lemminx --version
  5. Confirm the installed version is 0.19.0 or higher
Caveat No specific breaking changes documented for this security update

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

Fix this in Lemminx Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-0672 — 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-0672 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