CVE-2016-6328

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: 2018-10-31 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2016-6328 is rated Moderate Risk (56.4/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.57%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2016-6328

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-27 0.69% 0.57% -0.12%
2 2026-03-29 1.12% 0.69% -0.43%
3 2025-10-01 — 1.12% —

Full EPSS history (15 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2016-6328

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.1 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 5.2 [email protected]
6.1 3.0 MEDIUM
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:L Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 1.8 4.2 [email protected]
5.8 2.0 MEDIUM
AV:N/AC:M/Au:N/C:P/I:N/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:P)
Partial availability impact.
 8.6 4.9 [email protected]

Weakness enumeration for CVE-2016-6328

OS Trackers for CVE-2016-6328

vendor priority summary link
alpine — CVE-2016-6328: 1 source package rows (libexif); 10 state rows across 10 repos (3.10-main, 3.11-main, 3.12-main, 3.17-community, 3.18-community, 3.19-community, 3.20-community, 3.21-community, 3.22-community, edge-community); fixed 10, open 0. https://security.alpinelinux.org/vuln/CVE-2016-6328
debian not yet assigned CVE-2016-6328 not yet assigned priority: Debian including 1 source packages (libexif), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2016-6328
gentoo normal CVE-2016-6328: 1 GLSA(s) (202007-05), 1 atom(s) (media-libs/libexif); latest impact normal. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2016-6328
redhat low — https://access.redhat.com/security/cve/CVE-2016-6328
suse medium CVE-2016-6328 severity moderate: SUSE including 27 source package names (libexif, libexif-32bit, …), 112 product×package rows across 64 product lines (HPE Helion OpenStack 8, SUSE Enterprise Storage 5, … (64 product lines)): Fixed 105, Known Not Affected 7. https://www.suse.com/security/cve/CVE-2016-6328/
ubuntu low CVE-2016-6328 low priority: Ubuntu including 1 source packages (libexif), 9 status rows across 9 suites (artful, bionic, cosmic, disco, eoan, trusty, upstream, xenial, zesty): ignored 3, not-affected 3, released 2, needed 1. https://ubuntu.com/security/CVE-2016-6328

Affected software / configurations for CVE-2016-6328

Vendor Product Version Raw CPE
libexif_project libexif < 0.6.22 cpe:2.3:a:libexif_project:libexif:*:*:*:*:*:*:*:*
canonical ubuntu_linux 12.04 cpe:2.3:o:canonical:ubuntu_linux:12.04:*:*:*:-:*:*:*
canonical ubuntu_linux 14.04 cpe:2.3:o:canonical:ubuntu_linux:14.04:*:*:*:esm:*:*:*
canonical ubuntu_linux 16.04 cpe:2.3:o:canonical:ubuntu_linux:16.04:*:*:*:esm:*:*:*
canonical ubuntu_linux 18.04 cpe:2.3:o:canonical:ubuntu_linux:18.04:*:*:*:lts:*:*:*
canonical ubuntu_linux 19.10 cpe:2.3:o:canonical:ubuntu_linux:19.10:*:*:*:*:*:*:*
debian debian_linux 8.0 cpe:2.3:o:debian:debian_linux:8.0:*:*:*:*:*:*:*

References for CVE-2016-6328

cvelogic Threat Intelligence