BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2023
CVE-2023-0842High confidence

xml2js 0.4.23 - Prototype Pollution

Unknown · xml2js

5.3MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 16 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:High, raised one band.upgradedsince 3 Dec 2025

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 1.40% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs Unknown xml2js and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 16 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

5 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcenode-xml2jsVendor fix publishedDebian records a fixed source-package version for this release.0.4.23+~cs15.4.0+dfsg-7Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcenode-xml2jsVendor fix publishedDebian records a fixed source-package version for this release.0.4.23+~cs15.4.0+dfsg-7Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcenode-xml2jsVendor fix publishedDebian records a fixed source-package version for this release.0.4.23+~cs15.4.0+dfsg-7Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcenode-xml2jsVendor fix publishedDebian records a fixed source-package version for this release.0.4.23+~cs15.4.0+dfsg-7Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivenode-xml2jsUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2023-0842 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitynode-xml2js: xml2js is vulnerable to prototype pollution
16 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • openshift-service-mesh/kiali-rhel8 as a component of OpenShift Service Mesh 2.1
  • openshift-service-mesh/kiali-rhel8 as a component of OpenShift Service Mesh 2
  • xml2js as a component of Red Hat Data Grid 8
  • firefox as a component of Red Hat Enterprise Linux 6
  • firefox.src as a component of Red Hat Enterprise Linux 6
  • firefox as a component of Red Hat Enterprise Linux 7
  • firefox.src as a component of Red Hat Enterprise Linux 7
  • node-xml2js as a component of Red Hat Fuse 7
  • openshift3/ose-console as a component of Red Hat OpenShift Container Platform 3.11
  • ocs4/mcg-core-rhel8 as a component of Red Hat Openshift Container Storage 4
  • noobaa-core-container as a component of Red Hat Openshift Data Foundation 4
  • odf4/mcg-core-rhel8 as a component of Red Hat Openshift Data Foundation 4
Summary
A flaw was found in node-xml2js. This flaw allows an external attacker to edit or add new properties to an object. This is possible because the application does not properly validate incoming JSON keys, making it possible to edit the __proto__ property.
Remediation
Affected
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2023-1222

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Medium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 16 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

xml2js version 0.4.23 allows an external attacker to edit or add new properties to an object. This is possible because the application does not properly validate incoming JSON keys, thus allowing the __proto__ property to be edited.

What

xml2js version 0.4.23 allows an external attacker to edit or add new properties to an object. This is possible because the application does not properly validate incoming JSON keys, thus allowing the __proto__ property to be edited.

Why

The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

xml2js version 0.4.23 allows an external attacker to edit or add new properties to an object. This is possible because the application does not properly validate incoming JSON keys, thus allowing the __proto__ property to be edited.

Why

The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Reference recorded

A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.

Likely attack path
a network path → Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-1321 ↗

CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution'). The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.ILowIntegrity impact: A successful attack can cause a limited loss.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-1321Public exploit reference
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-0180Dell Data Protection Advisor: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Dell Data Protection Advisor ausnutzen, um beliebigen Code auszuführen, einen Denial-of-Service-Zustand zu erzeugen, Sicherheitsmaßnahmen zu umgehen und nicht näher spezifizierte Angriffe zu starten.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20230412Security Bulletin 12 Apr 2023

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 12 Apr 2023, published on 12 April 2023. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1233Multiples vulnérabilités dans les produits IBM

