diff --git a/2021/3xxx/CVE-2021-3156.json b/2021/3xxx/CVE-2021-3156.json
index 810840dc6ea..5fe811f2e73 100644
--- a/2021/3xxx/CVE-2021-3156.json
+++ b/2021/3xxx/CVE-2021-3156.json
@@ -211,6 +211,11 @@
                 "refsource": "MISC",
                 "name": "http://packetstormsecurity.com/files/176932/glibc-syslog-Heap-Based-Buffer-Overflow.html",
                 "url": "http://packetstormsecurity.com/files/176932/glibc-syslog-Heap-Based-Buffer-Overflow.html"
+            },
+            {
+                "refsource": "FULLDISC",
+                "name": "20240204 CVE-2023-6246: Heap-based buffer overflow in the glibc's syslog()",
+                "url": "http://seclists.org/fulldisclosure/2024/Feb/3"
             }
         ]
     }
diff --git a/2022/39xxx/CVE-2022-39046.json b/2022/39xxx/CVE-2022-39046.json
index be25df08eda..efdf8617f09 100644
--- a/2022/39xxx/CVE-2022-39046.json
+++ b/2022/39xxx/CVE-2022-39046.json
@@ -81,6 +81,11 @@
                 "refsource": "MISC",
                 "name": "http://packetstormsecurity.com/files/176932/glibc-syslog-Heap-Based-Buffer-Overflow.html",
                 "url": "http://packetstormsecurity.com/files/176932/glibc-syslog-Heap-Based-Buffer-Overflow.html"
+            },
+            {
+                "refsource": "FULLDISC",
+                "name": "20240204 CVE-2023-6246: Heap-based buffer overflow in the glibc's syslog()",
+                "url": "http://seclists.org/fulldisclosure/2024/Feb/3"
             }
         ]
     },
diff --git a/2022/3xxx/CVE-2022-3358.json b/2022/3xxx/CVE-2022-3358.json
index 44af0299da2..802049df85e 100644
--- a/2022/3xxx/CVE-2022-3358.json
+++ b/2022/3xxx/CVE-2022-3358.json
@@ -86,6 +86,11 @@
                 "refsource": "CONFIRM",
                 "name": "https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2022-0023",
                 "url": "https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2022-0023"
+            },
+            {
+                "refsource": "GENTOO",
+                "name": "GLSA-202402-08",
+                "url": "https://security.gentoo.org/glsa/202402-08"
             }
         ]
     }
diff --git a/2022/4xxx/CVE-2022-4203.json b/2022/4xxx/CVE-2022-4203.json
index 06dfac8bdcd..70e71bb39cf 100644
--- a/2022/4xxx/CVE-2022-4203.json
+++ b/2022/4xxx/CVE-2022-4203.json
@@ -11,7 +11,7 @@
         "description_data": [
             {
                 "lang": "eng",
-                "value": "A read buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Note that this occurs after certificate chain signature verification and requires either a CA to have signed the malicious certificate or for the application to continue certificate verification despite failure to construct a path to a trusted issuer. The read buffer overrun might result in a crash which could lead to a denial of service attack. In theory it could also result in the disclosure of private memory contents (such as private keys, or sensitive plaintext) although we are not aware of any working exploit leading to memory contents disclosure as of the time of release of this advisory. In a TLS client, this can be triggered by connecting to a malicious server. In a TLS server, this can be triggered if the server requests client authentication and a malicious client connects."
+                "value": "A read buffer overrun can be triggered in X.509 certificate verification,\nspecifically in name constraint checking. Note that this occurs\nafter certificate chain signature verification and requires either a\nCA to have signed the malicious certificate or for the application to\ncontinue certificate verification despite failure to construct a path\nto a trusted issuer.\n\nThe read buffer overrun might result in a crash which could lead to\na denial of service attack. In theory it could also result in the disclosure\nof private memory contents (such as private keys, or sensitive plaintext)\nalthough we are not aware of any working exploit leading to memory\ncontents disclosure as of the time of release of this advisory.\n\nIn a TLS client, this can be triggered by connecting to a malicious\nserver. In a TLS server, this can be triggered if the server requests\nclient authentication and a malicious client connects.\n\n"
             }
         ]
     },
