glibc/advisories/GLIBC-SA-2023-0002

getaddrinfo: Stack read overflow in no-aaaa mode

If the system is configured in no-aaaa mode via /etc/resolv.conf,
getaddrinfo is called for the AF_UNSPEC address family, and a DNS
response is received over TCP that is larger than 2048 bytes,
getaddrinfo may potentially disclose stack contents via the returned
address data, or crash.

CVE-Id: CVE-2023-4527
Public-Date: 2023-09-12
Vulnerable-Commit: f282cdbe7f436c75864e5640a409a10485e9abb2 (2.36)
Fix-Commit: bd77dd7e73e3530203be1c52c8a29d08270cb25d (2.39)
Fix-Commit: 4ea972b7edd7e36610e8cde18bf7a8149d7bac4f (2.36-113)
Fix-Commit: b7529346025a130fee483d42178b5c118da971bb (2.37-38)
Fix-Commit: b25508dd774b617f99419bdc3cf2ace4560cd2d6 (2.38-19)
Move CVE information into advisories directory One of the requirements to becoming a CVE Numbering Authority (CNA) is to publish advisories. Do this by maintaining a file for each CVE fixed in the advisories directory in the source tree. Links to the advisories can then be shared as: https://sourceware.org/git/?p=glibc.git;a=blob_plain;f=advisories/GLIBC-SA-YYYY-NNNN The file format at the moment is rudimentary and derives from the git commit format, i.e. a subject line and a potentially multi-paragraph description and then tags to describe some meta information. This is a loose format at the moment and could change as we evolve this. Also add a script process-fixed-cves.sh that processes these advisories and generates a list to add to NEWS at release time. Signed-off-by: Siddhesh Poyarekar <siddhesh@sourceware.org> 2023-10-12 16:50:49 +00:00			`getaddrinfo: Stack read overflow in no-aaaa mode`

			`If the system is configured in no-aaaa mode via /etc/resolv.conf,`
			`getaddrinfo is called for the AF_UNSPEC address family, and a DNS`
			`response is received over TCP that is larger than 2048 bytes,`
			`getaddrinfo may potentially disclose stack contents via the returned`
			`address data, or crash.`

			`CVE-Id: CVE-2023-4527`
			`Public-Date: 2023-09-12`
			`Vulnerable-Commit: f282cdbe7f436c75864e5640a409a10485e9abb2 (2.36)`
			`Fix-Commit: bd77dd7e73e3530203be1c52c8a29d08270cb25d (2.39)`
Update advisory format and introduce some automation Simplify the advisory format by dropping the -Backport tags and instead stick to using just the -Commit tags. To identify backports, put a substring of git-describe into the release version in the brackets next to the commit ref. This way, it not only identifies that the fix (or regression) is on the release/2.YY/master branch, it also disambiguates regressions/fixes in the branch from those in the tarball. Add a README to make it easier for consumers to understand the format. Additionally, the Release wiki needs to be updated to inform the release manager to: 1. Generate a NEWS snipped from the advisories directory AND 2. on release/2.YY/master, replace the advisories directory with a text file pointing to the advisories directory in master so that we don't have to update multiple locations. Signed-off-by: Siddhesh Poyarekar <siddhesh@sourceware.org> Reviewed-by: Andreas K. Hüttel <dilfridge@gentoo.org> 2024-01-24 18:37:20 +00:00			`Fix-Commit: 4ea972b7edd7e36610e8cde18bf7a8149d7bac4f (2.36-113)`
			`Fix-Commit: b7529346025a130fee483d42178b5c118da971bb (2.37-38)`
			`Fix-Commit: b25508dd774b617f99419bdc3cf2ace4560cd2d6 (2.38-19)`