dbcve.org
Libjpeg TurboApplication · D.r.commander

CVE-2012-2806

HIGH · 8.8 CVSS v3.1 Published 2012-08-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Heap-based buffer overflow in the get_sos function in jdmarker.c in libjpeg-turbo 1.2.0 allows remote attackers to cause a denial of service (application crash) and possibly execute arbitrary code via a large component count in the header of a JPEG 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 confidence

Heap-based buffer overflow in the get_sos function in jdmarker.c in libjpeg-turbo 1.2.0. The vulnerability occurs when parsing JPEG image headers with a large component count, leading to memory corruption that can cause denial of service (application crash) and potentially allow arbitrary code execution.

MitigationUpgrade libjpeg-turbo to a version that includes proper bounds checking on the component count during JPEG header parsing in the get_sos function.

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
Libjpeg TurboApplication
Affected:= 1.2.0

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
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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 libjpeg-turbo version
    Run 'dpkg -l | grep libjpeg-turbo' on Debian/Ubuntu, 'rpm -qa | grep libjpeg-turbo' on RHEL/CentOS, or check the library file with 'strings /usr/lib/*/libjpeg.so.* | grep -i turbo' to find the version string
    Affected if version is 1.2.0 exactly
  2. Inspect library file version directly
    Use 'file' on the libjpeg shared library and check version info, or use 'ldd --version' to see if libjpeg-turbo is the active JPEG library
    Affected if the library reports version 1.2.0
  3. Verify the get_sos function is present
    Check if the vulnerable jdmarker.c component is compiled into the installed library by examining symbols: 'nm /usr/lib/*/libjpeg.so.* 2>/dev/null | grep get_sos'
    Affected if get_sos symbol exists and library version is 1.2.0

A system is affected only if the installed libjpeg-turbo library version is exactly 1.2.0; any other version is not vulnerable to this specific CVE.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade libjpeg-turbo to a version that includes proper bounds checking on the component count during JPEG header parsing in the get_sos function.

Fix this in Libjpeg Turbo Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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