CVE-2015-7802
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedgifread.c in gif2png, as used in OptiPNG before 0.7.6, allows remote attackers to cause a denial of service (uninitialized memory read) via a crafted GIF file.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA vulnerability exists in gifread.c in gif2png (used by OptiPNG before version 0.7.6) where the code reads uninitialized memory when processing a crafted GIF file. This uninitialized memory read can cause a denial of service condition.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 12.04= 14.04= 15.10= 0.7.5CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify OptiPNG is installedRun `optipng --version` or check for the optipng package using your system package manager (e.g., `dpkg -l | grep optipng` on Debian/Ubuntu, `rpm -qa | grep optipng` on RHEL/CentOS)Affected if OptiPNG is installed and the version is 0.7.5 or earlier
-
Confirm installed OptiPNG versionExamine the version number output from `optipng --version`. Compare it against the affected version 0.7.5Affected if Version is 0.7.5 or any version lower than 0.7.6
-
Check for gif2png componentLook for the gif2png binary or library on the system (e.g., `which gif2png`, `find /usr -name gif2png*`, or check within the OptiPNG installation directory)Affected if gif2png is present on the system and is from an unpatched OptiPNG installation (pre-0.7.6)
-
Identify Ubuntu distribution versionRun `lsb_release -r` or check `/etc/lsb-release` to determine if the system is running Ubuntu 12.04, 14.04, or 15.10Affected if System is Ubuntu 12.04, 14.04, or 15.10 and has OptiPNG installed from the distribution packages
A user is affected if OptiPNG version 0.7.5 or earlier (or from Ubuntu 12.04/14.04/15.10 repositories) is installed and the gif2png component is present on the system.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade OptiPNG to version 0.7.6 or later, which includes the patched gif2png component that properly initializes memory before reading in the GIF parsing routine.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-7802 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-7802 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data