# CVE-2014-2653: Security feature bypass in n/a

> A malicious SSH server can bypass SSHFP DNS RR verification in the OpenSSH client by presenting an unacceptable HostCertificate.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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:** 27 Mar 2014
- **Updated:** 28 May 2026
- **Also known as:** DEBIAN-CVE-2014-2653, GHSA-52r2-7jx8-c8gc, MGASA-2014-0166

## What is CVE-2014-2653?

CVE-2014-2653 is a medium-severity vulnerability in OpenSSH, published on 27 Mar 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The verify_host_key function in sshconnect.c in the client in OpenSSH 6.6 and earlier allows remote servers to trigger the skipping of SSHFP DNS RR checking by presenting an unacceptable HostCertificate.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: OpenSSH.

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

Apply the vendor's patch.

## Is CVE-2014-2653 being exploited?

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

## Other vulnerabilities in OpenSSH

- [CVE-2003-0786](https://insights.sbomify.com/CVE-2003-0786/): Auth bypass in n/a (critical 10.0)
- [CVE-2003-0693](https://insights.sbomify.com/CVE-2003-0693/): Memory corruption in n/a (critical 10.0)
- [CVE-2002-0640](https://insights.sbomify.com/CVE-2002-0640/): Memory corruption in n/a (critical 10.0)
- [CVE-2001-0144](https://insights.sbomify.com/CVE-2001-0144/): Integer overflow in n/a (critical 10.0)
- [CVE-2000-0999](https://insights.sbomify.com/CVE-2000-0999/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-2653 and fix it if it is affected.

What it is: CVE-2014-2653 is a medium-severity vulnerability in OpenSSH, published on 27 Mar 2014. 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-2014-2653 in the wild and no public exploit code.

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

## Sources

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

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