CVE-2020-0182
published 2020-06-11CVE-2020-0182: In exif_entry_get_value of exif-entry.c, there is a possible out of bounds read due to a missing bounds check. This could lead to local information disclosure…
PriorityP431medium6.5CVSS 3.1
AVNACLPRNUINSUCLINAL
EPSS
1.11%
62.1th percentile
In exif_entry_get_value of exif-entry.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 not needed for exploitation.Product: AndroidVersions: Android-10Android ID: A-147140917
Affected
12 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | debian_linux | — | — |
| debian | libexif | < libexif 0.6.22-1 (bookworm) | libexif 0.6.22-1 (bookworm) |
| android | — | — | |
| android | — | — | |
| libexif_project | libexif | >= 0 < 0.6.22-1 | 0.6.22-1 |
| libexif_project | libexif | >= 0 < 0.6.22-1 | 0.6.22-1 |
| libexif_project | libexif | >= 0 < 0.6.22-1 | 0.6.22-1 |
| libexif_project | libexif | >= 0 < 0.6.22-1 | 0.6.22-1 |
| libexif_project | libexif | >= 0 < 0.6.21-2ubuntu0.5 | 0.6.21-2ubuntu0.5 |
| libexif_project | libexif | >= 0 < 0.6.21-4ubuntu0.5 | 0.6.21-4ubuntu0.5 |
| libexif_project | libexif | >= 0 < 0.6.21-6ubuntu0.3 | 0.6.21-6ubuntu0.3 |
| libexif_project | libexif | >= 0 < 0.6.21-1ubuntu1+esm5 | 0.6.21-1ubuntu1+esm5 |
CVSS provenance
nvdv3.16.5MEDIUMCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L
nvdv2.06.4MEDIUMAV:N/AC:L/Au:N/C:P/I:N/A:P
osv6.5MEDIUM
vendor_debian6.5LOW
vendor_redhat6.5MEDIUM
vendor_ubuntu5.0MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-5mj9-pf4j-ccp7: In exif_entry_get_value of exif-entry
ghsa_unreviewed·2022-05-24
CVE-2020-0182 [LOW] GHSA-5mj9-pf4j-ccp7: In exif_entry_get_value of exif-entry
In exif_entry_get_value of exif-entry.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 not needed for exploitation.Product: AndroidVersions: Android-10Android ID: A-147140917
OSV
libexif vulnerabilities
osv·2020-06-16·CVSS 5.0
CVE-2020-0093 [MEDIUM] libexif vulnerabilities
libexif vulnerabilities
It was discovered that libexif incorrectly handled certain inputs.
An attacker could possibly use this issue to expose sensitive information.
(CVE-2020-0093, CVE-2020-0182)
It was discovered that libexif incorrectly handled certain inputs.
An attacker could possibly use this issue to cause a remote denial of service.
(CVE-2020-0198)
It was discovered that libexif incorrectly handled certain inputs.
An attacker could possibly use this issue to expose sensitive information or
cause a crash. (CVE-2020-13112)
It was discovered that libexif incorrectly handled certain inputs.
An attacker could possibly use this issue to cause a crash.
(CVE-2020-13113)
It was discovered libexif incorrectly handled certain inputs.
An attacker could possibly use this issue to cause a d
OSV
CVE-2020-0182: In exif_entry_get_value of exif-entry
osv·2020-06-11·CVSS 6.5
CVE-2020-0182 [MEDIUM] CVE-2020-0182: In exif_entry_get_value of exif-entry
In exif_entry_get_value of exif-entry.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 not needed for exploitation.Product: AndroidVersions: Android-10Android ID: A-147140917
Ubuntu
libexif vulnerabilities
vendor_ubuntu·2020-06-16·CVSS 5.0
CVE-2020-0093 [MEDIUM] libexif vulnerabilities
Title: libexif vulnerabilities
Summary: Several security issues were fixed in libexif.
It was discovered that libexif incorrectly handled certain inputs.
An attacker could possibly use this issue to expose sensitive information.
(CVE-2020-0093, CVE-2020-0182)
It was discovered that libexif incorrectly handled certain inputs.
An attacker could possibly use this issue to cause a remote denial of service.
(CVE-2020-0198)
It was discovered that libexif incorrectly handled certain inputs.
An attacker could possibly use this issue to expose sensitive information or
cause a crash. (CVE-2020-13112)
It was discovered that libexif incorrectly handled certain inputs.
An attacker could possibly use this issue to cause a crash.
(CVE-2020-13113)
It was discovered libexif incorrectly handled certai
Red Hat
libexif: out of bounds read due to a missing bounds check in exif_entry_get_value function in exif-entry.c
vendor_redhat·2020-06-01·CVSS 6.5
CVE-2020-0182 [MEDIUM] CWE-125 libexif: out of bounds read due to a missing bounds check in exif_entry_get_value function in exif-entry.c
libexif: out of bounds read due to a missing bounds check in exif_entry_get_value function in exif-entry.c
In exif_entry_get_value of exif-entry.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 not needed for exploitation.Product: AndroidVersions: Android-10Android ID: A-147140917
Mitigation: This flaw could be mitigated by not passing untrusted input to libexif.
Package: libexif (Red Hat Enterprise Linux 5) - Out of support scope
Package: libexif (Red Hat Enterprise Linux 6) - Out of support scope
Debian
CVE-2020-0182: libexif - In exif_entry_get_value of exif-entry.c, there is a possible out of bounds read ...
vendor_debian·2020·CVSS 6.5
CVE-2020-0182 [MEDIUM] CVE-2020-0182: libexif - In exif_entry_get_value of exif-entry.c, there is a possible out of bounds read ...
In exif_entry_get_value of exif-entry.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 not needed for exploitation.Product: AndroidVersions: Android-10Android ID: A-147140917
Scope: local
bookworm: resolved (fixed in 0.6.22-1)
bullseye: resolved (fixed in 0.6.22-1)
forky: resolved (fixed in 0.6.22-1)
sid: resolved (fixed in 0.6.22-1)
trixie: resolved (fixed in 0.6.22-1)
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2020-0182 libexif: out of bounds read due to a missing bounds check in exif_entry_get_value function in exif-entry.c
bugzilla·2020-06-30·CVSS 6.5
CVE-2020-0182 [MEDIUM] CVE-2020-0182 libexif: out of bounds read due to a missing bounds check in exif_entry_get_value function in exif-entry.c
CVE-2020-0182 libexif: out of bounds read due to a missing bounds check in exif_entry_get_value function in exif-entry.c
In exif_entry_get_value of exif-entry.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 not needed for exploitation.
References:
https://source.android.com/security/bulletin/pixel/2020-06-01
https://android.googlesource.com/platform/external/libexif/+/4b7b14770c4290eaeaebadf0e99ffdfdbd8f725c
Discussion:
Created libexif tracking bugs for this issue:
Affects: fedora-all [bug 1852491]
---
There is a possible small out-of-bounds read in exif_entry_get_value() in cases where entry->data is not NULL-terminated or smaller than 7 bytes
Bugzilla
CVE-2020-0182 libexif: out of bounds read due to a missing bounds check in exif_entry_get_value function in exif-entry.c [fedora-all]
bugzilla·2020-06-30·CVSS 6.5
CVE-2020-0182 [MEDIUM] CVE-2020-0182 libexif: out of bounds read due to a missing bounds check in exif_entry_get_value function in exif-entry.c [fedora-all]
CVE-2020-0182 libexif: out of bounds read due to a missing bounds check in exif_entry_get_value function in exif-entry.c [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit messag
https://lists.debian.org/debian-lts-announce/2020/06/msg00020.htmlhttps://source.android.com/security/bulletin/pixel/2020-06-01https://usn.ubuntu.com/4396-1/https://lists.debian.org/debian-lts-announce/2020/06/msg00020.htmlhttps://source.android.com/security/bulletin/pixel/2020-06-01https://usn.ubuntu.com/4396-1/
2020-06-11
Published