Security Advisory

CVE-2018-15599: Dropbear SSH Username Enumeration

Last updated:
  • CVE-2018-15599

CVE-2018-15599 is a username enumeration flaw in the Dropbear SSH server through 2018.76: the server handled authentication requests for valid and invalid usernames differently, so a remote client could find out which accounts exist on a device. NVD scores it 5.3. Dropbear 2019.77 fixes it, and Debian, OpenWrt and Buildroot backported the patch in August 2018.

Vulnerability summary

CVSS base score

5.3

Medium severity

EPSS score (FIRST)

2.7%

Probability of exploitation in the wild in the next 30 days

CISA KEV catalog

No

Not listed

Published

Vulnerability ID: CVE-2018-15599 · Source: NVD

Affected components

ComponentCPEVersion range
Dropbear SSH servercpe:2.3:a:dropbear_ssh_project:dropbear_ssh:*:*:*:*:*:*:*:*Through 2018.76 per NVD (no lower bound); reporter tested back to 2013.58; fixed in 2019.77 (Dropbear CHANGES), upstream commit 52adbb34 of 2018-08-23
Debian dropbear source packagecpe:2.3:o:debian:debian_linux:8.0:*:*:*:*:*:*:*jessie fixed in 2014.65-1+deb8u3 (DLA-1476-1); stretch fixed in 2016.74-5+deb9u1; unstable fixed in 2018.76-4 (Debian security tracker)
OpenWrt package/network/services/dropbear—Patch added 2018-08-24 (master and openwrt-18.06, commit 8bb9d053); first 18.06 release with it is 18.06.2; 2026.94 in main as of 2026-11-19
Buildroot package/dropbear—Patch added 2018-08-26 (commit 4a3b0ba3); in Buildroot 2018.08 and 2018.02.5; 2026.94 in master as of 2026-11-19

What does this mean for affected devices?

CVE-2018-15599 is a username enumeration flaw in the Dropbear SSH server. The NVD description places it in recv_msg_userauth_request in svr-auth.c, in Dropbear through 2018.76: whether a username exists changes how the server handles the rest of an SSH_MSG_USERAUTH_REQUEST message, so a remote client can tell valid accounts from invalid ones. NVD's Primary score is 5.3, CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, with CWE-200 (information exposure). MITRE, the CNA, published the record on 2018-08-21 without a score (NVD, CVE record).

How does the username check leak?

Matthijs Koot of Secura reported on the Dropbear mailing list on 2018-08-20 that the OpenSSH enumeration issue (CVE-2018-15473) also worked against Dropbear 2018.76 and earlier, back to at least 2013.58, and that the public OpenSSH proof-of-concept script worked unchanged. In the public key branch, an invalid user got an immediate failure with no delay, while a valid user went on to key checking. He added that the same test reveals service accounts, so an attacker can probe for default users that hint at installed software. Maintainer Matt Johnston confirmed that probably all versions were affected and noted that the flaw lets someone learn whether a username exists, but "by itself it doesn't allow exploitation of a server". On a device, the risk is that it confirms names such as admin or root before a password-guessing run.

Which Dropbear versions and firmware builds are affected?

The upstream fix is the commit "Wait to fail invalid usernames" of 2018-08-23: password, PAM and public key handlers now read the full request before failing an invalid user. The Dropbear CHANGES file lists it in 2019.77 (23 March 2019), together with a more consistent failure delay. Build systems backported the patch months earlier:

  • Debian fixed jessie in 2014.65-1+deb8u3 (DLA-1476-1), stretch in 2016.74-5+deb9u1 and unstable in 2018.76-4 (Debian security tracker).
  • OpenWrt added the upstream patch on 2018-08-24 in master and in the openwrt-18.06 branch (commit 8bb9d053); the first 18.06 release with it is 18.06.2, so 18.06.1 and earlier images are affected.
  • Buildroot added the patch on 2018-08-26 (commit 4a3b0ba3); it is in Buildroot 2018.08 and, as a backport, 2018.02.5.

As of 2026-11-19 both OpenWrt and Buildroot package Dropbear 2026.94. NVD's CPE range is "through 2018.76" with no lower bound, so a scanner flags every older version string, including vendor builds that carry the backport.

How do you fix or mitigate CVE-2018-15599?

Ship Dropbear 2019.77 or later, or confirm that the vendor or build system applied the "Wait to fail invalid usernames" patch. If a rebuild has to wait, limit who can reach the SSH port, keep the account list short, and make sure guessed names do not lead anywhere: disable password login where keys are possible and remove default accounts. Our Dropbear SSH vulnerabilities guide explains how to read the Dropbear version from a firmware image, and the authentication bypass fix guide covers hardening login paths. The same older builds often also carry the format string bug CVE-2016-7406, the listener double free CVE-2017-9078 and the client flaw CVE-2021-36369.

Is CVE-2018-15599 exploited?

CVE-2018-15599 is not in the CISA KEV catalog as of 2026-11-19 (catalog version 2026.11.18, 1,786 entries). FIRST EPSS gives it 0.02686, the 86.1st percentile, in the 2026-11-18 dataset (CISA KEV, FIRST EPSS).

How to fix this class of issueNo dedicated SoftWSP guide covers this weakness class; the fix is usually the vendor patch or firmware update referenced above. Our related guide explains how to plan and verify it: NIST SP 800-40 Rev. 4: enterprise patch management planning, explained.

