Exiv2 0.27.2 allows attackers to trigger a crash in Exiv2::getULong in types.cpp when called from Exiv2::Internal::CiffDirectory::readDirect
Noroxi assessment
Priority: Monitor (action score 27/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.8% (FIRST EPSS); higher than 78.9% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: exiv2-devel (AlmaLinux:8) 0.27.3-2.el8; exiv2-doc (AlmaLinux:8) 0.27.3-2.el8; exiv2 (Alpine:v3.10) 0.26-r1.
Low priority for now. Upgrade to exiv2-devel (AlmaLinux:8) 0.27.3-2.el8; exiv2-doc (AlmaLinux:8) 0.27.3-2.el8; exiv2 (Alpine:v3.10) 0.26-r1 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 0.27.2 allows attackers to trigger a crash in Exiv2::getULong in types.cpp when called from Exiv2::Internal::CiffDirectory::readDirectory in crwimage_int.cpp, because there is no validation of the relationship of the total size to the offset and size.
- Published
- Oct 9, 2019
- Updated
- Jun 16, 2026
- EPSS
- 1.8% · 78th percentile
- CWE
- CWE-120
Report tools
Action score
27
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 1.8%
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 |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
| canonical | ubuntu linux | cpe:2.3:o:canonical:ubuntu_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- canonical ubuntu linux16.04
- canonical ubuntu linux18.04
- canonical ubuntu linux19.04
- canonical ubuntu linux19.10
- debian debian linux10.0
- debian debian linux8.0
- exiv2 exiv20.27.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | exiv2-devel | before 0.27.3-2.el8 | 0.27.3-2.el8 |
| AlmaLinux:8 | exiv2-doc | before 0.27.3-2.el8 | 0.27.3-2.el8 |
| Alpine:v3.10 | exiv2 | before 0.26-r1 | 0.26-r1 |
| Alpine:v3.11 | exiv2 | before 0.27.2-r2 | 0.27.2-r2 |
| Debian:10 | exiv2 | before 0.25-4+deb10u4 | 0.25-4+deb10u4 |
| Debian:12 | exiv2 | before 0.27.3-1 | 0.27.3-1 |
| Debian:8 | exiv2 | before 0.24-4.1+deb8u5 | 0.24-4.1+deb8u5 |
| openSUSE:Leap 15.3 | exiv2 | before 0.26-150000.6.26.1 | 0.26-150000.6.26.1 |
| openSUSE:Leap 15.4 | exiv2-0_26 | before 0.26-150400.9.21.1 | 0.26-150400.9.21.1 |
| Red Hat:enterprise_linux:7::client | exiv2 | before 0:0.27.0-3.el7_8 | 0:0.27.0-3.el7_8 |
| Red Hat:enterprise_linux:7::client | exiv2-debuginfo | before 0:0.27.0-3.el7_8 | 0:0.27.0-3.el7_8 |
| Red Hat:enterprise_linux:7::client | exiv2-devel | before 0:0.27.0-3.el7_8 | 0:0.27.0-3.el7_8 |
| Red Hat:enterprise_linux:7::client | exiv2-doc | before 0:0.27.0-3.el7_8 | 0:0.27.0-3.el7_8 |
| Red Hat:enterprise_linux:7::client | exiv2-libs | before 0:0.27.0-3.el7_8 | 0:0.27.0-3.el7_8 |
| Red Hat:enterprise_linux:8::appstream | exiv2 | before 0:0.27.3-2.el8 | 0:0.27.3-2.el8 |
| Red Hat:enterprise_linux:8::appstream | exiv2-debuginfo | before 0:0.27.3-2.el8 | 0:0.27.3-2.el8 |
| Red Hat:enterprise_linux:8::appstream | exiv2-debugsource | before 0:0.27.3-2.el8 | 0:0.27.3-2.el8 |
| Red Hat:enterprise_linux:8::appstream | exiv2-libs | before 0:0.27.3-2.el8 | 0:0.27.3-2.el8 |
| Red Hat:enterprise_linux:8::appstream | exiv2-libs-debuginfo | before 0:0.27.3-2.el8 | 0:0.27.3-2.el8 |
| Red Hat:enterprise_linux:8::crb | exiv2-devel | before 0:0.27.3-2.el8 | 0:0.27.3-2.el8 |
| Red Hat:enterprise_linux:8::crb | exiv2-doc | before 0:0.27.3-2.el8 | 0:0.27.3-2.el8 |
| Rocky Linux:8 | exiv2 | before 0:0.27.3-2.el8 | 0:0.27.3-2.el8 |
| SUSE:Linux Enterprise Module for Desktop Applications 15 SP3 | exiv2 | before 0.26-150000.6.26.1 | 0.26-150000.6.26.1 |
| SUSE:Linux Enterprise Module for Desktop Applications 15 SP4 | exiv2-0_26 | before 0.26-150400.9.21.1 | 0.26-150400.9.21.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-2019-14370Jul 28, 2019 · In Exiv2 0.27.99.0, there is an out-of-bounds read in Exiv2::MrwImage::readMetadata() in mrwimage.cpp.26Monitor
- ← EarlierCVE-2019-14982Aug 12, 2019 · In Exiv2 before v0.27.2, there is an integer overflow vulnerability in the WebPImage::getHeaderOffset function in webpimage.cpp.27Monitor
- Later →CVE-2019-20421Jan 27, 2020 · In Jp2Image::readMetadata() in jp2image.cpp in Exiv2 0.27.2, an input file can result in an infinite loop and hang, with high CPU consumptio31Monitor
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 |
|---|---|---|
| almalinux:exiv2-devel | 0.27.3-2.el8 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:exiv2-doc | 0.27.3-2.el8 · AlmaLinux:8 | Package registry (OSV) |
| alpine:exiv2 | 0.26-r1 · Alpine:v3.10 | Package registry (OSV) |
| debian:exiv2 | 0.27.3-1 · Debian:12 | Package registry (OSV) |
| opensuse:exiv2 | 0.26-150000.6.26.1 · openSUSE:Leap 15.3 | Package registry (OSV) |
| opensuse:exiv2-0_26 | 0.26-150400.9.21.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| red hat:exiv2 | 0:0.27.0-3.el7_8 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:exiv2-debuginfo | 0:0.27.0-3.el7_8 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:exiv2-debugsource | 0:0.27.3-2.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:exiv2-devel | 0:0.27.0-3.el7_8 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:exiv2-doc | 0:0.27.0-3.el7_8 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:exiv2-libs | 0:0.27.0-3.el7_8 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:exiv2-libs-debuginfo | 0:0.27.3-2.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| rocky linux:exiv2 | 0:0.27.3-2.el8 · Rocky Linux:8 | Package registry (OSV) |
| suse:exiv2 | 0.23-12.8.1 · SUSE:Linux Enterprise Software Development Kit 12 SP4 | Package registry (OSV) |
| suse:exiv2 | 0.26-150000.6.26.1 · SUSE:Linux Enterprise Module for Desktop Applications 15 SP3 | Package registry (OSV) |
| suse:exiv2-0_26 | 0.26-150400.9.21.1 · SUSE:Linux Enterprise Module for Desktop Applications 15 SP4 | 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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.
- 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
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- 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:R/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 (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.