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

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

- **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-6629, GHSA-7vr8-hqr3-rjrw, RHSA-2013:1804

## What is CVE-2013-6629?

CVE-2013-6629 is a medium-severity vulnerability in Canonical Ubuntu Linux, 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_sos function in jdmarker.c in (1) libjpeg 6b and (2) libjpeg-turbo through 1.3.0, as used in Google Chrome before 31.0.1650.48, Ghostscript, and other products, does not check for certain duplications of component data during the reading of segments that follow Start Of Scan (SOS) JPEG markers, which allows remote attackers to obtain sensitive information from uninitialized memory locations via a crafted JPEG image.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 11 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libjpeg` | Red Hat:enterprise_linux:5::client | All versions | 0:6b-38 |
| `libjpeg-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 0:6b-38 |
| `libjpeg` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:6b-38 |
| `libjpeg-debuginfo` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:6b-38 |
| `libjpeg-devel` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:6b-38 |
| `libjpeg` | Red Hat:enterprise_linux:5::server | All versions | 0:6b-38 |
| `libjpeg-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:6b-38 |
| `libjpeg-devel` | Red Hat:enterprise_linux:5::server | All versions | 0:6b-38 |

Products: Artifex Gpl Ghostscript, Canonical Ubuntu Linux, Debian Debian Linux, Fedoraproject Fedora, Google Chrome, Libjpeg-Turbo Libjpeg-Turbo, Mozilla Firefox, Mozilla Seamonkey, Mozilla Thunderbird, Opensuse Opensuse, Oracle Solaris.

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

Upgrade to a fixed version.

## Is CVE-2013-6629 being exploited?

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

## Other vulnerabilities in Canonical Ubuntu Linux

- [CVE-2012-4875](https://insights.sbomify.com/CVE-2012-4875/): Memory corruption in n/a (critical 9.3)
- [CVE-2010-1628](https://insights.sbomify.com/CVE-2010-1628/): Memory corruption in n/a (critical 9.3)
- [CVE-2010-1869](https://insights.sbomify.com/CVE-2010-1869/): Memory corruption in n/a (critical 9.3)
- [CVE-2016-9601](https://insights.sbomify.com/CVE-2016-9601/): Memory corruption in ghostscript (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-6629 is a medium-severity vulnerability in Canonical Ubuntu Linux, 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-6629 in the wild and no public exploit code.

Affected product: Canonical Ubuntu Linux. 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-6629/ (Markdown: https://insights.sbomify.com/CVE-2013-6629/index.md)
```

## Sources

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

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