dbcve.org
GnashApplication · Gnu

CVE-2012-1175

MEDIUM · 6.8 CVSS v2.0 Published 2012-08-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/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
Integer overflow in the GnashImage::size method in libbase/GnashImage.h in GNU Gnash 0.8.10 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a crafted SWF file, which triggers a heap-based buffer overflow.

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

Integer overflow in the GnashImage::size method in libbase/GnashImage.h in GNU Gnash 0.8.10 allows remote attackers to cause a heap-based buffer overflow via a crafted SWF file, potentially leading to denial of service or arbitrary code execution.

MitigationAvoid processing untrusted SWF files with vulnerable Gnash versions; obtain and apply any vendor patches for the integer overflow in GnashImage::size calculation.

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
GnashApplication
Affected:= 0.8.10

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
M
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:M/Au:N/C:P/I:P/A:P

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 Gnash is installed
    Run 'gnash --version' or check your package manager for gnash packages (dpkg -l | grep gnash, rpm -qa | grep gnash, etc.)
    Affected if Gnash is not installed or the command returns nothing
  2. Verify the installed Gnash version
    Compare the version output from 'gnash --version' to the affected version 0.8.10
    Affected if The installed version is exactly 0.8.10
  3. Confirm the vulnerable library exists
    Check for the presence of libbase/GnashImage.h or the compiled GnashImage library file in the installation directory (typically in /usr/include/gnash/libbase/ or /usr/lib/)
    Affected if The GnashImage source or library file exists and the version is 0.8.10
  4. Determine if Gnash can process SWF files
    Check Gnash configuration or test if Gnash can be invoked to load/process SWF files (e.g., 'gnash --help' to see supported file handlers, or attempt to run gnash on a test SWF)
    Affected if Gnash is configured to handle SWF file inputs and the version is 0.8.10

You are affected if Gnash version 0.8.10 is installed and configured to process SWF files, as the integer overflow in GnashImage::size will trigger when parsing a crafted SWF.

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

Avoid processing untrusted SWF files with vulnerable Gnash versions; obtain and apply any vendor patches for the integer overflow in GnashImage::size calculation.

Fix this in Gnash Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-1175 — 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-2012-1175 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