Security readout for executives and security teams
XML::Parser for Perl through version 2.45 can mishandle UTF-8 stream input and corrupt memory. In practical terms, software that parses untrusted XML with this library may crash and, per the CVSS rating, could face broader compromise risk. No provided source shows active exploitation. Exposure is most likely in Perl applications or services using XML::Parser version 2.45 or earlier to process XML streams, especially untrusted input with UTF-8 PerlIO handling. Systems using OS-packaged Perl modules should verify their distribution’s package version and backport status. Treat as urgent for internet-facing or partner-facing systems that parse XML using Perl XML::Parser. Patch validation should be prioritized, but response messaging should avoid claims of active exploitation unless new evidence appears. Mitigation focus: Upgrade XML::Parser to version 2.46 or a vendor package containing the referenced patch.; Check operating system or Perl distribution advisories for backported fixes.; Reduce exposure of XML parsing endpoints that accept untrusted input until patched..
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-122: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-176: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2006-10002 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://rt.cpan.org/Ticket/Display.html?id=19859CVE reference · issue-tracking
- https://github.com/cpan-authors/XML-Parser/issues/64CVE reference · issue-tracking
- https://metacpan.org/release/TODDR/XML-Parser-2.46/changesCVE reference · release-notes
- https://github.com/cpan-authors/XML-Parser/commit/56b0509dfc6b559cd7555ea81ee62e3622069255.patchCVE reference · patch
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Heap-based Buffer Overflow
Heap-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Handling of Unicode Encoding
Improper Handling of Unicode Encoding represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
