dbcve.org
Ubuntu LinuxOperating system · Canonical

CVE-2014-1528

HIGH · 10.0 CVSS v2.0 Published 2014-04-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
The sse2_composite_src_x888_8888 function in Pixman, as used in Cairo in Mozilla Firefox 28.0 and SeaMonkey 2.25 on Windows, allows remote attackers to execute arbitrary code or cause a denial of service (out-of-bounds write and application crash) by painting on a CANVAS element.

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

Memory corruption vulnerability in Pixman's SSE2-optimized sse2_composite_src_x888_8888 function used via Cairo in Firefox 28.0 and SeaMonkey 2.25 on Windows. Remote attackers can trigger out-of-bounds writes by crafting malicious CANVAS element painting operations, leading to arbitrary code execution or denial of service.

MitigationUpdate to patched versions of Firefox/SeaMonkey that include the fixed Pixman library; alternatively, apply Pixman security updates and rebuild the software stack.

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
Ubuntu LinuxOperating system
Affected:= 12.04= 12.10= 13.10= 14.04
FirefoxWeb browser
Affected:= 28.0
FedoraOperating system
Affected:= 19
OpensuseOperating system
Affected:= 13.1
OpensuseOperating system
Affected:= 12.3
SolarisOperating system
Affected:= 11.3
SeamonkeyApplication
Affected:= 2.25

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

AV:N/AC:L/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 installed Firefox version
    Run 'firefox --version' or go to Help > About Firefox in the application
    Affected if Version is exactly 28.0
  2. Check installed SeaMonkey version
    Run 'seamonkey --version' or go to Help > About SeaMonkey in the application
    Affected if Version is exactly 2.25
  3. Verify operating system
    Check if running Windows - the vulnerability specifically affects Windows deployments per the advisory
    Affected if Running Windows with affected Firefox/SeaMonkey versions
  4. Confirm Cairo graphics library usage
    The vulnerability lies in Pixman's SSE2 path used via Cairo for CANVAS rendering - check if applications use graphical rendering
    Affected if CANVAS element rendering is active in the browser

You are affected if running Firefox 28.0 or SeaMonkey 2.25 on Windows with graphical CANVAS rendering enabled.

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

Update to patched versions of Firefox/SeaMonkey that include the fixed Pixman library; alternatively, apply Pixman security updates and rebuild the software stack.

Recommended fix High confidence

Firefox 28.0 → Firefox 29.0 or later; SeaMonkey 2.25 → SeaMonkey 2.26 or later

  1. 1. Backup all personal data and browser bookmarks before upgrading.
  2. 2. For Firefox: Download and install Firefox 29.0 or later from the official Mozilla website (firefox.com) or use your system's package manager to upgrade.
  3. 3. For SeaMonkey: Upgrade to SeaMonkey 2.26 or later which contains the fixed Pixman/Cairo components.
  4. 4. Verify the installed version by navigating to 'Help' > 'About Firefox/SeaMonkey' and confirming the version number is 29.0 or higher.
  5. 5. Test that web browsing and canvas rendering functionality work correctly after upgrade.
Caveat Minor: Some older browser extensions may not be compatible with the new major version; test extensions before production use

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

Fix this in Ubuntu Linux Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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