CVE-2024-29133: Apache Commons Configuration: StackOverflowError calling ListDelimiterHandler.flatten(Object, int) with a cyclical object tree
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.7% (FIRST EPSS); higher than 77.6% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Apache Software Foundation Apache Commons Configuration 2.10.1.
Low priority for now. Upgrade to Apache Software Foundation Apache Commons Configuration 2.10.1 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
Out-of-bounds Write vulnerability in Apache Commons Configuration.This issue affects Apache Commons Configuration: from 2.0 before 2.10.1. Users are recommended to upgrade to version 2.10.1, which fixes the issue.
- Published
- Mar 21, 2024
- Updated
- Jun 17, 2026
- EPSS
- 1.7% · 77th percentile
- CWE
- CWE-787
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 21 / 40 · 5.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 1.7%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- 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 |
|---|---|---|
| apache | commons configuration | cpe:2.3:a:apache:commons_configuration |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- apache commons configuration2.0 and later · before 2.10.1
- fedoraproject fedora39
- fedoraproject fedora40
Versions reported by the vendor
Affected version ranges reported by the assigning authority (apache). Independent of NVD's CPE analysis and usually ahead of it.
Apache Software Foundation Apache Commons Configuration
- 2.0 and later · before 2.10.1affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | commons-configuration2 | from 0 | — |
| Debian:13 | commons-configuration2 | before 2.10.1-1 | 2.10.1-1 |
| Maven | org.apache.commons:commons-configuration2 | from 2.0 · before 2.10.1 | 2.10.1 |
| openSUSE:Leap 15.5 | apache-commons-configuration | before 1.10-150200.3.11.1 | 1.10-150200.3.11.1 |
| openSUSE:Leap 15.5 | apache-commons-configuration2 | before 2.10.1-150200.5.8.1 | 2.10.1-150200.5.8.1 |
| openSUSE:Tumbleweed | apache-commons-configuration2 | before 2.10.1-1.1 | 2.10.1-1.1 |
| SUSE:Linux Enterprise Module for Development Tools 15 SP5 | apache-commons-configuration | before 1.10-150200.3.11.1 | 1.10-150200.3.11.1 |
| SUSE:Linux Enterprise Module for Development Tools 15 SP5 | apache-commons-configuration2 | before 2.10.1-150200.5.8.1 | 2.10.1-150200.5.8.1 |
Same product
apache: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-33980Apache Commons Configuration insecure interpolation defaults52Plan
- CVE-2020-1953Apache Commons Configuration uses a third-party library to parse YAML files which by default allows the instantiation of classes if the YAML42Plan
- CVE-2024-29131Apache Commons Configuration: StackOverflowError adding property in AbstractListDelimiterHandler.flattenIterator()30Monitor
Published before and after this one in the same product
- Later →CVE-2025-46392May 9, 2025 · Apache Commons Configuration: Uncontrolled Resource Consumption when loading untrusted configurations in 1.x27Monitor
- Later →CVE-2026-45205May 14, 2026 · Apache Commons Configuration: StackOverflowError for YAML input with cycles21Monitor
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 |
|---|---|---|
| Apache Software Foundation Apache Commons Configuration | 2.10.1 | Vendor (CNA) |
| debian:commons-configuration2 | 2.10.1-1 · Debian:13 | Package registry (OSV) |
| Maven:org.apache.commons:commons-configuration2 | 2.10.1 | Package registry (OSV) |
| opensuse:apache-commons-configuration | 1.10-150200.3.11.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:apache-commons-configuration2 | 2.10.1-150200.5.8.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| suse:apache-commons-configuration | 1.10-150200.3.11.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP5 | Package registry (OSV) |
| suse:apache-commons-configuration2 | 2.10.1-150200.5.8.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP5 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
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.
No dated events beyond publication.
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.
- Gary Gregoryfinder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2024-291310 days apartApache Commons Configuration: StackOverflowError adding property in AbstractListDelimiterHandler.flattenIterator()30Monitor
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.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-787 · Out-of-bounds WriteCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.