dbcve.org
Firefox MobileWeb browser · Mozilla

CVE-2012-1130

HIGH · 9.3 CVSS v2.0 Published 2012-04-25
Fix available
A fix is available. Upgrade to after 10.0.3 or later.
See remediation →
100/100
Remediation priority · Urgent
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
FreeType before 2.4.9, as used in Mozilla Firefox Mobile before 10.0.4 and other products, allows remote attackers to cause a denial of service (invalid heap read operation and memory corruption) or possibly execute arbitrary code via crafted property data in a PCF font.

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

Heap-based memory corruption vulnerability in FreeType versions before 2.4.9 when parsing crafted PCF (Portable Compiled Format) font files. The vulnerability allows remote attackers to perform invalid heap reads and potentially execute arbitrary code via malicious property data embedded in the font.

MitigationUpgrade FreeType library to version 2.4.9 or later. In Firefox Mobile, ensure version 10.0.4 or later is deployed. Validate and restrict font file sources to trusted files only as a defense-in-depth measure.

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
Firefox MobileWeb browser
Affected:<= 10.0.3= 1.0= 4.0= 5.0= 6.0= 6.0.1= 6.0.2= 7.0= 8.0= 9.0= 10.0= 10.0.1
FreetypeApplication
Affected:<= 2.4.8= 1.3.1= 2.0.0= 2.0.1= 2.0.2= 2.0.3= 2.0.4= 2.0.5= 2.0.6= 2.0.7= 2.0.8= 2.0.9

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
Complete
Integrity
Complete
Availability
Complete

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

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. Identify installed FreeType library version
    Query the FreeType library version via headers (FT_FREETYPE_H or freetype.h defines like FREETYPE_MAJOR, FREETYPE_MINOR, FREETYPE_PATCH) or run 'freetype-config --version' if available
    Affected if Version is 2.4.8 or earlier, or any 2.0.x version, or version 1.3.1
  2. Identify Firefox Mobile version
    Open Firefox Mobile, navigate to Settings > About Firefox, or check the application package details
    Affected if Version is 10.0.3 or earlier, or any of these specific versions: 1.0, 4.0, 5.0, 6.0, 6.0.1, 6.0.2, 7.0, 8.0, 9.0, 10.0, 10.0.1
  3. Determine if PCF font parsing is occurring
    Inspect application logs or network traffic for PCF font file loading; check if the application loads fonts from untrusted or external sources
    Affected if PCF font files are being parsed by a vulnerable FreeType version, or any font loading from untrusted sources is occurring on affected versions
  4. Check for malicious font file handling
    Review font file processing code paths in the application to see if PCF font parsing is enabled or used
    Affected if The application or library attempts to parse PCF format fonts using an affected FreeType version

You are affected if FreeType library version is below 2.4.9 (or is 2.0.x/1.3.1) OR Firefox Mobile version is 10.0.3 or earlier, and the system processes PCF font files from untrusted sources.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 10.0.3
Interim mitigation

Upgrade FreeType library to version 2.4.9 or later. In Firefox Mobile, ensure version 10.0.4 or later is deployed. Validate and restrict font file sources to trusted files only as a defense-in-depth measure.

Recommended fix High confidence

FreeType 2.4.9+ and Firefox Mobile 10.0.4+

  1. Upgrade FreeType library to version 2.4.9 or later
  2. Upgrade Firefox Mobile to version 10.0.4 or later
  3. Rebuild or repackage any applications that bundle the vulnerable FreeType library
  4. For systems using package managers, run: zypper update freetype (OpenSUSE) or yum update freetype (Red Hat) to apply security updates
  5. For Firefox Mobile users, update via the Mozilla repository or app store to obtain version 10.0.4 or newer
Caveat Minor - upgrading to the next minor versions should not introduce breaking changes; ensure any custom font rendering code is tested

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Firefox Mobile Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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