CVE-2022-41966: XStream Denial of Service via stack overflow
Noroxi assessment
Priority: Monitor (action score 33/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 9.3% (FIRST EPSS); higher than 95.4% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: x-stream xstream 1.4.20.
Low priority for now. Upgrade to x-stream xstream 1.4.20 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
XStream serializes Java objects to XML and back again. Versions prior to 1.4.20 may allow a remote attacker to terminate the application with a stack overflow error, resulting in a denial of service only via manipulation the processed input stream. The attack uses the hash code implementation for collections and maps to force recursive hash calculation causing a stack overflow. This issue is patched in version 1.4.20 which handles the stack overflow and raises an InputManipulationException instead. A potential workaround for users who only use HashMap or HashSet and whose XML refers these only as default map or set, is to change the default implementation of java.util.Map and java.util per the code example in the referenced advisory. However, this implies that your application does not care about the implementation of the map and all elements are comparable.
- Published
- Dec 27, 2022
- Updated
- Jun 17, 2026
- EPSS
- 9.3% · 95th percentile
- CWE
- CWE-120
Report tools
Action score
33
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 3 / 30 · 9.3%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.5
- CNA · GitHub_M
- 8.2
- 0.7 point gap
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| xstream | xstream | cpe:2.3:a:xstream:xstream |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- xstream xstreambefore 1.4.20
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
x-stream xstream
- < 1.4.20affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:10 | libxstream-java | before 1.4.11.1-1+deb10u4 | 1.4.11.1-1+deb10u4 |
| Debian:11 | libxstream-java | before 1.4.15-3+deb11u2 | 1.4.15-3+deb11u2 |
| Debian:12 | libxstream-java | before 1.4.20-1 | 1.4.20-1 |
| Maven | com.thoughtworks.xstream:xstream | before 1.4.20 | 1.4.20 |
| openSUSE:Leap 15.4 | xstream | before 1.4.20-150200.3.25.1 | 1.4.20-150200.3.25.1 |
| openSUSE:Tumbleweed | xstream | before 1.4.20-1.1 | 1.4.20-1.1 |
| Red Hat:ocp_tools:4.11::el8 | jenkins | before 0:2.401.1.1686831596-3.el8 | 0:2.401.1.1686831596-3.el8 |
| Red Hat:ocp_tools:4.11::el8 | jenkins-2-plugins | before 0:4.11.1686831822-1.el8 | 0:4.11.1686831822-1.el8 |
| Red Hat:openshift:4.10::el8 | jenkins | before 0:2.401.1.1685677065-1.el8 | 0:2.401.1.1685677065-1.el8 |
| Red Hat:openshift:4.10::el8 | jenkins-2-plugins | before 0:4.10.1685679861-1.el8 | 0:4.10.1685679861-1.el8 |
| SUSE:Linux Enterprise Module for Development Tools 15 SP4 | xstream | before 1.4.20-150200.3.25.1 | 1.4.20-150200.3.25.1 |
Same product
xstream: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-39144XStream is vulnerable to a Remote Command Execution attackKEV93Now
- CVE-2019-10173It was found that xstream API version 1.4.10 before 1.4.11 introduced a regression for a previous deserialization flaw.68This week
- CVE-2013-7285Xstream API versions up to 1.4.6 and version 1.4.10, if the security framework has not been initialized, may allow a remote attacker to run 64This week
Published before and after this one in the same product
- ← EarlierCVE-2021-43859Feb 1, 2022 · Denial of Service by injecting highly recursive collections or maps in XStream32Monitor
- ← EarlierCVE-2022-40151Sep 16, 2022 · Stack Buffer Overflow in xstream31Monitor
- ← EarlierCVE-2022-40152Sep 16, 2022 · Stack Buffer Overflow in Woodstox35Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| x-stream xstream | 1.4.20 · description | Vendor (CNA) |
| debian:libxstream-java | 1.4.20-1 · Debian:12 | Package registry (OSV) |
| Maven:com.thoughtworks.xstream:xstream | 1.4.20 | Package registry (OSV) |
| opensuse:xstream | 1.4.20-150200.3.25.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| red hat:jenkins | 0:2.401.1.1685677065-1.el8 · Red Hat:openshift:4.10::el8 | Package registry (OSV) |
| red hat:jenkins-2-plugins | 0:4.10.1685679861-1.el8 · Red Hat:openshift:4.10::el8 | Package registry (OSV) |
| suse:xstream | 1.4.20-150200.3.25.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP4 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:3 | 2023-01-06 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+9 d
- TodayNov 8, 2026+1412 d
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-120 · Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Root cause
When data is copied, the source length is not compared with the size of the destination buffer. Excess data overwrites adjacent memory.
The bug in code
The whole CWE-120 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
char buf[256];
memcpy(buf, pkt->data, pkt->len);Fixed
char buf[256];
if (pkt->len > sizeof(buf)) {
return -EINVAL;
}
memcpy(buf, pkt->data, pkt->len);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
- Overflow Variables and TagsCAPEC-46likelihood: High · High
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.