OESA-2024-2400 (CVE-2024-47072)
Vulnerability from osv_openeuler – Published: 2024-11-15 11:07 – Updated: 2026-08-06 11:07 – Source websiteXStream is a simple library to serialize objects to XML and back again. A high level facade is supplied that simplifies common use cases. Custom objects can be serialized without need for specifying mappings. Speed and low memory footprint are a crucial part of the design, making it suitable for large object graphs or systems with high message throughput. No information is duplicated that can be obtained via reflection. This results in XML that is easier to read for humans and more compact than native Java serialization. XStream serializes internal fields, including private and final. Supports non-public and inner classes. Classes are not required to have default constructor. Duplicate references encountered in the object-model will be maintained. Supports circular references. By implementing an interface, XStream can serialize directly to/from any tree structure (not just XML). Strategies can be registered allowing customization of how particular types are represented as XML. When an exception occurs due to malformed XML, detailed diagnostics are provided to help isolate and fix the problem.
Security Fix(es):
XStream provides a BinaryStreamDriver with an own optimized serialization format. The format uses ids for string values as deduplication. The mapping for these ids are created on-the-fly at marshalling time. At unmarshalling time the reader_x27;s implementation simply used a simple one-time recursion after reading a mapping token to process the next normal token of the data stream. However, an endless recursion could be triggered with manipulated input data resulting in a stack overflow causing a denial of service.(CVE-2024-47072)
| URL | Type | |
|---|---|---|
{
"affected": [
{
"ecosystem_specific": {
"noarch": [
"xstream-1.4.20-2.oe2403.noarch.rpm",
"xstream-benchmark-1.4.20-2.oe2403.noarch.rpm",
"xstream-hibernate-1.4.20-2.oe2403.noarch.rpm",
"xstream-javadoc-1.4.20-2.oe2403.noarch.rpm",
"xstream-parent-1.4.20-2.oe2403.noarch.rpm"
],
"src": [
"xstream-1.4.20-2.oe2403.src.rpm"
]
},
"package": {
"ecosystem": "openEuler:24.03-LTS",
"name": "xstream",
"purl": "pkg:rpm/openEuler/xstream\u0026distro=openEuler-24.03-LTS"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.4.20-2.oe2403"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"ecosystem_specific": {
"noarch": [
"xstream-1.4.20-2.oe2203sp4.noarch.rpm",
"xstream-benchmark-1.4.20-2.oe2203sp4.noarch.rpm",
"xstream-hibernate-1.4.20-2.oe2203sp4.noarch.rpm",
"xstream-javadoc-1.4.20-2.oe2203sp4.noarch.rpm",
"xstream-parent-1.4.20-2.oe2203sp4.noarch.rpm"
],
"src": [
"xstream-1.4.20-2.oe2203sp4.src.rpm"
]
},
"package": {
"ecosystem": "openEuler:22.03-LTS-SP4",
"name": "xstream",
"purl": "pkg:rpm/openEuler/xstream\u0026distro=openEuler-22.03-LTS-SP4"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.4.20-2.oe2203sp4"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"ecosystem_specific": {
"noarch": [
"xstream-1.4.20-2.oe2203sp3.noarch.rpm",
"xstream-benchmark-1.4.20-2.oe2203sp3.noarch.rpm",
"xstream-hibernate-1.4.20-2.oe2203sp3.noarch.rpm",
"xstream-javadoc-1.4.20-2.oe2203sp3.noarch.rpm",
"xstream-parent-1.4.20-2.oe2203sp3.noarch.rpm"
],
"src": [
"xstream-1.4.20-2.oe2203sp3.src.rpm"
]
},
"package": {
"ecosystem": "openEuler:22.03-LTS-SP3",
"name": "xstream",
"purl": "pkg:rpm/openEuler/xstream\u0026distro=openEuler-22.03-LTS-SP3"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.4.20-2.oe2203sp3"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"ecosystem_specific": {
"noarch": [
"xstream-1.4.20-2.oe2003sp4.noarch.rpm",
"xstream-benchmark-1.4.20-2.oe2003sp4.noarch.rpm",
"xstream-hibernate-1.4.20-2.oe2003sp4.noarch.rpm",
"xstream-javadoc-1.4.20-2.oe2003sp4.noarch.rpm",
"xstream-parent-1.4.20-2.oe2003sp4.noarch.rpm"
],
"src": [
"xstream-1.4.20-2.oe2003sp4.src.rpm"
]
},
"package": {
"ecosystem": "openEuler:20.03-LTS-SP4",
"name": "xstream",
"purl": "pkg:rpm/openEuler/xstream\u0026distro=openEuler-20.03-LTS-SP4"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.4.20-2.oe2003sp4"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"ecosystem_specific": {
"noarch": [
"xstream-1.4.20-2.oe2203sp1.noarch.rpm",
"xstream-benchmark-1.4.20-2.oe2203sp1.noarch.rpm",
"xstream-hibernate-1.4.20-2.oe2203sp1.noarch.rpm",
"xstream-javadoc-1.4.20-2.oe2203sp1.noarch.rpm",
"xstream-parent-1.4.20-2.oe2203sp1.noarch.rpm"
],
"src": [
"xstream-1.4.20-2.oe2203sp1.src.rpm"
]
},
"package": {
"ecosystem": "openEuler:22.03-LTS-SP1",
"name": "xstream",
"purl": "pkg:rpm/openEuler/xstream\u0026distro=openEuler-22.03-LTS-SP1"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.4.20-2.oe2203sp1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "High"
},
"details": "XStream is a simple library to serialize objects to XML and back again. A high level facade is supplied that simplifies common use cases. Custom objects can be serialized without need for specifying mappings. Speed and low memory footprint are a crucial part of the design, making it suitable for large object graphs or systems with high message throughput. No information is duplicated that can be obtained via reflection. This results in XML that is easier to read for humans and more compact than native Java serialization. XStream serializes internal fields, including private and final. Supports non-public and inner classes. Classes are not required to have default constructor. Duplicate references encountered in the object-model will be maintained. Supports circular references. By implementing an interface, XStream can serialize directly to/from any tree structure (not just XML). Strategies can be registered allowing customization of how particular types are represented as XML. When an exception occurs due to malformed XML, detailed diagnostics are provided to help isolate and fix the problem.\r\n\r\nSecurity Fix(es):\r\n\r\nXStream provides a BinaryStreamDriver with an own optimized serialization format. The format uses ids for string values as deduplication. The mapping for these ids are created on-the-fly at marshalling time. At unmarshalling time the reader_x27;s implementation simply used a simple one-time recursion after reading a mapping token to process the next normal token of the data stream. However, an endless recursion could be triggered with manipulated input data resulting in a stack overflow causing a denial of service.(CVE-2024-47072)",
"id": "OESA-2024-2400",
"modified": "2026-08-06T11:07:52Z",
"published": "2024-11-15T11:07:52Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2400"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47072"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
],
"summary": "xstream security update",
"upstream": [
"CVE-2024-47072"
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.