@@ -63,6 +63,11 @@
                 "url": "https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=c927a3492698c254637da836762f9b1f86cffabc",
                 "refsource": "MISC",
                 "name": "https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=c927a3492698c254637da836762f9b1f86cffabc"
+            },
+            {
+                "url": "https://security.gentoo.org/glsa/202402-08",
+                "refsource": "MISC",
+                "name": "https://security.gentoo.org/glsa/202402-08"
             }
         ]
     },
diff --git a/2022/4xxx/CVE-2022-4304.json b/2022/4xxx/CVE-2022-4304.json
index a32c269adf5..d907890b98a 100644
--- a/2022/4xxx/CVE-2022-4304.json
+++ b/2022/4xxx/CVE-2022-4304.json
@@ -11,7 +11,7 @@
         "description_data": [
             {
                 "lang": "eng",
-                "value": "A timing based side channel exists in the OpenSSL RSA Decryption implementation which could be sufficient to recover a plaintext across a network in a Bleichenbacher style attack. To achieve a successful decryption an attacker would have to be able to send a very large number of trial messages for decryption. The vulnerability affects all RSA padding modes: PKCS#1 v1.5, RSA-OEAP and RSASVE. For example, in a TLS connection, RSA is commonly used by a client to send an encrypted pre-master secret to the server. An attacker that had observed a genuine connection between a client and a server could use this flaw to send trial messages to the server and record the time taken to process them. After a sufficiently large number of messages the attacker could recover the pre-master secret used for the original connection and thus be able to decrypt the application data sent over that connection."
+                "value": "A timing based side channel exists in the OpenSSL RSA Decryption implementation\nwhich could be sufficient to recover a plaintext across a network in a\nBleichenbacher style attack. To achieve a successful decryption an attacker\nwould have to be able to send a very large number of trial messages for\ndecryption. The vulnerability affects all RSA padding modes: PKCS#1 v1.5,\nRSA-OEAP and RSASVE.\n\nFor example, in a TLS connection, RSA is commonly used by a client to send an\nencrypted pre-master secret to the server. An attacker that had observed a\ngenuine connection between a client and a server could use this flaw to send\ntrial messages to the server and record the time taken to process them. After a\nsufficiently large number of messages the attacker could recover the pre-master\nsecret used for the original connection and thus be able to decrypt the\napplication data sent over that connection.\n\n"
             }
         ]
     },
@@ -39,16 +39,19 @@
                                 "version": {
                                     "version_data": [
                                         {
-                                            "version_value": "3.0.0",
-                                            "version_affected": "="
+                                            "version_affected": "<",
+                                            "version_name": "3.0.0",
+                                            "version_value": "3.0.8"
                                         },
                                         {
-                                            "version_value": "1.1.1",
-                                            "version_affected": "="
+                                            "version_affected": "<",
+                                            "version_name": "1.1.1",
+                                            "version_value": "1.1.1t"
                                         },
                                         {
-                                            "version_value": "1.0.2",
-                                            "version_affected": "="
+                                            "version_affected": "<",
+                                            "version_name": "1.0.2",
+                                            "version_value": "1.0.2zg"
                                         }
                                     ]
                                 }
@@ -65,6 +68,11 @@
                 "url": "https://www.openssl.org/news/secadv/20230207.txt",
                 "refsource": "MISC",
                 "name": "https://www.openssl.org/news/secadv/20230207.txt"
+            },
+            {
+                "url": "https://security.gentoo.org/glsa/202402-08",
+                "refsource": "MISC",
+                "name": "https://security.gentoo.org/glsa/202402-08"
             }
         ]
     },