ord?id=CVE-2021-44906 Référence CVE CVE-2022-24771 https://www.cve.org/CVERecord?id=CVE-2022-24771 Référence CVE CVE-2022-25883 https://www.cve.org/CVERecord?id=CVE-2022-25883 Référence CVE CVE-2022-2596 https://www.cve.org/CVERecord?id=CVE-2022-2596 Référence CVE CVE-2022-35948 https://www.cve.org/CVERecord?id=CVE-2022-35948 Référence CVE CVE-2022-35961 https://www.cve.org/CVERecord?id=CVE-2022-35961 Référence CVE CVE-2022-37620 https://www.cve.org/CVERecord?id=CVE-2022-37620 Référence CVE CVE-2022-46175 https://www.cve.org/CVERecord?id=CVE-2022-46175 Référence CVE CVE-2022-46337 https://www.cve.org/CVERecord?id=CVE-2022-46337 Référence CVE CVE-2023-0842 https://www.cve.org/CVERecord?id=CVE-2023-0842 Référence CVE CVE-2023-26158 https://www.cve.org/CVERecord?id=CVE-2023-26158 Référence CVE CVE-2023-44270 https://www.cve.org/CVERecord?id=CVE-2023-44270 Référence CVE CVE-2023-45133 https://www.cve.org/CVERecord?id=CVE-2023-45133 Référence CVE CVE-2024-21538 https://www.cve.org/CVERecord?id=CVE-2024-21538 Référence CVE CVE-2024-22195 https://www.cve.org/CVERecord?id=CVE-2024-22195 Référence CVE CVE-2024-29041 https://www.cve.org/CVERecord?id=CVE-2024-29041 Référence CVE CVE-2024-34064 https://www.cve.org/CVERecord?id=CVE-2024-34064 Référence CVE CVE-2024-37890 https://www.cve.org/CVERecord?id=C

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0923Multiples vulnérabilités dans les produits IBM

ord?id=CVE-2022-24736 Référence CVE CVE-2022-24834 https://www.cve.org/CVERecord?id=CVE-2022-24834 Référence CVE CVE-2022-25883 https://www.cve.org/CVERecord?id=CVE-2022-25883 Référence CVE CVE-2022-29622 https://www.cve.org/CVERecord?id=CVE-2022-29622 Référence CVE CVE-2022-3517 https://www.cve.org/CVERecord?id=CVE-2022-3517 Référence CVE CVE-2022-36943 https://www.cve.org/CVERecord?id=CVE-2022-36943 Référence CVE CVE-2022-38900 https://www.cve.org/CVERecord?id=CVE-2022-38900 Référence CVE CVE-2022-43383 https://www.cve.org/CVERecord?id=CVE-2022-43383 Référence CVE CVE-2022-46175 https://www.cve.org/CVERecord?id=CVE-2022-46175 Référence CVE CVE-2023-0842 https://www.cve.org/CVERecord?id=CVE-2023-0842 Référence CVE CVE-2023-22467 https://www.cve.org/CVERecord?id=CVE-2023-22467 Référence CVE CVE-2023-25166 https://www.cve.org/CVERecord?id=CVE-2023-25166 Référence CVE CVE-2023-26048 https://www.cve.org/CVERecord?id=CVE-2023-26048 Référence CVE CVE-2023-26049 https://www.cve.org/CVERecord?id=CVE-2023-26049 Référence CVE CVE-2023-28856 https://www.cve.org/CVERecord?id=CVE-2023-28856 Référence CVE CVE-2023-29262 https://www.cve.org/CVERecord?id=CVE-2023-29262 Référence CVE CVE-2023-36479 https://www.cve.org/CVERecord?id=CVE-2023-36479 Référence CVE CVE-2023-38009 https://www.cve.org/CVERecord?id=C

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0630Multiples vulnérabilités dans IBM QRadar

