# CVE-2013-6449: The ssl_get_algorithm2 function in ssl/s3_lib.c in OpenSSL before 1.0.2 obtains a certain version number from an incorrect data structure, w


- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 23 Dec 2013
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2013-6449, GHSA-h84w-39m4-37j6, MGASA-2014-0008

## What is CVE-2013-6449?

CVE-2013-6449 is a medium-severity vulnerability in Openssl Openssl, published on 23 Dec 2013. 

### Official description

The ssl_get_algorithm2 function in ssl/s3_lib.c in OpenSSL before 1.0.2 obtains a certain version number from an incorrect data structure, which allows remote attackers to cause a denial of service (daemon crash) via crafted traffic from a TLS 1.2 client.

Weakness: CWE-310

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

It affects 1 product.


Products: Openssl Openssl.

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

Upgrade to a fixed version.

## Is CVE-2013-6449 being exploited?

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

## 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-6449 and fix it if it is affected.

What it is: CVE-2013-6449 is a medium-severity vulnerability in Openssl Openssl, published on 23 Dec 2013. 
Exploitation: There is no known exploitation of CVE-2013-6449 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-6449/ (Markdown: https://insights.sbomify.com/CVE-2013-6449/index.md)
```

## Sources

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

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