aboutsummaryrefslogtreecommitdiff
path: root/advisories
AgeCommit message (Collapse)AuthorFilesLines
2024-05-06Document CVE-2024-33599, CVE-2024-33600, CVE-2024-33601, CVE-2024-33602Carlos O'Donell4-0/+108
This commit adds advisory data for the above CVE(s). Reviewed-by: Siddhesh Poyarekar <siddhesh@sourceware.org>
2024-04-25GLIBC-SA-2024-0004: add commit for 2.31 branchAurelien Jarno1-0/+1
Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org> Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
2024-04-18advisories: Add Reported-BySiddhesh Poyarekar1-0/+4
Add a new tag to give credit to vulnerability discoverers. Signed-off-by: Siddhesh Poyarekar <siddhesh@sourceware.org>
2024-04-17Fix 'Reported-By' to use Camel Case for commit 6a98f4640ea453fAdhemerval Zanella1-1/+1
2024-04-17Document CVE-2024-2961Adhemerval Zanella1-0/+27
This commit adds "advisories" entries for the above three CVEs.
2024-01-30Update advisory format and introduce some automationSiddhesh Poyarekar6-26/+97
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-30Document CVE-2023-6246, CVE-2023-6779, and CVE-2023-6780Arjun Shankar3-0/+43
This commit adds "advisories" entries for the above three CVEs.
2023-12-07Move CVE information into advisories directorySiddhesh Poyarekar5-0/+80
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>
generated by cgit v1.1 at 2024-12-21 12:32:26 +0000