Object property tampering via prototype replacement
Published Apr 5, 2023 · Updated Dec 3, 2025
Prototype pollution in Marek Kubica xml2js 0.4.23 allows remote attackers to alter parsed-object properties via crafted XML. The parser creates ordinary JavaScript objects and assigns attacker-controlled element or attribute names, so a proto key replaces an inherited prototype. A consuming application must parse attacker-controlled XML; the resulting inherited-property changes can corrupt application logic, while the library exposes no network service itself.
Summary
What happened
Prototype pollution in Marek Kubica xml2js 0.4.23 allows remote attackers to alter parsed-object properties via crafted XML. The parser creates ordinary JavaScript objects and assigns attacker-controlled element or attribute names, so a proto key replaces an inherited prototype. A consuming application must parse attacker-controlled XML; the resulting inherited-property changes can corrupt application logic, while the library exposes no network service itself.
The record
- CVE
- CVE-2023-0842
- Published
- Apr 5, 2023
- Updated
- Dec 3, 2025
- Vendor
- Marek Kubica
- Product
- xml2js
- Classifications
- CWE-1321
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 5, 2023CVE publishedPublication date reported by the CVE source.
- Dec 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.4.23
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo