glibc/advisories/GLIBC-SA-2023-0001

printf: incorrect output for integers with thousands separator and width field

When the printf family of functions is called with a format specifier
that uses an <apostrophe> (enable grouping) and a minimum width
specifier, the resulting output could be larger than reasonably expected
by a caller that computed a tight bound on the buffer size.  The
resulting larger than expected output could result in a buffer overflow
in the printf family of functions.

CVE-Id: CVE-2023-25139
Public-Date: 2023-02-02
Vulnerable-Commit: e88b9f0e5cc50cab57a299dc7efe1a4eb385161d (2.37)
Fix-Commit: c980549cc6a1c03c23cc2fe3e7b0fe626a0364b0 (2.38)
Fix-Commit: 07b9521fc6369d000216b96562ff7c0ed32a16c4 (2.37-4)
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			`printf: incorrect output for integers with thousands separator and width field`

			`When the printf family of functions is called with a format specifier`
			`that uses an <apostrophe> (enable grouping) and a minimum width`
			`specifier, the resulting output could be larger than reasonably expected`
			`by a caller that computed a tight bound on the buffer size. The`
			`resulting larger than expected output could result in a buffer overflow`
			`in the printf family of functions.`

			`CVE-Id: CVE-2023-25139`
			`Public-Date: 2023-02-02`
			`Vulnerable-Commit: e88b9f0e5cc50cab57a299dc7efe1a4eb385161d (2.37)`
			`Fix-Commit: c980549cc6a1c03c23cc2fe3e7b0fe626a0364b0 (2.38)`
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: 07b9521fc6369d000216b96562ff7c0ed32a16c4 (2.37-4)`