CVE-2016-6328: A vulnerability was found in libexif.
Noroxi assessment
Priority: Monitor (action score 33/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.6% (FIRST EPSS); higher than 77.2% 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: libexif (Alpine:v3.10) 0.6.22-r0; libexif (Debian:12) 0.6.21-2.1; libexif (Debian:8) 0.6.21-2+deb8u2.
- Severity is disputed: the assigning authority (CNA) scores it 6.1, NVD 8.1.
Low priority for now. Upgrade to libexif (Alpine:v3.10) 0.6.22-r0; libexif (Debian:12) 0.6.21-2.1; 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
A vulnerability was found in libexif. An integer overflow when parsing the MNOTE entry data of the input file. This can cause Denial-of-Service (DoS) and Information Disclosure (disclosing some critical heap chunk metadata, even other applications' private data).
- Published
- Oct 31, 2018
- Updated
- Jun 16, 2026
- EPSS
- 1.6% · 77th percentile
- CWE
- CWE-190
Report tools
Action score
33
Low priority for now.
- CVSS
- 32 / 40 · 8.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 1.6%
CNA vs NVD score
- NVD
- 8.1
- CNA · redhat
- 6.1
- 2.0 point gap
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:L
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- 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 |
| canonical | ubuntu linux | cpe:2.3:o:canonical:ubuntu_linux |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
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.
[UNKNOWN] libexif
- n/aaffected
Affected versions · NVD (7)
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
- debian debian linux8.0
- libexif project libexifbefore 0.6.22
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-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 |
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-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.22-r0 · 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
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:0 | 2024-11-12 |
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.
- Published
- First PoC+2203 d
- TodayNov 16, 2026+2937 d
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.
- 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
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-190 · Integer Overflow or WraparoundCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.