forked from rpms/glibc
265 lines
11 KiB
Diff
265 lines
11 KiB
Diff
|
commit 6d1e3fb07b45e2e31e469b16cf21b24bccf8914c
|
||
|
|
Author: Andreas K. Hüttel <dilfridge@gentoo.org>
|
||
|
|
Date: Wed Jan 31 02:12:43 2024 +0100
|
||
|
|
|
||
|
|
Replace advisories directory
|
||
|
|
|
||
|
|
Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>
|
||
|
|
|
||
|
|
diff --git a/ADVISORIES b/ADVISORIES
|
||
|
|
new file mode 100644
|
||
|
|
index 0000000000000000..d4e33f2df3d74cd8
|
||
|
|
--- /dev/null
|
||
|
|
+++ b/ADVISORIES
|
||
|
|
@@ -0,0 +1,2 @@
|
||
|
|
+For the GNU C Library Security Advisories, see the git master branch:
|
||
|
|
+https://sourceware.org/git/?p=glibc.git;a=tree;f=advisories;hb=HEAD
|
||
|
|
diff --git a/advisories/GLIBC-SA-2023-0001 b/advisories/GLIBC-SA-2023-0001
|
||
|
|
deleted file mode 100644
|
||
|
|
index 3d19c91b6a676ffd..0000000000000000
|
||
|
|
--- a/advisories/GLIBC-SA-2023-0001
|
||
|
|
+++ /dev/null
|
||
|
|
@@ -1,14 +0,0 @@
|
||
|
|
-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)
|
||
|
|
diff --git a/advisories/GLIBC-SA-2023-0002 b/advisories/GLIBC-SA-2023-0002
|
||
|
|
deleted file mode 100644
|
||
|
|
index 5122669a6451f803..0000000000000000
|
||
|
|
--- a/advisories/GLIBC-SA-2023-0002
|
||
|
|
+++ /dev/null
|
||
|
|
@@ -1,15 +0,0 @@
|
||
|
|
-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)
|
||
|
|
diff --git a/advisories/GLIBC-SA-2023-0003 b/advisories/GLIBC-SA-2023-0003
|
||
|
|
deleted file mode 100644
|
||
|
|
index d3aef803480bc298..0000000000000000
|
||
|
|
--- a/advisories/GLIBC-SA-2023-0003
|
||
|
|
+++ /dev/null
|
||
|
|
@@ -1,15 +0,0 @@
|
||
|
|
-getaddrinfo: Potential use-after-free
|
||
|
|
-
|
||
|
|
-When an NSS plugin only implements the _gethostbyname2_r and
|
||
|
|
-_getcanonname_r callbacks, getaddrinfo could use memory that was freed
|
||
|
|
-during buffer resizing, potentially causing a crash or read or write to
|
||
|
|
-arbitrary memory.
|
||
|
|
-
|
||
|
|
-CVE-Id: CVE-2023-4806
|
||
|
|
-Public-Date: 2023-09-12
|
||
|
|
-Fix-Commit: 973fe93a5675c42798b2161c6f29c01b0e243994 (2.39)
|
||
|
|
-Fix-Commit: e09ee267c03e3150c2c9ba28625ab130705a485e (2.34-420)
|
||
|
|
-Fix-Commit: e3ccb230a961b4797510e6a1f5f21fd9021853e7 (2.35-270)
|
||
|
|
-Fix-Commit: a9728f798ec7f05454c95637ee6581afaa9b487d (2.36-115)
|
||
|
|
-Fix-Commit: 6529a7466c935f36e9006b854d6f4e1d4876f942 (2.37-39)
|
||
|
|
-Fix-Commit: 00ae4f10b504bc4564e9f22f00907093f1ab9338 (2.38-20)
|
||
|
|
diff --git a/advisories/GLIBC-SA-2023-0004 b/advisories/GLIBC-SA-2023-0004
|
||
|
|
deleted file mode 100644
|
||
|
|
index 5286a7aa545cd942..0000000000000000
|
||
|
|
--- a/advisories/GLIBC-SA-2023-0004
|
||
|
|
+++ /dev/null
|
||
|
|
@@ -1,16 +0,0 @@
|
||
|
|
-tunables: local privilege escalation through buffer overflow
|
||
|
|
-
|
||
|
|
-If a tunable of the form NAME=NAME=VAL is passed in the environment of a
|
||
|
|
-setuid program and NAME is valid, it may result in a buffer overflow,
|
||
|
|
-which could be exploited to achieve escalated privileges. This flaw was
|
||
|
|
-introduced in glibc 2.34.
|
||
|
|
-
|
||
|
|
-CVE-Id: CVE-2023-4911
|
||
|
|
-Public-Date: 2023-10-03
|
||
|
|
-Vulnerable-Commit: 2ed18c5b534d9e92fc006202a5af0df6b72e7aca (2.34)
|
||
|
|
-Fix-Commit: 1056e5b4c3f2d90ed2b4a55f96add28da2f4c8fa (2.39)
|
||
|
|
-Fix-Commit: dcc367f148bc92e7f3778a125f7a416b093964d9 (2.34-423)
|
||
|
|
-Fix-Commit: c84018a05aec80f5ee6f682db0da1130b0196aef (2.35-274)
|
||
|
|
-Fix-Commit: 22955ad85186ee05834e47e665056148ca07699c (2.36-118)
|
||
|
|
-Fix-Commit: b4e23c75aea756b4bddc4abcf27a1c6dca8b6bd3 (2.37-45)
|
||
|
|
-Fix-Commit: 750a45a783906a19591fb8ff6b7841470f1f5701 (2.38-27)
|
||
|
|
diff --git a/advisories/GLIBC-SA-2023-0005 b/advisories/GLIBC-SA-2023-0005
|
||
|
|
deleted file mode 100644
|
||
|
|
index cc4eb90b8283dc14..0000000000000000
|
||
|
|
--- a/advisories/GLIBC-SA-2023-0005
|
||
|
|
+++ /dev/null
|
||
|
|
@@ -1,18 +0,0 @@
|
||
|
|
-getaddrinfo: DoS due to memory leak
|
||
|
|
-
|
||
|
|
-The fix for CVE-2023-4806 introduced a memory leak when an application
|
||
|
|
-calls getaddrinfo for AF_INET6 with AI_CANONNAME, AI_ALL and AI_V4MAPPED
|
||
|
|
-flags set.
|
||
|
|
-
|
||
|
|
-CVE-Id: CVE-2023-5156
|
||
|
|
-Public-Date: 2023-09-25
|
||
|
|
-Vulnerable-Commit: e09ee267c03e3150c2c9ba28625ab130705a485e (2.34-420)
|
||
|
|
-Vulnerable-Commit: e3ccb230a961b4797510e6a1f5f21fd9021853e7 (2.35-270)
|
||
|
|
-Vulnerable-Commit: a9728f798ec7f05454c95637ee6581afaa9b487d (2.36-115)
|
||
|
|
-Vulnerable-Commit: 6529a7466c935f36e9006b854d6f4e1d4876f942 (2.37-39)
|
||
|
|
-Vulnerable-Commit: 00ae4f10b504bc4564e9f22f00907093f1ab9338 (2.38-20)
|
||
|
|
-Fix-Commit: 8006457ab7e1cd556b919f477348a96fe88f2e49 (2.34-421)
|
||
|
|
-Fix-Commit: 17092c0311f954e6f3c010f73ce3a78c24ac279a (2.35-272)
|
||
|
|
-Fix-Commit: 856bac55f98dc840e7c27cfa82262b933385de90 (2.36-116)
|
||
|
|
-Fix-Commit: 4473d1b87d04b25cdd0e0354814eeaa421328268 (2.37-42)
|
||
|
|
-Fix-Commit: 5ee59ca371b99984232d7584fe2b1a758b4421d3 (2.38-24)
|
||
|
|
diff --git a/advisories/GLIBC-SA-2024-0001 b/advisories/GLIBC-SA-2024-0001
|
||
|
|
deleted file mode 100644
|
||
|
|
index 28931c75ae018cc3..0000000000000000
|
||
|
|
--- a/advisories/GLIBC-SA-2024-0001
|
||
|
|
+++ /dev/null
|
||
|
|
@@ -1,15 +0,0 @@
|
||
|
|
-syslog: Heap buffer overflow in __vsyslog_internal
|
||
|
|
-
|
||
|
|
-__vsyslog_internal did not handle a case where printing a SYSLOG_HEADER
|
||
|
|
-containing a long program name failed to update the required buffer
|
||
|
|
-size, leading to the allocation and overflow of a too-small buffer on
|
||
|
|
-the heap.
|
||
|
|
-
|
||
|
|
-CVE-Id: CVE-2023-6246
|
||
|
|
-Public-Date: 2024-01-30
|
||
|
|
-Vulnerable-Commit: 52a5be0df411ef3ff45c10c7c308cb92993d15b1 (2.37)
|
||
|
|
-Fix-Commit: 6bd0e4efcc78f3c0115e5ea9739a1642807450da (2.39)
|
||
|
|
-Fix-Commit: 23514c72b780f3da097ecf33a793b7ba9c2070d2 (2.38-42)
|
||
|
|
-Fix-Commit: 97a4292aa4a2642e251472b878d0ec4c46a0e59a (2.37-57)
|
||
|
|
-Vulnerable-Commit: b0e7888d1fa2dbd2d9e1645ec8c796abf78880b9 (2.36-16)
|
||
|
|
-Fix-Commit: d1a83b6767f68b3cb5b4b4ea2617254acd040c82 (2.36-126)
|
||
|
|
diff --git a/advisories/GLIBC-SA-2024-0002 b/advisories/GLIBC-SA-2024-0002
|
||
|
|
deleted file mode 100644
|
||
|
|
index 940bfcf2fcb76050..0000000000000000
|
||
|
|
--- a/advisories/GLIBC-SA-2024-0002
|
||
|
|
+++ /dev/null
|
||
|
|
@@ -1,15 +0,0 @@
|
||
|
|
-syslog: Heap buffer overflow in __vsyslog_internal
|
||
|
|
-
|
||
|
|
-__vsyslog_internal used the return value of snprintf/vsnprintf to
|
||
|
|
-calculate buffer sizes for memory allocation. If these functions (for
|
||
|
|
-any reason) failed and returned -1, the resulting buffer would be too
|
||
|
|
-small to hold output.
|
||
|
|
-
|
||
|
|
-CVE-Id: CVE-2023-6779
|
||
|
|
-Public-Date: 2024-01-30
|
||
|
|
-Vulnerable-Commit: 52a5be0df411ef3ff45c10c7c308cb92993d15b1 (2.37)
|
||
|
|
-Fix-Commit: 7e5a0c286da33159d47d0122007aac016f3e02cd (2.39)
|
||
|
|
-Fix-Commit: d0338312aace5bbfef85e03055e1212dd0e49578 (2.38-43)
|
||
|
|
-Fix-Commit: 67062eccd9a65d7fda9976a56aeaaf6c25a80214 (2.37-58)
|
||
|
|
-Vulnerable-Commit: b0e7888d1fa2dbd2d9e1645ec8c796abf78880b9 (2.36-16)
|
||
|
|
-Fix-Commit: 2bc9d7c002bdac38b5c2a3f11b78e309d7765b83 (2.36-127)
|
||
|
|
diff --git a/advisories/GLIBC-SA-2024-0003 b/advisories/GLIBC-SA-2024-0003
|
||
|
|
deleted file mode 100644
|
||
|
|
index b43a5150ab1b0cc4..0000000000000000
|
||
|
|
--- a/advisories/GLIBC-SA-2024-0003
|
||
|
|
+++ /dev/null
|
||
|
|
@@ -1,13 +0,0 @@
|
||
|
|
-syslog: Integer overflow in __vsyslog_internal
|
||
|
|
-
|
||
|
|
-__vsyslog_internal calculated a buffer size by adding two integers, but
|
||
|
|
-did not first check if the addition would overflow.
|
||
|
|
-
|
||
|
|
-CVE-Id: CVE-2023-6780
|
||
|
|
-Public-Date: 2024-01-30
|
||
|
|
-Vulnerable-Commit: 52a5be0df411ef3ff45c10c7c308cb92993d15b1 (2.37)
|
||
|
|
-Fix-Commit: ddf542da94caf97ff43cc2875c88749880b7259b (2.39)
|
||
|
|
-Fix-Commit: d37c2b20a4787463d192b32041c3406c2bd91de0 (2.38-44)
|
||
|
|
-Fix-Commit: 2b58cba076e912961ceaa5fa58588e4b10f791c0 (2.37-59)
|
||
|
|
-Vulnerable-Commit: b0e7888d1fa2dbd2d9e1645ec8c796abf78880b9 (2.36-16)
|
||
|
|
-Fix-Commit: b9b7d6a27aa0632f334352fa400771115b3c69b7 (2.36-128)
|
||
|
|
diff --git a/advisories/README b/advisories/README
|
||
|
|
deleted file mode 100644
|
||
|
|
index 94e68b1350bbad0e..0000000000000000
|
||
|
|
--- a/advisories/README
|
||
|
|
+++ /dev/null
|
||
|
|
@@ -1,73 +0,0 @@
|
||
|
|
-GNU C Library Security Advisory Format
|
||
|
|
-======================================
|
||
|
|
-
|
||
|
|
-Security advisories in this directory follow a simple git commit log
|
||
|
|
-format, with a heading and free-format description augmented with tags
|
||
|
|
-to allow parsing key information. References to code changes are
|
||
|
|
-specific to the glibc repository and follow a specific format:
|
||
|
|
-
|
||
|
|
- Tag-name: <commit-ref> (release-version)
|
||
|
|
-
|
||
|
|
-The <commit-ref> indicates a specific commit in the repository. The
|
||
|
|
-release-version indicates the publicly consumable release in which this
|
||
|
|
-commit is known to exist. The release-version is derived from the
|
||
|
|
-git-describe format, (i.e. stripped out from glibc-2.34.NNN-gxxxx) and
|
||
|
|
-is of the form 2.34-NNN. If the -NNN suffix is absent, it means that
|
||
|
|
-the change is in that release tarball, otherwise the change is on the
|
||
|
|
-release/2.YY/master branch and not in any released tarball.
|
||
|
|
-
|
||
|
|
-The following tags are currently being used:
|
||
|
|
-
|
||
|
|
-CVE-Id:
|
||
|
|
-This is the CVE-Id assigned under the CVE Program
|
||
|
|
-(https://www.cve.org/).
|
||
|
|
-
|
||
|
|
-Public-Date:
|
||
|
|
-The date this issue became publicly known.
|
||
|
|
-
|
||
|
|
-Vulnerable-Commit:
|
||
|
|
-The commit that introduced this vulnerability. There could be multiple
|
||
|
|
-entries, one for each release branch in the glibc repository; the
|
||
|
|
-release-version portion of this tag should tell you which branch this is
|
||
|
|
-on.
|
||
|
|
-
|
||
|
|
-Fix-Commit:
|
||
|
|
-The commit that fixed this vulnerability. There could be multiple
|
||
|
|
-entries for each release branch in the glibc repository, indicating that
|
||
|
|
-all of those commits contributed to fixing that issue in each of those
|
||
|
|
-branches.
|
||
|
|
-
|
||
|
|
-Adding an Advisory
|
||
|
|
-------------------
|
||
|
|
-
|
||
|
|
-An advisory for a CVE needs to be added on the master branch in two steps:
|
||
|
|
-
|
||
|
|
-1. Add the text of the advisory without any Fix-Commit tags along with
|
||
|
|
- the fix for the CVE. Add the Vulnerable-Commit tag, if applicable.
|
||
|
|
- The advisories directory does not exist in release branches, so keep
|
||
|
|
- the advisory text commit distinct from the code changes, to ease
|
||
|
|
- backports. Ask for the GLIBC-SA advisory number from the security
|
||
|
|
- team.
|
||
|
|
-
|
||
|
|
-2. Finish all backports on release branches and then back on the msater
|
||
|
|
- branch, add all commit refs to the advisory using the Fix-Commit
|
||
|
|
- tags. Don't bother adding the release-version subscript since the
|
||
|
|
- next step will overwrite it.
|
||
|
|
-
|
||
|
|
-3. Run the process-advisories.sh script in the scripts directory on the
|
||
|
|
- advisory:
|
||
|
|
-
|
||
|
|
- scripts/process-advisories.sh update GLIBC-SA-YYYY-NNNN
|
||
|
|
-
|
||
|
|
- (replace YYYY-NNNN with the actual advisory number).
|
||
|
|
-
|
||
|
|
-4. Verify the updated advisory and push the result.
|
||
|
|
-
|
||
|
|
-Getting a NEWS snippet from advisories
|
||
|
|
---------------------------------------
|
||
|
|
-
|
||
|
|
-Run:
|
||
|
|
-
|
||
|
|
- scripts/process-advisories.sh news
|
||
|
|
-
|
||
|
|
-and copy the content into the NEWS file.
|