dbcve.org
Firefox MobileWeb browser · Mozilla

CVE-2012-1144

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 write operation and memory corruption) or possibly execute arbitrary code via a crafted TrueType 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 overflow vulnerability in FreeType font parsing library allows remote attackers to write invalid heap values and corrupt memory via crafted TrueType font files, potentially enabling arbitrary code execution.

MitigationUpdate FreeType library to version 2.4.9 or later, or update affected products (e.g., Firefox Mobile to 10.0.4 or later) that include the patched 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. Check FreeType library version
    Query the installed FreeType library version using pkg-config (pkg-config --modversion freetype2) or check the library file version (freetype-config --version) if available on the system
    Affected if The installed version is 2.4.8 or earlier, or matches any of these versions: 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
  2. Check Mozilla Firefox Mobile version
    Inspect the application version through the browser about dialog or check the application manifest/package metadata
    Affected if Firefox Mobile version is 10.0.3 or earlier, or exactly matches: 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. Identify if FreeType is used for font rendering
    Examine the application configuration or dependencies to confirm FreeType library is loaded for TrueType font parsing
    Affected if FreeType library is actively used for rendering TrueType fonts in any affected application

If the FreeType library version is 2.4.8 or earlier (including 1.3.1 or 2.0.x series), or if Firefox Mobile version is 10.0.3 or earlier, the environment is vulnerable to heap-based buffer overflow via crafted TrueType fonts.

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 (e.g., Firefox Mobile to 10.0.4 or later) that include the patched library version.

Recommended fix High confidence

FreeType 2.4.9+ or Firefox Mobile 10.0.4+

  1. Identify whether the vulnerability is in the FreeType library or Firefox Mobile application in your environment
  2. For FreeType: upgrade to version 2.4.9 or later from the FreeType project (freetype.org)
  3. For Firefox Mobile: upgrade to version 10.0.4 or later from Mozilla
  4. After upgrading, verify the installed version matches the fixed release using --version or about:version
Caveat Standard upgrade risk: test application compatibility with the new library/application version before production deployment

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

Fix this in Firefox Mobile Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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