diff --git a/2022/4xxx/CVE-2022-4450.json b/2022/4xxx/CVE-2022-4450.json
index 75900c6e4ab..2a1344face8 100644
--- a/2022/4xxx/CVE-2022-4450.json
+++ b/2022/4xxx/CVE-2022-4450.json
@@ -11,7 +11,7 @@
         "description_data": [
             {
                 "lang": "eng",
-                "value": "The function PEM_read_bio_ex() reads a PEM file from a BIO and parses and decodes the \"name\" (e.g. \"CERTIFICATE\"), any header data and the payload data. If the function succeeds then the \"name_out\", \"header\" and \"data\" arguments are populated with pointers to buffers containing the relevant decoded data. The caller is responsible for freeing those buffers. It is possible to construct a PEM file that results in 0 bytes of payload data. In this case PEM_read_bio_ex() will return a failure code but will populate the header argument with a pointer to a buffer that has already been freed. If the caller also frees this buffer then a double free will occur. This will most likely lead to a crash. This could be exploited by an attacker who has the ability to supply malicious PEM files for parsing to achieve a denial of service attack. The functions PEM_read_bio() and PEM_read() are simple wrappers around PEM_read_bio_ex() and therefore these functions are also directly affected. These functions are also called indirectly by a number of other OpenSSL functions including PEM_X509_INFO_read_bio_ex() and SSL_CTX_use_serverinfo_file() which are also vulnerable. Some OpenSSL internal uses of these functions are not vulnerable because the caller does not free the header argument if PEM_read_bio_ex() returns a failure code. These locations include the PEM_read_bio_TYPE() functions as well as the decoders introduced in OpenSSL 3.0. The OpenSSL asn1parse command line application is also impacted by this issue."
+                "value": "The function PEM_read_bio_ex() reads a PEM file from a BIO and parses and\ndecodes the \"name\" (e.g. \"CERTIFICATE\"), any header data and the payload data.\nIf the function succeeds then the \"name_out\", \"header\" and \"data\" arguments are\npopulated with pointers to buffers containing the relevant decoded data. The\ncaller is responsible for freeing those buffers. It is possible to construct a\nPEM file that results in 0 bytes of payload data. In this case PEM_read_bio_ex()\nwill return a failure code but will populate the header argument with a pointer\nto a buffer that has already been freed. If the caller also frees this buffer\nthen a double free will occur. This will most likely lead to a crash. This\ncould be exploited by an attacker who has the ability to supply malicious PEM\nfiles for parsing to achieve a denial of service attack.\n\nThe functions PEM_read_bio() and PEM_read() are simple wrappers around\nPEM_read_bio_ex() and therefore these functions are also directly affected.\n\nThese functions are also called indirectly by a number of other OpenSSL\nfunctions including PEM_X509_INFO_read_bio_ex() and\nSSL_CTX_use_serverinfo_file() which are also vulnerable. Some OpenSSL internal\nuses of these functions are not vulnerable because the caller does not free the\nheader argument if PEM_read_bio_ex() returns a failure code. These locations\ninclude the PEM_read_bio_TYPE() functions as well as the decoders introduced in\nOpenSSL 3.0.\n\nThe OpenSSL asn1parse command line application is also impacted by this issue.\n\n\n"
             }
         ]
     },
@@ -73,6 +73,11 @@
                 "url": "https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=bbcf509bd046b34cca19c766bbddc31683d0858b",
                 "refsource": "MISC",
                 "name": "https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=bbcf509bd046b34cca19c766bbddc31683d0858b"
+            },
+            {
+                "url": "https://security.gentoo.org/glsa/202402-08",
+                "refsource": "MISC",
+                "name": "https://security.gentoo.org/glsa/202402-08"
             }
         ]
     },
diff --git a/2023/0xxx/CVE-2023-0215.json b/2023/0xxx/CVE-2023-0215.json
index dc6427bab33..a4e07d3d0a7 100644
--- a/2023/0xxx/CVE-2023-0215.json
+++ b/2023/0xxx/CVE-2023-0215.json
@@ -93,6 +93,11 @@
                 "url": "https://security.netapp.com/advisory/ntap-20230427-0009/",
                 "refsource": "MISC",
                 "name": "https://security.netapp.com/advisory/ntap-20230427-0009/"
+            },
+            {
+                "url": "https://security.gentoo.org/glsa/202402-08",
+                "refsource": "MISC",
+                "name": "https://security.gentoo.org/glsa/202402-08"
             }
         ]
     },
