CVE-2017-7544: libexif through 0.6.21 is vulnerable to out-of-bounds heap read vulnerability in exif_data_save_data_entry function in libexif/exif-data.c…
Noroxi assessment
Priority: Monitor (action score 37/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: 3.2% (FIRST EPSS); higher than 88.6% 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.
- Fixed version: libexif (Alpine:v3.10) 0.6.21-r3; libexif (Alpine:v3.5) 0.6.21-r2; libexif (Debian:12) 0.6.21-2.1.
Low priority for now. Upgrade to libexif (Alpine:v3.10) 0.6.21-r3; libexif (Alpine:v3.5) 0.6.21-r2; libexif (Debian:12) 0.6.21-2.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
libexif through 0.6.21 is vulnerable to out-of-bounds heap read vulnerability in exif_data_save_data_entry function in libexif/exif-data.c caused by improper length computation of the allocated data of an ExifMnote entry which can cause denial-of-service or possibly information disclosure.
- Published
- Sep 21, 2017
- Updated
- Jun 16, 2026
- EPSS
- 3.2% · 88th percentile
- CWE
- CWE-125
Report tools
Action score
37
Low priority for now.
- CVSS
- 36 / 40 · 9.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 3.2%
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.
Is your version affected? Check itNoroxi 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 |
|---|---|---|
| libexif project | libexif | cpe:2.3:a:libexif_project:libexif |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
Red Hat, Inc. libexif
- through 0.6.21affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- libexif project libexifup to 0.6.21 inclusive
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.10 | libexif | before 0.6.21-r3 | 0.6.21-r3 |
| Alpine:v3.5 | libexif | before 0.6.21-r2 | 0.6.21-r2 |
| Debian:12 | libexif | before 0.6.21-2.1 | 0.6.21-2.1 |
| Debian:8 | libexif | before 0.6.21-2+deb8u2 | 0.6.21-2+deb8u2 |
| openSUSE:Leap 15.1 | libexif | before 0.6.22-lp151.4.6.1 | 0.6.22-lp151.4.6.1 |
| openSUSE:Tumbleweed | libexif | before 0.6.23-1.2 | 0.6.23-1.2 |
| SUSE:HPE Helion OpenStack 8 | libexif | before 0.6.22-8.9.1 | 0.6.22-8.9.1 |
| SUSE:Linux Enterprise Desktop 12 SP2 | libexif | before 0.6.21-8.3.1 | 0.6.21-8.3.1 |
| SUSE:Linux Enterprise Module for Desktop Applications 15 SP1 | libexif | before 0.6.22-5.6.1 | 0.6.22-5.6.1 |
| SUSE:Linux Enterprise Software Development Kit 11 SP4 | libexif | before 0.6.17-2.14.3.1 | 0.6.17-2.14.3.1 |
Same product
libexif project: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-13112An issue was discovered in libexif before 0.6.22.37Monitor
- CVE-2020-13113An issue was discovered in libexif before 0.6.22.33Monitor
- CVE-2016-6328A vulnerability was found in libexif.33Monitor
Published before and after this one in the same product
- ← EarlierCVE-2012-2840Jul 13, 2012 · Off-by-one error in the exif_convert_utf16_to_utf8 function in exif-entry.c in the EXIF Tag Parsing Library (aka libexif) before 0.6.21…32Monitor
- ← EarlierCVE-2012-2841Jul 13, 2012 · Integer underflow in the exif_entry_get_value function in exif-entry.c in the EXIF Tag Parsing Library (aka libexif) 0.6.20 might allow…32Monitor
- Later →CVE-2018-20030Feb 20, 2019 · An error when processing the EXIF_IFD_INTEROPERABILITY and EXIF_IFD_EXIF tags within libexif version 0.6.21 can be exploited to exhaust…31Monitor
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:libexif | 0.6.21-r3 · Alpine:v3.10 | Package registry (OSV) |
| debian:libexif | 0.6.21-2.1 · Debian:12 | Package registry (OSV) |
| opensuse:libexif | 0.6.22-lp151.4.6.1 · openSUSE:Leap 15.1 | Package registry (OSV) |
| suse:libexif | 0.6.21-8.3.1 · SUSE:Linux Enterprise Desktop 12 SP2 | 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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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
- high · data can be read
- 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
- High
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-125 · Out-of-bounds ReadCVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
nvd-primary
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)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.