CVE-2016-0798: High severity openssl vulnerability

Published Mar 3, 2016

Updated

Memory leak in the SRPVBASEgetbyuser implementation in OpenSSL 1.0.1 before 1.0.1s and 1.0.2 before 1.0.2g allows remote attackers to cause a denial of service (memory consumption) by providing an invalid username in a connection attempt, related to apps/sserver.c and crypto/srp/srpvfy.c.

Affected Software

32 affected components

OpenSSL OpenSSL=1.0.1

OpenSSL OpenSSL=1.0.1-beta1

OpenSSL OpenSSL=1.0.1-beta2

OpenSSL OpenSSL=1.0.1-beta3

OpenSSL OpenSSL=1.0.1a

OpenSSL OpenSSL=1.0.1b

OpenSSL OpenSSL=1.0.1c

OpenSSL OpenSSL=1.0.1d

OpenSSL OpenSSL=1.0.1e

OpenSSL OpenSSL=1.0.1f

OpenSSL OpenSSL=1.0.1g

OpenSSL OpenSSL=1.0.1h

OpenSSL OpenSSL=1.0.1i

OpenSSL OpenSSL=1.0.1j

OpenSSL OpenSSL=1.0.1k

OpenSSL OpenSSL=1.0.1l

OpenSSL OpenSSL=1.0.1m

OpenSSL OpenSSL=1.0.1n

OpenSSL OpenSSL=1.0.1o

OpenSSL OpenSSL=1.0.1p

OpenSSL OpenSSL=1.0.1q

OpenSSL OpenSSL=1.0.1r

OpenSSL OpenSSL=1.0.2

OpenSSL OpenSSL=1.0.2-beta1

OpenSSL OpenSSL=1.0.2-beta2

OpenSSL OpenSSL=1.0.2-beta3

OpenSSL OpenSSL=1.0.2a

OpenSSL OpenSSL=1.0.2b

OpenSSL OpenSSL=1.0.2c

OpenSSL OpenSSL=1.0.2d

OpenSSL OpenSSL=1.0.2e

OpenSSL OpenSSL=1.0.2f

Event History

Mar 3, 2016

CVE Published

via MITRE·12:00 AM

Data Sourced

via MITRE·12:00 AM

Description

Frequently Asked Questions

What is the severity of CVE-2016-0798?

CVE-2016-0798 has a medium severity rating as it can lead to a denial of service through memory consumption.

How do I fix CVE-2016-0798?

To fix CVE-2016-0798, upgrade OpenSSL to version 1.0.1s or 1.0.2g or later.

Who is affected by CVE-2016-0798?

CVE-2016-0798 affects users of OpenSSL versions 1.0.1 prior to 1.0.1s and 1.0.2 prior to 1.0.2g.

What causes CVE-2016-0798?

CVE-2016-0798 is caused by a memory leak in the SRP_VBASE_get_by_user implementation when an invalid username is provided.

Can CVE-2016-0798 be exploited remotely?

Yes, CVE-2016-0798 can be exploited by remote attackers to cause denial of service.