In exif_data_save_data_entry of exif-data.c, there is a possible out of bounds read due to a missing bounds check.
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.30% (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: libexif (Alpine:v3.10) 0.6.22-r0; libexif (Debian:12) 0.6.21-8; libexif (Debian:8) 0.6.21-2+deb8u2.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to libexif (Alpine:v3.10) 0.6.22-r0; libexif (Debian:12) 0.6.21-8; libexif (Debian:8) 0.6.21-2+deb8u2 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
In exif_data_save_data_entry of exif-data.c, there is a possible out of bounds read due to a missing bounds check. This could lead to local information disclosure with no additional execution privileges needed. User interaction is needed for exploitation.Product: AndroidVersions: Android-8.0 Android-8.1 Android-9 Android-10Android ID: A-148705132
- Published
- May 14, 2020
- Updated
- Jun 16, 2026
- EPSS
- 0.3% · 21th percentile
- CWE
- CWE-125
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.3%
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 |
|---|---|---|
| android | cpe:2.3:o:google:android | |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
| canonical | ubuntu linux | cpe:2.3:o:canonical:ubuntu_linux |
| libexif project | libexif | cpe:2.3:a:libexif_project:libexif |
| opensuse | leap | cpe:2.3:o:opensuse:leap |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- canonical ubuntu linux12.04
- canonical ubuntu linux14.04
- canonical ubuntu linux16.04
- canonical ubuntu linux18.04
- canonical ubuntu linux19.10
- canonical ubuntu linux20.04
- debian debian linux8.0
- google android10.0
- google android8.0
- google android8.1
- google android9.0
- libexif project libexifbefore 0.6.22
- opensuse leap15.1
Versions reported by the vendor
Affected version ranges reported by the assigning authority (google_android). Independent of NVD's CPE analysis and usually ahead of it.
n/a Android
- Android-8.0 Android-8.1 Android-9 Android-10affected
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.22-r0 | 0.6.22-r0 |
| Debian:12 | libexif | before 0.6.21-8 | 0.6.21-8 |
| 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 |
| Red Hat:enterprise_linux:7::client | libexif | before 0:0.6.22-1.el7 | 0:0.6.22-1.el7 |
| Red Hat:enterprise_linux:7::client | libexif-debuginfo | before 0:0.6.22-1.el7 | 0:0.6.22-1.el7 |
| Red Hat:enterprise_linux:7::client | libexif-devel | before 0:0.6.22-1.el7 | 0:0.6.22-1.el7 |
| Red Hat:enterprise_linux:7::client | libexif-doc | before 0:0.6.22-1.el7 | 0:0.6.22-1.el7 |
| Red Hat:enterprise_linux:8::appstream | libexif | before 0:0.6.22-4.el8 | 0:0.6.22-4.el8 |
| Red Hat:enterprise_linux:8::appstream | libexif-debuginfo | before 0:0.6.22-4.el8 | 0:0.6.22-4.el8 |
| Red Hat:enterprise_linux:8::appstream | libexif-debugsource | before 0:0.6.22-4.el8 | 0:0.6.22-4.el8 |
| Red Hat:enterprise_linux:8::crb | libexif-devel | before 0:0.6.22-4.el8 | 0:0.6.22-4.el8 |
| SUSE:HPE Helion OpenStack 8 | libexif | before 0.6.22-8.9.1 | 0.6.22-8.9.1 |
| SUSE:Linux Enterprise Module for Desktop Applications 15 SP1 | libexif | before 0.6.22-5.6.1 | 0.6.22-5.6.1 |
Same product
google: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-2215A use-after-free in binder.c allows an elevation of privilege from an application to the Linux Kernel.KEV83Now
- CVE-2011-1823The vold volume manager daemon on Android 3.0 and 2.x before 2.3.4 trusts messages that are received from a PF_NETLINK socket, which allows KEV73This week
- CVE-2015-1538Integer overflow in the SampleTable::setSampleToChunkParams function in SampleTable.cpp in libstagefright in Android before 5.1.1 LMY48I all70This week
Published before and after this one in the same product
- ← EarlierCVE-2020-0091May 14, 2020 · In mnld, an incorrect configuration in driver_cfg of mnld for meta factory mode.Product: AndroidVersions: Android SoCAndroid ID: A-14980870022Monitor
- ← EarlierCVE-2020-0092May 14, 2020 · In setHideSensitive of NotificationStackScrollLayout.java, there is a possible disclosure of sensitive notification content due to a permiss20Monitor
- Later →CVE-2020-0094May 14, 2020 · In setImageHeight and setImageWidth of ExifUtils.cpp, there is a possible out of bounds write due to an incorrect bounds check.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.22-r0 · Alpine:v3.10 | Package registry (OSV) |
| debian:libexif | 0.6.21-8 · Debian:12 | Package registry (OSV) |
| opensuse:libexif | 0.6.22-lp151.4.6.1 · openSUSE:Leap 15.1 | Package registry (OSV) |
| red hat:libexif | 0:0.6.22-1.el7 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:libexif-debuginfo | 0:0.6.22-1.el7 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:libexif-debugsource | 0:0.6.22-4.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:libexif-devel | 0:0.6.22-1.el7 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:libexif-doc | 0:0.6.22-1.el7 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| suse:libexif | 0.6.22-8.9.1 · SUSE:HPE Helion OpenStack 8 | 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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-20-348 · May 15, 2020(Android Zafiyeti)
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
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-125 · Out-of-bounds ReadCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.