dbcve.org
Firefox MobileWeb browser · Mozilla

CVE-2012-1132

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 dictionary data in a Type 1 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 buffer vulnerability in FreeType font parsing library versions before 2.4.9 allows remote attackers to cause denial of service via invalid heap read operations and memory corruption, or potentially execute arbitrary code, through crafted dictionary data embedded in Type 1 font files.

MitigationUpdate FreeType library to version 2.4.9 or later, or update affected products (Firefox Mobile to 10.0.4+) that bundle the vulnerable library version.

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
    Run 'freetype-config --version' or check the library file version (e.g., libfreetype.so) using 'ldd --version' or inspect the shared object metadata
    Affected if FreeType version is 2.4.8 or earlier, or any of these specific versions: 1.3.1, 2.0.0 through 2.0.9
  2. Identify Firefox Mobile version
    Check the application version in the Firefox Mobile app settings or examine the application binary metadata
    Affected if Firefox Mobile version is 10.0.3 or earlier, or exactly 1.0, 4.0, 5.0, 6.0, 6.0.1, 6.0.2, 7.0, 8.0, 9.0, 10.0, or 10.0.1
  3. Check if Type 1 font parsing is active
    Monitor or inspect processes that load Type 1 fonts (.pfb, .pfa files) through FreeType, as the vulnerability triggers during dictionary data parsing in these font files
    Affected if Type 1 fonts are being processed by a vulnerable FreeType version (before 2.4.9)

Your environment is affected if FreeType library version is before 2.4.9 (including any 2.0.x versions) or if Firefox Mobile version is 10.0.3 or earlier, and Type 1 fonts are being parsed.

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

Update FreeType library to version 2.4.9 or later, or update affected products (Firefox Mobile to 10.0.4+) that bundle the vulnerable library version.

Recommended fix High confidence

FreeType 2.4.9 or later; Firefox Mobile 10.0.4 or later

  1. Identify the FreeType library version in use by checking the installed package or library file
  2. If using FreeType directly, upgrade to FreeType 2.4.9 or later
  3. If using Firefox Mobile, upgrade to Firefox Mobile 10.0.4 or later
  4. Verify the upgrade was successful by checking the new version number

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
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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