From: Alberto Leiva Popper <ydahhrk@gmail.com>
Date: Wed, 18 Dec 2024 18:57:46 +0000 (-0600)
Subject: Name CVE-2024-56169 and CVE-2024-56170
X-Git-Tag: 1.6.5~2
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=f99f662cec3e0fe083acf4a51916270b496018e1;p=thirdparty%2FFORT-validator.git

Name CVE-2024-56169 and CVE-2024-56170
---

diff --git a/docs/CVE.md b/docs/CVE.md
index 4d1ee52a..ca0239f4 100644
--- a/docs/CVE.md
+++ b/docs/CVE.md
@@ -67,9 +67,7 @@ Malicious rsync repositories can block Fort by drip-feeding repository objects.
 | Patch | Commit [4ee88d1](https://github.com/NICMx/FORT-validator/commit/4ee88d1c3fa7df763dd52312134cd93c1ce50870), released in Fort 1.6.4. |
 | Acknowledgments | Thanks to Koen van Hove for his research and disclosure, and Job Snijders for the proposed fix. |
 
-## CVE-XXXX-XXXXX
-
-(Awaiting CVE ID number assignment.)
+## CVE-2024-56170
 
 Fort is employing the latest fetched manifest, rather than the one with the most recent metadata.
 
@@ -78,9 +76,7 @@ Fort is employing the latest fetched manifest, rather than the one with the most
 | Patch | Scheduled for Fort release [2.0.0](https://github.com/NICMx/FORT-validator/milestone/12). |
 | Acknowledgments | Job Snijders |
 
-## CVE-YYYY-YYYYY
-
-(Awaiting CVE ID number assignment.)
+## CVE-2024-56169
 
 Fort's cache provides insufficient fallbacking.