ChromeWeb browser · Google

CVE-2013-6630

MEDIUM · 5.0 CVSS v2.0 Published 2013-11-19

Fix available

A fix is available. Upgrade to after 31.0.1650.47 or later.

See remediation →

59/100

Remediation priority · Elevated

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

The get_dht function in jdmarker.c in libjpeg-turbo through 1.3.0, as used in Google Chrome before 31.0.1650.48 and other products, does not set all elements of a certain Huffman value array during the reading of segments that follow Define Huffman Table (DHT) JPEG markers, which allows remote attackers to obtain sensitive information from uninitialized memory locations via a crafted JPEG image.

Technical summary

dbcve analysis · high confidence

The get_dht function in jdmarker.c in libjpeg-turbo fails to fully initialize a Huffman value array when parsing Define Huffman Table (DHT) JPEG markers and subsequent segments. This causes uninitialized memory contents to be leaked to attackers via crafted JPEG images, resulting in potential information disclosure.

MitigationUpdate libjpeg-turbo to version 1.3.1 or later, or update dependent products (e.g., Google Chrome to 31.0.1650.48 or later) to incorporate the patched library.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

ChromeWeb browser

Affected:<= 31.0.1650.47= 31.0.1650.0= 31.0.1650.2= 31.0.1650.3= 31.0.1650.4= 31.0.1650.5= 31.0.1650.6= 31.0.1650.7= 31.0.1650.8= 31.0.1650.9= 31.0.1650.10= 31.0.1650.11

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Authentication: None
Confidentiality: Partial
Integrity: None
Availability: None

AV:N/AC:L/Au:N/C:P/I:N/A:N

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Check Google Chrome version

Navigate to chrome://settings/help or use 'Help > About Google Chrome' to view the installed version number

Affected if The installed version is 31.0.1650.47 or earlier, specifically any version from 31.0.1650.0 through 31.0.1650.47
Confirm libjpeg-turbo version (if accessible)

Check the libjpeg-turbo library version included with Chrome. On Linux this may be found in /usr/lib or the Chrome application bundle. On Windows check the Chrome installation directory for jpeg*.dll or related libraries

Affected if The bundled libjpeg-turbo library version is earlier than 1.3.1
Verify JPEG parsing behavior

Attempt to parse a specially crafted JPEG image containing Define Huffman Table (DHT) markers with abnormal table data. Monitor for unexpected memory contents in the output or process memory

Affected if Uninitialized memory contents appear in the output when processing JPEG files with non-standard DHT markers
Check for presence of vulnerable code path

If source code is available, inspect the get_dht function in jdmarker.c for incomplete initialization of the Huffman value array. Look for instances where memset or initialization loops may be missing or insufficient

Affected if The code shows the Huffman value array (bits/val arrays) are not fully zeroed before use in the get_dht function

A user is affected if their Google Chrome version is 31.0.1650.47 or earlier, or if the bundled libjpeg-turbo library is version 1.3.0 or earlier and they process untrusted JPEG images.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Upgrade available Upgrade to a release after 31.0.1650.47

Interim mitigation

Update libjpeg-turbo to version 1.3.1 or later, or update dependent products (e.g., Google Chrome to 31.0.1650.48 or later) to incorporate the patched library.

Fix this in Chrome Scoped from the published advisory

Consultation2.0 h
Implementation4.0 h
Testing8.0 h
Review / QA4.0 h

18.0 hours of engineering $3,040

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-6630 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2013-6630?

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.

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

At a glance

A fix existsUpgrade to after 31.0.1650.47 or later

Severity 5.0 Medium

Exploit likelihood EPSS, next 30 days 2.1%

Affects: Chrome

Remediation

Need this fixed?

Fix this in Chrome 18 hrs · Low

Typical engagement from $3,040

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2013-6630 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References