ecord?id=CVE-2021-42740 Référence CVE CVE-2021-43138 https://www.cve.org/CVERecord?id=CVE-2021-43138 Référence CVE CVE-2022-25881 https://www.cve.org/CVERecord?id=CVE-2022-25881 Référence CVE CVE-2022-25883 https://www.cve.org/CVERecord?id=CVE-2022-25883 Référence CVE CVE-2022-3517 https://www.cve.org/CVERecord?id=CVE-2022-3517 Référence CVE CVE-2022-37601 https://www.cve.org/CVERecord?id=CVE-2022-37601 Référence CVE CVE-2022-37603 https://www.cve.org/CVERecord?id=CVE-2022-37603 Référence CVE CVE-2022-43441 https://www.cve.org/CVERecord?id=CVE-2022-43441 Référence CVE CVE-2023-0361 https://www.cve.org/CVERecord?id=CVE-2023-0361 Référence CVE CVE-2023-0842 https://www.cve.org/CVERecord?id=CVE-2023-0842 Référence CVE CVE-2023-32233 https://www.cve.org/CVERecord?id=CVE-2023-32233 Référence CVE CVE-2023-3341 https://www.cve.org/CVERecord?id=CVE-2023-3341 Référence CVE CVE-2023-3446 https://www.cve.org/CVERecord?id=CVE-2023-3446 Référence CVE CVE-2023-35001 https://www.cve.org/CVERecord?id=CVE-2023-35001 Référence CVE CVE-2023-3609 https://www.cve.org/CVERecord?id=CVE-2023-3609 Référence CVE CVE-2023-36632 https://www.cve.org/CVERecord?id=CVE-2023-36632 Référence CVE CVE-2023-3817 https://www.cve.org/CVERecord?id=CVE-2023-3817 Référence CVE CVE-2023-38546 https://www.cve.org/CVERecord?id=CVE-2023-

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2023-006775node-xml2js project のnode-xml2js におけるオブジェクトプロトタイプ属性の不適切に制御された変更に関する脆弱性

node-xml2js project のnode-xml2js には、オブジェクトプロトタイプ属性の不適切に制御された変更に関する脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 5 Apr 2023 · Last source change 3 Dec 2025, 20:14 UTC · CWE-1321 · Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2023-1222
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCISA ADP
NVD statusNVD modified after enrichment

Missing structured fields: affected product. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    openshift-service-mesh/kiali-rhel8 as a component of OpenShift Service Mesh 2.1; openshift-service-mesh/kiali-rhel8 as a component of OpenShift Service Mesh 2; xml2js as a component of Red Hat Data Grid 8; firefox as a component of Red Hat Enterprise Linux 6; firefox.src as a component of Red Hat Enterprise Linux 6; firefox as a component of Red Hat Enterprise Linux 7; firefox.src as a component of Red Hat Enterprise Linux 7; node-xml2js as a component of Red Hat Fuse 7; openshift3/ose-console as a component of Red Hat OpenShift Container Platform 3.11; ocs4/mcg-core-rhel8 as a component of Red Hat Openshift Container Storage 4; noobaa-core-container as a component of Red Hat Openshift Data Foundation 4; odf4/mcg-core-rhel9 as a component of Red Hat Openshift Data Foundation 4; rhods/odh-dashboard-rhel8 as a component of Red Hat OpenShift Data Science (RHODS); devspaces-theia-rhel8-container as a component of Red Hat OpenShift Dev Spaces; devspaces/code-rhel8 as a component of Red Hat OpenShift Dev Spaces; quay/quay-rhel8 as a component of Red Hat Quay 3
    After
    openshift-service-mesh/kiali-rhel8 as a component of OpenShift Service Mesh 2.1; openshift-service-mesh/kiali-rhel8 as a component of OpenShift Service Mesh 2; xml2js as a component of Red Hat Data Grid 8; firefox as a component of Red Hat Enterprise Linux 6; firefox.src as a component of Red Hat Enterprise Linux 6; firefox as a component of Red Hat Enterprise Linux 7; firefox.src as a component of Red Hat Enterprise Linux 7; node-xml2js as a component of Red Hat Fuse 7; openshift3/ose-console as a component of Red Hat OpenShift Container Platform 3.11; ocs4/mcg-core-rhel8 as a component of Red Hat Openshift Container Storage 4; noobaa-core-container as a component of Red Hat Openshift Data Foundation 4; odf4/mcg-core-rhel8 as a component of Red Hat Openshift Data Foundation 4; rhods/odh-dashboard-rhel8 as a component of Red Hat OpenShift Data Science (RHODS); devspaces-theia-rhel8-container as a component of Red Hat OpenShift Dev Spaces; devspaces/code-rhel8 as a component of Red Hat OpenShift Dev Spaces; quay/quay-rhel8 as a component of Red Hat Quay 3
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2023-0842 · cve.blacktree.nl