Bug 1215281 (CVE-2023-4806)

Summary:	VUL-0: CVE-2023-4806: glibc: potential use-after-free in getaddrinfo()
Product:	[Novell Products] SUSE Security Incidents	Reporter:	Cathy Hu <cathy.hu>
Component:	Incidents	Assignee:	Andreas Schwab <schwab>
Status:	RESOLVED FIXED	QA Contact:	Security Team bot <security-team>
Severity:	Normal
Priority:	P3 - Medium	CC:	security-team, stoyan.manolov
Version:	unspecified
Target Milestone:	---
Hardware:	Other
OS:	Other
URL:	https://smash.suse.de/issue/377994/
Whiteboard:	CVSSv3.1:SUSE:CVE-2023-4806:5.9:(AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H)
Found By:	Security Response Team	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Bug Depends on:	1215714
Bug Blocks:

Description Cathy Hu 2023-09-13 07:39:37 UTC

CVE-2023-4806

In an extremely rare situation, the getaddrinfo function in glibc may access memory that has already been freed, resulting in an application crash.

This issue is only exploitable when a NSS module implements only the _nss_*_gethostbyname2_r hook without implementing the _nss_*_gethostbyname3_r hook. There are no known modules that are implemented in this way.

In addition to that condition, the resolved name should return a large number of IPv6 as well as IPv4 and the call to the getaddrinfo function should have AF_INET6 with AI_CANONNAME, AI_ALL and AI_V4MAPPED as flags.

Reference:
https://sourceware.org/bugzilla/show_bug.cgi?id=30843

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4806
https://bugzilla.redhat.com/show_bug.cgi?id=2237782

Comment 1 Cathy Hu 2023-09-13 07:40:13 UTC

afaik no patch upstream yet

Comment 2 Cathy Hu 2023-09-18 08:51:52 UTC

Patch is upstream: https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=973fe93a5675c42798b2161c6f29c01b0e243994

Comment 3 OBSbugzilla Bot 2023-09-18 09:45:05 UTC

This is an autogenerated message for OBS integration:
This bug (1215281) was mentioned in
https://build.opensuse.org/request/show/1111922 Factory / glibc

Comment 5 Cathy Hu 2023-09-26 08:38:57 UTC

The fix for this CVE introduces a memory leak, which is tracked via CVE-2023-5156 bnc#1215714. Could you please fix both at the same time with a submit? Thanks!