CVE-2015-5180

Published: 10 August 2015

res_query in libresolv in glibc before 2.25 allows remote attackers to cause a denial of service (NULL pointer dereference and process crash).

From the Ubuntu security team

Florian Weimer discovered a NULL pointer dereference in the DNS resolver of the GNU C Library. An attacker could use this to cause a denial of service.

Priority

Low

CVSS 3 base score: 7.5

Status

Package Release Status
eglibc
Launchpad, Ubuntu, Debian
Upstream Needed

Ubuntu 20.10 (Groovy Gorilla) Does not exist

Ubuntu 20.04 LTS (Focal Fossa) Does not exist

Ubuntu 18.04 LTS (Bionic Beaver) Does not exist

Ubuntu 16.04 LTS (Xenial Xerus) Does not exist

Ubuntu 14.04 ESM (Trusty Tahr) Ignored

glibc
Launchpad, Ubuntu, Debian
Upstream
Released (2.25)
Ubuntu 20.10 (Groovy Gorilla) Not vulnerable
(2.27-3ubuntu1)
Ubuntu 20.04 LTS (Focal Fossa) Not vulnerable
(2.27-3ubuntu1)
Ubuntu 18.04 LTS (Bionic Beaver) Not vulnerable
(2.27-3ubuntu1)
Ubuntu 16.04 LTS (Xenial Xerus) Ignored

Ubuntu 14.04 ESM (Trusty Tahr) Does not exist

Patches:
Upstream: https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=fc82b0a2dfe7dbd35671c10510a8da1043d746a5 (2.25)
Upstream: https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=b3b37f1a5559a7620e31c8053ed1b44f798f2b6d (2.24)

Notes

AuthorNote
tyhicks
See test case in the bug
no fix upstream as of 2016-09-09
sbeattie
patch committed upstream on 2016-12-31; renames symbol so
backporting may not be easy.
commit included in glibc 2.25 release
debian fixed this in unstable in 2.24-9
fixing this does indeed break the internal ABI between
libnss_dns and libresolv. We're backing out this change.
reverted from zesty in 2.24-9ubuntu2 by infinity.
For existing releases, DO NOT APPLY THIS PATCH due to ABI
breakage. Fix will come in to 17.10 when we get glibc-2.25 as we
do not guarantee ABI for libresolv internals across different glibc
releases, just for upgrades for same versions e.g. (2.24 -> 2.24)
REPEAT: DO NOT APPLY THIS PATCH (UNMODIFIED) IN A STABLE RELEASE
mdeslaur
marking this issue as ignored, as we will not be fixing this
in Ubuntu stable releases.

References

Bugs