[Git][security-tracker-team/security-tracker][master] Drop some TODO items for CVEs meant to be REJECTED

Salvatore Bonaccorso (@carnil) carnil at debian.org
Sun Jan 1 09:31:47 GMT 2023



Salvatore Bonaccorso pushed to branch master at Debian Security Tracker / security-tracker


Commits:
b6ea994f by Salvatore Bonaccorso at 2023-01-01T10:30:20+01:00
Drop some TODO items for CVEs meant to be REJECTED

The assigning CNA (Altassian) has only updated the description for some
reason but not properly marked the CVEs as REJECTED. For now associate
them with a NFU for Atlassian, which hopefully propagates soon to a
clean rejected entry.

- - - - -


1 changed file:

- data/CVE/list


Changes:

=====================================
data/CVE/list
=====================================
@@ -17096,101 +17096,101 @@ CVE-2022-43832
 CVE-2022-43831
 	RESERVED
 CVE-2022-43830 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-43829 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-43828 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-43827 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-43826 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-43825 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-43824 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-43823 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-43822 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-43821 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-43820 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-43819 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-43818 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-43817 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-43816 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-43815 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-43814 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-43813 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-43812 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-43811 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-43810 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-43809 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-43808 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-43807 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-43806 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-43805 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-43804 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-43803 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-43802 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-43801 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-43800 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-43799 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-43798 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-43797 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-43796 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-43795 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-43794 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-43793 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-43792 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-43791 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-43790 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-43789 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-43788 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-43787 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-43786 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-43785 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-43784 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-43783 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-43782 (Affected versions of Atlassian Crowd allow an attacker to authenticate ...)
 	NOT-FOR-US: Atlassian
 CVE-2022-43781 (There is a command injection vulnerability using environment variables ...)
@@ -36002,7 +36002,7 @@ CVE-2022-36829 (PendingIntent hijacking vulnerability in releaseAlarm in Charm b
 CVE-2022-36828
 	RESERVED
 CVE-2022-36827 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-36826
 	RESERVED
 CVE-2022-36825
@@ -36024,7 +36024,7 @@ CVE-2022-36818
 CVE-2022-36817
 	RESERVED
 CVE-2022-36816 (To maintain compliance with CNA rules, we have rejected this CVE recor ...)
-	TODO: check
+	NOT-FOR-US: Atlassian
 CVE-2022-36815
 	RESERVED
 CVE-2022-36814



View it on GitLab: https://salsa.debian.org/security-tracker-team/security-tracker/-/commit/b6ea994f6eb0cd41ff73ee8d17ed0750b27a233f

-- 
View it on GitLab: https://salsa.debian.org/security-tracker-team/security-tracker/-/commit/b6ea994f6eb0cd41ff73ee8d17ed0750b27a233f
You're receiving this email because of your account on salsa.debian.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/debian-security-tracker-commits/attachments/20230101/cd9503ba/attachment.htm>


More information about the debian-security-tracker-commits mailing list