CVE-2012-2812: The exif_entry_get_value function in exif-entry.c in the EXIF Tag Parsing Library (aka libexif) before 0.6.21 allows remote attackers to…
Noroxi assessment
Priority: Monitor (action score 26/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.8% (FIRST EPSS); higher than 90.4% of all records.
- No special conditions are required; it is repeatable.
- Fixed version: libexif (Alpine:v3.10) 0.6.21-r0; libexif (Debian:12) 0.6.20-3; libexif (Debian:6.0) 0.6.19-1+squeeze1.
Low priority for now. Upgrade to libexif (Alpine:v3.10) 0.6.21-r0; libexif (Debian:12) 0.6.20-3; libexif (Debian:6.0) 0.6.19-1+squeeze1 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
The exif_entry_get_value function in exif-entry.c in the EXIF Tag Parsing Library (aka libexif) before 0.6.21 allows remote attackers to cause a denial of service (out-of-bounds read) or possibly obtain sensitive information from process memory via crafted EXIF tags in an image.
- Published
- Jul 13, 2012
- Updated
- Jun 16, 2026
- EPSS
- 3.8% · 90th percentile
- CWE
- CWE-119
Report tools
Action score
26
Low priority for now.
- CVSS
- 25 / 40 · 6.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 3.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.
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 |
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.20 inclusive
- libexif project libexif0.6.14
- libexif project libexif0.6.15
- libexif project libexif0.6.16
- libexif project libexif0.6.18
- libexif project libexif0.6.19
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-r0 | 0.6.21-r0 |
| Debian:12 | libexif | before 0.6.20-3 | 0.6.20-3 |
| Debian:6.0 | libexif | before 0.6.19-1+squeeze1 | 0.6.19-1+squeeze1 |
| openSUSE:Tumbleweed | libexif | before 0.6.21-10.8 | 0.6.21-10.8 |
| Red Hat:enterprise_linux:5::client | libexif | before 0:0.6.21-1.el5_8 | 0:0.6.21-1.el5_8 |
| Red Hat:enterprise_linux:5::client | libexif-debuginfo | before 0:0.6.21-1.el5_8 | 0:0.6.21-1.el5_8 |
| Red Hat:enterprise_linux:5::client_workstation | libexif-devel | before 0:0.6.21-1.el5_8 | 0:0.6.21-1.el5_8 |
| Red Hat:enterprise_linux:6::client | libexif | before 0:0.6.21-5.el6_3 | 0:0.6.21-5.el6_3 |
| Red Hat:enterprise_linux:6::client | libexif-debuginfo | before 0:0.6.21-5.el6_3 | 0:0.6.21-5.el6_3 |
| Red Hat:enterprise_linux:6::client | libexif-devel | before 0:0.6.21-5.el6_3 | 0:0.6.21-5.el6_3 |
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-2017-7544libexif 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…37Monitor
- CVE-2020-13113An issue was discovered in libexif before 0.6.22.33Monitor
Published before and after this one in the same product
- ← EarlierCVE-2007-6351Dec 19, 2007 · libexif 0.6.16 and earlier allows context-dependent attackers to cause a denial of service (infinite recursion) via an image file with…18Monitor
- ← EarlierCVE-2009-3895Nov 20, 2009 · Heap-based buffer overflow in the exif_entry_fix function (aka the tag fixup routine) in libexif/exif-entry.c in libexif 0.6.18 allows…29Monitor
- Later →CVE-2012-2813Jul 13, 2012 · The exif_convert_utf16_to_utf8 function in exif-entry.c in the EXIF Tag Parsing Library (aka libexif) before 0.6.21 allows remote attackers…26Monitor
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-r0 · Alpine:v3.10 | Package registry (OSV) |
| debian:libexif | 0.6.20-3 · Debian:12 | Package registry (OSV) |
| opensuse:libexif | 0.6.21-10.8 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:libexif | 0:0.6.21-1.el5_8 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
| red hat:libexif-debuginfo | 0:0.6.21-1.el5_8 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
| red hat:libexif-devel | 0:0.6.21-1.el5_8 · Red Hat:enterprise_linux:5::client_workstation | 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
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- P · data can be read
- Integrity
- none
- Availability
- P · the service can be disrupted
- Attack complexity
- Low
- Confidentiality impact
- P
- Integrity impact
- None
- Availability impact
- P
Weakness class (CWE)
CWE-119 · Improper Restriction of Operations within the Bounds of a Memory BufferCVSS vector
AV:N/AC:L/Au:N/C:P/I:N/A:P
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)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Buffer ManipulationCAPEC-123likelihood: 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
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.