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

> Remote attackers can recover plaintext from TLS/DTLS connections via timing side-channel attacks on CBC padding, affecting libraries like OpenSSL and OpenJDK.

- **Severity:** Low 2.6 (`AV:N/AC:H/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:** Not needed
- **Fix available:** Yes
- **Published:** 8 Feb 2013
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2013-0169, GHSA-pg96-42c4-p633, UBUNTU-CVE-2013-0169

## What is CVE-2013-0169?

CVE-2013-0169 is a low-severity vulnerability in Openssl Openssl, published on 8 Feb 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The TLS protocol 1.1 and 1.2 and the DTLS protocol 1.0 and 1.2, as used in OpenSSL, OpenJDK, PolarSSL, and other products, do not properly consider timing side-channel attacks on a MAC check requirement during the processing of malformed CBC padding, which allows remote attackers to conduct distinguishing attacks and plaintext-recovery attacks via statistical analysis of timing data for crafted packets, aka the "Lucky Thirteen" issue.

Weakness: CWE-310

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

It affects 3 products.


Products: Openssl Openssl, Oracle Openjdk, Polarssl Polarssl.

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

Apply the vendor's patch.

## Is CVE-2013-0169 being exploited?

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

Public exploit code:

- Exploit for cve-2013-0169 (github_poc): https://github.com/wearohat/lucky13

## Other vulnerabilities in Openssl Openssl

- [CVE-2009-3245](https://insights.sbomify.com/CVE-2009-3245/): Null dereference in n/a (critical 10.0)
- [CVE-2006-3738](https://insights.sbomify.com/CVE-2006-3738/): Memory corruption in n/a (critical 10.0)
- [CVE-2026-63073](https://insights.sbomify.com/CVE-2026-63073/): Untrusted Sender DN Used as Format String in CMP Response Validation (critical 9.8)
- [CVE-2016-6309](https://insights.sbomify.com/CVE-2016-6309/): Use after free in n/a (critical 9.8)
- [CVE-2016-0799](https://insights.sbomify.com/CVE-2016-0799/): Integer overflow in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-0169 is a low-severity vulnerability in Openssl Openssl, published on 8 Feb 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-0169 in the wild and no public exploit code.

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

## Sources

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

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