dbcve.org
Apng2gifApplication · Apng2gif Project

CVE-2017-6962

HIGH · 7.5 CVSS v3.0 Published 2017-03-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
An issue was discovered in apng2gif 1.7. There is an integer overflow resulting in a heap-based buffer overflow. This is related to the read_chunk function making an unchecked addition of 12.

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 confidence

apng2gif 1.7 contains an integer overflow vulnerability in the read_chunk function where an unchecked addition of 12 to a user-controlled value results in a heap-based buffer overflow. An attacker could exploit this by supplying a specially crafted APNG file with a malicious chunk size field.

MitigationApply a bounds check before performing the arithmetic operation in read_chunk to ensure the resulting size value does not exceed available buffer limits or integer overflow constraints.

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
Apng2gifApplication
Affected:= 1.7

CVSS 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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if apng2gif is installed
    Run 'which apng2gif' or 'apng2gif --version' to locate the binary
    Affected if apng2gif is present on the system and version equals 1.7
  2. Confirm the installed version
    Run 'apng2gif --version' and verify the output shows version 1.7 exactly
    Affected if The installed version is exactly 1.7 (other versions are not affected)
  3. Identify apng2gif usage in processing pipelines
    Search for scripts, cron jobs, or services that invoke apng2gif to process APNG files, especially from untrusted sources
    Affected if apng2gif is used to process APNG files from untrusted or external sources
  4. Audit APNG file inputs
    Review any APNG files being fed to apng2gif, particularly those from external or unverified sources
    Affected if apng2gif processes APNG files with potentially malicious chunk size fields

The environment is affected only if apng2gif version 1.7 is installed and actively used to process APNG files, since the vulnerability triggers during chunk parsing of a crafted file.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply a bounds check before performing the arithmetic operation in read_chunk to ensure the resulting size value does not exceed available buffer limits or integer overflow constraints.

Fix this in Apng2gif Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-6962 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-6962 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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