[Git][security-tracker-team/security-tracker][master] Unify some of upstream tag references

Salvatore Bonaccorso (@carnil) carnil at debian.org
Tue Sep 17 06:10:41 BST 2024



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


Commits:
0c16d646 by Salvatore Bonaccorso at 2024-09-17T07:08:54+02:00
Unify some of upstream tag references

- - - - -


1 changed file:

- data/CVE/list


Changes:

=====================================
data/CVE/list
=====================================
@@ -183988,7 +183988,7 @@ CVE-2022-32086 (MariaDB v10.4 to v10.8 was discovered to contain a segmentation
 	NOTE: https://jira.mariadb.org/browse/MDEV-26412
 	NOTE: Fixed in:  10.4.25, 10.5.16, 10.6.8, 10.7.4, 10.8.3
 	NOTE: Older version returns error -Unknown column 't1.i' in 'field list'
-	NOTE: MariaDB commit: https://github.com/MariaDB/server/commit/39feab3cd31b5414aa9b428eaba915c251ac34a2 (10.4.25)
+	NOTE: MariaDB commit: https://github.com/MariaDB/server/commit/39feab3cd31b5414aa9b428eaba915c251ac34a2 (mariadb-10.4.25)
 CVE-2022-32085 (MariaDB v10.2 to v10.7 was discovered to contain a segmentation fault  ...)
 	{DLA-3114-1}
 	- mariadb-10.6 1:10.6.8-1
@@ -183999,8 +183999,8 @@ CVE-2022-32085 (MariaDB v10.2 to v10.7 was discovered to contain a segmentation
 	NOTE: Duplicate https://jira.mariadb.org/browse/MDEV-24176
 	NOTE: Fixed in:  10.3.35, 10.4.25, 10.5.16, 10.6.8, 10.7.4
 	NOTE: Does not affects version before 10.3 due to need virtual column feature
-	NOTE: Commit [1/2]: https://github.com/MariaDB/server/commit/08c7ab404f69d9c4ca6ca7a9cf7eec74c804f917 (10.3.35)
-	NOTE: Commit [2/2]:  https://github.com/MariaDB/server/commit/b3c3291f0b7c1623cb20663f7cf31b7f749768bc (10.3.35)
+	NOTE: Commit [1/2]: https://github.com/MariaDB/server/commit/08c7ab404f69d9c4ca6ca7a9cf7eec74c804f917 (mariadb-10.3.35)
+	NOTE: Commit [2/2]: https://github.com/MariaDB/server/commit/b3c3291f0b7c1623cb20663f7cf31b7f749768bc (mariadb-10.3.35)
 CVE-2022-32084 (MariaDB v10.2 to v10.7 was discovered to contain a segmentation fault  ...)
 	{DLA-3114-1}
 	- mariadb-10.6 1:10.6.9-1
@@ -184009,7 +184009,7 @@ CVE-2022-32084 (MariaDB v10.2 to v10.7 was discovered to contain a segmentation
 	- mariadb-10.3 <removed>
 	NOTE: https://jira.mariadb.org/browse/MDEV-26427
 	NOTE: Fixed in  10.3.36, 10.4.26, 10.5.17, 10.6.9, 10.7.5, 10.8.4, 10.9.2
-	NOTE: Fixed by https://github.com/MariaDB/server/commit/49e14000eeb245ea27e9207d2f63cb0a28be1ca9 (MariaDB 10.3.36)
+	NOTE: Fixed by: https://github.com/MariaDB/server/commit/49e14000eeb245ea27e9207d2f63cb0a28be1ca9 (mariadb-10.3.36)
 	NOTE: Affect windows function introduced in 10.2 see https://mariadb.com/kb/en/changes-improvements-in-mariadb-10-2/
 CVE-2022-32083 (MariaDB v10.2 to v10.6.1 was discovered to contain a segmentation faul ...)
 	{DLA-3114-1}
@@ -184018,7 +184018,7 @@ CVE-2022-32083 (MariaDB v10.2 to v10.6.1 was discovered to contain a segmentatio
 	[bullseye] - mariadb-10.5 1:10.5.18-0+deb11u1
 	- mariadb-10.3 <removed>
 	NOTE: MariaDB bug: https://jira.mariadb.org/browse/MDEV-26047
-	NOTE: MariaDB commit: https://github.com/MariaDB/server/commit/5100b20b15edd93200f34a79d25f1b14e46a677e (10.2.44)
+	NOTE: MariaDB commit: https://github.com/MariaDB/server/commit/5100b20b15edd93200f34a79d25f1b14e46a677e (mariadb-10.2.44)
 	NOTE: Fixed in version  10.2.44, 10.3.35, 10.4.25, 10.5.16, 10.6.8, 10.7.4, 10.8.3
 	NOTE: Same fix than CVE-2022-27384
 CVE-2022-32082 (MariaDB v10.5 to v10.7 was discovered to contain an assertion failure  ...)
@@ -184028,7 +184028,7 @@ CVE-2022-32082 (MariaDB v10.5 to v10.7 was discovered to contain an assertion fa
 	- mariadb-10.3 <not-affected> (Only affects MariaDB 10.5 onwards)
 	NOTE: https://jira.mariadb.org/browse/MDEV-26433
 	NOTE: Fixed in MariaDB  10.5.17, 10.6.9, 10.7.5, 10.8.4, 10.9.2
-	NOTE: MariaDB commit: https://github.com/MariaDB/server/commit/8494758e8e06aea5c8d4cddcff6c0a913bac4d23 (10.5.17)
+	NOTE: MariaDB commit: https://github.com/MariaDB/server/commit/8494758e8e06aea5c8d4cddcff6c0a913bac4d23 (mariadb-10.5.17)
 CVE-2022-32081 (MariaDB v10.4 to v10.7 was discovered to contain an use-after-poison i ...)
 	- mariadb-10.6 1:10.6.9-1
 	- mariadb-10.5 <removed>
@@ -184036,7 +184036,7 @@ CVE-2022-32081 (MariaDB v10.4 to v10.7 was discovered to contain an use-after-po
 	- mariadb-10.3 <not-affected> (Only affects MariaDB 10.4 onwards)
 	NOTE: https://jira.mariadb.org/browse/MDEV-26420
 	NOTE: Fixed in 10.4.26, 10.5.17, 10.6.9, 10.7.5, 10.8.4, 10.9.2, 10.10.1
-	NOTE: MariaDB commit: https://github.com/MariaDB/server/commit/9a897335eb4387980aed7698b832a893dbaa3d81 (10.4.26)
+	NOTE: MariaDB commit: https://github.com/MariaDB/server/commit/9a897335eb4387980aed7698b832a893dbaa3d81 (mariadb-10.4.26)
 CVE-2022-32080
 	RESERVED
 CVE-2022-32079



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

-- 
View it on GitLab: https://salsa.debian.org/security-tracker-team/security-tracker/-/commit/0c16d64635e45c0ae9e1b8a6ff3e08cb5d724f84
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/20240917/0dae0608/attachment-0001.htm>


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