🛡️ CVE-2022-0671 — vscode-xml
Description
Server-Side Request Forgery and Uncontrolled Resource Consumption in LemMinX
A 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.
How this vulnerability can be exploited
This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality high, integrity none, availability high.
Weakness class
CVE-2022-0671 is classified as CWE-400: Uncontrolled Resource Consumption. A request can consume memory, CPU or storage without limit, exhausting capacity for everyone else.
Affected software
CVE-2022-0671 is recorded against 2 packages.
- org.eclipse.lemminx:lemminx-parent (fixed in 0.19.0)
- vscode-xml (fixed in 0.19.0)
Timeline and source
Published on 19 February 2022 and last revised on 8 November 2023. No public exploit is currently recorded for this entry. Record sourced from NVD.
References
nvd.nist.gov (Advisory)
github.com (Web)
github.com (Package)
github.com (Web)
github.com (Web)
Details
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| org.eclipse.lemminx:lemminx-parent | — | 0.19.0 |
| vscode-xml | — | 0.19.0 |
References
Similar Threats
- Medium CVE-2022-0672
- Medium CVE-2022-0673
More CVE 2022 advisories
Browse all of CVE 2022 in the advisory index.
Exploit Protection
Are you running vscode-xml?
CVE-2022-0671 carries CVSS 9.5 Critical rating. BotEraser checks your installation against this and other known CVE records, and blocks IPs associated with exploit activity.
Check My Site For CVE-2022-0671 →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.