diff --git a/2023/0xxx/CVE-2023-0216.json b/2023/0xxx/CVE-2023-0216.json
index aa98e174542..07f552d2fc1 100644
--- a/2023/0xxx/CVE-2023-0216.json
+++ b/2023/0xxx/CVE-2023-0216.json
@@ -11,7 +11,7 @@
         "description_data": [
             {
                 "lang": "eng",
-                "value": "An invalid pointer dereference on read can be triggered when an application tries to load malformed PKCS7 data with the d2i_PKCS7(), d2i_PKCS7_bio() or d2i_PKCS7_fp() functions. The result of the dereference is an application crash which could lead to a denial of service attack. The TLS implementation in OpenSSL does not call this function however third party applications might call these functions on untrusted data."
+                "value": "An invalid pointer dereference on read can be triggered when an\napplication tries to load malformed PKCS7 data with the\nd2i_PKCS7(), d2i_PKCS7_bio() or d2i_PKCS7_fp() functions.\n\nThe result of the dereference is an application crash which could\nlead to a denial of service attack. The TLS implementation in OpenSSL\ndoes not call this function however third party applications might\ncall these functions on untrusted data.\n\n"
             }
         ]
     },
@@ -63,6 +63,11 @@
                 "url": "https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=934a04f0e775309cadbef0aa6b9692e1b12a76c6",
                 "refsource": "MISC",
                 "name": "https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=934a04f0e775309cadbef0aa6b9692e1b12a76c6"
+            },
+            {
+                "url": "https://security.gentoo.org/glsa/202402-08",
+                "refsource": "MISC",
+                "name": "https://security.gentoo.org/glsa/202402-08"
             }
         ]
     },
diff --git a/2023/0xxx/CVE-2023-0217.json b/2023/0xxx/CVE-2023-0217.json
index 12d96d88589..94c4e454704 100644
--- a/2023/0xxx/CVE-2023-0217.json
+++ b/2023/0xxx/CVE-2023-0217.json
@@ -11,7 +11,7 @@
         "description_data": [
             {
                 "lang": "eng",
-                "value": "An invalid pointer dereference on read can be triggered when an application tries to check a malformed DSA public key by the EVP_PKEY_public_check() function. This will most likely lead to an application crash. This function can be called on public keys supplied from untrusted sources which could allow an attacker to cause a denial of service attack. The TLS implementation in OpenSSL does not call this function but applications might call the function if there are additional security requirements imposed by standards such as FIPS 140-3."
+                "value": "An invalid pointer dereference on read can be triggered when an\napplication tries to check a malformed DSA public key by the\nEVP_PKEY_public_check() function. This will most likely lead\nto an application crash. This function can be called on public\nkeys supplied from untrusted sources which could allow an attacker\nto cause a denial of service attack.\n\nThe TLS implementation in OpenSSL does not call this function\nbut applications might call the function if there are additional\nsecurity requirements imposed by standards such as FIPS 140-3.\n\n"
             }
         ]
     },
@@ -63,6 +63,11 @@
                 "url": "https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=23985bac83fd50c8e29431009302b5442f985096",
                 "refsource": "MISC",
                 "name": "https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=23985bac83fd50c8e29431009302b5442f985096"
+            },
+            {
+                "url": "https://security.gentoo.org/glsa/202402-08",
+                "refsource": "MISC",
+                "name": "https://security.gentoo.org/glsa/202402-08"
             }
         ]
     },
