# CVE-2014-3511: The ssl23_get_client_hello function in s23_srvr.c in OpenSSL 1.0.1 before 1.0.1i allows man-in-the-middle attackers to force the use of TLS


- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 13 Aug 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-3511, GHSA-xfjr-6mmm-7hc7, UBUNTU-CVE-2014-3511

## What is CVE-2014-3511?

CVE-2014-3511 is a medium-severity vulnerability in Openssl Openssl, published on 13 Aug 2014. 

### Official description

The ssl23_get_client_hello function in s23_srvr.c in OpenSSL 1.0.1 before 1.0.1i allows man-in-the-middle attackers to force the use of TLS 1.0 by triggering ClientHello message fragmentation in communication between a client and server that both support later TLS versions, related to a "protocol downgrade" issue.

## Which versions are affected by CVE-2014-3511?

It affects 1 product.


Products: Openssl Openssl.

## How do I fix CVE-2014-3511?

Upgrade to a fixed version.

## Is CVE-2014-3511 being exploited?

There is no known exploitation of CVE-2014-3511 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-2014-3511 and fix it if it is affected.

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

## Sources

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

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