Security readout for executives and security teams
XStream 1.4.10 reintroduced an older unsafe deserialization flaw. If an application unmarshals attacker-controlled XML, JSON, or another supported format before XStream’s security framework is initialized, a remote attacker may execute shell commands. This is high risk for internet-facing services that parse untrusted data with this library version. Exposure is most likely in Java applications or vendor products bundling XStream 1.4.10 that unmarshal externally supplied XML, JSON, or other supported formats. Red Hat and Oracle advisories indicate downstream product impact, but the bundle does not enumerate every affected product here. Treat as a high-priority dependency remediation where XStream is present in exposed services. The main business concern is remote command execution through data parsing. Absence from KEV lowers evidence of known exploitation, but the low-complexity network attack conditions justify prompt inventory and patching. Mitigation focus: Upgrade XStream from 1.4.10 to the fixed 1.4.11 release.; Apply relevant Red Hat or Oracle security updates where XStream is bundled.; Prioritize systems parsing untrusted XML, JSON, or supported serialized formats..
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-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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-2019-10173 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
- High
- CVSS
- 7.3 (3.0)
- Known Exploited
- No
- Published
Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L3.93.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.0 score
7.3HighVector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Source materials
- CVE List V5 sourceCVE List V5
- RHSA-2019:3892CVE reference · vendor-advisory, x_refsource_REDHAT
- RHSA-2019:4352CVE reference · vendor-advisory, x_refsource_REDHAT
- RHSA-2020:0445CVE reference · vendor-advisory, x_refsource_REDHAT
- RHSA-2020:0727CVE reference · vendor-advisory, x_refsource_REDHAT
- https://www.oracle.com/security-alerts/cpuapr2020.htmlCVE reference · x_refsource_MISC
- https://www.oracle.com/security-alerts/cpuoct2020.htmlCVE reference · x_refsource_MISC
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10173CVE reference · x_refsource_CONFIRM
- https://www.oracle.com/security-alerts/cpujan2021.htmlCVE reference · x_refsource_MISC
- https://www.oracle.com/security-alerts/cpuApr2021.htmlCVE reference · x_refsource_MISC
- https://www.oracle.com//security-alerts/cpujul2021.htmlCVE reference · x_refsource_MISC
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.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.