# CVE-2007-1099: Security feature bypass in n/a

> Insufficient hostkey mismatch warnings in Dropbear SSH client allow remote attackers to perform man-in-the-middle attacks.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **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:** 26 Feb 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-1099, GHSA-4qp5-f859-rjjf

## What is CVE-2007-1099?

CVE-2007-1099 is a high-severity vulnerability in n/a, published on 26 Feb 2007. 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

dbclient in Dropbear SSH client before 0.49 does not sufficiently warn the user when it detects a hostkey mismatch, which might allow remote attackers to conduct man-in-the-middle attacks.

## Which versions are affected by CVE-2007-1099?

It affects 1 product.


Products: Dropbear Ssh Project Dropbear Ssh.

## How do I fix CVE-2007-1099?

Upgrade to a fixed version.

## Is CVE-2007-1099 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-7406](https://insights.sbomify.com/CVE-2016-7406/): Code injection in n/a (critical 9.8)
- [CVE-2016-7407](https://insights.sbomify.com/CVE-2016-7407/): Code injection in n/a (critical 9.8)
- [CVE-2016-7408](https://insights.sbomify.com/CVE-2016-7408/): Command injection in n/a (high 8.8)
- [CVE-2020-36254](https://insights.sbomify.com/CVE-2020-36254/): Path traversal in n/a (high 8.1)
- [CVE-2004-2486](https://insights.sbomify.com/CVE-2004-2486/): Use after free in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-1099 and fix it if it is affected.

What it is: CVE-2007-1099 is a high-severity vulnerability in n/a, published on 26 Feb 2007. 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-2007-1099 in the wild and no public exploit code.

Affected product: n/a. 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-2007-1099/ (Markdown: https://insights.sbomify.com/CVE-2007-1099/index.md)
```

## Sources

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

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