Integer Overflow Vulnerability in libexif

libexif Updated 02 Oct 2025

Summary

31/10/2018
N/A
Yes i
High
8.1

CVE-2016-6328: A vulnerability was found in libexif. Affects libexif across 3 version ranges.

< 0.6.22-r0 < 3cc7842ca200a4da4bd65850e3c20d5a1811afa7 < edad134a28caaa7ea324b8c075bde52da05ad7d9

Fixed in 0.6.22-r0. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

libexif is an open-source library used for parsing, editing, and manipulating Exif data in image files. Exif data contains metadata such as camera settings, date and time, and location information. This vulnerability (CVE-2016-6328) arises from an integer overflow when parsing the MNOTE entry data of the input file. It can lead to Denial-of-Service (DoS) attacks and Information Disclosure, potentially exposing critical heap chunk metadata and even other applications' private data.

Vulnerability Detail

The integer overflow vulnerability in libexif allows an attacker to manipulate the MNOTE entry data in a way that triggers the overflow. By providing specially crafted input files, an attacker can cause the application using libexif to crash (DoS) or disclose sensitive information from the heap. This vulnerability has a CVSS score of 8.1, indicating a high severity level.

How To Fix

Minimum fixed version

0.6.22-r0

This is the first release that contains the fix.

sudo apk add --upgrade libexif

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is crucial to update to the fixed version of libexif to mitigate the risk.

Conclusion

The integer overflow vulnerability in libexif can have serious consequences, including DoS attacks and Information Disclosure. It is crucial to update to the fixed version of libexif (0.6.22-r0 or later) to mitigate the risk. For further support on vulnerability remediation, contact DevNack.com.

See every vulnerability recorded for libexif →

Share this vulnerability

FAQ

libexif is an open-source library used for parsing and manipulating Exif data in image files.

Exif data is metadata embedded in image files that contains information about the image, such as camera settings, date and time, and location.

An integer overflow occurs when the result of an arithmetic operation exceeds the maximum value that can be represented by the data type.

This vulnerability can lead to Denial-of-Service (DoS) attacks and Information Disclosure, potentially exposing critical heap chunk metadata and even other applications' private data.

To fix this vulnerability, update libexif to version 0.6.22-r0 or later.

Related vulnerabilities

Recent vulnerabilities recorded for libexif.

How To Fix

Minimum fixed version

0.6.22-r0

This is the first release that contains the fix.

sudo apk add --upgrade libexif

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback