# CVE-2013-6630: Information disclosure in n/a

> Remote attackers can read sensitive uninitialized memory via crafted JPEG images in libjpeg-turbo, affecting applications like Chrome.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 15 Nov 2013
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2013-6630, GHSA-pwx8-2f52-93wg

## What is CVE-2013-6630?

CVE-2013-6630 is a medium-severity vulnerability in Google Chrome, published on 15 Nov 2013. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-189

## Which versions are affected by CVE-2013-6630?

It affects 1 product.


Products: Google Chrome.

## How do I fix CVE-2013-6630?

Upgrade to a fixed version.

## Is CVE-2013-6630 being exploited?

There is no known exploitation of CVE-2013-6630 in the wild and no public exploit code.

## Other vulnerabilities in Google Chrome

- [CVE-2022-4135](https://insights.sbomify.com/CVE-2022-4135/): Google Chromium GPU Heap Buffer Overflow (critical 9.6, exploited in the wild)
- [CVE-2020-16017](https://insights.sbomify.com/CVE-2020-16017/): Google Chrome Use-After-Free (critical 9.6, exploited in the wild)
- [CVE-2020-16010](https://insights.sbomify.com/CVE-2020-16010/): Google Chrome for Android UI Heap Buffer Overflow (critical 9.6, exploited in the wild)
- [CVE-2026-87491](https://insights.sbomify.com/CVE-2026-87491/): Google Chromium V8 Out of Bounds Write (high 8.8, exploited in the wild)
- [CVE-2026-85046](https://insights.sbomify.com/CVE-2026-85046/): Google Chromium V8 Type Confusion (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-6630 and fix it if it is affected.

What it is: CVE-2013-6630 is a medium-severity vulnerability in Google Chrome, published on 15 Nov 2013. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2013-6630 in the wild and no public exploit code.

Affected product: Google Chrome. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2013-6630/ (Markdown: https://insights.sbomify.com/CVE-2013-6630/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2013-6630
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-6630
- OSV: https://osv.dev/vulnerability/CVE-2013-6630

---
From sbomify Insights: https://insights.sbomify.com/CVE-2013-6630/
Summaries are generated and may contain mistakes; the official description above is the record.