A vulnerability chain in LSP4XML, the XML parsing library used by VSCode-XML, Eclipse wildwebdeveloper, Theia XML tooling, and related products, allowed attackers to achieve code execution by luring users into opening a malicious XML file. The first flaw, CVE-2019-18213, was an XXE issue that could be triggered during XML parsing and enabled effects including blind SSRF and NetNTLMv2 credential leakage on Windows systems.
Researchers found a second flaw, CVE-2019-18212, in LSP4XML’s caching logic that allowed path traversal and arbitrary file write in user-accessible directories. By chaining the XXE bug with the file-write weakness, an attacker could place startup or autostart files and gain execution after the victim logged out and back in. The issues were fixed in LSP4XML 0.9.1, and the case highlights how XML parser weaknesses can be combined with server-side request forgery behavior and local file-write primitives to escalate into full compromise.

See affected versions and whether adversaries are exploiting it.
2 events from the most recent confirmed update back to the earliest known activity.
On 2019-10-17, LSP4XML version 0.9.1 was released to address the XXE and path traversal vulnerabilities. The fixes remediated the issues that enabled blind SSRF, NetNTLMv2 exfiltration on Windows, arbitrary file write, and a path to code execution.
In September 2019, researchers identified an XXE issue in LSP4XML tracked as CVE-2019-18213 and a path traversal flaw tracked as CVE-2019-18212. The bugs affected XML tooling used by products including VSCode-XML, Eclipse wildwebdeveloper, and Theia XML tooling, and could be chained toward code execution.
Vulnerabilities, threat actors, malware, products, organizations, breaches, and observables Mallory has linked to this story. Indicator values are masked here and available in full in the app.
Indicator values are masked on this page. See the values in Mallory Domains, IPs, hashes, and URLs are exportable to your SIEM.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
2 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.