CVE-2024-25112: Denial of service due to unbounded recursion in QuickTimeVideo::multipleEntriesDecoder in Exiv2
Noroxi assessment
Priority: Monitor (action score 20/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: 0.22% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: exiv2 (Alpine:v3.19) 0.28.2-r0; exiv2 (Debian:13) 0.28.3+dfsg-2; exiv2 (openSUSE:Leap 16.0) 0.28.8-160000.1.1.
Low priority for now. Upgrade to exiv2 (Alpine:v3.19) 0.28.2-r0; exiv2 (Debian:13) 0.28.3+dfsg-2; exiv2 (openSUSE:Leap 16.0) 0.28.8-160000.1.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
Exiv2 is a command-line utility and C++ library for reading, writing, deleting, and modifying the metadata of image files. A denial-of-service was found in Exiv2 version v0.28.1: an unbounded recursion can cause Exiv2 to crash by exhausting the stack. The vulnerable function, `QuickTimeVideo::multipleEntriesDecoder`, was new in v0.28.0, so Exiv2 versions before v0.28 are _not_ affected. The denial-of-service is triggered when Exiv2 is used to read the metadata of a crafted video file. This bug is fixed in version v0.28.2. Users are advised to upgrade. There are no known workarounds for this vulnerability.
- Published
- Feb 12, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- CWE-400
Report tools
Action score
20
Monitor
Low priority for now.
- CVSS
- 20 / 40 · 5.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 5.0
- CNA · GitHub_M
- 5.5
- 0.5 point gap
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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
- 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 |
|---|---|---|
| exiv2 | exiv2 | cpe:2.3:a:exiv2:exiv2 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- exiv2 exiv20.28.0
- exiv2 exiv20.28.1
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.
Exiv2 exiv2
- >= 0.28.0 < 0.28.2affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.19 | exiv2 | before 0.28.2-r0 | 0.28.2-r0 |
| Debian:12 | exiv2 | from 0 | — |
| Debian:13 | exiv2 | before 0.28.3+dfsg-2 | 0.28.3+dfsg-2 |
| openSUSE:Leap 16.0 | exiv2 | before 0.28.8-160000.1.1 | 0.28.8-160000.1.1 |
| openSUSE:Tumbleweed | exiv2 | before 0.28.2-1.1 | 0.28.2-1.1 |
| PyPI | exiv2 | from 0.16.0 · before 0.16.1 | 0.16.1 |
| SUSE:Linux Enterprise Server 16.0 | exiv2 | before 0.28.8-160000.1.1 | 0.28.8-160000.1.1 |
Same product
exiv2: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-11531Exiv2 0.26 has a heap-based buffer overflow in getData in preview.cpp.40Plan
- CVE-2019-9144An issue was discovered in Exiv2 0.27.36Monitor
- CVE-2019-9143An issue was discovered in Exiv2 0.27.36Monitor
Published before and after this one in the same product
- ← EarlierCVE-2023-44398Nov 6, 2023 · Out-of-bounds write in exiv235Monitor
- ← EarlierCVE-2024-24826Feb 12, 2024 · Out-of-bounds read in QuickTimeVideo::NikonTagsDecoder in Exiv220Monitor
- Later →CVE-2024-39695Jul 8, 2024 · Exiv2 has an out-of-bounds read in AsfVideo::streamProperties26Monitor
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 |
|---|---|---|
| alpine:exiv2 | 0.28.2-r0 · Alpine:v3.19 | Package registry (OSV) |
| debian:exiv2 | 0.28.3+dfsg-2 · Debian:13 | Package registry (OSV) |
| opensuse:exiv2 | 0.28.2-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| PyPI:exiv2 | 0.16.1 | Package registry (OSV) |
| suse:exiv2 | 0.28.8-160000.1.1 · SUSE:Linux Enterprise Server 16.0 | 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.
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
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-400 · Uncontrolled Resource ConsumptionCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:H
nvd-primary
Root cause
Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.
The bug in code
The whole CWE-400 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
function expand(node) {
return node.children.map(expand);
}Fixed
const MAX_DEPTH = 32;
function expand(node, depth = 0) {
if (depth > MAX_DEPTH) throw new Error("too deep");
return node.children.map((c) => expand(c, depth + 1));
}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
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.