dbcve.org
Dropbear SshApplication · Dropbear Ssh Project

CVE-2007-1099

HIGH · 7.5 CVSS v2.0 Published 2007-02-26
Fix available
A fix is available. Upgrade to 0.49 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The dbclient component in Dropbear SSH client versions prior to 0.49 fails to adequately alert users when it detects a hostkey mismatch. This vulnerability could enable man-in-the-middle attacks since users are not warned of potential key changes that might indicate their connection is being intercepted.

MitigationUpgrade Dropbear SSH client to version 0.49 or later to ensure proper hostkey mismatch warnings are displayed to users.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Dropbear SshApplication
Affected:< 0.49

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Dropbear dbclient is installed
    Run 'which dbclient' or check for /usr/bin/dbclient, /usr/local/bin/dbclient, or similar paths where SSH clients are commonly installed
    Affected if dbclient binary is found on the system
  2. Determine installed Dropbear client version
    Run 'dbclient --version' or 'dbclient -V' to display the version number
    Affected if The version displayed is less than 0.49 (for example, 0.48, 0.47, etc.)
  3. Confirm version format matches affected range
    Compare your displayed version number against the 0.49 threshold - versions are typically shown as numbers like 0.48, 0.47, 0.46
    Affected if The version number is a release prior to 0.49 (versions before the 0.49 release)
  4. Check for alternative version reporting
    If version flag does not work, try 'dbclient -h' for help output that may contain version, or check package management info with 'dpkg -l dropbear' or 'rpm -qi dropbear'
    Affected if Package info shows version < 0.49

The system is affected if Dropbear dbclient is installed and its version is any release prior to 0.49, as those versions do not adequately warn users of hostkey mismatches.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 0.49 or later
Fixed in 0.49
Interim mitigation

Upgrade Dropbear SSH client to version 0.49 or later to ensure proper hostkey mismatch warnings are displayed to users.

Fix this in Dropbear Ssh Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-1099 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2007-1099 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data