Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1619063 - (CVE-2018-15473) CVE-2018-15473 openssh: User enumeration via malformed packets in authentication requests
CVE-2018-15473 openssh: User enumeration via malformed packets in authenticat...
Status: NEW
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
impact=low,public=20180816,reported=2...
: Security
Depends On: 1619065 1619079 1619064
Blocks: 1619067
  Show dependency treegraph
 
Reported: 2018-08-19 21:20 EDT by Sam Fowler
Modified: 2018-10-25 19:16 EDT (History)
22 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Sam Fowler 2018-08-19 21:20:12 EDT
OpenSSH through 7.7 is prone to a user enumeration vulnerability due to not delaying bailout for an invalid authenticating user until after the packet containing the request has been fully parsed, related to auth2-gss.c, auth2-hostbased.c, and auth2-pubkey.c.


Upstream Patch:

https://github.com/openbsd/src/commit/779974d35b4859c07bc3cb8a12c74b43b0a7d1e0


Reference:

http://www.openwall.com/lists/oss-security/2018/08/15/5
Comment 1 Sam Fowler 2018-08-19 21:21:00 EDT
Created openssh tracking bugs for this issue:

Affects: fedora-all [bug 1619064]
Comment 13 Doran Moppert 2018-10-01 22:10:41 EDT
Statement:

Red Hat Product Security has rated this issue as having Low severity. An attacker could use this flaw to determine whether given usernames exist or not on the server, but no further information is disclosed and there is no availability or integrity impact. A future update may address this issue.
Comment 14 Doran Moppert 2018-10-01 22:10:55 EDT
Mitigation:

Configuring your firewall to limit the origin and/or rate of incoming ssh connections (using the netfilter xt_recent module) will limit the impact of this attack, as it requires a new TCP connection for each username tested. This configuration also provides some protection against brute-force attacks on SSH passwords or keys.

Note You need to log in before you can comment on or make changes to this bug.