diff --git a/2023/0xxx/CVE-2023-0286.json b/2023/0xxx/CVE-2023-0286.json
index 15f9f279e7c..045e2d75af7 100644
--- a/2023/0xxx/CVE-2023-0286.json
+++ b/2023/0xxx/CVE-2023-0286.json
@@ -11,7 +11,7 @@
         "description_data": [
             {
                 "lang": "eng",
-                "value": "There is a type confusion vulnerability relating to X.400 address processing inside an X.509 GeneralName. X.400 addresses were parsed as an ASN1_STRING but the public structure definition for GENERAL_NAME incorrectly specified the type of the x400Address field as ASN1_TYPE. This field is subsequently interpreted by the OpenSSL function GENERAL_NAME_cmp as an ASN1_TYPE rather than an ASN1_STRING. When CRL checking is enabled (i.e. the application sets the X509_V_FLAG_CRL_CHECK flag), this vulnerability may allow an attacker to pass arbitrary pointers to a memcmp call, enabling them to read memory contents or enact a denial of service. In most cases, the attack requires the attacker to provide both the certificate chain and CRL, neither of which need to have a valid signature. If the attacker only controls one of these inputs, the other input must already contain an X.400 address as a CRL distribution point, which is uncommon. As such, this vulnerability is most likely to only affect applications which have implemented their own functionality for retrieving CRLs over a network."
+                "value": "There is a type confusion vulnerability relating to X.400 address processing\ninside an X.509 GeneralName. X.400 addresses were parsed as an ASN1_STRING but\nthe public structure definition for GENERAL_NAME incorrectly specified the type\nof the x400Address field as ASN1_TYPE. This field is subsequently interpreted by\nthe OpenSSL function GENERAL_NAME_cmp as an ASN1_TYPE rather than an\nASN1_STRING.\n\nWhen CRL checking is enabled (i.e. the application sets the\nX509_V_FLAG_CRL_CHECK flag), this vulnerability may allow an attacker to pass\narbitrary pointers to a memcmp call, enabling them to read memory contents or\nenact a denial of service. In most cases, the attack requires the attacker to\nprovide both the certificate chain and CRL, neither of which need to have a\nvalid signature. If the attacker only controls one of these inputs, the other\ninput must already contain an X.400 address as a CRL distribution point, which\nis uncommon. As such, this vulnerability is most likely to only affect\napplications which have implemented their own functionality for retrieving CRLs\nover a network.\n\n"
             }
         ]
     },
@@ -93,6 +93,11 @@
                 "url": "https://ftp.openbsd.org/pub/OpenBSD/LibreSSL/libressl-3.6.2-relnotes.txt",
                 "refsource": "MISC",
                 "name": "https://ftp.openbsd.org/pub/OpenBSD/LibreSSL/libressl-3.6.2-relnotes.txt"
+            },
+            {
+                "url": "https://security.gentoo.org/glsa/202402-08",
+                "refsource": "MISC",
+                "name": "https://security.gentoo.org/glsa/202402-08"
             }
         ]
     },
diff --git a/2023/0xxx/CVE-2023-0401.json b/2023/0xxx/CVE-2023-0401.json
index 2fb64936b29..53252b7ccb0 100644
--- a/2023/0xxx/CVE-2023-0401.json
+++ b/2023/0xxx/CVE-2023-0401.json
@@ -11,7 +11,7 @@
         "description_data": [
             {
                 "lang": "eng",
-                "value": "A NULL pointer can be dereferenced when signatures are being verified on PKCS7 signed or signedAndEnveloped data. In case the hash algorithm used for the signature is known to the OpenSSL library but the implementation of the hash algorithm is not available the digest initialization will fail. There is a missing check for the return value from the initialization function which later leads to invalid usage of the digest API most likely leading to a crash. The unavailability of an algorithm can be caused by using FIPS enabled configuration of providers or more commonly by not loading the legacy provider. PKCS7 data is processed by the SMIME library calls and also by the time stamp (TS) library calls. The TLS implementation in OpenSSL does not call these functions however third party applications would be affected if they call these functions to verify signatures on untrusted data."
+                "value": "A NULL pointer can be dereferenced when signatures are being\nverified on PKCS7 signed or signedAndEnveloped data. In case the hash\nalgorithm used for the signature is known to the OpenSSL library but\nthe implementation of the hash algorithm is not available the digest\ninitialization will fail. There is a missing check for the return\nvalue from the initialization function which later leads to invalid\nusage of the digest API most likely leading to a crash.\n\nThe unavailability of an algorithm can be caused by using FIPS\nenabled configuration of providers or more commonly by not loading\nthe legacy provider.\n\nPKCS7 data is processed by the SMIME library calls and also by the\ntime stamp (TS) library calls. The TLS implementation in OpenSSL does\nnot call these functions however third party applications would be\naffected if they call these functions to verify signatures on untrusted\ndata.\n\n"
             }
         ]
     },
