Bug 1153537 - (CVE-2019-16905) VUL-1: CVE-2019-16905: openssh: when compiled with an experimental key type, has a pre-authentication integer overflow if a client or server is configured to use a crafted XMSS key
(CVE-2019-16905)
VUL-1: CVE-2019-16905: openssh: when compiled with an experimental key type, ...
Status: RESOLVED INVALID
Classification: Novell Products
Product: SUSE Security Incidents
Classification: Novell Products
Component: Incidents
unspecified
Other Other
: P5 - None : Minor
: ---
Assigned To: Hans Petter Jansson
Security Team bot
https://smash.suse.de/issue/244561/
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2019-10-10 08:03 UTC by Robert Frohl
Modified: 2019-10-10 08:11 UTC (History)
1 user (show)

See Also:
Found By: Security Response Team
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Frohl 2019-10-10 08:03:39 UTC
CVE-2019-16905

OpenSSH 7.7 through 7.9 and 8.x before 8.1, when compiled with an experimental
key type, has a pre-authentication integer overflow if a client or server is
configured to use a crafted XMSS key. This leads to memory corruption and remote
code execution because of an error in the XMSS key parsing algorithm. NOTE: the
XMSS implementation is considered experimental in all released OpenSSH versions,
and there is no supported way to enable it when building portable OpenSSH.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-16905
https://www.openwall.com/lists/oss-security/2019/10/09/1
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16905
https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.bin/ssh/sshkey-xmss.c.diff?r1=1.5&r2=1.6&f=h
https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.bin/ssh/sshkey-xmss.c
https://www.openssh.com/releasenotes.html
Comment 1 Robert Frohl 2019-10-10 08:11:11 UTC
Only codestreams where we could be affected is SUSE:SLE-15-SP1:Update and openSUSE. But the algorithm was not enabled there. 

Which means we are not affected anywhere as far as I can tell.