FedoraOperating system · Fedoraproject
CVE-2015-7216
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 · uneditedThe gdk-pixbuf configuration in Mozilla Firefox before 43.0 on Linux GNOME platforms incorrectly enables the JasPer decoder, which allows remote attackers to cause a denial of service or possibly have unspecified other impact via a crafted JPEG 2000 image.
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 confidenceThe gdk-pixbuf image library configuration in Mozilla Firefox versions prior to 43.0 on Linux GNOME platforms incorrectly enables the JasPer decoder by default. This decoder handles JPEG 2000 image processing, and when enabled, allows specially crafted JPEG 2000 images to trigger a denial of service or potentially execute arbitrary code via memory corruption in the JasPer library.
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
FedoraOperating system
= 22= 23
FirefoxWeb browser
<= 42.0= 42.1= 13.1= 13.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Firefox versionOpen Firefox and go to Help > About Firefox, or run 'firefox --version' from command lineAffected if Version is 42.0 or lower on a Linux GNOME system
-
Verify operating system is Linux GNOMERun 'cat /etc/os-release' or check if running a Fedora, openSUSE, or similar GNOME-based Linux distributionAffected if OS is Fedora 22/23, openSUSE 13.1/13.2, or openSUSE Leap 42.1
-
Check if gdk-pixbuf JasPer decoder is enabledExamine gdk-pixbuf loader configuration files for JasPer module presence - typically in /etc/gdk-pixbuf-2.0/ or user gdk-pixbuf cache directories. Look for jasper or JPEG 2000 loader modules.Affected if JasPer/JPEG 2000 decoder support is found enabled in gdk-pixbuf configuration
User is affected if running Firefox 42.0 or earlier on a Linux GNOME system (Fedora 22/23, openSUSE 13.1/13.2, or openSUSE Leap 42.1) with the JasPer decoder enabled in gdk-pixbuf configuration.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade Firefox to version 43.0 or later, which disables the JasPer decoder by default, or manually disable the JasPer decoder in the gdk-pixbuf configuration on affected systems.
Fix this in Fedora
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-7216 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-7216 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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