CVE-2022-0673
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 · uneditedA flaw was found in LemMinX in versions prior to 0.19.0. Cache poisoning of external schema files due to directory traversal.
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 confidenceLemMinX XML parser prior to version 0.19.0 contains a cache poisoning vulnerability in its external schema file handling. The directory traversal flaw allows attackers to write cached schema files to arbitrary locations on the filesystem, potentially enabling injection of malicious schemas that could lead to XML parsing vulnerabilities or arbitrary code execution.
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< 0.19.0CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify LemMinX versionLocate the LemMinX installation and check its version metadata (check the plugin JAR, binary version, or IDE extension version details)Affected if The installed version is earlier than 0.19.0
-
Confirm external schema fetching is enabledInspect LemMinX configuration settings for XML catalog, schema cache, or remote schema fetching optionsAffected if External schema fetching or remote schema caching is enabled in the settings
-
Locate the schema cache directoryFind the configured cache directory where downloaded schema files are stored (check configuration files or runtime settings for cache path)Affected if A cache directory is configured and writable; the vulnerability allows writing outside this intended directory
-
Verify cache directory access controlsInspect file system permissions on the schema cache directory to determine if low-privilege processes can write outside the intended cache pathAffected if The cache directory has weak permissions allowing directory traversal exploitation
You are affected if LemMinX version is below 0.19.0 AND external schema fetching/caching is enabled, allowing an attacker to exploit the directory traversal to inject malicious schemas via the cache.
Generated from the published advisory. Verify against your own configuration.
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 · scoped0.19.0
Upgrade LemMinX to version 0.19.0 or later. If upgrade is not possible, implement strict path validation and restrict cache directory access to prevent directory traversal attacks.
LemMinX version 0.19.0
- Identify the current version of LemMinX being used in your environment
- Stop any running instances of LemMinX
- Upgrade LemMinX to version 0.19.0 or later
- Verify the upgrade was successful by checking the version number
- Restart the LemMinX service
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-0673 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-0673 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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