@@ -63,6 +63,11 @@
                 "url": "https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=d3b6dfd70db844c4499bec6ad6601623a565e674",
                 "refsource": "MISC",
                 "name": "https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=d3b6dfd70db844c4499bec6ad6601623a565e674"
+            },
+            {
+                "url": "https://security.gentoo.org/glsa/202402-08",
+                "refsource": "MISC",
+                "name": "https://security.gentoo.org/glsa/202402-08"
             }
         ]
     },
diff --git a/2023/0xxx/CVE-2023-0464.json b/2023/0xxx/CVE-2023-0464.json
index d62d345ed11..df0324b79b4 100644
--- a/2023/0xxx/CVE-2023-0464.json
+++ b/2023/0xxx/CVE-2023-0464.json
@@ -108,6 +108,11 @@
                 "url": "https://lists.debian.org/debian-lts-announce/2023/06/msg00011.html",
                 "refsource": "MISC",
                 "name": "https://lists.debian.org/debian-lts-announce/2023/06/msg00011.html"
+            },
+            {
+                "url": "https://security.gentoo.org/glsa/202402-08",
+                "refsource": "MISC",
+                "name": "https://security.gentoo.org/glsa/202402-08"
             }
         ]
     },
diff --git a/2023/0xxx/CVE-2023-0465.json b/2023/0xxx/CVE-2023-0465.json
index 6e1b43ab7c4..a40e27c0dd3 100644
--- a/2023/0xxx/CVE-2023-0465.json
+++ b/2023/0xxx/CVE-2023-0465.json
@@ -108,6 +108,11 @@
                 "url": "https://lists.debian.org/debian-lts-announce/2023/06/msg00011.html",
                 "refsource": "MISC",
                 "name": "https://lists.debian.org/debian-lts-announce/2023/06/msg00011.html"
+            },
+            {
+                "url": "https://security.gentoo.org/glsa/202402-08",
+                "refsource": "MISC",
+                "name": "https://security.gentoo.org/glsa/202402-08"
             }
         ]
     },
diff --git a/2023/0xxx/CVE-2023-0466.json b/2023/0xxx/CVE-2023-0466.json
index b79ce5ca5db..370ac5a867d 100644
--- a/2023/0xxx/CVE-2023-0466.json
+++ b/2023/0xxx/CVE-2023-0466.json
@@ -113,6 +113,11 @@
                 "url": "http://www.openwall.com/lists/oss-security/2023/09/28/4",
                 "refsource": "MISC",
                 "name": "http://www.openwall.com/lists/oss-security/2023/09/28/4"
+            },
+            {
+                "url": "https://security.gentoo.org/glsa/202402-08",
+                "refsource": "MISC",
+                "name": "https://security.gentoo.org/glsa/202402-08"
             }
         ]
     },
diff --git a/2023/2xxx/CVE-2023-2650.json b/2023/2xxx/CVE-2023-2650.json
index 135d1566972..e20549b21a7 100644
--- a/2023/2xxx/CVE-2023-2650.json
+++ b/2023/2xxx/CVE-2023-2650.json
@@ -123,6 +123,11 @@
                 "url": "https://security.netapp.com/advisory/ntap-20231027-0009/",
                 "refsource": "MISC",
                 "name": "https://security.netapp.com/advisory/ntap-20231027-0009/"
+            },
+            {
+                "url": "https://security.gentoo.org/glsa/202402-08",
+                "refsource": "MISC",
+                "name": "https://security.gentoo.org/glsa/202402-08"
             }
         ]
     },
diff --git a/2023/2xxx/CVE-2023-2975.json b/2023/2xxx/CVE-2023-2975.json
index 5092d4da16e..d4f72663078 100644
--- a/2023/2xxx/CVE-2023-2975.json
+++ b/2023/2xxx/CVE-2023-2975.json
@@ -88,6 +88,11 @@
                 "url": "https://security.netapp.com/advisory/ntap-20230725-0004/",
                 "refsource": "MISC",
                 "name": "https://security.netapp.com/advisory/ntap-20230725-0004/"