Evidence

  • NVD: recv_msg_userauth_request in svr-auth.c in Dropbear through 2018.76 is prone to user enumeration because username validity affects how SSH_MSG_USERAUTH fields are handled; NVD Primary CVSS v3.0 5.3 AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N; CWE-200; CPE dropbear_ssh up to and including 2018.76 and debian_linux 8.0; published 2018-08-21. Read 2026-11-19. — NVD
  • CVE.org: state PUBLISHED, CNA MITRE, published 2018-08-21, no CNA CVSS score. Read 2026-11-19. — CVE.org
  • Dropbear CHANGES: 2019.77 (23 March 2019) changes handling of failed authentication to avoid disclosing valid usernames, CVE-2018-15599, and makes the failure delay more consistent. Read 2026-11-19. — Dropbear
  • Dropbear mailing list, 2018-08-20: Matthijs Koot (Secura) reports the OpenSSH user enumeration issue also exists in Dropbear 2018.76 and earlier, back to at least 2013.58; invalid users got an immediate public key failure; the OpenSSH PoC works unchanged and can reveal service accounts. Read 2026-11-19. — Dropbear mailing list
  • Dropbear mailing list, 2018-08-20: maintainer Matt Johnston confirms probably all versions are affected; it reveals whether a username exists but by itself does not allow exploitation of a server. Read 2026-11-19. — Dropbear mailing list
  • Upstream commit 52adbb34 'Wait to fail invalid usernames' (2018-08-23) passes valid_user into the password, PAM and public key handlers so they read the request before failing invalid users. Read 2026-11-19. — Dropbear (GitHub mirror)
  • Debian DLA-1476-1 (2018-08-27): dropbear fixed in 2014.65-1+deb8u3 for Debian 8 jessie. Read 2026-11-19. — Debian LTS
  • Debian security tracker: fixed in jessie 2014.65-1+deb8u3 (DLA-1476-1), stretch 2016.74-5+deb9u1, unstable 2018.76-4; bookworm, trixie and sid listed fixed. Read 2026-11-19. — Debian security tracker
  • OpenWrt commit 8bb9d053 (2018-08-24, openwrt-18.06) backports the upstream fix as 020-Wait-to-fail-invalid-usernames.patch; contained in tag v18.06.2, not in v18.06.1; main packages Dropbear 2026.94 as of 2026-11-19. Read 2026-11-19. — OpenWrt
  • Buildroot commit 4a3b0ba3 (2018-08-26) adds the upstream security fix for CVE-2018-15599; contained in 2018.08; backport 6e2dd454 contained in 2018.02.5; master packages Dropbear 2026.94 as of 2026-11-19. Read 2026-11-19. — Buildroot

Related advisories

Sources

  1. NVD
  2. CVE.org record CVE-2018-15599 (CNA: MITRE)
  3. Dropbear CHANGES file
  4. Dropbear mailing list: User enumeration in Dropbear 2018.76 and earlier (report, 2018-08-20)
  5. Dropbear mailing list: maintainer reply (2018-08-20)
  6. Dropbear commit 52adbb34: Wait to fail invalid usernames
  7. Debian LTS: DLA-1476-1 dropbear security update
  8. Debian security tracker: CVE-2018-15599
  9. OpenWrt commit 8bb9d053: dropbear backport of CVE-2018-15599 fix (openwrt-18.06)
  10. OpenWrt: package/network/services/dropbear Makefile (main)
  11. Buildroot commit 4a3b0ba3: dropbear security fix for CVE-2018-15599
  12. Buildroot: package/dropbear/dropbear.mk (master)
  13. CISA KEV
  14. FIRST EPSS

Frequently asked questions

Which Dropbear version fixes CVE-2018-15599?

Dropbear 2019.77, released on 23 March 2019, and every later release. The fix itself is the upstream commit "Wait to fail invalid usernames" of 2018-08-23, which Debian (2014.65-1+deb8u3 for jessie, 2016.74-5+deb9u1 for stretch), OpenWrt 18.06.2 and Buildroot 2018.08 and 2018.02.5 carry as a backport (per the Dropbear CHANGES file, the Debian security tracker and the OpenWrt and Buildroot commits).

How can I reduce the risk of CVE-2018-15599 without rebuilding the firmware?

The flaw only reveals whether an account exists; the maintainer notes it does not by itself allow exploitation of a server. Limit network access to the SSH port, remove default or unused accounts, and prefer public key login over passwords so that a confirmed username does not help a guessing attack (per the Dropbear mailing list).

Why does a scanner flag my Dropbear build when the vendor says it is patched?

NVD's CPE covers every Dropbear version up to and including 2018.76 with no lower bound, and Debian, OpenWrt and Buildroot backported the fix without changing the version number, so a 2018.76 or older version string alone does not prove the device is affected (per NVD, the Debian security tracker and the OpenWrt and Buildroot commits).

How severe is CVE-2018-15599?

NVD scores it 5.3 (CVSS 3.0, AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) with CWE-200; MITRE, the CNA, published no score of its own. It is reachable by anyone who can connect to the SSH port, but it only discloses whether usernames exist (per NVD and CVE.org).

Is CVE-2018-15599 exploited in the wild?

It is not in the CISA KEV catalog as of 2026-11-19 (catalog version 2026.11.18). The public OpenSSH enumeration script works against Dropbear, according to the original report, and FIRST EPSS gives it 0.02686, the 86.1st percentile, in the 2026-11-18 dataset (per CISA KEV, the Dropbear mailing list and FIRST EPSS).