Skip to content
Fencer Intel
critical 9.1

CVE-2022-0671 json

Server-Side Request Forgery and Uncontrolled Resource Consumption in LemMinX

published 4y ago modified 4mo ago also GHSA-52vv-3vf7-f7wh , EUVD-2022-0826

cvss
9.1
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.3%
EPSS 1.3% chance of exploitation in 30 days, percentile 69%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.eclipse.lemminx:lemminx-parent 0.19.0
  • redhat vscode-xml 0.19.0

Is CVE-2022-0671 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.26% chance of exploitation in the next 30 days, higher than 69% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
NVD 2.0 6.4 AV:N/AC:L/Au:N/C:P/I:N/A:P
GitHub 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

Affected packages

ecosystem package affected fixed in
maven org.eclipse.lemminx:lemminx-parent
<0.19.0
0.19.0

Affected products

  • n/a vscode-xml

Classification

Weakness
  • CWE-918 Server-Side Request Forgery
  • CWE-400 Uncontrolled Resource Consumption

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.