Vscode XmlApplication · Redhat
CVE-2022-0671
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 vscode-xml in versions prior to 0.19.0. Schema download could lead to blind SSRF or DoS via a large file.
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 confidenceA flaw in vscode-xml versions prior to 0.19.0 allows the schema download functionality to be abused for blind SSRF attacks, where an attacker can craft malicious XML content to trigger the extension into making requests to attacker-controlled URLs, potentially exposing internal network services. Additionally, the lack of file size limits allows attackers to cause DoS via large file downloads.
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
Vscode XmlApplication
< 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
- High
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed vscode-xml versionOpen VSCode, navigate to the Extensions panel, search for 'XML' by Red Hat, and note the installed version numberAffected if Version is below 0.19.0
-
Identify XML file sourcesReview which XML files you or your team open in VSCode and determine whether they come from trusted internal sources or external/unknown sourcesAffected if You open XML files from untrusted or unknown external sources
-
Check for external schema referencesExamine recent XML files for references to remote schema URLs (such as http:// or https:// URLs in xsi:schemaLocation, DOCTYPE declarations, or external entity references)Affected if Recent XML files contain remote schema URLs or external entity references from potentially attacker-controlled locations
You are likely affected if the vscode-xml extension version is below 0.19.0 AND you work with XML files from untrusted sources that trigger automatic schema downloads.
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 vscode-xml to version 0.19.0 or later which contains bounds checking and URL validation for schema downloads. If upgrading is not immediately possible, avoid opening untrusted XML files from unknown sources.
vscode-xml version 0.19.0 or later
- Open Visual Studio Code
- Navigate to Extensions view (Ctrl+Shift+X or Cmd+Shift+X)
- Search for 'XML' or 'vscode-xml' in the Extensions marketplace
- Locate the 'XML' extension by Red Hat
- Check the extension version - if it's below 0.19.0, click 'Update' to upgrade to version 0.19.0 or later
- Reload VS Code when prompted after the update
- Alternatively, run command 'Extensions: Check for Extension Updates' to update all outdated extensions
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Vscode Xml
Scoped from the published advisory
- Consultation2.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,248.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-0671 — 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-0671 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