+            },
+            {
+                "url": "https://security.gentoo.org/glsa/202402-08",
+                "refsource": "MISC",
+                "name": "https://security.gentoo.org/glsa/202402-08"
             }
         ]
     },
diff --git a/2023/3xxx/CVE-2023-3446.json b/2023/3xxx/CVE-2023-3446.json
index d253dd3360d..bd95e9b75d4 100644
--- a/2023/3xxx/CVE-2023-3446.json
+++ b/2023/3xxx/CVE-2023-3446.json
@@ -123,6 +123,11 @@
                 "url": "https://lists.debian.org/debian-lts-announce/2023/08/msg00019.html",
                 "refsource": "MISC",
                 "name": "https://lists.debian.org/debian-lts-announce/2023/08/msg00019.html"
+            },
+            {
+                "url": "https://security.gentoo.org/glsa/202402-08",
+                "refsource": "MISC",
+                "name": "https://security.gentoo.org/glsa/202402-08"
             }
         ]
     },
diff --git a/2023/3xxx/CVE-2023-3817.json b/2023/3xxx/CVE-2023-3817.json
index e531e587731..5564236f068 100644
--- a/2023/3xxx/CVE-2023-3817.json
+++ b/2023/3xxx/CVE-2023-3817.json
@@ -133,6 +133,11 @@
                 "url": "http://www.openwall.com/lists/oss-security/2023/11/06/2",
                 "refsource": "MISC",
                 "name": "http://www.openwall.com/lists/oss-security/2023/11/06/2"
+            },
+            {
+                "url": "https://security.gentoo.org/glsa/202402-08",
+                "refsource": "MISC",
+                "name": "https://security.gentoo.org/glsa/202402-08"
             }
         ]
     },
diff --git a/2023/6xxx/CVE-2023-6246.json b/2023/6xxx/CVE-2023-6246.json
index ca7dc120ffe..b1fd12beb22 100644
--- a/2023/6xxx/CVE-2023-6246.json
+++ b/2023/6xxx/CVE-2023-6246.json
@@ -191,6 +191,11 @@
                 "url": "https://security.gentoo.org/glsa/202402-01",
                 "refsource": "MISC",
                 "name": "https://security.gentoo.org/glsa/202402-01"
+            },
+            {
+                "url": "http://seclists.org/fulldisclosure/2024/Feb/3",
+                "refsource": "MISC",
+                "name": "http://seclists.org/fulldisclosure/2024/Feb/3"
             }
         ]
     },
diff --git a/2023/6xxx/CVE-2023-6779.json b/2023/6xxx/CVE-2023-6779.json
index 3de1074ad43..c23ed63397b 100644
--- a/2023/6xxx/CVE-2023-6779.json
+++ b/2023/6xxx/CVE-2023-6779.json
@@ -186,6 +186,11 @@
                 "url": "https://security.gentoo.org/glsa/202402-01",
                 "refsource": "MISC",
                 "name": "https://security.gentoo.org/glsa/202402-01"
+            },
+            {
+                "url": "http://seclists.org/fulldisclosure/2024/Feb/3",
+                "refsource": "MISC",
+                "name": "http://seclists.org/fulldisclosure/2024/Feb/3"
             }
         ]
     },
diff --git a/2023/6xxx/CVE-2023-6780.json b/2023/6xxx/CVE-2023-6780.json
index d246add883a..8d07b428bf1 100644
--- a/2023/6xxx/CVE-2023-6780.json
+++ b/2023/6xxx/CVE-2023-6780.json
@@ -186,6 +186,11 @@
                 "url": "https://security.gentoo.org/glsa/202402-01",
                 "refsource": "MISC",
                 "name": "https://security.gentoo.org/glsa/202402-01"
+            },
+            {
+                "url": "http://seclists.org/fulldisclosure/2024/Feb/3",
+                "refsource": "MISC",
+                "name": "http://seclists.org/fulldisclosure/2024/Feb/3"
             }
         ]
     },