diff --git a/security/vuxml/Makefile b/security/vuxml/Makefile
index 56af61aba418..9a3ef8b7a291 100644
--- a/security/vuxml/Makefile
+++ b/security/vuxml/Makefile
@@ -1,108 +1,120 @@
 PORTNAME=	vuxml
 PORTVERSION=	1.1
 PORTREVISION=	6
 CATEGORIES=	security textproc
 MASTER_SITES=	http://www.vuxml.org/dtd/vuxml-1/
 DISTFILES=	vuxml-10.dtd  vuxml-model-10.mod \
 		vuxml-11.dtd  vuxml-model-11.mod \
 		xml1.dcl catalog catalog.xml
 DIST_SUBDIR=	vuxml
 
 MAINTAINER=	ports-secteam@FreeBSD.org
 COMMENT=	Vulnerability and eXposure Markup Language DTD
 WWW=		https://vuxml.freebsd.org/
 
 LICENSE=	BSD2CLAUSE
 
 RUN_DEPENDS=	xmlcatmgr:textproc/xmlcatmgr \
 		xsltproc:textproc/libxslt \
 		${LOCALBASE}/share/xml/dtd/xhtml-modularization/VERSION:textproc/xhtml-modularization \
 		${LOCALBASE}/share/xml/dtd/xhtml-basic/xhtml-basic10.dtd:textproc/xhtml-basic
 
 USES=		python:run
 
 NO_MTREE=	yes
 NO_ARCH=	yes
 NO_BUILD=	yes
 WRKSRC=		${WRKDIR}
 
 dir_DTD=	share/xml/dtd/vuxml
 
 .include <bsd.port.pre.mk>
 
 VUXML_FILE?=	${PKGDIR}/vuln.xml
 VUXML_FLAT_NAME=	vuln-flat.xml
 VUXML_FLAT_FILE?=	${PKGDIR}/${VUXML_FLAT_NAME}
 _YEAR!=	date +%Y
 VUXML_CURRENT_FILE?=	${PKGDIR}/vuln/${_YEAR}.xml
 
 post-clean:
 	@${RM} "${VUXML_FILE}.tidy"
 	@${RM} "${VUXML_FLAT_FILE}"
 
 do-extract:
 	@${RM} -r ${WRKDIR}
 	@${MKDIR} ${WRKDIR}
 .for f in ${DISTFILES}
 	${CP} ${_DISTDIR}/${f} ${WRKDIR}/${f}
 .endfor
 
 do-install:
 	@${MKDIR} ${STAGEDIR}${PREFIX}/${dir_DTD}
 .for f in ${DISTFILES}
 	${INSTALL_DATA} ${WRKSRC}/${f} ${STAGEDIR}${PREFIX}/${dir_DTD}/${f}
 .endfor
 
 do-test:
 	@${MKDIR} ${WRKDIR}/test
 	@${CP} -R ${.CURDIR}/vuln.xml ${.CURDIR}/vuln ${WRKDIR}/test
 	@cd ${.CURDIR} && make validate PKGDIR=${WRKDIR}/test
 
 ${VUXML_FLAT_NAME}: ${VUXML_FILE} vuln/*.xml
 	xmllint -noent ${.ALLSRC:[1]} > ${.TARGET}
 
 validate: tidy
 	@${SH} ${FILESDIR}/validate.sh "${VUXML_FLAT_FILE}"
 	@${ECHO_MSG} Checking if tidy differs...
 	@if ${DIFF} -u "${VUXML_FLAT_FILE}" "${VUXML_FILE}.tidy"; \
 	then \
 		${ECHO_MSG} ... seems okay; \
 		${RM} "${VUXML_FILE}.tidy"; \
 	else \
 		return 1; \
 	fi
 	@${ECHO_MSG} Checking for space/tab...
 	@unexpand "${VUXML_FLAT_FILE}" | ${SED} -E 's,[[:space:]]*$$,,g' > "${VUXML_FILE}.unexpanded"
 	@if ${DIFF} -u "${VUXML_FLAT_FILE}" "${VUXML_FILE}.unexpanded"; \
 	then \
 		${ECHO_MSG} ... seems okay; \
 		${RM} "${VUXML_FILE}.unexpanded"; \
 	else \
 		${ECHO_MSG} ... see above; \
 		${ECHO_CMD} Consider using ${VUXML_FILE}.unexpanded for final commit; \
 		return 1; \
 	fi
 	${PYTHON_CMD} ${FILESDIR}/extra-validation.py ${VUXML_FLAT_FILE}
+	@${ECHO_CMD}
+	@${ECHO_CMD} 'Be sure to get versioning right for PORTEPOCH and remember possible linux-* ports!'
+	@${ECHO_CMD} 'Also, <gt> tags are usually wrong in ranges. Use <ge> where adequate.'
+	@${ECHO_CMD}
 
 tidy: ${VUXML_FLAT_NAME}
 	@if [ ! -e ${LOCALBASE}/share/xml/dtd/vuxml/catalog.xml ]; \
 	then \
 		echo "Please install the VuXML port prior to running make validate/tidy."; \
 		exit 1; \
 	fi
 	${SH} ${FILESDIR}/tidy.sh "${FILESDIR}/tidy.xsl" "${VUXML_FLAT_FILE}" > "${VUXML_FILE}.tidy"
 
 newentry:
+	@${ECHO_CMD}
+	@${ECHO_CMD} 'Be sure to get versioning right for PORTEPOCH and remember possible linux-* ports!'
+	@${ECHO_CMD} 'Also, <gt> tags are usually wrong in ranges. Use <ge> where adequate.'
+	@${ECHO_CMD}
 	@${SH} ${FILESDIR}/newentry.sh "${VUXML_CURRENT_FILE}" "CVE_ID=${CVE_ID}" "SA_ID=${SA_ID}"
+	@${ECHO_CMD}
+	@${ECHO_CMD} 'Be sure to get versioning right for PORTEPOCH and remember possible linux-* ports!'
+	@${ECHO_CMD} 'Also, <gt> tags are usually wrong in ranges. Use <ge> where adequate.'
+	@${ECHO_CMD}
 
 .if defined(VID) && !empty(VID)
 html: work/${VID}.html
 work/${VID}.html: ${FILESDIR}/html.xsl ${FILESDIR}/common.css ${VUXML_FILE}
 	${MKDIR} work
 	xsltproc --stringparam vid "${VID}" \
 	    --output ${.TARGET} \
 	    ${FILESDIR}/html.xsl ${VUXML_FILE}
 	${INSTALL_DATA} ${FILESDIR}/common.css work
 .endif
 
 .include <bsd.port.post.mk>
diff --git a/security/vuxml/vuln/2024.xml b/security/vuxml/vuln/2024.xml
index c824f0b19868..64f19bfb38aa 100644
--- a/security/vuxml/vuln/2024.xml
+++ b/security/vuxml/vuln/2024.xml
@@ -1,13784 +1,13785 @@
   <vuln vid="a380f43e-19e5-11f0-9568-b42e991fc52e">
     <topic>Perl -- heap buffer overflow when transliterating non-ASCII bytes</topic>
     <affects>
       <package>
 	<name>perl5.36</name>
 	<range><lt>5.36.3</lt></range>
       </package>
       <package>
 	<name>perl5.38</name>
 	<range><lt>5.38.4</lt></range>
       </package>
       <package>
 	<name>perl5.40</name>
 	<range><lt>5.40.2</lt></range>
       </package>
       <package>
 	<name>perl5-devel</name>
 	<range><lt>5.41.10</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>9b29abf9-4ab0-4765-b253-1875cd9b441e reports:</p>
 	<blockquote cite="https://github.com/Perl/perl5/commit/87f42aa0e0096e9a346c9672aa3a0bd3bef8c1dd.patch">
 	<p>A heap buffer overflow vulnerability was discovered in Perl.
 	When there are non-ASCII bytes in the left-hand-side of the `tr`
 	operator, `S_do_trans_invmap` can overflow the destination pointer
 	`d`.
 	$ perl -e &apos;$_ = &quot;\x{FF}&quot; x 1000000; tr/\xFF/\x{100}/;&apos;
 	Segmentation fault (core dumped)
 	It is believed that this vulnerability can enable Denial of
 	Service and possibly Code Execution attacks on platforms that
 	lack sufficient defenses.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-56406</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-56406</url>
     </references>
     <dates>
       <discovery>2025-04-13</discovery>
       <entry>2025-04-15</entry>
     </dates>
   </vuln>
 
   <vuln vid="0230343c-1908-11f0-accc-b42e991fc52e">
     <topic>gogs -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>gogs</name>
 	<range><lt>0.13.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>cve@mitre.org reports:</p>
 	<blockquote cite="https://fysac.github.io/posts/2024/11/unpatched-remote-code-execution-in-gogs/">
 	<p>CVE-2024-44625: Directory Traversal via the editFilePost
 	function of internal/route/repo/editor.go.</p>
 	<p>CVE-2024-39933: Gogs allows argument injection during the
 	tagging of a new release.</p>
 	<p>CVE-2024-39932: Gogs allows argument injection during the
 	previewing of changes.</p>
 	<p>CVE-2024-39931: Gogs allows deletion of internal files.</p>
 	<p>CVE-2024-39930: The built-in SSH server of Gogs allows
 	argument injection in internal/ssh/ssh.go, leading to remote
 	code execution. Authenticated attackers can exploit this by
 	opening an SSH connection and sending a malicious
 	--split-string env request if the built-in SSH server is
 	activated.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-44625</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-44625</url>
       <cvename>CVE-2024-39933</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-39933</url>
       <cvename>CVE-2024-39932</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-39932</url>
       <cvename>CVE-2024-39931</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-39931</url>
       <cvename>CVE-2024-39930</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-39930</url>
     </references>
     <dates>
       <discovery>2024-11-15</discovery>
       <entry>2025-04-14</entry>
     </dates>
   </vuln>
 
   <vuln vid="ba6361be-1887-11f0-a8ce-b42e991fc52e">
     <topic>Mozilla -- null pointer dereference</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>133.0,2</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>133.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1923767">
 	  <p>A null pointer dereference may have inadvertently
 	  occurred in `pk12util`, and specifically in the
 	  `SEC_ASN1DecodeItem_Util` function, when handling malformed
 	  or improperly formatted input files.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-11706</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-11706</url>
     </references>
     <dates>
       <discovery>2024-11-26</discovery>
       <entry>2025-04-13</entry>
     </dates>
   </vuln>
 
   <vuln vid="b65b1217-1887-11f0-a8ce-b42e991fc52e">
     <topic>mozilla -- double free error</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>133.0,2</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>128.7.0</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>133.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1899402">
 	  <p>A double-free issue could have occurred in
 	  `sec_pkcs7_decoder_start_decrypt()` when handling an error
 	  path. Under specific conditions, the same symmetric key
 	  could have been freed twice, potentially leading to memory
 	  corruption.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-11704</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-11704</url>
     </references>
     <dates>
       <discovery>2024-11-26</discovery>
       <entry>2025-04-13</entry>
     </dates>
   </vuln>
 
   <vuln vid="ed0a052a-c5e6-11ef-a457-b42e991fc52e">
     <topic>Apache Tomcat -- RCE due to TOCTOU issue in JSP compilation</topic>
     <affects>
       <package>
 	<name>tomcat110</name>
 	<range>
 	  <gt>11.0.0</gt>
 	  <lt>11.0.1</lt>
 	</range>
       </package>
       <package>
 	<name>tomcat101</name>
 	<range>
 	  <gt>10.1.0</gt>
 	  <lt>10.1.33</lt>
 	</range>
       </package>
       <package>
 	<name>tomcat9</name>
 	<range>
 	  <gt>9.0.0</gt>
 	  <lt>9.0.97</lt>
 	</range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@apache.org reports:</p>
 	<blockquote cite="https://lists.apache.org/thread/b2b9qrgjrz1kvo4ym8y2wkfdvwoq6qbp">
 	  <p>Time-of-check Time-of-use (TOCTOU) Race Condition
 	The mitigation for CVE-2024-50379 was incomplete.
 	Users running Tomcat on a case insensitive file system with the
 	default servlet write enabled (readonly initialisation parameter
 	set to the non-default value of false) may need additional configuration
 	to fully mitigate CVE-2024-50379 depending on which version of Java
 	they are using with Tomcat: - running on Java 8 or Java 11: the
 	system propertysun.io.useCanonCaches must be explicitly set to false
 	(it defaults to true) - running on Java 17: thesystem property
 	sun.io.useCanonCaches, if set, must be set to false(it defaults to
 	false) - running on Java 21 onwards: no further configuration is
 	required(the system property and the problematic cache have been
 	removed)
 	Tomcat 11.0.3, 10.1.35 and 9.0.99 onwards will include checks
 	thatsun.io.useCanonCaches is set appropriately before allowing the
 	default servlet to be write enabled on a case insensitive file
 	system.  Tomcat will also setsun.io.useCanonCaches to false by
 	default where it can.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-56337</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-56337</url>
     </references>
     <dates>
       <discovery>2024-12-20</discovery>
       <entry>2024-12-29</entry>
     </dates>
   </vuln>
 
   <vuln vid="94b2d58a-c1e9-11ef-aa3f-dcfe074bd614">
     <topic>kanboard -- Insufficient session invalidation</topic>
     <affects>
       <package>
 	<name>kanboard</name>
 	<range><lt>1.2.43</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security-advisories@github.com reports:</p>
 	<blockquote cite="https://github.com/kanboard/kanboard/blob/main/app/Core/Session/SessionHandler.php#L40">
 	  <p>Kanboard is project management software that focuses on the Kanban
 	methodology.  In affected versions sessions are still usable even
 	though their lifetime has exceeded.  Kanboard implements a cutom
 	session handler (`app/Core/Session/SessionHandler.php`), to store
 	the session data in a database.  Therefore, when a `session_id` is
 	given, kanboard queries the data from the `sessions` sql table.  At
 	this point, it does not correctly verify, if a given `session_id`
 	has already exceeded its lifetime (`expires_at`).  Thus, a session
 	which&apos;s lifetime is already `&gt; time()`, is still queried
 	from the database and hence a valid login.  The implemented
 	**SessionHandlerInterface::gc** function, that does remove invalid
 	sessions, is called only **with a certain probability** (_Cleans
 	up expired sessions.  Called by `session_start()`, based on
 	`session.gc_divisor`, `session.gc_probability` and `session.gc_maxlifetime`
 	settings_) accordingly to the php documentation.  In the official
 	Kanboard docker image these values default to: session.gc_probability=1,
 	session.gc_divisor=1000. Thus, an expired session is only terminated
 	with probability 1/1000. There are no known workarounds for
 	this vulnerability.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-55603</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-55603</url>
     </references>
     <dates>
       <discovery>2024-12-19</discovery>
       <entry>2024-12-24</entry>
     </dates>
   </vuln>
 
   <vuln vid="0a8dbc7f-bedc-11ef-b5a1-000ec6d40964">
     <topic>Vaultwarden -- Admin organization permissions</topic>
     <affects>
       <package>
 	<name>vaultwarden</name>
 	<range><lt>1.32.7</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The Vaultwarden project reports:</p>
 	<blockquote cite="https://github.com/dani-garcia/vaultwarden/pull/5291">
 	  <p>Admins from any organization were able to modify or delete groups in any other organization if they know the group's uuid.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <url>https://github.com/dani-garcia/vaultwarden/pull/5291</url>
     </references>
     <dates>
       <discovery>2024-12-20</discovery>
       <entry>2024-12-20</entry>
     </dates>
   </vuln>
 
   <vuln vid="e18c5c8d-be01-11ef-8c1c-a8a1599412c6">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>131.0.6778.204</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>131.0.6778.204</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2024/12/stable-channel-update-for-desktop_18.html">
 	 <p>This update includes 3 security fixes:</p>
 	 <ul>
 	    <li>[382291459] High CVE-2024-12692: Type Confusion in V8. Reported by Seunghyun Lee (@0x10n) on 2024-12-05</li>
 	    <li>[382190919] High CVE-2024-12693: Out of bounds memory access in V8. Reported by 303f06e3 on 2024-12-04</li>
 	    <li>[368222741] High CVE-2024-12694: Use after free in Compositing. Reported by Anonymous on 2024-09-19</li>
 	    <li>[383647255] High CVE-2024-12695: Out of bounds write in V8. Reported by 303f06e3 on 2024-12-12</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-12692</cvename>
       <cvename>CVE-2024-12693</cvename>
       <cvename>CVE-2024-12694</cvename>
       <cvename>CVE-2024-12695</cvename>
       <url>https://chromereleases.googleblog.com/2024/12/stable-channel-update-for-desktop_18.html</url>
     </references>
     <dates>
       <discovery>2024-12-18</discovery>
       <entry>2024-12-19</entry>
     </dates>
   </vuln>
 
   <vuln vid="dc087dad-bd71-11ef-b5a1-000ec6d40964">
     <topic>liboqs -- Correctness error in HQC decapsulation</topic>
     <affects>
       <package>
 	<name>liboqs</name>
 	<range><lt>0.12.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The Open Quantum Safe project reports:</p>
 	<blockquote cite="https://github.com/open-quantum-safe/liboqs/security/advisories/GHSA-gpf4-vrrw-r8v7">
 	  <p>A correctness error has been identified in the reference implementation of the HQC key encapsulation mechanism. Due to an indexing error, part of the secret key is incorrectly treated as non-secret data. This results in an incorrect shared secret value being returned when the decapsulation function is called with a malformed ciphertext.</p>
 	  <p>No concrete attack exploiting the error has been identified at this point. However, the error involves mishandling of the secret key, and in principle this presents a security vulnerability.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-54137</cvename>
       <url>https://github.com/open-quantum-safe/liboqs/security/advisories/GHSA-gpf4-vrrw-r8v7</url>
     </references>
     <dates>
       <discovery>2024-11-29</discovery>
       <entry>2024-12-18</entry>
     </dates>
   </vuln>
 
   <vuln vid="38e6f778-bca3-11ef-8926-9b4f2d14eb53">
     <topic>gitea -- Fix misuse of PublicKeyCallback</topic>
     <affects>
       <package>
 	<name>gitea</name>
 	<range><lt>1.22.6</lt></range>
       </package>
     </affects>
     <description>
        <body xmlns="http://www.w3.org/1999/xhtml">
        <h1>Problem Description:</h1>
        <ul>
        <li>Misuse of ServerConfig.PublicKeyCallback may cause authorization
        bypass in golang.org/x/crypto</li>
        </ul>
       </body>
     </description>
     <references>
       <url>https://github.com/go-gitea/gitea/pull/32810</url>
       <url>https://github.com/advisories/GHSA-v778-237x-gjrc</url>
     </references>
     <dates>
       <discovery>2024-12-12</discovery>
       <entry>2024-12-17</entry>
     </dates>
   </vuln>
 
   <vuln vid="453cd84e-bca4-11ef-8926-9b4f2d14eb53">
     <topic>gitea -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>gitea</name>
 	<range><lt>1.22.5</lt></range>
       </package>
     </affects>
     <description>
        <body xmlns="http://www.w3.org/1999/xhtml">
        <h1>Problem Description:</h1>
        <ul>
        <li>Fix delete branch perm checking</li>
        <li>Upgrade crypto library</li>
        </ul>
       </body>
     </description>
     <references>
       <url>https://github.com/go-gitea/gitea/pull/32791</url>
       <url>https://github.com/go-gitea/gitea/pull/32654</url>
     </references>
     <dates>
       <discovery>2024-11-27</discovery>
       <entry>2024-12-17</entry>
     </dates>
   </vuln>
 
   <vuln vid="6ea20f0c-bca3-11ef-8926-9b4f2d14eb53">
     <topic>gitea -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>gitea</name>
 	<range><lt>1.22.4</lt></range>
       </package>
     </affects>
     <description>
        <body xmlns="http://www.w3.org/1999/xhtml">
        <h1>Problem Description:</h1>
        <ul>
        <li>Fix basic auth with webauthn</li>
        <li>Refactor internal routers (partial backport, auth token const time comparing)</li>
        </ul>
       </body>
     </description>
     <references>
       <url>https://github.com/go-gitea/gitea/pull/32531</url>
       <url>https://github.com/go-gitea/gitea/pull/32473</url>
     </references>
     <dates>
       <discovery>2024-11-16</discovery>
       <entry>2024-12-17</entry>
     </dates>
   </vuln>
 
   <vuln vid="5ca064a6-bca1-11ef-8926-9b4f2d14eb53">
     <topic>forgejo -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>forgejo</name>
 	<range><lt>9.0.2</lt></range>
       </package>
       <package>
 	<name>forgejo7</name>
 	<range><lt>7.0.11</lt></range>
       </package>
     </affects>
     <description>
        <body xmlns="http://www.w3.org/1999/xhtml">
        <h1>Problem Description:</h1>
        <ul>
        <li>It was possible to use a token sent via email for secondary email validation to reset the password instead. In other words, a token sent for a given action (registration, password reset or secondary email validation) could be used to perform a different action. It is no longer possible to use a token for an action that is different from its original purpose.</li>
        <li>A fork of a public repository would show in the list of forks, even if its owner was not a public user or organization. Such a fork is now hidden from the list of forks of the public repository.</li>
        <li>The members of an organization team with read access to a repository (e.g. to read issues) but no read access to the code could read the RSS or atom feeds which include the commit activity. Reading the RSS or atom feeds is now denied unless the team has read permissions on the code.</li>
        <li>The tokens used when replying by email to issues or pull requests were weaker than the rfc2104 recommendations. The tokens are now truncated to 128 bits instead of 80 bits. It is no longer possible to reply to emails sent before the upgrade because the weaker tokens are invalid.</li>
        <li>A registered user could modify the update frequency of any push mirror (e.g. every 4h instead of every 8h). They are now only able to do that if they have administrative permissions on the repository.</li>
        <li>It was possible to use basic authorization (i.e. user:password) for requests to the API even when security keys were enrolled for a user. It is no longer possible, an application token must be used instead.</li>
        <li>Some markup sanitation rules were not as strong as they could be (e.g. allowing emoji somethingelse as well as emoji). The rules are now stricter and do not allow for such cases.</li>
        <li>When Forgejo is configured to enable instance wide search (e.g. with bleve), results found in the repositories of private or limited users were displayed to anonymous visitors. The results found in private or limited organizations were not displayed. The search results found in the repositories of private or limited user are no longer displayed to anonymous visitors.</li>
        </ul>
       </body>
     </description>
     <references>
       <url>https://codeberg.org/forgejo/forgejo/pulls/5974</url>
       <url>https://codeberg.org/forgejo/forgejo/pulls/5974</url>
       <url>https://codeberg.org/forgejo/forgejo/pulls/5974</url>
       <url>https://codeberg.org/forgejo/forgejo/pulls/5974</url>
       <url>https://codeberg.org/forgejo/forgejo/pulls/5974</url>
       <url>https://codeberg.org/forgejo/forgejo/pulls/5974</url>
       <url>https://codeberg.org/forgejo/forgejo/pulls/5974</url>
       <url>https://codeberg.org/forgejo/forgejo/pulls/5974</url>
     </references>
     <dates>
       <discovery>2024-12-12</discovery>
       <entry>2024-12-17</entry>
       <modified>2024-12-18</modified>
     </dates>
   </vuln>
 
   <vuln vid="25a697de-bca1-11ef-8926-9b4f2d14eb53">
     <topic>forgejo -- unauthorized user impersonation</topic>
     <affects>
       <package>
 	<name>forgejo</name>
 	<range><lt>7.0.12</lt></range>
       </package>
     </affects>
     <description>
        <body xmlns="http://www.w3.org/1999/xhtml">
        <h1>Problem Description:</h1>
        <ul>
        <li>When Forgejo is configured to run the internal ssh server with
        [server].START_SSH_SERVER=true, it was possible for a registered user
        to impersonate another user.  The rootless container image uses the
        internal ssh server by default and was vulnerable.  A Forgejo
        instance running from a binary or from a root container image does
        not use the internal ssh server by default and was not vulnerable.
        The incorrect use of the crypto package is the root cause of the
        vulnerability and was fixed for the internal ssh server.</li>
        <li>Revert "allow synchronizing user status from OAuth2 login
        providers"</li>
        </ul>
       </body>
     </description>
     <references>
       <url>https://codeberg.org/forgejo/forgejo/pulls/6248</url>
     </references>
     <dates>
       <discovery>2024-12-12</discovery>
       <entry>2024-12-17</entry>
     </dates>
   </vuln>
 
   <vuln vid="6dcf6fc6-bca0-11ef-8926-9b4f2d14eb53">
     <topic>forgejo -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>forgejo</name>
 	<range><lt>9.0.3</lt></range>
       </package>
     </affects>
     <description>
        <body xmlns="http://www.w3.org/1999/xhtml">
        <h1>Problem Description:</h1>
        <ul>
        <li>When Forgejo is configured to run the internal ssh server with
        [server].START_SSH_SERVER=true, it was possible for a registered user
        to impersonate another user.  The rootless container image uses the
        internal ssh server by default and was vulnerable.  A Forgejo
        instance running from a binary or from a root container image does
        not use the internal ssh server by default and was not vulnerable.
        The incorrect use of the crypto package is the root cause of the
        vulnerability and was fixed for the internal ssh server.</li>
        <li>Revert "allow synchronizing user status from OAuth2 login
        providers"</li>
        </ul>
       </body>
     </description>
     <references>
       <url>https://codeberg.org/forgejo/forgejo/pulls/6248</url>
       <url>https://codeberg.org/forgejo/forgejo/pulls/6249</url>
     </references>
     <dates>
       <discovery>2024-12-12</discovery>
       <entry>2024-12-17</entry>
     </dates>
   </vuln>
 
   <vuln vid="71f3e9f0-bafc-11ef-885d-901b0e934d69">
     <topic>py-matrix-synapse -- multiple vulnerabilities in versions prior to 1.120.1</topic>
     <affects>
       <package>
 	<name>py38-matrix-synapse</name>
 	<name>py39-matrix-synapse</name>
 	<name>py310-matrix-synapse</name>
 	<name>py311-matrix-synapse</name>
 	<range><lt>1.120.1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 		<p>element-hq/synapse developers report:</p>
 	<blockquote cite="https://github.com/element-hq/synapse/releases/tag/v1.120.2">
 		<p>[The 1.120.1] release fixes multiple security
 		vulnerabilities, some affecting all prior versions of
 		Synapse. Server administrators are encouraged to
 		update Synapse as soon as possible. We are not aware
 		of these vulnerabilities being exploited in the
 		wild.</p>
 		<p>Administrators who are unable to update Synapse may
 		use the workarounds described in the linked GitHub
 		Security Advisory below.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-52805</cvename>
       <url>https://github.com/element-hq/synapse/security/advisories/GHSA-rfq8-j7rh-8hf2</url>
       <cvename>CVE-2024-52815</cvename>
       <url>https://github.com/element-hq/synapse/security/advisories/GHSA-f3r3-h2mq-hx2h</url>
       <cvename>CVE-2024-53863</cvename>
       <url>https://github.com/element-hq/synapse/security/advisories/GHSA-vp6v-whfm-rv3g</url>
       <cvename>CVE-2024-53867</cvename>
       <url>https://github.com/element-hq/synapse/security/advisories/GHSA-56w4-5538-8v8h</url>
       <cvename>CVE-2024-37302</cvename>
       <url>https://github.com/element-hq/synapse/security/advisories/GHSA-4mhg-xv73-xq2x</url>
       <cvename>CVE-2024-37303</cvename>
       <url>https://github.com/element-hq/synapse/security/advisories/GHSA-gjgr-7834-rhxr</url>
     </references>
     <dates>
       <discovery>2024-12-03</discovery>
       <entry>2024-12-15</entry>
     </dates>
   </vuln>
 
   <vuln vid="ef56065e-81fe-4731-a1e3-606c55925bef">
     <topic>zeek -- potential DoS vulnerability</topic>
     <affects>
       <package>
 	<name>zeek</name>
 	<range><lt>7.0.5</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Tim Wojtulewicz of Corelight reports:</p>
 	<blockquote cite="https://github.com/zeek/zeek/releases/tag/v7.0.5">
 	  <p> Large QUIC packets can cause Zeek to overflow memory
 	  and potentially crash. Due to the possibility of receiving
 	  these packets from remote hosts, this is a DoS risk. </p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <url>https://github.com/zeek/zeek/releases/tag/v7.0.5</url>
     </references>
     <dates>
       <discovery>2024-12-16</discovery>
       <entry>2024-12-16</entry>
     </dates>
   </vuln>
 
   <vuln vid="275ac414-b847-11ef-9877-2cf05da270f3">
     <topic>Gitlab -- Vulnerabilities</topic>
     <affects>
       <package>
 	<name>gitlab-ce</name>
 	<name>gitlab-ee</name>
 	<range><ge>17.6.0</ge><lt>17.6.2</lt></range>
 	<range><ge>17.5.0</ge><lt>17.5.4</lt></range>
 	<range><ge>9.4.0</ge><lt>17.4.6</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Gitlab reports:</p>
 	<blockquote cite="https://about.gitlab.com/releases/2024/12/11/patch-release-gitlab-17-6-2-released/">
 	  <p>Injection of Network Error Logging (NEL) headers in kubernetes proxy response could lead to ATO abusing OAuth flows</p>
 	  <p>Denial of Service by repeatedly sending unauthenticated requests for diff-files</p>
 	  <p>CI_JOB_TOKEN could be used to obtain GitLab session</p>
 	  <p>Open redirect in releases API</p>
 	  <p>Client-Side Path Traversal in Harbor artifact links</p>
 	  <p>HTML injection in vulnerability details could lead to Cross Site Scripting</p>
 	  <p>Leak branch names of projects with confidential repository</p>
 	  <p>Non member can view unresolved threads marked as internal notes</p>
 	  <p>Uncontrolled Resource Consumption through a maliciously crafted file</p>
 	  <p>Certain sensitive information passed as literals inside GraphQL mutations retained in GraphQL logs</p>
 	  <p>Information disclosure of confidential incidents details to a group member in Gitlab Wiki</p>
 	  <p>Domain Confusion in GitLab Pages Unique Domain Implementation</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-11274</cvename>
       <cvename>CVE-2024-8233</cvename>
       <cvename>CVE-2024-9387</cvename>
       <cvename>CVE-2024-8647</cvename>
       <cvename>CVE-2024-8179</cvename>
       <cvename>CVE-2024-8116</cvename>
       <cvename>CVE-2024-8650</cvename>
       <cvename>CVE-2024-9367</cvename>
       <cvename>CVE-2024-12292</cvename>
       <cvename>CVE-2024-12292</cvename>
       <cvename>CVE-2024-10043</cvename>
       <url>https://about.gitlab.com/releases/2024/12/11/patch-release-gitlab-17-6-2-released/</url>
     </references>
     <dates>
       <discovery>2024-12-11</discovery>
       <entry>2024-12-12</entry>
     </dates>
   </vuln>
 
   <vuln vid="aeee5ebd-356c-49c1-8959-7c88981de5fd">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>131.0.6778.139</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>131.0.6778.139</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2024/12/stable-channel-update-for-desktop_10.html">
 	 <p>This update includes 3 security fixes:</p>
 	 <ul>
 	    <li>[381696874] High CVE-2024-12381: Type Confusion in V8. Reported by Seunghyun Lee (@0x10n) on 2024-12-02</li>
 	    <li>[379516109] High CVE-2024-12382: Use after free in Translate. Reported by lime(@limeSec_) from TIANGONG Team of Legendsec at QI-ANXIN Group on 2024-11-18</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-12381</cvename>
       <cvename>CVE-2024-12382</cvename>
       <url>https://chromereleases.googleblog.com/2024/12/stable-channel-update-for-desktop_10.html</url>
     </references>
     <dates>
       <discovery>2024-12-10</discovery>
       <entry>2024-12-11</entry>
     </dates>
   </vuln>
 
   <vuln vid="3d5b7860-48ad-48c2-aa36-601b8ab9cc43">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>131.0.6778.108</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>131.0.6778.108</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2024/12/stable-channel-update-for-desktop.html">
 	 <p>This update includes 4 security fixes:</p>
 	 <ul>
 	    <li>[379009132] High CVE-2024-12053: Type Confusion in V8. Reported by gal1ium and chluo on 2024-11-14</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-12053</cvename>
       <url>https://chromereleases.googleblog.com/2024/12/stable-channel-update-for-desktop.html</url>
     </references>
     <dates>
       <discovery>2024-12-03</discovery>
       <entry>2024-12-11</entry>
     </dates>
   </vuln>
 
   <vuln vid="0e20e42c-b728-11ef-805a-b42e991fc52e">
     <topic>firefox -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>133.0.0,2</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>128.5,1</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>128.5</lt></range>
 	<range><ge>129</ge><lt>133</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1929600">
 	<ul>
 	<li>CVE-2024-11692: An attacker could cause a select dropdown
 	to be shown over another tab; this could have led to user
 	confusion and possible spoofing attacks.</li>
 	<li>CVE-2024-11696: The application failed to account for
 	exceptions thrown by the `loadManifestFromFile` method during
 	add-on signature verification.  This flaw, triggered by an
 	invalid or unsupported extension manifest, could have caused
 	runtime errors that disrupted the signature validation process.
 	As a result, the enforcement of signature validation for
 	unrelated add-ons may have been bypassed.  Signature validation
 	in this context is used to ensure that third-party
 	applications on the user&apos;s computer have not tampered
 	with the user&apos;s extensions, limiting the impact of this
 	issue.</li>
 	<li>CVE-2024-11697: When handling keypress events, an attacker
 	may have been able to trick a user into bypassing the &quot;
 	Open Executable File?&quot; confirmation dialog.  This could
 	have led to malicious code execution.</li>
 	<li>CVE-2024-11699: Memory safety bugs present in Firefox 132,
 	Firefox ESR 128.4, and Thunderbird 128.4.  Some of these bugs
 	showed evidence of memory corruption and we presume that with
 	enough effort some of these could have been exploited to run
 	arbitrary code.</li>
 	</ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-11692</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-11692</url>
       <cvename>CVE-2024-11696</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-11696</url>
       <cvename>CVE-2024-11697</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-11697</url>
       <cvename>CVE-2024-11699</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-11699</url>
     </references>
     <dates>
       <discovery>2024-11-26</discovery>
       <entry>2024-12-10</entry>
     </dates>
   </vuln>
 
   <vuln vid="c2fd83e4-b450-11ef-b680-4ccc6adda413">
     <topic>qt6-webengine -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>qt6-webengine</name>
 	<range><lt>6.7.3_3</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Qt qtwebengine-chromium repo reports:</p>
 	<blockquote cite="https://code.qt.io/cgit/qt/qtwebengine-chromium.git/log/?h=118-based">
 	  <p>Backports for 5 security bugs in Chromium:</p>
 	  <ul>
 	    <li>CVE-2024-11110: Inappropriate implementation in Blink</li>
 	    <li>CVE-2024-11112: Use after free in Media</li>
 	    <li>CVE-2024-11114: Inappropriate implementation in Views</li>
 	    <li>CVE-2024-11116: Inappropriate implementation in Paint</li>
 	    <li>CVE-2024-11117: Inappropriate implementation in FileSystem</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-11110</cvename>
       <cvename>CVE-2024-11112</cvename>
       <cvename>CVE-2024-11114</cvename>
       <cvename>CVE-2024-11116</cvename>
       <cvename>CVE-2024-11117</cvename>
       <url>https://code.qt.io/cgit/qt/qtwebengine-chromium.git/log/?h=118-based</url>
     </references>
     <dates>
       <discovery>2024-11-29</discovery>
       <entry>2024-12-07</entry>
     </dates>
   </vuln>
 
   <vuln vid="7f3a302b-b3e8-11ef-b680-4ccc6adda413">
     <topic>gstreamer1-plugins-vorbis -- Stack buffer-overflow in Vorbis decoder</topic>
     <affects>
       <package>
 	<name>gstreamer1-plugins-vorbis</name>
 	<range><lt>1.24.10</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The GStreamer Security Center reports:</p>
 	<blockquote cite="https://gstreamer.freedesktop.org/security/">
 	  <p>Stack buffer-overflow in Vorbis decoder that can cause crashes for
 	    certain input files.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-47538</cvename>
       <url>https://gstreamer.freedesktop.org/security/sa-2024-0022.html</url>
     </references>
     <dates>
       <discovery>2024-12-03</discovery>
       <entry>2024-12-06</entry>
     </dates>
   </vuln>
 
   <vuln vid="7d1b4e5d-b3e8-11ef-b680-4ccc6adda413">
     <topic>gstreamer1-plugins-opus -- Stack buffer-overflow in Opus decoder</topic>
     <affects>
       <package>
 	<name>gstreamer1-plugins-opus</name>
 	<range><lt>1.24.10</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The GStreamer Security Center reports:</p>
 	<blockquote cite="https://gstreamer.freedesktop.org/security/">
 	  <p>Stack buffer-overflow in Opus decoder that can cause crashes for
 	    certain input files.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-47607</cvename>
       <url>https://gstreamer.freedesktop.org/security/sa-2024-0024.html</url>
     </references>
     <dates>
       <discovery>2024-12-03</discovery>
       <entry>2024-12-06</entry>
     </dates>
   </vuln>
 
   <vuln vid="7b34ddf7-b3e8-11ef-b680-4ccc6adda413">
     <topic>gstreamer1-plugins-ogg -- Out-of-bounds write in Ogg demuxer</topic>
     <affects>
       <package>
 	<name>gstreamer1-plugins-ogg</name>
 	<range><lt>1.24.10</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The GStreamer Security Center reports:</p>
 	<blockquote cite="https://gstreamer.freedesktop.org/security/">
 	  <p>An out-of-bounds write in the Ogg demuxer that can cause crashes
 	    for certain input files.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-47615</cvename>
       <url>https://gstreamer.freedesktop.org/security/sa-2024-0026.html</url>
     </references>
     <dates>
       <discovery>2024-12-03</discovery>
       <entry>2024-12-06</entry>
     </dates>
   </vuln>
 
   <vuln vid="7945c543-b3e8-11ef-b680-4ccc6adda413">
     <topic>gstreamer1-plugins-jpeg -- NULL-pointer dereferences in JPEG decoder</topic>
     <affects>
       <package>
 	<name>gstreamer1-plugins-jpeg</name>
 	<range><lt>1.24.10</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The GStreamer Security Center reports:</p>
 	<blockquote cite="https://gstreamer.freedesktop.org/security/">
 	  <p>Insufficient error handling in the JPEG decoder that can lead to
 	    NULL-pointer dereferences, and that can cause crashes for certain
 	    input files.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-47599</cvename>
       <url>https://gstreamer.freedesktop.org/security/sa-2024-0016.html</url>
     </references>
     <dates>
       <discovery>2024-12-03</discovery>
       <entry>2024-12-06</entry>
     </dates>
   </vuln>
 
   <vuln vid="772d8625-b3e8-11ef-b680-4ccc6adda413">
     <topic>gstreamer1-plugins-gdkpixbuf -- NULL-pointer dereference</topic>
     <affects>
       <package>
 	<name>gstreamer1-plugins-gdkpixbuf</name>
 	<range><lt>1.24.10</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The GStreamer Security Center reports:</p>
 	<blockquote cite="https://gstreamer.freedesktop.org/security/">
 	  <p>A NULL-pointer dereference in the gdk-pixbuf decoder that can
 	    cause crashes for certain input files.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-47613</cvename>
       <url>https://gstreamer.freedesktop.org/security/sa-2024-0025.html</url>
     </references>
     <dates>
       <discovery>2024-12-03</discovery>
       <entry>2024-12-06</entry>
     </dates>
   </vuln>
 
   <vuln vid="750ab972-b3e8-11ef-b680-4ccc6adda413">
     <topic>gstreamer1-plugins-good -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>gstreamer1-plugins-good</name>
 	<range><lt>1.24.10</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The GStreamer Security Center reports:</p>
 	<blockquote cite="https://gstreamer.freedesktop.org/security/">
 	  <p>20 security bugs.</p>
 	  <ul>
 	    <li>CVE-2024-47537: Integer overflow in MP4/MOV sample table parser leading to out-of-bounds writes</li>
 	    <li>CVE-2024-47598: MP4/MOV sample table parser out-of-bounds read</li>
 	    <li>CVE-2024-47539: MP4/MOV Closed Caption handling out-of-bounds write</li>
 	    <li>CVE-2024-47543: MP4/MOV demuxer out-of-bounds read</li>
 	    <li>CVE-2024-47545: Integer overflow in MP4/MOV demuxer that can result in out-of-bounds read</li>
 	    <li>CVE-2024-47544: NULL-pointer dereferences in MP4/MOV demuxer CENC handling</li>
 	    <li>CVE-2024-47597: Out-of-bounds reads in MP4/MOV demuxer sample table parser</li>
 	    <li>CVE-2024-47546: Integer underflow in MP4/MOV demuxer that can lead to out-of-bounds reads</li>
 	    <li>CVE-2024-47606: Integer overflows in MP4/MOV demuxer and memory allocator that can lead to out-of-bounds writes</li>
 	    <li>CVE-2024-47596: Integer underflow in MP4/MOV demuxer that can lead to out-of-bounds reads</li>
 	    <li>CVE-2024-47540: Usage of uninitialized stack memory in Matroska/WebM demuxer</li>
 	    <li>CVE-2024-47602: NULL-pointer dereferences and out-of-bounds reads in Matroska/WebM demuxer</li>
 	    <li>CVE-2024-47601: NULL-pointer dereference in Matroska/WebM demuxer</li>
 	    <li>CVE-2024-47603: NULL-pointer dereference in Matroska/WebM demuxer</li>
 	    <li>CVE-2024-47775: Out-of-bounds read in WAV parser</li>
 	    <li>CVE-2024-47776: Out-of-bounds read in WAV parser</li>
 	    <li>CVE-2024-47777: Out-of-bounds read in WAV parser</li>
 	    <li>CVE-2024-47778: Out-of-bounds read in WAV parser</li>
 	    <li>CVE-2024-47774: Integer overflow in AVI subtitle parser that leads to out-of-bounds reads</li>
 	    <li>CVE-2024-47834: Use-after-free in Matroska demuxer</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-47537</cvename>
       <url>https://gstreamer.freedesktop.org/security/sa-2024-0005.html</url>
       <cvename>CVE-2024-47598</cvename>
       <url>https://gstreamer.freedesktop.org/security/sa-2024-0006.html</url>
       <cvename>CVE-2024-47539</cvename>
       <url>https://gstreamer.freedesktop.org/security/sa-2024-0007.html</url>
       <cvename>CVE-2024-47543</cvename>
       <url>https://gstreamer.freedesktop.org/security/sa-2024-0009.html</url>
       <cvename>CVE-2024-47545</cvename>
       <url>https://gstreamer.freedesktop.org/security/sa-2024-0010.html</url>
       <cvename>CVE-2024-47544</cvename>
       <url>https://gstreamer.freedesktop.org/security/sa-2024-0011.html</url>
       <cvename>CVE-2024-47597</cvename>
       <url>https://gstreamer.freedesktop.org/security/sa-2024-0012.html</url>
       <cvename>CVE-2024-47546</cvename>
       <url>https://gstreamer.freedesktop.org/security/sa-2024-0013.html</url>
       <cvename>CVE-2024-47606</cvename>
       <url>https://gstreamer.freedesktop.org/security/sa-2024-0014.html</url>
       <cvename>CVE-2024-47596</cvename>
       <url>https://gstreamer.freedesktop.org/security/sa-2024-0015.html</url>
       <cvename>CVE-2024-47540</cvename>
       <url>https://gstreamer.freedesktop.org/security/sa-2024-0017.html</url>
       <cvename>CVE-2024-47602</cvename>
       <url>https://gstreamer.freedesktop.org/security/sa-2024-0019.html</url>
       <cvename>CVE-2024-47601</cvename>
       <url>https://gstreamer.freedesktop.org/security/sa-2024-0020.html</url>
       <cvename>CVE-2024-47603</cvename>
       <url>https://gstreamer.freedesktop.org/security/sa-2024-0021.html</url>
       <cvename>CVE-2024-47775</cvename>
       <url>https://gstreamer.freedesktop.org/security/sa-2024-0027.html</url>
       <cvename>CVE-2024-47776</cvename>
       <url>https://gstreamer.freedesktop.org/security/sa-2024-0027.html</url>
       <cvename>CVE-2024-47777</cvename>
       <url>https://gstreamer.freedesktop.org/security/sa-2024-0027.html</url>
       <cvename>CVE-2024-47778</cvename>
       <url>https://gstreamer.freedesktop.org/security/sa-2024-0027.html</url>
       <cvename>CVE-2024-47835</cvename>
       <url>https://gstreamer.freedesktop.org/security/sa-2024-0028.html</url>
       <cvename>CVE-2024-47834</cvename>
       <url>https://gstreamer.freedesktop.org/security/sa-2024-0030.html</url>
     </references>
     <dates>
       <discovery>2024-12-03</discovery>
       <entry>2024-12-06</entry>
     </dates>
   </vuln>
 
   <vuln vid="7256fae8-b3e8-11ef-b680-4ccc6adda413">
     <topic>gstreamer1-plugins -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>gstreamer1-plugins</name>
 	<range><lt>1.24.10</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The GStreamer Security Center reports:</p>
 	<blockquote cite="https://gstreamer.freedesktop.org/security/">
 	  <p>3 security bugs.</p>
 	  <ul>
 	    <li>CVE-2024-47542: ID3v2 parser out-of-bounds read and NULL-pointer dereference</li>
 	    <li>CVE-2024-47600: Out-of-bounds read in gst-discoverer-1.0 commandline tool</li>
 	    <li>CVE-2024-47541: Out-of-bounds write in SSA subtitle parser</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-47542</cvename>
       <url>https://gstreamer.freedesktop.org/security/sa-2024-0008.html</url>
       <cvename>CVE-2024-47600</cvename>
       <url>https://gstreamer.freedesktop.org/security/sa-2024-0018.html</url>
       <cvename>CVE-2024-47541</cvename>
       <url>https://gstreamer.freedesktop.org/security/sa-2024-0023.html</url>
     </references>
     <dates>
       <discovery>2024-12-03</discovery>
       <entry>2024-12-06</entry>
     </dates>
   </vuln>
 
   <vuln vid="f0d33375-b0e0-11ef-a724-b42e991fc52e">
     <topic>zabbix -- SQL injection in user.get API</topic>
     <affects>
       <package>
 	<name>zabbix6-frontend</name>
 	<range><lt>6.0.31</lt></range>
       </package>
       <package>
 	<name>zabbix64-frontend</name>
 	<range><lt>6.4.16</lt></range>
       </package>
       <package>
 	<name>zabbix7-frontend</name>
 	<range><lt>7.0.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@zabbix.com reports:</p>
 	<blockquote cite="https://support.zabbix.com/browse/ZBX-25623">
 	  <p>A non-admin user account on the Zabbix frontend with the default
 	User role, or with any other role that gives API access can exploit
 	this vulnerability.  An SQLi exists in the CUser class in the
 	addRelatedObjects function, this function is being called from the
 	CUser.get function which is available for every user who has API
 	access.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-42327</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-42327</url>
     </references>
     <dates>
       <discovery>2024-11-27</discovery>
       <entry>2024-12-02</entry>
     </dates>
   </vuln>
 
   <vuln vid="8b6e97a9-804e-4366-9f75-d102b22a716d">
     <topic>electron33 -- Inappropriate implementation in Extensions</topic>
     <affects>
       <package>
 	<name>electron33</name>
 	<range><lt>33.2.1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Electron developers report:</p>
 	<blockquote cite="https://github.com/electron/electron/releases/tag/v33.2.1">
 	  <p>This update fixes the following vulnerability:</p>
 	  <ul>
 	    <li>Security: backported fix for CVE-2024-11110.</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-11110</cvename>
       <url>https://github.com/advisories/GHSA-4mww-gp9h-h59m</url>
     </references>
     <dates>
       <discovery>2024-11-27</discovery>
       <entry>2024-12-02</entry>
     </dates>
   </vuln>
 
   <vuln vid="c5dafd73-adfd-11ef-af27-00e081b7aa2d">
     <topic>jenkins -- Denial of service vulnerability in bundled json-lib</topic>
     <affects>
       <package>
 	<name>jenkins</name>
 	<range><lt>2.487</lt></range>
       </package>
       <package>
 	<name>jenkins-lts</name>
 	<range><lt>2.479.2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Jenkins Security Advisory:</p>
 	<blockquote cite="https://www.jenkins.io/security/advisory/2024-11-27/">
 	  <h1>Description</h1>
 	  <h5>(High) SECURITY-3463 / CVE-2024-47855</h5>
 	  <p>Denial of service vulnerability in bundled json-lib</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-47855</cvename>
       <url>https://www.jenkins.io/security/advisory/2024-11-27/</url>
     </references>
     <dates>
       <discovery>2024-11-27</discovery>
       <entry>2024-11-29</entry>
     </dates>
   </vuln>
 
   <vuln vid="7d7a28cd-7f5a-450a-852f-c49aaab3fa7e">
     <topic>keycloak -- Multiple security fixes</topic>
     <affects>
       <package>
 	<name>keycloak</name>
 	<range><lt>26.0.6</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Keycloak reports:</p>
 	<blockquote cite="https://www.keycloak.org/2024/11/keycloak-2606-released.html">
 	  <p>This update includes 5 security fixes:</p>
 	  <ul>
 	    <li>CVE-2024-10451: Sensitive Data Exposure in Keycloak Build Process</li>
 	    <li>CVE-2024-10270: Potential Denial of Service</li>
 	    <li>CVE-2024-10492: Keycloak path trasversal</li>
 	    <li>CVE-2024-9666: Keycloak proxy header handling Denial-of-Service (DoS) vulnerability</li>
 	    <li>CVE-2024-10039: Bypassing mTLS validation</li>
 	  </ul>
 	</blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2021-9666</cvename>
       <cvename>CVE-2021-10039</cvename>
       <cvename>CVE-2021-10270</cvename>
       <cvename>CVE-2021-10451</cvename>
       <cvename>CVE-2021-10492</cvename>
     </references>
     <dates>
       <discovery>2024-11-22</discovery>
       <entry>2024-11-25</entry>
     </dates>
   </vuln>
 
   <vuln vid="2263ea04-ac81-11ef-998c-2cf05da270f3">
     <topic>Gitlab -- vulnerabilities</topic>
     <affects>
       <package>
 	<name>gitlab-ce</name>
 	<name>gitlab-ee</name>
 	<range><ge>17.6.0</ge><lt>17.6.1</lt></range>
 	<range><ge>17.5.0</ge><lt>17.5.3</lt></range>
 	<range><ge>8.12.0</ge><lt>17.4.5</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Gitlab reports:</p>
 	<blockquote cite="https://about.gitlab.com/releases/2024/11/26/patch-release-gitlab-17-6-1-released/">
 	  <p>Privilege Escalation via LFS Tokens</p>
 	  <p>DoS through uncontrolled resource consumption when viewing a maliciously crafted cargo.toml file</p>
 	  <p>Unintended Access to Usage Data via Scoped Tokens</p>
 	  <p>Gitlab DOS via Harbor registry integration</p>
 	  <p>Resource exhaustion and denial of service with test_report API calls</p>
 	  <p>Streaming endpoint did not invalidate tokens after revocation</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-8114</cvename>
       <cvename>CVE-2024-8237</cvename>
       <cvename>CVE-2024-11669</cvename>
       <cvename>CVE-2024-8177</cvename>
       <cvename>CVE-2024-11828</cvename>
       <cvename>CVE-2024-11668</cvename>
       <url>https://about.gitlab.com/releases/2024/11/26/patch-release-gitlab-17-6-1-released/</url>
     </references>
     <dates>
       <discovery>2024-11-26</discovery>
       <entry>2024-11-27</entry>
     </dates>
   </vuln>
 
   <vuln vid="9dfca0cd-ab09-11ef-8c1c-a8a1599412c6">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>131.0.6778.85</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>131.0.6778.85</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2024/11/stable-channel-update-for-desktop_19.html">
 	 <p>This update includes 3 security fixes:</p>
 	 <ul>
 	    <li>[377384894] High CVE-2024-11395: Type Confusion in V8. Reported by Anonymous on 2024-11-05</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-11395</cvename>
       <url>https://chromereleases.googleblog.com/2024/11/stable-channel-update-for-desktop_19.html</url>
     </references>
     <dates>
       <discovery>2024-11-19</discovery>
       <entry>2024-11-25</entry>
     </dates>
   </vuln>
 
   <vuln vid="889eddee-a964-11ef-b680-4ccc6adda413">
     <topic>qt6-webengine -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>qt6-webengine</name>
 	<range><lt>6.7.3_2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Qt qtwebengine-chromium repo reports:</p>
 	<blockquote cite="https://code.qt.io/cgit/qt/qtwebengine-chromium.git/log/?h=118-based">
 	  <p>Backports for 16 security bugs in Chromium:</p>
 	  <ul>
 	    <li>CVE-2024-9120: Use after free in Dawn</li>
 	    <li>CVE-2024-9122: Type Confusion in V8</li>
 	    <li>CVE-2024-9123: Integer overflow in Skia</li>
 	    <li>CVE-2024-9369: Insufficient data validation in Mojo</li>
 	    <li>CVE-2024-9602: Type confusion in V8</li>
 	    <li>CVE-2024-9603: Type confusion in V8</li>
 	    <li>CVE-2024-9965: Insufficient data validation in DevTools</li>
 	    <li>CVE-2024-9966: Inappropriate implementation in Navigations</li>
 	    <li>CVE-2024-10229: Inappropriate implementation in Extensions</li>
 	    <li>CVE-2024-10230: Type confusion in V8</li>
 	    <li>CVE-2024-10231: Type confusion in V8</li>
 	    <li>CVE-2024-10487: Out of bounds write in Dawn</li>
 	    <li>CVE-2024-10827: Use after free in Serial</li>
 	    <li>CVE-2024-45490: Negative length in libexpat</li>
 	    <li>CVE-2024-45491: Integer overflow in libexpat</li>
 	    <li>CVE-2024-45492: Integer overflow in libexpat</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-9120</cvename>
       <cvename>CVE-2024-9122</cvename>
       <cvename>CVE-2024-9123</cvename>
       <cvename>CVE-2024-9369</cvename>
       <cvename>CVE-2024-9602</cvename>
       <cvename>CVE-2024-9603</cvename>
       <cvename>CVE-2024-9965</cvename>
       <cvename>CVE-2024-9966</cvename>
       <cvename>CVE-2024-10229</cvename>
       <cvename>CVE-2024-10230</cvename>
       <cvename>CVE-2024-10231</cvename>
       <cvename>CVE-2024-10487</cvename>
       <cvename>CVE-2024-10827</cvename>
       <cvename>CVE-2024-45490</cvename>
       <cvename>CVE-2024-45491</cvename>
       <cvename>CVE-2024-45492</cvename>
       <url>https://code.qt.io/cgit/qt/qtwebengine-chromium.git/log/?h=118-based</url>
     </references>
     <dates>
       <discovery>2024-09-26</discovery>
       <entry>2024-11-23</entry>
     </dates>
   </vuln>
 
   <vuln vid="16e472d5-a8aa-11ef-b680-4ccc6adda413">
     <topic>qt5-webengine -- Use after free in Serial</topic>
     <affects>
       <package>
 	<name>qt5-webengine</name>
 	<range><lt>5.15.18p5</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Qt qtwebengine-chromium repo reports:</p>
 	<blockquote cite="https://code.qt.io/cgit/qt/qtwebengine-chromium.git/log/?h=87-based">
 	  <p>Backports for 1 security bug in Chromium:</p>
 	  <ul>
 	    <li>CVE-2024-10827: Use after free in Serial</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-10827</cvename>
       <url>https://code.qt.io/cgit/qt/qtwebengine-chromium.git/log/?h=87-based</url>
     </references>
     <dates>
       <discovery>2024-10-24</discovery>
       <entry>2024-11-22</entry>
     </dates>
   </vuln>
 
   <vuln vid="141f2a22-a6a7-11ef-b282-0c9d92850f7a">
     <topic>xorg server -- _XkbSetCompatMap vulnerability</topic>
     <affects>
       <package>
 	<name>xorg-server</name>
 	<range><lt>21.1.14,1</lt></range>
       </package>
       <package>
 	<name>xwayland</name>
 	<range><lt>24.1.4,1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The X.Org project reports:</p>
 	<blockquote cite="https://lists.x.org/archives/xorg-announce/2024-October/003545.html">
 	  <ul>
 	    <li>
 	      CVE-2024-9632: Heap buffer Heap-based buffer overflow
 		privilege escalation in _XkbSetCompatMap
 
 	      <p>The _XkbSetCompatMap() function attempts to resize
 		the `sym_interpret` buffer.
 
 		However, It didn't update its size properly.
 		It updated `num_si` only, without updating `size_si`.
 
 		This may lead to local privilege escalation if the
 		server is run as root or remote code execution
 		(e.g. x11 over ssh).</p>
 	    </li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-9632</cvename>
       <url>https://lists.x.org/archives/xorg-announce/2024-October/003545.html</url>
     </references>
     <dates>
       <discovery>2024-10-29</discovery>
       <entry>2024-11-19</entry>
     </dates>
   </vuln>
 
   <vuln vid="28ffa931-a510-11ef-8109-b42e991fc52e">
     <topic>mongodb -- Buffer over-reads in MongoDB Server</topic>
     <affects>
       <package>
 	<name>mongodb50</name>
 	<range><lt>5.0.30</lt></range>
       </package>
       <package>
 	<name>mongodb60</name>
 	<range><lt>6.0.19</lt></range>
       </package>
       <package>
 	<name>mongodb70</name>
 	<range><lt>7.0.15</lt></range>
       </package>
       <package>
 	<name>mongodb80</name>
 	<range><lt>8.0.2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>cna@mongodb.com reports:</p>
 	<blockquote cite="https://jira.mongodb.org/browse/SERVER-96419">
 	  <p>An authorized user may trigger crashes or receive the contents of
 	buffer over-reads of Server memory by issuing specially crafted
 	requests that construct malformed BSON in the MongoDB Server.
 	</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-10921</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-10921</url>
     </references>
     <dates>
       <discovery>2024-11-14</discovery>
       <entry>2024-11-17</entry>
     </dates>
   </vuln>
 
   <vuln vid="efd4537e-a5e8-11ef-bedb-180373b66b37">
     <topic>Vaultwarden -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>vaultwarden</name>
 	<range><lt>1.32.5</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The Vaultwarden project reports:</p>
 	<blockquote cite="https://github.com/dani-garcia/vaultwarden/releases/tag/1.32.5">
 	  <p>This release further fixed some CVE Reports reported by a third
 	  party security auditor and we recommend everybody to update to the
 	  latest version as soon as possible.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <url>https://github.com/dani-garcia/vaultwarden/releases/tag/1.32.5</url>
     </references>
     <dates>
       <discovery>2024-11-11</discovery>
       <entry>2024-11-18</entry>
     </dates>
   </vuln>
 
   <vuln vid="aba28514-a414-11ef-98e7-84a93843eb75">
     <topic>Vaultwarden -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>vaultwarden</name>
 	<range><lt>1.32.4</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The Vaultwarden project reports:</p>
 	<blockquote cite="https://github.com/dani-garcia/vaultwarden/releases/tag/1.32.4">
 	  <p>This release has fixed some CVE Reports reported by a third party
 	    security auditor and we recommend everybody to update to the
 	    latest version as soon as possible.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <url>https://github.com/dani-garcia/vaultwarden/releases/tag/1.32.4</url>
     </references>
     <dates>
       <discovery>2024-11-10</discovery>
       <entry>2024-11-16</entry>
     </dates>
   </vuln>
 
   <vuln vid="8fe4f296-a3ec-11ef-8c1c-a8a1599412c6">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>131.0.6778.69</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>131.0.6778.69</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2024/11/stable-channel-update-for-desktop_12.html">
 	 <p>This update includes 12 security fixes:</p>
 	 <ul>
 	    <li>[373263969] High CVE-2024-11110: Inappropriate implementation in Blink. Reported by Vsevolod Kokorin (Slonser) of Solidlab on 2024-10-14</li>
 	    <li>[360520331] Medium CVE-2024-11111: Inappropriate implementation in Autofill. Reported by Narendra Bhati, Suma Soft Pvt. Ltd - Pune (India) on 2024-08-18</li>
 	    <li>[354824998] Medium CVE-2024-11112: Use after free in Media. Reported by Nan Wang(@eternalsakura13) and Zhenghang Xiao(@Kipreyyy) of 360 Vulnerability Research Institute on 2024-07-23</li>
 	    <li>[360274917] Medium CVE-2024-11113: Use after free in Accessibility. Reported by Weipeng Jiang (@Krace) of VRI on 2024-08-16</li>
 	    <li>[370856871] Medium CVE-2024-11114: Inappropriate implementation in Views. Reported by Micky on 2024-10-02</li>
 	    <li>[371929521] Medium CVE-2024-11115: Insufficient policy enforcement in Navigation. Reported by mastersplinter on 2024-10-07</li>
 	    <li>[40942531] Medium CVE-2024-11116: Inappropriate implementation in Paint. Reported by Thomas Orlita on 2023-11-14</li>
 	    <li>[40062534] Low CVE-2024-11117: Inappropriate implementation in FileSystem. Reported by Ameen Basha M K on 2023-01-06</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-11110</cvename>
       <cvename>CVE-2024-11111</cvename>
       <cvename>CVE-2024-11112</cvename>
       <cvename>CVE-2024-11113</cvename>
       <cvename>CVE-2024-11114</cvename>
       <cvename>CVE-2024-11115</cvename>
       <cvename>CVE-2024-11116</cvename>
       <cvename>CVE-2024-11117</cvename>
       <url>https://chromereleases.googleblog.com/2024/11/stable-channel-update-for-desktop_12.html</url>
     </references>
     <dates>
       <discovery>2024-11-12</discovery>
       <entry>2024-11-16</entry>
     </dates>
   </vuln>
 
   <vuln vid="773e7eb2-af19-4fc7-be7f-0f6a2523b98b">
     <topic>electron31 -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>electron31</name>
 	<range><lt>31.7.5</lt></range>
       </package>
       <package>
 	<name>electron32</name>
 	<range><lt>32.2.5</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Electron developers report:</p>
 	<blockquote cite="https://github.com/electron/electron/releases/tag/v31.7.5">
 	  <p>This update fixes the following vulnerabilities:</p>
 	  <ul>
 	    <li>Security: backported fix for CVE-2024-10827.</li>
 	    <li>Security: backported fix for CVE-2024-11110.</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-10827</cvename>
       <url>https://github.com/advisories/GHSA-58wv-w3hc-2c76</url>
       <cvename>CVE-2024-11110</cvename>
       <url>https://github.com/advisories/GHSA-4mww-gp9h-h59m</url>
     </references>
     <dates>
       <discovery>2024-11-15</discovery>
       <entry>2024-11-15</entry>
       <modified>2024-11-16</modified>
     </dates>
   </vuln>
 
   <vuln vid="a03636f4-a29f-11ef-af48-6cc21735f730">
     <topic>PostgreSQL -- PL/Perl environment variable changes execute arbitrary code</topic>
     <affects>
       <package>
 	<name>postgresql17-plperl</name>
 	<range><lt>17.1</lt></range>
       </package>
       <package>
 	<name>postgresql16-plperl</name>
 	<range><lt>16.5</lt></range>
       </package>
       <package>
 	<name>postgresql15-plperl</name>
 	<range><lt>15.9</lt></range>
       </package>
       <package>
 	<name>postgresql14-plperl</name>
 	<range><lt>14.14</lt></range>
       </package>
       <package>
 	<name>postgresql13-plperl</name>
 	<range><lt>13.17</lt></range>
       </package>
       <package>
 	<name>postgresql12-plperl</name>
 	<range><lt>12.21</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>PostgreSQL project reports:</p>
 	<blockquote cite="https://www.postgresql.org/support/security/CVE-2024-10979/">
 	<p>
 	Incorrect control of environment variables in PostgreSQL
 	PL/Perl allows an unprivileged database user to change
 	sensitive process environment variables (e.g. PATH).
 	That often suffices to enable arbitrary code execution,
 	even if the attacker lacks a database server operating
 	system user.
 	</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-10979</cvename>
       <url>https://www.postgresql.org/support/security/CVE-2024-10979/</url>
     </references>
     <dates>
       <discovery>2024-11-14</discovery>
       <entry>2024-11-14</entry>
     </dates>
   </vuln>
 
   <vuln vid="12e3feab-a29f-11ef-af48-6cc21735f730">
     <topic>PostgreSQL -- SET ROLE, SET SESSION AUTHORIZATION reset to wrong user ID</topic>
     <affects>
       <package>
 	<name>postgresql17-server</name>
 	<range><lt>17.1</lt></range>
       </package>
       <package>
 	<name>postgresql16-server</name>
 	<range><lt>16.5</lt></range>
       </package>
       <package>
 	<name>postgresql15-server</name>
 	<range><lt>15.9</lt></range>
       </package>
       <package>
 	<name>postgresql14-server</name>
 	<range><lt>14.14</lt></range>
       </package>
       <package>
 	<name>postgresql13-server</name>
 	<range><lt>13.17</lt></range>
       </package>
       <package>
 	<name>postgresql12-server</name>
 	<range><lt>12.21</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>PostgreSQL project reports:</p>
 	<blockquote cite="https://www.postgresql.org/support/security/CVE-2024-10978/">
 	<p>
 	Incorrect privilege assignment in PostgreSQL allows a
 	less-privileged application user to view or change
 	different rows from those intended. An attack requires
 	the application to use SET ROLE, SET SESSION
 	AUTHORIZATION, or an equivalent feature. The problem
 	arises when an application query uses parameters from
 	the attacker or conveys query results to the attacker.
 	If that query reacts to current_setting('role') or the
 	current user ID, it may modify or return data as though
 	the session had not used SET ROLE or SET SESSION
 	AUTHORIZATION. The attacker does not control which
 	incorrect user ID applies. Query text from
 	less-privileged sources is not a concern here, because
 	SET ROLE and SET SESSION AUTHORIZATION are not sandboxes
 	for unvetted queries
 	</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-10978</cvename>
       <url>https://www.postgresql.org/support/security/CVE-2024-10978/</url>
     </references>
     <dates>
       <discovery>2024-11-14</discovery>
       <entry>2024-11-14</entry>
     </dates>
   </vuln>
 
   <vuln vid="a61ef21b-a29e-11ef-af48-6cc21735f730">
     <topic>PostgreSQL -- libpq retains an error message from man-in-the-middle</topic>
     <affects>
       <package>
 	<name>postgresql17-client</name>
 	<range><lt>17.1</lt></range>
       </package>
       <package>
 	<name>postgresql16-client</name>
 	<range><lt>16.5</lt></range>
       </package>
       <package>
 	<name>postgresql15-client</name>
 	<range><lt>15.9</lt></range>
       </package>
       <package>
 	<name>postgresql14-client</name>
 	<range><lt>14.14</lt></range>
       </package>
       <package>
 	<name>postgresql13-client</name>
 	<range><lt>13.17</lt></range>
       </package>
       <package>
 	<name>postgresql12-client</name>
 	<range><lt>12.21</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>PostgreSQL project reports:</p>
 	<blockquote cite="https://www.postgresql.org/support/security/CVE-2024-10977/">
 	<p>
 	Client use of server error message in PostgreSQL allows
 	a server not trusted under current SSL or GSS settings
 	to furnish arbitrary non-NUL bytes to the libpq
 	application. For example, a man-in-the-middle attacker
 	could send a long error message that a human or
 	screen-scraper user of psql mistakes for valid query
 	results. This is probably not a concern for clients
 	where the user interface unambiguously indicates the
 	boundary between one error message and other text.
 	</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-10977</cvename>
       <url>https://www.postgresql.org/support/security/CVE-2024-10977/</url>
     </references>
     <dates>
       <discovery>2024-11-14</discovery>
       <entry>2024-11-14</entry>
     </dates>
   </vuln>
 
   <vuln vid="3831292b-a29d-11ef-af48-6cc21735f730">
     <topic>PostgreSQL -- PostgreSQL row security below e.g. subqueries disregards user ID changes</topic>
     <affects>
       <package>
 	<name>postgresql17-server</name>
 	<range><lt>17.1</lt></range>
       </package>
       <package>
 	<name>postgresql16-server</name>
 	<range><lt>16.5</lt></range>
       </package>
       <package>
 	<name>postgresql15-server</name>
 	<range><lt>15.9</lt></range>
       </package>
       <package>
 	<name>postgresql14-server</name>
 	<range><lt>14.14</lt></range>
       </package>
       <package>
 	<name>postgresql13-server</name>
 	<range><lt>13.17</lt></range>
       </package>
       <package>
 	<name>postgresql12-server</name>
 	<range><lt>12.21</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>PostgreSQL project reports:</p>
 	<blockquote cite="https://www.postgresql.org/support/security/CVE-2024-10976/">
 	<p>
 	Incomplete tracking in PostgreSQL of tables with row
 	security allows a reused query to view or change
 	different rows from those intended. CVE-2023-2455 and
 	CVE-2016-2193 fixed most interaction between row
 	security and user ID changes. They missed cases where a
 	subquery, WITH query, security invoker view, or
 	SQL-language function references a table with a
 	row-level security policy. This has the same
 	consequences as the two earlier CVEs. That is to say, it
 	leads to potentially incorrect policies being applied in
 	cases where role-specific policies are used and a given
 	query is planned under one role and then executed under
 	other roles. This scenario can happen under security
 	definer functions or when a common user and query is
 	planned initially and then re-used across multiple SET
 	ROLEs.
 
 	Applying an incorrect policy may permit a user to complete
 	otherwise-forbidden reads and modifications. This affects only databases
 	that have used CREATE POLICY to define a row security policy. An
 	attacker must tailor an attack to a particular application's pattern of
 	query plan reuse, user ID changes, and role-specific row security
 	policies.
 	</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-10976</cvename>
       <url>https://www.postgresql.org/support/security/CVE-2024-10976/</url>
     </references>
     <dates>
       <discovery>2024-11-14</discovery>
       <entry>2024-11-14</entry>
     </dates>
   </vuln>
 
   <vuln vid="6b591e05-971c-4077-8ae4-1310554971b7">
     <topic>electron31 -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>electron31</name>
 	<range><lt>31.7.4</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Electron developers report:</p>
 	<blockquote cite="https://github.com/electron/electron/releases/tag/v31.7.4">
 	  <p>This update fixes the following vulnerabilities:</p>
 	  <ul>
 	    <li>Security: backported fix for CVE-2024-10231.</li>
 	    <li>Security: backported fix for CVE-2024-10229.</li>
 	    <li>Security: backported fix for CVE-2024-10487.</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-10231</cvename>
       <url>https://github.com/advisories/GHSA-3wfx-mj93-vf8v</url>
       <cvename>CVE-2024-10229</cvename>
       <url>https://github.com/advisories/GHSA-3hjp-j522-245f</url>
       <cvename>CVE-2024-10487</cvename>
       <url>https://github.com/advisories/GHSA-h72p-7xmw-gpp8</url>
     </references>
     <dates>
       <discovery>2024-11-12</discovery>
       <entry>2024-11-14</entry>
     </dates>
   </vuln>
 
   <vuln vid="1eb4d32c-a245-11ef-998c-2cf05da270f3">
     <topic>Gitlab -- vulnerabilities</topic>
     <affects>
       <package>
 	<name>gitlab-ce</name>
 	<name>gitlab-ee</name>
 	<range><ge>17.5.0</ge><lt>17.5.2</lt></range>
 	<range><ge>17.4.0</ge><lt>17.4.4</lt></range>
 	<range><ge>16.0.0</ge><lt>17.3.7</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Gitlab reports:</p>
 	<blockquote cite="https://about.gitlab.com/releases/2024/11/13/patch-release-gitlab-17-5-2-released/">
 	  <p>Unauthorized access to Kubernetes cluster agent</p>
 	  <p>Device OAuth flow allows for cross window forgery</p>
 	  <p>Denial of Service by importing malicious crafted FogBugz import payload</p>
 	  <p>Stored XSS through javascript URL in Analytics dashboards</p>
 	  <p>HTML injection in vulnerability Code flow could lead to XSS on self hosted instances</p>
 	  <p>Information disclosure through an API endpoint</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-9693</cvename>
       <cvename>CVE-2024-7404</cvename>
       <cvename>CVE-2024-8648</cvename>
       <cvename>CVE-2024-8180</cvename>
       <cvename>CVE-2024-10240</cvename>
       <url>https://about.gitlab.com/releases/2024/11/13/patch-release-gitlab-17-5-2-released/</url>
     </references>
     <dates>
       <discovery>2024-11-13</discovery>
       <entry>2024-11-14</entry>
     </dates>
   </vuln>
 
   <vuln vid="ce0f52e1-a174-11ef-9a62-002590c1f29c">
     <topic>FreeBSD -- Certificate revocation list fetch(1) option fails</topic>
     <affects>
       <package>
 	<name>FreeBSD</name>
 	<range><ge>14.1</ge><lt>14.1_6</lt></range>
 	<range><ge>13.4</ge><lt>13.4_2</lt></range>
 	<range><ge>13.3</ge><lt>13.3_8</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<h1>Problem Description:</h1>
 	<p>The fetch(3) library uses environment variables for passing
 	certain information, including the revocation file pathname.  The
 	environment variable name used by fetch(1) to pass the filename to
 	the library was incorrect, in effect ignoring the option.</p>
 	<h1>Impact:</h1>
 	<p>Fetch would still connect to a host presenting a certificate
 	included in the revocation file passed to the --crl option.</p>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-45289</cvename>
       <freebsdsa>SA-24:19.fetch</freebsdsa>
     </references>
     <dates>
       <discovery>2024-10-29</discovery>
       <entry>2024-11-13</entry>
     </dates>
   </vuln>
 
   <vuln vid="8caa5d60-a174-11ef-9a62-002590c1f29c">
     <topic>FreeBSD -- Unbounded allocation in ctl(4) CAM Target Layer</topic>
     <affects>
       <package>
 	<name>FreeBSD-kernel</name>
 	<range><ge>14.1</ge><lt>14.1_6</lt></range>
 	<range><ge>13.4</ge><lt>13.4_2</lt></range>
 	<range><ge>13.3</ge><lt>13.3_8</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<h1>Problem Description:</h1>
 	<p>The command ctl_persistent_reserve_out allows the caller to
 	specify an arbitrary size which will be passed to the kernel's
 	memory allocator.</p>
 	<h1>Impact:</h1>
 	<p>A malicious guest could cause a Denial of Service (DoS) on the
 	host.</p>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-39281</cvename>
       <freebsdsa>SA-24:18.ctl</freebsdsa>
     </references>
     <dates>
       <discovery>2024-10-29</discovery>
       <entry>2024-11-13</entry>
     </dates>
   </vuln>
 
   <vuln vid="eb5c615d-a173-11ef-9a62-002590c1f29c">
     <topic>FreeBSD -- Multiple issues in the bhyve hypervisor</topic>
     <affects>
       <package>
 	<name>FreeBSD</name>
 	<range><ge>14.1</ge><lt>14.1_6</lt></range>
 	<range><ge>13.4</ge><lt>13.4_2</lt></range>
 	<range><ge>13.3</ge><lt>13.3_8</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<h1>Problem Description:</h1>
 	<p>Several vulnerabilities were found in the bhyve hypervisor's
 	device models.</p>
 	<p>The NVMe driver function nvme_opc_get_log_page is vulnerable to a
 	buffer over- read from a guest-controlled value.  (CVE-2024-51562)</p>
 	<p>The virtio_vq_recordon function is subject to a time-of-check to
 	time-of-use (TOCTOU) race condition.  (CVE-2024-51563)</p>
 	<p>A guest can trigger an infinite loop in the hda audio driver.
 	(CVE-2024-51564)</p>
 	<p>The hda driver is vulnerable to a buffer over-read from a
 	guest-controlled value.  (CVE-2024-51565)</p>
 	<p>The NVMe driver queue processing is vulernable to guest-induced
 	infinite loops.  (CVE-2024-51566)</p>
 	<h1>Impact:</h1>
 	<p>Malicious guest virtual machines may be able to perform a denial
 	of service (DoS) of the bhyve host, and may read memory within the
 	bhyve process that they should not be able to access.</p>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-51562</cvename>
       <cvename>CVE-2024-51563</cvename>
       <cvename>CVE-2024-51564</cvename>
       <cvename>CVE-2024-51565</cvename>
       <cvename>CVE-2024-51566</cvename>
       <freebsdsa>SA-24:17.bhyve</freebsdsa>
     </references>
     <dates>
       <discovery>2024-10-29</discovery>
       <entry>2024-11-13</entry>
     </dates>
   </vuln>
 
   <vuln vid="ab4e6f65-a142-11ef-84e9-901b0e9408dc">
     <topic>element-web -- several vulnerabilities</topic>
     <affects>
       <package>
 	<name>element-web</name>
 	<range><lt>1.11.85</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Element team reports:</p>
 	<blockquote cite="https://github.com/element-hq/element-web/security/advisories/GHSA-5486-384g-mcx2">
 	  <p>Versions of Element Web and Desktop earlier than 1.11.85 do
 	  not check if thumbnails for attachments, stickers and images
 	  are coherent. It is possible to add thumbnails to events
 	  trigger a file download once clicked.</p>
 	</blockquote>
 	<blockquote cite="https://github.com/element-hq/element-web/security/advisories/GHSA-w36j-v56h-q9pc">
 	  <p>A malicious homeserver can send invalid messages over
 	  federation which can prevent Element Web and Desktop from
 	  rendering single messages or the entire room containing
 	  them.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-51749</cvename>
       <cvename>CVE-2024-51750</cvename>
       <url>https://github.com/element-hq/element-web/security/advisories/GHSA-5486-384g-mcx2</url>
       <url>https://github.com/element-hq/element-web/security/advisories/GHSA-w36j-v56h-q9pc</url>
     </references>
     <dates>
       <discovery>2024-11-12</discovery>
       <entry>2024-11-12</entry>
     </dates>
   </vuln>
 
   <vuln vid="574f7bc9-a141-11ef-84e9-901b0e9408dc">
     <topic>Matrix clients -- mxc uri validation in js sdk</topic>
     <affects>
       <package>
 	<name>cinny</name>
 	<range><lt>4.2.3</lt></range>
       </package>
       <package>
 	<name>element-web</name>
 	<range><lt>1.11.85</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>matrix-js-sdk upstream reports:</p>
 	<blockquote cite="https://github.com/matrix-org/matrix-js-sdk/security/advisories/GHSA-xvg8-m4x3-w6xr">
 	  <p>matrix-js-sdk before 34.11.0 is vulnerable to client-side
 	  path traversal via crafted MXC URIs. A malicious room member
 	  can trigger clients based on the matrix-js-sdk to issue
 	  arbitrary authenticated GET requests to the client's
 	  homeserver.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-50336</cvename>
       <url>https://github.com/matrix-org/matrix-js-sdk/security/advisories/GHSA-xvg8-m4x3-w6xr</url>
     </references>
     <dates>
       <discovery>2024-11-12</discovery>
       <entry>2024-11-12</entry>
     </dates>
   </vuln>
 
   <vuln vid="0a82bc4d-a129-11ef-8351-589cfc0f81b0">
     <topic>icinga2 -- TLS Certificate Validation Bypass</topic>
     <affects>
       <package>
 	<name>icinga2</name>
 	<range><lt>2.14.3</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The Icinga project reports:</p>
 	<blockquote cite="https://github.com/Icinga/icinga2/commit/0419a2c36de408e9a703aec0962061ec9a285d3c">
 	  <p>Icinga is a monitoring system which checks the availability of
 	network resources, notifies users of outages, and generates performance
 	data for reporting.  The TLS certificate validation in all Icinga
 	2 versions starting from 2.4.0 was flawed, allowing an attacker to
 	impersonate both trusted cluster nodes as well as any API users
 	that use TLS client certificates for authentication (ApiUser objects
 	with the client_cn attribute set).  This vulnerability has been
 	fixed in v2.14.3, v2.13.10, v2.12.11, and v2.11.12.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-49369</cvename>
       <url>https://icinga.com/blog/2024/11/12/critical-icinga-2-security-releases-2-14-3/</url>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-49369</url>
     </references>
     <dates>
       <discovery>2024-11-12</discovery>
       <entry>2024-11-12</entry>
     </dates>
   </vuln>
 
   <vuln vid="33236f80-a11d-11ef-a964-1c697a616631">
     <topic>Intel CPUs -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>cpu-microcode-intel</name>
 	<range><lt>20241112</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Intel reports:</p>
 	<blockquote cite="https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01101.html">
 	 <p>
 	  A potential security vulnerability in some 4th and 5th Generation
 	  Intel Xeon Processors may allow denial of service. Intel released
 	  microcode updates to mitigate this potential vulnerability.
 	 </p>
 	</blockquote>
 	<blockquote cite="https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01079.html">
 	 <p>
 	  Potential security vulnerabilities in some Intel Xeon processors using
 	  Intel Software Guard Extensions (Intel SGX) may allow escalation of
 	  privilege.  Intel released firmware updates to mitigate these
 	  potential vulnerabilities.
 	 </p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-21853</cvename>
       <cvename>CVE-2024-23918</cvename>
       <cvename>CVE-2024-21820</cvename>
       <url>https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases/tag/microcode-20241112</url>
     </references>
     <dates>
       <discovery>2024-09-10</discovery>
       <entry>2024-09-10</entry>
     </dates>
   </vuln>
 
   <vuln vid="305ceb2c-9df8-11ef-a660-d85ed309193e">
     <topic>x11vnc -- access to shared memory segments</topic>
     <affects>
       <package>
 	<name>x11vnc</name>
 	<range><lt>0.9.16_8</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>cve@mitre.org reports:</p>
 	<blockquote cite="https://nvd.nist.gov/vuln/detail/CVE-2020-29074">
 	  <p>scan.c in x11vnc 0.9.16 uses IPC_CREAT|0777 in shmget calls,
 	  which allows access by actors other than the current user.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2020-29074</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2020-29074</url>
     </references>
     <dates>
       <discovery>2020-11-18</discovery>
       <entry>2024-11-08</entry>
     </dates>
   </vuln>
 
   <vuln vid="adffe51e-9df5-11ef-a660-d85ed309193e">
     <topic>lrzsz -- Integer overflow in zmodem, crash and information leak</topic>
     <affects>
       <package>
 	<name>lrzsz</name>
 	<range><lt>0.12.20_7</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>cve@mitre.org reports:</p>
 	<blockquote cite="https://nvd.nist.gov/vuln/detail/CVE-2018-10195">
 	  <p>Lrzsz has an integer overflow vulernability in the
 	  src/zm.c:zsdata() function. An attacker could exploit this with
 	  the sz command to cause a crash or potentially leak information
 	  to the receiving server.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2018-10195</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2018-10195</url>
     </references>
     <dates>
       <discovery>2018-04-26</discovery>
       <entry>2024-11-08</entry>
     </dates>
   </vuln>
 
   <vuln vid="776aaafc-939f-11ef-87ad-a8a15998b5cb">
     <topic>tnef -- An attacker may be able to write to the victim's .ssh/authorized_keys file via an e-mail message</topic>
     <affects>
       <package>
 	<name>tnef</name>
 	<range><lt>1.4.18</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>cve@mitre.org reports:</p>
 	<blockquote cite="https://github.com/verdammelt/tnef/compare/1.4.17...1.4.18">
 	  <p>In tnef before 1.4.18, an attacker may be able to write to the
 	victim&apos;s .ssh/authorized_keys file via an e-mail message with
 	a crafted winmail.dat application/ms-tnef attachment, because of a
 	heap-based buffer over-read involving strdup.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2019-18849</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2019-18849</url>
     </references>
     <dates>
       <discovery>2019-11-11</discovery>
       <entry>2024-10-26</entry>
     </dates>
   </vuln>
 
   <vuln vid="70cf37c8-939b-11ef-87ad-a8a15998b5cb">
     <topic>tnef -- Invalid read and write operations, controlled by an attacker</topic>
     <affects>
       <package>
 	<name>tnef</name>
 	<range><le>1.4.12</le></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>cve@mitre.org reports:</p>
 	<blockquote cite="http://www.debian.org/security/2017/dsa-3798">
 	  <p>CVE-2017-6307: An issue was discovered in tnef before
 	  1.4.13.  Two OOB Writes have been identified in
 	  src/mapi_attr.c:mapi_attr_read().  These might lead to
 	  invalid read and write operations, controlled by an
 	  attacker.</p>
 	</blockquote>
 	<blockquote cite="http://www.debian.org/security/2017/dsa-3798">
 	  <p>CVE-2017-6308: An issue was discovered in tnef before
 	  1.4.13.  Several Integer Overflows, which can lead to Heap
 	  Overflows, have been identified in the functions that wrap
 	  memory allocation.</p>
 	</blockquote>
 	<blockquote cite="http://www.debian.org/security/2017/dsa-3798">
 	  <p>CVE-2017-6309: An issue was discovered in tnef before
 	  1.4.13.  Two type confusions have been identified in the
 	  parse_file() function.  These might lead to invalid read and
 	  write operations, controlled by an attacker.</p>
 	</blockquote>
 	<blockquote cite="http://www.debian.org/security/2017/dsa-3798">
 	  <p>CVE-2017-6310: An issue was discovered in tnef before
 	  1.4.13.  Four type confusions have been identified in the
 	  file_add_mapi_attrs() function.  These might lead to invalid
 	  read and write operations, controlled by an attacker.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2017-6307</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2017-6307</url>
       <cvename>CVE-2017-6308</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2017-6308</url>
       <cvename>CVE-2017-6309</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2017-6309</url>
       <cvename>CVE-2017-6310</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2017-6310</url>
     </references>
     <dates>
       <discovery>2017-02-24</discovery>
       <entry>2024-10-26</entry>
     </dates>
   </vuln>
 
   <vuln vid="96266fc9-1200-43b5-8393-4c51f54bb7bc">
     <topic>electron32 -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>electron32</name>
 	<range><lt>32.2.3</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Electron developers report:</p>
 	<blockquote cite="https://github.com/electron/electron/releases/tag/v32.2.3">
 	  <p>This update fixes the following vulnerabilities:</p>
 	  <ul>
 	    <li>Security: backported fix for CVE-2024-10230.</li>
 	    <li>Security: backported fix for CVE-2024-10231.</li>
 	    <li>Security: backported fix for CVE-2024-10229.</li>
 	    <li>Security: backported fix for CVE-2024-10487.</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-10230</cvename>
       <url>https://github.com/advisories/GHSA-g4gj-m346-585c</url>
       <cvename>CVE-2024-10231</cvename>
       <url>https://github.com/advisories/GHSA-3wfx-mj93-vf8v</url>
       <cvename>CVE-2024-10229</cvename>
       <url>https://github.com/advisories/GHSA-3hjp-j522-245f</url>
       <cvename>CVE-2024-10487</cvename>
       <url>https://github.com/advisories/GHSA-h72p-7xmw-gpp8</url>
     </references>
     <dates>
       <discovery>2024-11-08</discovery>
       <entry>2024-11-08</entry>
     </dates>
   </vuln>
 
   <vuln vid="d48a2224-9b4c-11ef-bdd9-4ccc6adda413">
     <topic>gstreamer1-rtsp-server -- Potential Denial-of-Service (DoS) with specially crafted client requests</topic>
     <affects>
       <package>
 	<name>gstreamer1-rtsp-server</name>
 	<range><ge>1.18.0</ge><lt>1.24.9</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Qingpeng Du reports:</p>
 	<blockquote cite="https://gstreamer.freedesktop.org/security/sa-2024-0004.html">
 	  <p>A series of specially crafted client requests during streaming setup
 	   (post client authentication, if any) can cause the RTSP server library
 	   to abort, if it has been compiled with assertions enabled.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-44331</cvename>
       <url>https://gstreamer.freedesktop.org/security/sa-2024-0004.html</url>
     </references>
     <dates>
       <discovery>2024-10-29</discovery>
       <entry>2024-11-07</entry>
     </dates>
   </vuln>
 
   <vuln vid="ab254c9d-9c36-11ef-8c1c-a8a1599412c6">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>130.0.6723.116</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>130.0.6723.116</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2024/11/stable-channel-update-for-desktop.html">
 	 <p>This update includes 2 security fixes:</p>
 	 <ul>
 	    <li>[370217726] High CVE-2024-10826: Use after free in Family Experiences. Reported by Anonymous on 2024-09-29</li>
 	    <li>[375065084] High CVE-2024-10827: Use after free in Serial. Reported by Anonymous on 2024-10-23</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-10826</cvename>
       <cvename>CVE-2024-10827</cvename>
       <url>https://chromereleases.googleblog.com/2024/11/stable-channel-update-for-desktop.html</url>
     </references>
     <dates>
       <discovery>2024-11-05</discovery>
       <entry>2024-11-06</entry>
     </dates>
   </vuln>
 
   <vuln vid="ecf9a798-9aa9-11ef-a8f0-a8a15998b5cb">
     <topic>libqb -- Buffer overflow</topic>
     <affects>
       <package>
 	<name>libqb</name>
 	<range><lt>2.0.8</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>cve@mitre.org reports:</p>
 	<blockquote cite="https://github.com/ClusterLabs/libqb/commit/1bbaa929b77113532785c408dd1b41cd0521ffc8">
 	  <p>log_blackbox.c in libqb before 2.0.8 allows a buffer overflow via
 	long log messages because the header size is not considered.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-39976</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2023-39976</url>
     </references>
     <dates>
       <discovery>2023-08-08</discovery>
       <entry>2024-11-04</entry>
     </dates>
   </vuln>
 
   <vuln vid="e17384ef-c5e8-4b5d-bb62-c13405e7f1f7">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>130.0.6723.91</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>130.0.6723.91</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2024/10/stable-channel-update-for-desktop_29.html">
 	 <p>This update includes 2 security fixes:</p>
 	 <ul>
 	    <li>[375123371] Critical CVE-2024-10487: Out of bounds write in Dawn. Reported by Apple Security Engineering and Architecture (SEAR) on 2024-10-23</li>
 	    <li>[374310077] High CVE-2024-10488: Use after free in WebRTC. Reported by Cassidy Kim(@cassidy6564) on 2024-10-18</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-10487</cvename>
       <cvename>CVE-2024-10488</cvename>
       <url>https://chromereleases.googleblog.com/2024/10/stable-channel-update-for-desktop_29.html</url>
     </references>
     <dates>
       <discovery>2024-10-29</discovery>
       <entry>2024-11-02</entry>
     </dates>
   </vuln>
 
   <vuln vid="3092668e-97e4-11ef-bdd9-4ccc6adda413">
     <topic>qt5-webengine -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>qt5-webengine</name>
 	<range><lt>5.15.18p2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<blockquote cite="https://code.qt.io/cgit/qt/qtwebengine-chromium.git/log/?h=87-based">
 	  <p>Backports for 15 security bugs in Chromium:</p>
 	  <ul>
 	    <li>CVE-2024-4761: Out of bounds write in V8</li>
 	    <li>CVE-2024-5158: Type confusion in V8</li>
 	    <li>CVE-2024-7532: Out of bounds memory access in ANGLE</li>
 	    <li>CVE-2024-7965: Inappropriate implementation in V8</li>
 	    <li>CVE-2024-7967: Heap buffer overflow in Fonts</li>
 	    <li>CVE-2024-7971: Type confusion in V8</li>
 	    <li>CVE-2024-8198: Heap buffer overflow in Skia</li>
 	    <li>CVE-2024-8636: Heap buffer overflow in Skia</li>
 	    <li>CVE-2024-9123: Integer overflow in Skia</li>
 	    <li>CVE-2024-9602: Type confusion in V8</li>
 	    <li>CVE-2024-9603: Type confusion in V8</li>
 	    <li>CVE-2024-10229: Inappropriate implementation in Extensions</li>
 	    <li>CVE-2024-45490: Negative length in libexpat</li>
 	    <li>CVE-2024-45491: Integer overflow in libexpat</li>
 	    <li>CVE-2024-45492: Integer overflow in libexpat</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-4761</cvename>
       <cvename>CVE-2024-5158</cvename>
       <cvename>CVE-2024-7532</cvename>
       <cvename>CVE-2024-7965</cvename>
       <cvename>CVE-2024-7967</cvename>
       <cvename>CVE-2024-7971</cvename>
       <cvename>CVE-2024-8198</cvename>
       <cvename>CVE-2024-8636</cvename>
       <cvename>CVE-2024-9123</cvename>
       <cvename>CVE-2024-9602</cvename>
       <cvename>CVE-2024-9603</cvename>
       <cvename>CVE-2024-10229</cvename>
       <cvename>CVE-2024-45490</cvename>
       <cvename>CVE-2024-45491</cvename>
       <cvename>CVE-2024-45492</cvename>
       <url>https://code.qt.io/cgit/qt/qtwebengine-chromium.git/log/?h=87-based</url>
     </references>
     <dates>
       <discovery>2024-09-18</discovery>
       <entry>2024-10-31</entry>
     </dates>
   </vuln>
 
   <vuln vid="fd538d14-5778-4764-b321-2ddd61a8a58f">
     <topic>keycloak -- Missing server identity checks when sending mails via SMTPS</topic>
     <affects>
       <package>
 	<name>keycloak</name>
 	<range><lt>26.0.4</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Red Hat reports:</p>
 	<blockquote cite="https://bugzilla.redhat.com/show_bug.cgi?id=2315808">
 	  <p>A vulnerability was found in Apache Sling Commons Messaging
 	    Mail(angus-mail), which provides a simple interface for sending
 	    emails via SMTPS in OSGi, does not offer an option to enable
 	    server identity checks, leaving connections vulnerable to
 	    "man-in-the-middle" attacks and can allow insecure email
 	    communication.</p>
 	</blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2021-44549</cvename>
       <url>https://www.cve.org/CVERecord?id=CVE-2021-44549</url>
     </references>
     <dates>
       <discovery>2024-10-01</discovery>
       <entry>2024-10-31</entry>
     </dates>
   </vuln>
 
   <vuln vid="b73d1f2a-96de-11ef-9e71-00d8612f03c8">
     <topic>librewolf -- Undefined behavior in selection node cache</topic>
     <affects>
       <package>
 	<name>librewolf</name>
 	<range><lt>131.0.3</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1920381">
 	  <p>When manipulating the selection node cache, an attacker may have
 	been able to cause unexpected behavior, potentially leading to an
 	exploitable crash.  This vulnerability affects Firefox &lt; 131.0.3.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-9936</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-9936</url>
     </references>
     <dates>
       <discovery>2024-10-14</discovery>
       <entry>2024-10-30</entry>
     </dates>
   </vuln>
 
   <vuln vid="4b3a8e7d-9372-11ef-87ad-a8a15998b5cb">
     <topic>hwloc2 -- Denial of service or other unspecified impacts</topic>
     <affects>
       <package>
 	<name>hwloc2</name>
 	<range><ge>2.1.0</ge><le>2.9.2</le></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>cve@mitre.org reports:</p>
 	<blockquote cite="https://github.com/open-mpi/hwloc/issues/544">
 	  <p>An issue was discovered in open-mpi hwloc 2.1.0 allows attackers
 	to cause a denial of service or other unspecified impacts via
 	glibc-cpuset in topology-linux.c.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2022-47022</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2022-47022</url>
     </references>
     <dates>
       <discovery>2023-08-22</discovery>
       <entry>2024-10-29</entry>
     </dates>
   </vuln>
 
   <vuln vid="f07c8f87-8e65-11ef-81b8-659bf0027d16">
     <topic>forgejo -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>forgejo</name>
 	<range><lt>9.0.1</lt></range>
       </package>
       <package>
 	<name>forgejo7</name>
 	<range><lt>7.0.10</lt></range>
       </package>
     </affects>
     <description>
        <body xmlns="http://www.w3.org/1999/xhtml">
        <h1>Problem Description:</h1>
        <ul>
        <li>Forgejo generates a token which is used to authenticate web
        endpoints that are only meant to be used internally, for instance
        when the SSH daemon is used to push a commit with Git.  The
        verification of this token was not done in constant time and was
        susceptible to timing attacks.  A pre-condition for such an attack is
        the precise measurements of the time for each operation.  Since it
        requires observing the timing of network operations, the issue is
        mitigated when a Forgejo instance is accessed over the internet
        because the ISP introduce unpredictable random delays.</li>
        <li>Because of a missing permission check, the branch used to propose
        a pull request to a repository can always be deleted by the user
        performing the merge.  It was fixed so that such a deletion is only
        allowed if the user performing the merge has write permission to the
        repository from which the pull request was made.</li>
        </ul>
       </body>
     </description>
     <references>
       <url>https://codeberg.org/forgejo/forgejo/milestone/8544</url>
       <url>https://codeberg.org/forgejo/forgejo/pulls/5719</url>
       <url>https://codeberg.org/forgejo/forgejo/pulls/5718</url>
     </references>
     <dates>
       <discovery>2024-10-28</discovery>
       <entry>2024-10-29</entry>
     </dates>
   </vuln>
 
   <vuln vid="fafaef4d-f364-4a07-bbdd-bf53448c593c">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>130.0.6723.69</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>130.0.6723.69</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2024/10/stable-channel-update-for-desktop_22.html">
 	 <p>This update includes 3 security fixes:</p>
 	 <ul>
 	    <li>[371011220] High CVE-2024-10229: Inappropriate implementation in Extensions. Reported by Vsevolod Kokorin (Slonser) of Solidlab on 2024-10-02</li>
 	    <li>[371565065] High CVE-2024-10230: Type Confusion in V8. Reported by Seunghyun Lee (@0x10n) on 2024-10-05</li>
 	    <li>[372269618] High CVE-2024-10231: Type Confusion in V8. Reported by Seunghyun Lee (@0x10n) on 2024-10-09</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-10229</cvename>
       <cvename>CVE-2024-10230</cvename>
       <cvename>CVE-2024-10231</cvename>
       <url>https://chromereleases.googleblog.com/2024/10/stable-channel-update-for-desktop_22.html</url>
     </references>
     <dates>
       <discovery>2024-10-22</discovery>
       <entry>2024-10-26</entry>
     </dates>
   </vuln>
 
   <vuln vid="1e71e366-080b-4e8f-a9e6-150bf698186b">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>130.0.6723.58</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>130.0.6723.58</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2024/10/stable-channel-update-for-desktop_15.html">
 	 <p>This update includes 17 security fixes:</p>
 	 <ul>
 	    <li>[367755363] High CVE-2024-9954: Use after free in AI. Reported by DarkNavy on 2024-09-18</li>
 	    <li>[370133761] Medium CVE-2024-9955: Use after free in Web Authentication. Reported by anonymous on 2024-09-29</li>
 	    <li>[370482421] Medium CVE-2024-9956: Inappropriate implementation in Web Authentication. Reported by mastersplinter on 2024-09-30</li>
 	    <li>[358151317] Medium CVE-2024-9957: Use after free in UI. Reported by lime(@limeSec_) and fmyy(@binary_fmyy) From TIANGONG Team of Legendsec at QI-ANXIN Group on 2024-08-08</li>
 	    <li>[40076120] Medium CVE-2024-9958: Inappropriate implementation in PictureInPicture. Reported by Lyra Rebane (rebane2001) on 2023-11-02</li>
 	    <li>[368672129] Medium CVE-2024-9959: Use after free in DevTools. Reported by Sakana.S on 2024-09-21</li>
 	    <li>[354748063] Medium CVE-2024-9960: Use after free in Dawn. Reported by Anonymous on 2024-07-23</li>
 	    <li>[357776197] Medium CVE-2024-9961: Use after free in Parcel Tracking. Reported by lime(@limeSec_) and fmyy(@binary_fmyy) From TIANGONG Team of Legendsec at QI-ANXIN Group on 2024-08-06</li>
 	    <li>[364508693] Medium CVE-2024-9962: Inappropriate implementation in Permissions. Reported by Shaheen Fazim on 2024-09-04</li>
 	    <li>[328278718] Medium CVE-2024-9963: Insufficient data validation in Downloads. Reported by Anonymous on 2024-03-06</li>
 	    <li>[361711121] Low CVE-2024-9964: Inappropriate implementation in Payments. Reported by Hafiizh on 2024-08-23</li>
 	    <li>[352651673] Low CVE-2024-9965: Insufficient data validation in DevTools. Reported by Shaheen Fazim on 2024-07-12</li>
 	    <li>[364773822] Low CVE-2024-9966: Inappropriate implementation in Navigations. Reported by Harry Chen on 2024-09-05</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-9954</cvename>
       <cvename>CVE-2024-9955</cvename>
       <cvename>CVE-2024-9956</cvename>
       <cvename>CVE-2024-9957</cvename>
       <cvename>CVE-2024-9958</cvename>
       <cvename>CVE-2024-9959</cvename>
       <cvename>CVE-2024-9960</cvename>
       <cvename>CVE-2024-9961</cvename>
       <cvename>CVE-2024-9962</cvename>
       <cvename>CVE-2024-9963</cvename>
       <cvename>CVE-2024-9964</cvename>
       <cvename>CVE-2024-9965</cvename>
       <cvename>CVE-2024-9966</cvename>
       <url>https://chromereleases.googleblog.com/2024/10/stable-channel-update-for-desktop_15.html</url>
     </references>
     <dates>
       <discovery>2024-10-15</discovery>
       <entry>2024-10-26</entry>
     </dates>
   </vuln>
 
   <vuln vid="3152a474-9390-11ef-87ad-a8a15998b5cb">
     <topic>halibut -- Segmentation fault, denial of service or possibly other unspecified impact via a crafted text document</topic>
     <affects>
       <package>
 	<name>halibut</name>
 	<range><eq>1.2</eq></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>cve@mitre.org reports:</p>
 	<blockquote cite="https://carteryagemann.com/halibut-case-study.html#poc-halibut-text-uaf">
 	  <p>CVE-2021-42612: A use after free in cleanup_index in index.c in Halibut 1.2 allows
 	an attacker to cause a segmentation fault or possibly have other
 	unspecified impact via a crafted text document.</p>
 	</blockquote>
 	<blockquote cite="https://carteryagemann.com/halibut-case-study.html#poc-halibut-winhelp-df">
 	  <p>CVE-2021-42613: A double free in cleanup_index in index.c in Halibut 1.2 allows an
 	attacker to cause a denial of service or possibly have other
 	unspecified impact via a crafted text document.</p>
 	</blockquote>
 	<blockquote cite="https://carteryagemann.com/halibut-case-study.html#poc-halibut-info-uaf">
 	  <p>CVE-2021-42614: A use after free in info_width_internal in bk_info.c in Halibut 1.2
 	allows an attacker to cause a segmentation fault or possibly have
 	unspecified other impact via a crafted text document.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2021-42612</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2021-42612</url>
       <cvename>CVE-2021-42613</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2021-42613</url>
       <cvename>CVE-2021-42614</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2021-42614</url>
     </references>
     <dates>
       <discovery>2022-05-24</discovery>
       <entry>2024-10-26</entry>
     </dates>
   </vuln>
 
   <vuln vid="fcb0e00f-d7d3-49b6-a4a1-852528230912">
     <topic>electron31 -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>electron31</name>
 	<range><lt>31.7.2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Electron developers report:</p>
 	<blockquote cite="https://github.com/electron/electron/releases/tag/v31.7.2">
 	  <p>This update fixes the following vulnerabilities:</p>
 	  <ul>
 	    <li>Security: backported fix for CVE-2024-9121.</li>
 	    <li>Security: backported fix for CVE-2024-9122.</li>
 	    <li>Security: backported fix for CVE-2024-7025.</li>
 	    <li>Security: backported fix for CVE-2024-9369.</li>
 	    <li>Security: backported fix for CVE-2024-7965.</li>
 	    <li>Security: backported fix for CVE-2024-7966.</li>
 	    <li>Security: backported fix for CVE-2024-7967.</li>
 	    <li>Security: backported fix for CVE-2024-8198.</li>
 	    <li>Security: backported fix for CVE-2024-8193.</li>
 	    <li>Security: backported fix for CVE-2024-7969.</li>
 	    <li>Security: backported fix for CVE-2024-7970.</li>
 	    <li>Security: backported fix for CVE-2024-8362.</li>
 	    <li>Security: backported fix for CVE-2024-8636.</li>
 	    <li>Security: backported fix for CVE-2024-9123.</li>
 	    <li>Security: backported fix for CVE-2024-9120.</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-9121</cvename>
       <url>https://github.com/advisories/GHSA-qcr8-x9j3-5j62</url>
       <cvename>CVE-2024-9122</cvename>
       <url>https://github.com/advisories/GHSA-4fw3-822r-pqw6</url>
       <cvename>CVE-2024-7025</cvename>
       <cvename>CVE-2024-9369</cvename>
       <cvename>CVE-2024-7965</cvename>
       <url>https://github.com/advisories/GHSA-x38q-hvmx-rwhg</url>
       <cvename>CVE-2024-7966</cvename>
       <url>https://github.com/advisories/GHSA-4pj3-wmgx-2h8r</url>
       <cvename>CVE-2024-7967</cvename>
       <url>https://github.com/advisories/GHSA-57cq-jgq2-x7vg</url>
       <cvename>CVE-2024-8198</cvename>
       <url>https://github.com/advisories/GHSA-76vg-grjj-w595</url>
       <cvename>CVE-2024-8193</cvename>
       <url>https://github.com/advisories/GHSA-5q6v-fp9h-6rjg</url>
       <cvename>CVE-2024-7969</cvename>
       <url>https://github.com/advisories/GHSA-p8h7-64p8-w5pq</url>
       <cvename>CVE-2024-7970</cvename>
       <url>https://github.com/advisories/GHSA-4c4w-77f9-v9mq</url>
       <cvename>CVE-2024-8362</cvename>
       <url>https://github.com/advisories/GHSA-rw7g-4966-p363</url>
       <cvename>CVE-2024-8636</cvename>
       <url>https://github.com/advisories/GHSA-r6cg-gw4p-5gmj</url>
       <cvename>CVE-2024-9123</cvename>
       <url>https://github.com/advisories/GHSA-xwv3-34j2-7jgx</url>
       <cvename>CVE-2024-9120</cvename>
       <url>https://github.com/advisories/GHSA-xh87-v57g-jhpw</url>
     </references>
     <dates>
       <discovery>2024-10-24</discovery>
       <entry>2024-10-24</entry>
     </dates>
   </vuln>
 
   <vuln vid="78e6c113-91c1-11ef-a904-2cf05da270f3">
     <topic>Gitlab -- vulnerabilities</topic>
     <affects>
       <package>
 	<name>gitlab-ce</name>
 	<name>gitlab-ee</name>
 	<range><ge>17.5.0</ge><lt>17.5.1</lt></range>
 	<range><ge>17.4.0</ge><lt>17.4.3</lt></range>
 	<range><ge>11.2.0</ge><lt>17.3.6</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Gitlab reports:</p>
 	<blockquote cite="https://about.gitlab.com/releases/2024/10/23/patch-release-gitlab-17-5-1-released/">
 	  <p>HTML injection in Global Search may lead to XSS</p>
 	  <p>DoS via XML manifest file import</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-8312</cvename>
       <cvename>CVE-2024-6826</cvename>
       <url>https://about.gitlab.com/releases/2024/10/23/patch-release-gitlab-17-5-1-released/</url>
     </references>
     <dates>
       <discovery>2024-10-23</discovery>
       <entry>2024-10-24</entry>
     </dates>
   </vuln>
 
   <vuln vid="cc068959-ce2b-42eb-81ed-055551fe0e51">
     <topic>electron32 -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>electron32</name>
 	<range><lt>32.2.2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Electron developers report:</p>
 	<blockquote cite="https://github.com/electron/electron/releases/tag/v32.2.2">
 	  <p>This update fixes the following vulnerabilities:</p>
 	  <ul>
 	    <li>Security: backported fix for CVE-2024-7966.</li>
 	    <li>Security: backported fix for CVE-2024-9370.</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-7966</cvename>
       <url>https://github.com/advisories/GHSA-4pj3-wmgx-2h8r</url>
       <cvename>CVE-2024-9370</cvename>
     </references>
     <dates>
       <discovery>2024-10-23</discovery>
       <entry>2024-10-23</entry>
     </dates>
   </vuln>
 
   <vuln vid="dbe8c5bd-8d3f-11ef-8d2e-a04a5edf46d9">
     <topic>oauth2-proxy -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>oauth2-proxy</name>
 	<range><lt>7.7.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The oauth2-proxy project reports:</p>
 	<blockquote cite="https://github.com/oauth2-proxy/oauth2-proxy/releases/tag/v7.7.0">
 	  <p>Vulnerabilities have been addressed:</p>
 	  <ul>
 	    <li>CVE-2024-24786</li>
 	    <li>CVE-2024-24791</li>
 	    <li>CVE-2024-24790</li>
 	    <li>CVE-2024-24784</li>
 	    <li>CVE-2024-28180</li>
 	    <li>CVE-2023-45288</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-24786</cvename>
       <cvename>CVE-2024-24791</cvename>
       <cvename>CVE-2024-24790</cvename>
       <cvename>CVE-2024-24784</cvename>
       <cvename>CVE-2024-28180</cvename>
       <cvename>CVE-2024-45288</cvename>
       <url>https://github.com/oauth2-proxy/oauth2-proxy/releases/tag/v7.7.0</url>
     </references>
     <dates>
       <discovery>2024-10-02</discovery>
       <entry>2024-10-18</entry>
     </dates>
   </vuln>
 
   <vuln vid="c6f4177c-8e29-11ef-98e7-84a93843eb75">
     <topic>OpenSSL -- OOB memory access vulnerability</topic>
     <affects>
       <package>
 	<name>openssl</name>
 	<range><lt>3.0.15_1,1</lt></range>
       </package>
       <package>
 	<name>openssl31</name>
 	<range><lt>3.1.7_1</lt></range>
       </package>
       <package>
 	<name>openssl32</name>
 	<range><lt>3.2.3_1</lt></range>
       </package>
       <package>
 	<name>openssl33</name>
 	<range><lt>3.3.2_1</lt></range>
       </package>
       <package>
 	<name>openssl-quictls</name>
 	<range><lt>3.0.15_1,1</lt></range>
       </package>
       <package>
 	<name>openssl31-quictls</name>
 	<range><lt>3.1.7_1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The OpenSSL project reports:</p>
 	<blockquote cite="https://openssl-library.org/news/secadv/20241016.txt">
 	  <p>Low-level invalid GF(2^m) parameters lead to OOB memory access
 	   (CVE-2024-9143) (Low)</p>
 	  <p> Use of the low-level GF(2^m) elliptic curve APIs with untrusted
 	    explicit values for the field polynomial can lead to out-of-bounds
 	    memory reads or writes.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-9143</cvename>
       <url>https://openssl-library.org/news/secadv/20241016.txt</url>
     </references>
     <dates>
       <discovery>2024-10-16</discovery>
       <entry>2024-10-19</entry>
     </dates>
   </vuln>
 
   <vuln vid="815bf172-ab9e-4c4b-9662-d18b0054330d">
     <topic>electron{31,32} -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>electron31</name>
 	<range><lt>31.7.1</lt></range>
       </package>
       <package>
 	<name>electron32</name>
 	<range><lt>32.2.1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Electron developers report:</p>
 	<blockquote cite="https://github.com/electron/electron/releases/tag/v31.7.1">
 	  <p>This update fixes the following vulnerabilities:</p>
 	  <ul>
 	    <li>Security: backported fix for CVE-2024-9602.</li>
 	    <li>Security: backported fix for CVE-2024-9603.</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-9602</cvename>
       <url>https://github.com/advisories/GHSA-4v8q-vp3v-vvxh</url>
       <cvename>CVE-2024-9603</cvename>
       <url>https://github.com/advisories/GHSA-92m3-m5pw-p2x9</url>
     </references>
     <dates>
       <discovery>2024-10-16</discovery>
       <entry>2024-10-18</entry>
     </dates>
   </vuln>
 
   <vuln vid="851ce3e4-8b03-11ef-84e9-901b0e9408dc">
     <topic>element-web -- Potential exposure of access token via authenticated media</topic>
     <affects>
       <package>
 	<name>element-web</name>
 	<range><ge>1.11.70</ge><lt>1.11.81</lt>
 	</range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Element team reports:</p>
 	<blockquote cite="https://github.com/element-hq/element-web/security/advisories/GHSA-3jm3-x98c-r34x">
 	  <p>Element Web versions 1.11.70 through 1.11.80 contain a
 	  vulnerability which can, under specially crafted conditions,
 	  lead to the access token becoming exposed to third
 	  parties. At least one vector has been identified internally,
 	  involving malicious widgets, but other vectors may
 	  exist. Users are strongly advised to upgrade to version
 	  1.11.81 to remediate the issue.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-47779</cvename>
       <url>https://github.com/element-hq/element-web/security/advisories/GHSA-3jm3-x98c-r34x</url>
     </references>
     <dates>
       <discovery>2024-10-15</discovery>
       <entry>2024-10-15</entry>
     </dates>
   </vuln>
 
   <vuln vid="64e299b6-d12b-4a7a-a94f-ab133703925a">
     <topic>vscode -- Visual Studio Code for Linux Remote Code Execution Vulnerability</topic>
     <affects>
       <package>
 	<name>vscode</name>
 	<range><lt>1.94.1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>VSCode developers report:</p>
 	<blockquote cite="https://github.com/microsoft/vscode/security/advisories/GHSA-g56j-w527-8x6f">
 	  <p>Visual Studio Code for Linux Remote Code Execution Vulnerability</p>
 	  <p>A remote code execution vulnerability exists in VS Code 1.94.0 and earlier versions in the elevated save flow.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-43601</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-43601</url>
       <url>https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-43601</url>
     </references>
     <dates>
       <discovery>2024-10-08</discovery>
       <entry>2024-10-11</entry>
     </dates>
   </vuln>
 
   <vuln vid="2fb13238-872d-11ef-bd1e-b42e991fc52e">
     <topic>firefox -- use-after-free code execution</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>131.0.2,2</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>128.3.1,1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1923344">
 	  <p>An attacker was able to achieve code execution in the
 	content process by exploiting a use-after-free in Animation
 	timelines. We have had reports of this vulnerability being
 	exploited in the wild.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-9680</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-9680</url>
     </references>
     <dates>
       <discovery>2024-10-09</discovery>
       <entry>2024-10-10</entry>
     </dates>
   </vuln>
 
   <vuln vid="cc1ac01e-86b0-11ef-9369-2cf05da270f3">
     <topic>Gitlab -- vulnerabilities</topic>
     <affects>
       <package>
 	<name>gitlab-ce</name>
 	<name>gitlab-ee</name>
 	<range><ge>17.4.0</ge><lt>17.4.2</lt></range>
 	<range><ge>17.3.0</ge><lt>17.3.5</lt></range>
 	<range><ge>8.16</ge><lt>17.2.9</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Gitlab reports:</p>
 	<blockquote cite="https://about.gitlab.com/releases/2024/10/09/patch-release-gitlab-17-4-2-released/">
 	  <p>Run pipelines on arbitrary branches</p>
 	  <p>An attacker can impersonate arbitrary user</p>
 	  <p>SSRF in Analytics Dashboard</p>
 	  <p>Viewing diffs of MR with conflicts can be slow</p>
 	  <p>HTMLi in OAuth page</p>
 	  <p>Deploy Keys can push changes to an archived repository</p>
 	  <p>Guests can disclose project templates</p>
 	  <p>GitLab instance version disclosed to unauthorized users</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-9164</cvename>
       <cvename>CVE-2024-8970</cvename>
       <cvename>CVE-2024-8977</cvename>
       <cvename>CVE-2024-9631</cvename>
       <cvename>CVE-2024-6530</cvename>
       <cvename>CVE-2024-9623</cvename>
       <cvename>CVE-2024-5005</cvename>
       <cvename>CVE-2024-9596</cvename>
       <url>https://about.gitlab.com/releases/2024/10/09/patch-release-gitlab-17-4-2-released/</url>
     </references>
     <dates>
       <discovery>2024-10-09</discovery>
       <entry>2024-10-10</entry>
     </dates>
   </vuln>
 
   <vuln vid="79b1f4ee-860a-11ef-b2dc-cbccbf25b7ea">
     <topic>gitea -- token missing access control for packages</topic>
     <affects>
       <package>
 	<name>gitea</name>
 	<range><lt>1.22.3</lt></range>
       </package>
     </affects>
     <description>
        <body xmlns="http://www.w3.org/1999/xhtml">
        <h1>Problem Description:</h1>
        <ul>
        <li>Fix bug when a token is given public only</li>
        </ul>
       </body>
     </description>
     <references>
       <url>https://github.com/go-gitea/gitea/pull/32204</url>
     </references>
     <dates>
       <discovery>2024-10-06</discovery>
       <entry>2024-10-09</entry>
     </dates>
   </vuln>
 
   <vuln vid="8727b513-855b-11ef-9e50-6805ca2fa271">
     <topic>powerdns-recursor -- denial of service</topic>
     <affects>
       <package>
 	<name>powerdns-recursor</name>
 	<range><lt>5.1.2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>PowerDNS Team reports:</p>
 	<blockquote cite="https://blog.powerdns.com/2024/10/03/powerdns-recursor-4-9-9-5-0-9-5-1-2-released">
 	  <p>PowerDNS Security Advisory 2024-04: Crafted responses can lead to
 	   a denial of service due to cache inefficiencies in the Recursor</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-25590</cvename>
       <url>https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2024-04.html</url>
     </references>
     <dates>
       <discovery>2024-10-03</discovery>
       <entry>2024-10-09</entry>
     </dates>
   </vuln>
 
   <vuln vid="7217f6e8-3ff4-4387-845d-d1744bb7f95e">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>129.0.6668.100</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>129.0.6668.100</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2024/10/stable-channel-update-for-desktop_8.html">
 	 <p>This update includes 3 security fixes:</p>
 	 <ul>
 	    <li>[368241697] High CVE-2024-9602: Type Confusion in V8. Reported by Seunghyun Lee (@0x10n) on 2024-09-20</li>
 	    <li>[367818758] High CVE-2024-9603: Type Confusion in V8. Reported by @WeShotTheMoon and @Nguyen Hoang Thach of starlabs on 2024-09-18</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-9602</cvename>
       <cvename>CVE-2024-9603</cvename>
       <url>https://chromereleases.googleblog.com/2024/10/stable-channel-update-for-desktop_8.html</url>
     </references>
     <dates>
       <discovery>2024-10-08</discovery>
       <entry>2024-10-09</entry>
     </dates>
   </vuln>
 
   <vuln vid="83117378-f773-4617-bf74-477d569dcd74">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>129.0.6668.89</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>129.0.6668.89</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2024/10/stable-channel-update-for-desktop.html">
 	 <p>This update includes 4 security fixes:</p>
 	 <ul>
 	    <li>[367764861] High CVE-2024-7025: Integer overflow in Layout. Reported by Tashita Software Security on 2024-09-18</li>
 	    <li>[368208152] High CVE-2024-9369: Insufficient data validation in Mojo. Reported by Xiantong Hou and Pisanbao of Wuheng Lab on 2024-09-19</li>
 	    <li>[368311899] High CVE-2024-9370: Inappropriate implementation in V8. Reported by Nguyễn Hoàng Thạch, Đỗ Minh Tuấn, and Wu JinLin of STAR Labs SG Pte. Ltd. on 2024-09-19</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-7025</cvename>
       <cvename>CVE-2024-9369</cvename>
       <cvename>CVE-2024-9370</cvename>
       <url>https://chromereleases.googleblog.com/2024/10/stable-channel-update-for-desktop.html</url>
     </references>
     <dates>
       <discovery>2024-10-01</discovery>
       <entry>2024-10-09</entry>
     </dates>
   </vuln>
 
   <vuln vid="2368755b-83f6-11ef-8d2e-a04a5edf46d9">
     <topic>Unbound -- Denial of service attack</topic>
     <affects>
       <package>
 	<name>unbound</name>
 	<range><lt>1.21.1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>NLnet labs report:</p>
 	<blockquote cite="https://nlnetlabs.nl/news/2024/Oct/03/unbound-1.21.1-released/">
 	  <p>A vulnerability has been discovered in Unbound when handling
 	    replies with very large RRsets that Unbound needs to perform name
 	    compression for.</p>
 	  <p>Malicious upstreams responses with very large RRsets can cause
 	    Unbound to spend a considerable time applying name compression to
 	    downstream replies. This can lead to degraded performance and
 	    eventually denial of service in well orchestrated attacks.</p>
 	  <p>Unbound version 1.21.1 introduces a hard limit on the number of
 	    name compression calculations it is willing to do per packet.
 	    Packets that need more compression will result in semi-compressed
 	    packets or truncated packets, even on TCP for huge messages, to
 	    avoid locking the CPU for long.</p>
 	  <p>This change should not affect normal DNS traffic.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-8508</cvename>
       <url>https://nlnetlabs.nl/news/2024/Oct/03/unbound-1.21.1-released/</url>
     </references>
     <dates>
       <discovery>2024-10-03</discovery>
       <entry>2024-10-06</entry>
     </dates>
   </vuln>
 
   <vuln vid="fe7031d3-3000-4b43-9fa6-52c2b624b8f9">
     <topic>zeek -- potential DoS vulnerability</topic>
     <affects>
       <package>
 	<name>zeek</name>
 	<range><lt>7.0.3</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Tim Wojtulewicz of Corelight reports:</p>
 	<blockquote cite="https://github.com/zeek/zeek/releases/tag/v7.0.3">
 	  <p> Adding to the POP3 hardening in 7.0.2, the parser now
 	  simply discards too many pending commands, rather than
 	  any attempting to process them. Further, invalid server
 	  responses do not result in command completion anymore.
 	  Processing out-of-order commands or finishing commands
 	  based on invalid server responses could result in
 	  inconsistent analyzer state, potentially triggering null
 	  pointer references for crafted traffic. </p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <url>https://github.com/zeek/zeek/releases/tag/v7.0.3</url>
     </references>
     <dates>
       <discovery>2024-10-05</discovery>
       <entry>2024-10-05</entry>
     </dates>
   </vuln>
 
   <vuln vid="0417d41a-8175-11ef-a5dc-b42e991fc52e">
     <topic>firefox -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>131.0,2</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>128.3.0,1</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>128.3.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/buglist.cgi?bug_id=1872744%2C1897792%2C1911317%2C1913445%2C1914106%2C1914475%2C1914963%2C1915008%2C1916476">
 	<ul>
 	<li>CVE-2024-9392: A compromised content process could have
 	allowed for the arbitrary loading of cross-origin pages.</li>
 	<li>CVE-2024-9396: It is currently unknown if this issue is
 	exploitable but a condition may arise where the structured
 	clone of certain objects could lead to memory corruption.</li>
 	<li>CVE-2024-9400: A potential memory corruption vulnerability
 	could be triggered if an attacker had the ability to trigger
 	an OOM at a specific moment during JIT compilation.</li>
 	<li>CVE-2024-9401: Memory safety bugs present in Firefox 130,
 	Firefox ESR 115.15, Firefox ESR 128.2, and Thunderbird 128.2.
 	Some of these bugs showed evidence of memory corruption and we
 	presume that with enough effort some of these could have been
 	exploited to run arbitrary code.</li>
 	<li>CVE-2024-9402: Memory safety bugs present in Firefox 130,
 	Firefox ESR 128.2, and Thunderbird 128.2.  Some of these bugs
 	showed evidence of memory corruption and we presume that with
 	enough effort some of these could have been exploited to run
 	arbitrary code.</li>
 	<li>CVE-2024-9403: Memory safety bugs present in Firefox 130.
 	Some of these bugs showed evidence of memory corruption and we
 	presume that with enough effort some of these could have been
 	exploited to run arbitrary code.</li>
 	</ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-9392</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-9392</url>
       <cvename>CVE-2024-9396</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-9396</url>
       <cvename>CVE-2024-9400</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-9400</url>
       <cvename>CVE-2024-9401</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-9401</url>
       <cvename>CVE-2024-9402</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-9402</url>
       <cvename>CVE-2024-9403</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-9403</url>
     </references>
     <dates>
       <discovery>2024-10-01</discovery>
       <entry>2024-10-03</entry>
     </dates>
   </vuln>
 
   <vuln vid="3c6f8270-3210-4e2f-ba72-a9cdca7417a0">
     <topic>jenkins -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>jenkins</name>
 	<range><lt>2.479</lt></range>
       </package>
       <package>
 	<name>jenkins-lts</name>
 	<range><lt>2.462.3</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Jenkins Security Advisory:</p>
 	<blockquote cite="https://www.jenkins.io/security/advisory/2024-10-02/">
 	  <h1>Description</h1>
 	  <h5>(Medium) SECURITY-3451 / CVE-2024-47803</h5>
 	  <p>Exposure of multi-line secrets through error messages in Jenkins</p>
 	  <h1>Description</h1>
 	  <h5>(Medium) SECURITY-3448 / CVE-2024-47804</h5>
 	  <p>Item creation restriction bypass vulnerability in Jenkins</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-47803</cvename>
       <cvename>CVE-2024-47804</cvename>
       <url>https://www.jenkins.io/security/advisory/2024-10-02/</url>
     </references>
     <dates>
       <discovery>2024-10-02</discovery>
       <entry>2024-10-03</entry>
     </dates>
   </vuln>
 
   <vuln vid="8b20f21a-8113-11ef-b988-08002784c58d">
     <topic>redis,valkey -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>redis</name>
 	<range><ge>7.4.0</ge><lt>7.4.1</lt></range>
 	<range><ge>7.2.0</ge><lt>7.2.6</lt></range>
       </package>
       <package>
 	<name>redis72</name>
 	<range><ge>7.2.0</ge><lt>7.2.6</lt></range>
       </package>
       <package>
 	<name>redis62</name>
 	<range><ge>6.2.0</ge><lt>6.2.16</lt></range>
       </package>
       <package>
 	<name>valkey</name>
 	<range><ge>8,0,0</ge><lt>8.0.1</lt></range>
 	<range><ge>7.2.0</ge><lt>7.2.7</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Redis core team reports:</p>
 	<blockquote cite="https://github.com/redis/redis/releases/tag/7.4.1">
 	  <dl>
 	    <dt>CVE-2024-31449</dt>
 	    <dd>Lua library commands may lead to stack overflow and potential RCE.</dd>
 	    <dt>CVE-2024-31227</dt>
 	    <dd>Potential Denial-of-service due to malformed ACL selectors.</dd>
 	    <dt>CVE-2024-31228</dt>
 	    <dd>Potential Denial-of-service due to unbounded pattern matching.</dd>
 	  </dl>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-31449</cvename>
       <cvename>CVE-2024-31227</cvename>
       <cvename>CVE-2024-31228</cvename>
       <url>https://github.com/redis/redis/releases/tag/7.4.1</url>
     </references>
     <dates>
       <discovery>2024-10-02</discovery>
       <entry>2024-10-02</entry>
     </dates>
   </vuln>
 
   <vuln vid="fe5c1e7a-7eed-11ef-9533-f875a43e1796">
     <topic>php -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	      <name>php81</name>
 	      <range><lt>8.1.30</lt></range>
       </package>
       <package>
 	      <name>php82</name>
 	      <range><lt>8.2.24</lt></range>
       </package>
       <package>
 	      <name>php83</name>
 	      <range><lt>8.3.12</lt></range>
       </package>
     </affects>
     <description>
 	    <body xmlns="http://www.w3.org/1999/xhtml">
 	      <p>php.net reports:</p>
 	      <blockquote cite="https://www.php.net/ChangeLog-8.php">
 					<ul>
 						<li>CVE-2024-8926: CGI: Fixed bug GHSA-9pqp-7h25-4f32 (Bypass of CVE-2024-4577, Parameter Injection Vulnerability).</li>
 						<li>CVE-2024-8927: CGI: Fixed bug GHSA-94p6-54jq-9mwp (cgi.force_redirect configuration is bypassable due to the environment variable collision).</li>
 						<li>CVE-2024-9026: FPM: Fixed bug GHSA-865w-9rf3-2wh5 (Logs from childrens may be altered).</li>
 						<li>CVE-2024-8925: SAPI: Fixed bug GHSA-9pqp-7h25-4f32 (Erroneous parsing of multipart form data).</li>
 					</ul>
 	      </blockquote>
 	    </body>
     </description>
     <references>
       <cvename>CVE-2024-8926</cvename>
       <cvename>CVE-2024-8927</cvename>
       <cvename>CVE-2024-9026</cvename>
       <cvename>CVE-2024-8925</cvename>
       <url>https://www.php.net/ChangeLog-8.php</url>
     </references>
     <dates>
       <discovery>2024-09-26</discovery>
       <entry>2024-09-30</entry>
     </dates>
   </vuln>
 
   <vuln vid="f9cfdb00-7f43-11ef-9b27-592d55dd336d">
     <topic>Slixmpp -- Lack of SSL Certificate hostname validation in XMLStream</topic>
     <affects>
       <package>
 	<name>py38-slixmpp</name>
 	<name>py39-slixmpp</name>
 	<name>py310-slixmpp</name>
 	<name>py311-slixmpp</name>
 	<range><lt>1.8.3</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>NIST reports:</p>
 	<blockquote cite="https://nvd.nist.gov/vuln/detail/CVE-2022-45197">
 	  <p>Slixmpp before 1.8.3 lacks SSL Certificate hostname validation in XMLStream,
 	allowing an attacker to pose as any server in the eyes of Slixmpp.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2022-45197</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2022-45197</url>
     </references>
     <dates>
       <discovery>2022-12-25</discovery>
       <entry>2024-09-30</entry>
     </dates>
   </vuln>
 
   <vuln vid="2f82696c-adad-447b-9938-c99441805fa3">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>129.0.6668.70</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>129.0.6668.70</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2024/09/stable-channel-update-for-desktop_24.html">
 	 <p>This update includes 5 security fixes:</p>
 	 <ul>
 	    <li>[365254285] High CVE-2024-9120: Use after free in Dawn. Reported by Anonymous on 2024-09-08</li>
 	    <li>[363538434] High CVE-2024-9121: Inappropriate implementation in V8. Reported by Tashita Software Security on 2024-09-01</li>
 	    <li>[365802567] High CVE-2024-9122: Type Confusion in V8. Reported by Seunghyun Lee (@0x10n) on 2024-09-10</li>
 	    <li>[365884464] High CVE-2024-9123: Integer overflow in Skia. Reported by raven at KunLun lab on 2024-09-11</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-9120</cvename>
       <cvename>CVE-2024-9121</cvename>
       <cvename>CVE-2024-9122</cvename>
       <cvename>CVE-2024-9123</cvename>
       <url>https://chromereleases.googleblog.com/2024/09/stable-channel-update-for-desktop_24.html</url>
     </references>
     <dates>
       <discovery>2024-09-24</discovery>
       <entry>2024-09-30</entry>
     </dates>
   </vuln>
 
   <vuln vid="42ec2207-7e85-11ef-89a4-b42e991fc52e">
     <topic>sqlite -- use-after-free bug in jsonparseaddnodearray</topic>
     <affects>
       <package>
 	<name>sqlite3</name>
-	<range><ge>3.43.0</ge><lt>3.43.2,1</lt></range>
+	<range><ge>3.43.0,1</ge><lt>3.43.2,1</lt></range>
       </package>
       <package>
 	<name>linux-rl9-sqlite</name>
-	<range><ge>3.43.0</ge><lt>3.43.2</lt></range>
+	<range><ge>3.43.0,1</ge><lt>3.43.2,1</lt></range>
       </package>
       <package>
 	<name>linux-c7-sqlite</name>
-	<range><ge>3.43.0</ge><lt>3.43.2</lt></range>
+	<range><ge>3.43.0,1</ge><lt>3.43.2,1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>secalert@redhat.com reports:</p>
 	<blockquote cite="https://access.redhat.com/security/cve/CVE-2024-0232">
 	  <p>A heap use-after-free issue has been identified in SQLite in the
 	jsonParseAddNodeArray() function in sqlite3.c.  This flaw allows a
 	local attacker to leverage a victim to pass specially crafted
 	malicious input to the application, potentially causing a crash and
 	leading to a denial of service.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-0232</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-0232</url>
     </references>
     <dates>
       <discovery>2024-01-16</discovery>
       <entry>2024-09-29</entry>
+      <modified>2025-08-01</modified>
     </dates>
   </vuln>
 
   <vuln vid="24375796-7cbc-11ef-a3a9-001cc0382b2f">
     <topic>cups-filters -- remote code execution</topic>
     <affects>
       <package>
 	<name>cups-filters</name>
 	<range><lt>1.28.17_6</lt></range>
       </package>
       <package>
 	<name>cups</name>
 	<range><lt>2.4.11</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>OpenPrinting reports:</p>
 	<blockquote cite="https://github.com/OpenPrinting/cups-browsed/security/advisories/GHSA-rj88-6mr5-rcw8">
 	  <p>Due to the service binding to *:631 ( INADDR_ANY ), multiple bugs
 	    in cups-browsed can be exploited in sequence to introduce a
 	    malicious printer to the system. This chain of exploits ultimately
 	    enables an attacker to execute arbitrary commands remotely on the
 	    target machine without authentication when a print job is started.
 	    Posing a significant security risk over the network. Notably, this
 	    vulnerability is particularly concerning as it can be exploited
 	    from the public internet, potentially exposing a vast number of
 	    systems to remote attacks if their CUPS services are enabled.</p>
 	</blockquote>
 	<p>The vulnerability allows an attacker on the internet to create a
 	  new printer device with arbitrary commands in the PPD file of the
 	  printer. Attacks using mDNS on the local network can also replace an
 	  existing printer. The commands are executed when a user attempts to
 	  print on the malicious device. They run with the privileges of the
 	  user "cups".</p>
 	<p>It is recommended to disable the cups_browsed service until patches
 	  become available. On FreeBSD this is the default. You can check the
 	  status and disable the service with the following commands:</p>
 	<p><code># service cups_browsed status<br />
 	  # service cups_browsed stop<br />
 	  # service cups_browsed disable</code></p>
 	<p>If you choose to leave the service enabled, attacks from the
 	  internet can be blocked by removing the "cups" protocol from the
 	  BrowseRemoteProtocols and BrowseProtocols directives in
 	  /usr/local/etc/cups/cups-browsed.conf. Attacks using mDNS can be
 	  blocked by removing the "dnssd" protocol as well. Access can be
 	  limited to specific IP addresses using BrowseAllow, BrowseDeny, and
 	  BrowseOrder directives as documented in cups-browsed.conf(5). Then
 	  restart the service with the following command:</p>
 	<p><code># service cups_browsed restart</code></p>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-47076</cvename>
       <cvename>CVE-2024-47175</cvename>
       <cvename>CVE-2024-47176</cvename>
       <url>https://github.com/OpenPrinting/cups-browsed/security/advisories/GHSA-rj88-6mr5-rcw8</url>
     </references>
     <dates>
       <discovery>2024-09-26</discovery>
       <entry>2024-09-27</entry>
       <modified>2024-10-02</modified>
     </dates>
   </vuln>
 
   <vuln vid="ca5f3bbc-7a62-11ef-9533-f875a43e1796">
     <topic>expat -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>expat</name>
 	<range><lt>2.6.3</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>libexpat reports:</p>
 	<blockquote cite="https://github.com/libexpat/libexpat/blob/master/expat/Changes">
 	<ul>
 	<li>CVE-2024-45490: Calling function XML_ParseBuffer with
 	len &lt; 0 without noticing and then calling XML_GetBuffer
 	will have XML_ParseBuffer fail to recognize the problem
 	and XML_GetBuffer corrupt memory.
 	With the fix, XML_ParseBuffer now complains with error
 	XML_ERROR_INVALID_ARGUMENT just like sibling XML_Parse
 	has been doing since Expat 2.2.1, and now documented.
 	Impact is denial of service to potentially artitrary code
 	execution.</li>
 	<li>CVE-2024-45491: Internal function dtdCopy can have an
 	integer overflow for nDefaultAtts on 32-bit platforms
 	(where UINT_MAX equals SIZE_MAX).
 	Impact is denial of service to potentially artitrary code
 	execution.</li>
 	<li>CVE-2024-45492: Internal function nextScaffoldPart can
 	have an integer overflow for m_groupSize on 32-bit
 	platforms (where UINT_MAX equals SIZE_MAX).
 	Impact is denial of service to potentially artitrary code
 	execution.</li>
 	</ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-45490</cvename>
       <cvename>CVE-2024-45491</cvename>
       <cvename>CVE-2024-45492</cvename>
       <url>https://github.com/libexpat/libexpat/blob/master/expat/Changes</url>
     </references>
     <dates>
       <discovery>2024-09-24</discovery>
       <entry>2024-09-24</entry>
     </dates>
   </vuln>
 
   <vuln vid="4b7ed61f-7bbf-11ef-9369-2cf05da270f3">
     <topic>Gitlab -- vulnerabilities</topic>
     <affects>
       <package>
 	<name>gitlab-ce</name>
 	<name>gitlab-ee</name>
 	<range><ge>17.4.0</ge><lt>17.4.1</lt></range>
 	<range><ge>17.3.0</ge><lt>17.3.4</lt></range>
 	<range><ge>15.6.0</ge><lt>17.2.8</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Gitlab reports:</p>
 	<blockquote cite="https://about.gitlab.com/releases/2024/09/25/patch-release-gitlab-17-4-1-released/">
 	  <p>Maintainer can leak Dependency Proxy password by changing Dependency Proxy URL via crafted POST request</p>
 	  <p>AI feature reads unsanitized content, allowing for attacker to hide prompt injection</p>
 	  <p>Project reference can be exposed in system notes</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-4278</cvename>
       <cvename>CVE-2024-4099</cvename>
       <cvename>CVE-2024-8974</cvename>
       <url>https://about.gitlab.com/releases/2024/09/25/patch-release-gitlab-17-4-1-released/</url>
     </references>
     <dates>
       <discovery>2024-09-25</discovery>
       <entry>2024-09-26</entry>
     </dates>
   </vuln>
 
   <vuln vid="802961eb-7a89-11ef-bdd7-a0423f48a938">
     <topic>frr - BGP</topic>
     <affects>
       <package>
 	<name>frr9</name>
 	<range><lt>9.1.2</lt></range>
       </package>
       <package>
 	<name>frr8</name>
 	<range><lt>8.5.6</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>cve@mitre.org reports:</p>
 	<blockquote cite="https://github.com/FRRouting/frr/pull/16497">
 	  <p>An issue was discovered in FRRouting (FRR). bgp_attr_encap
 	in bgpd/bgp_attr.c does not check the actual remaining stream length
 	before taking the TLV value.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-44070</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-44070</url>
     </references>
     <dates>
       <discovery>2024-08-19</discovery>
       <entry>2024-09-24</entry>
     </dates>
   </vuln>
 
   <vuln vid="d47b7ae7-fe1d-4f7f-919a-480ca8035f00">
     <topic>zeek -- potential DoS vulnerability</topic>
     <affects>
       <package>
 	<name>zeek</name>
 	<range><lt>7.0.2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Tim Wojtulewicz of Corelight reports:</p>
 	<blockquote cite="https://github.com/zeek/zeek/releases/tag/v7.0.2">
 	  <p> The POP3 parser has been hardened to avoid unbounded
 	  state growth in the face of one-sided traffic capture or
 	  when enabled for non-POP3 traffic. </p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <url>https://github.com/zeek/zeek/releases/tag/v7.0.2</url>
     </references>
     <dates>
       <discovery>2024-09-24</discovery>
       <entry>2024-09-24</entry>
     </dates>
   </vuln>
 
   <vuln vid="c02b8db5-771b-11ef-9a62-002590c1f29c">
     <topic>FreeBSD -- NFS client accepts file names containing path separators</topic>
     <affects>
       <package>
 	<name>FreeBSD-kernel</name>
 	<range><ge>14.1</ge><lt>14.1_3</lt></range>
 	<range><ge>14.0</ge><lt>14.0_9</lt></range>
 	<range><ge>13.3</ge><lt>13.3_5</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<h1>Problem Description:</h1>
 	<p>When mounting a remote filesystem using NFS, the kernel did not
 	sanitize remotely provided filenames for the path separator character,
 	"/".  This allows readdir(3) and related functions to return
 	filesystem entries with names containing additional path components.</p>
 	<h1>Impact:</h1>
 	<p>The lack of validation described above gives rise to a confused
 	deputy problem.  For example, a program copying files from an NFS
 	mount could be tricked into copying from outside the intended source
 	directory, and/or to a location outside the intended destination
 	directory.</p>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-6759</cvename>
       <freebsdsa>SA-24:07.nfsclient</freebsdsa>
     </references>
     <dates>
       <discovery>2024-08-07</discovery>
       <entry>2024-09-20</entry>
     </dates>
   </vuln>
 
   <vuln vid="8fb61d94-771b-11ef-9a62-002590c1f29c">
     <topic>FreeBSD -- ktrace(2) fails to detach when executing a setuid binary</topic>
     <affects>
       <package>
 	<name>FreeBSD-kernel</name>
 	<range><ge>14.1</ge><lt>14.1_3</lt></range>
 	<range><ge>14.0</ge><lt>14.0_9</lt></range>
 	<range><ge>13.3</ge><lt>13.3_5</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<h1>Problem Description:</h1>
 	<p>A logic bug in the code which disables kernel tracing for setuid
 	programs meant that tracing was not disabled when it should have,
 	allowing unprivileged users to trace and inspect the behavior of
 	setuid programs.</p>
 	<h1>Impact:</h1>
 	<p>The bug may be used by an unprivileged user to read the contents
 	of files to which they would not otherwise have access, such as the
 	local password database.</p>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-6760</cvename>
       <freebsdsa>SA-24:06.ktrace</freebsdsa>
     </references>
     <dates>
       <discovery>2024-08-07</discovery>
       <entry>2024-09-20</entry>
     </dates>
   </vuln>
 
   <vuln vid="f140cff0-771a-11ef-9a62-002590c1f29c">
     <topic>FreeBSD -- pf incorrectly matches different ICMPv6 states in the state table</topic>
     <affects>
       <package>
 	<name>FreeBSD-kernel</name>
 	<range><ge>14.1</ge><lt>14.1_3</lt></range>
 	<range><ge>14.0</ge><lt>14.0_9</lt></range>
 	<range><ge>13.3</ge><lt>13.3_5</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<h1>Problem Description:</h1>
 	<p>In ICMPv6 Neighbor Discovery (ND), the ID is always 0.  When
 	pf is configured to allow ND and block incoming Echo Requests, a
 	crafted Echo Request packet after a Neighbor Solicitation (NS) can
 	trigger an Echo Reply.  The packet has to come from the same host
 	as the NS and have a zero as identifier to match the state created
 	by the Neighbor Discovery and allow replies to be generated.</p>
 	<h1>Impact:</h1>
 	<p>ICMPv6 packets with identifier value of zero bypass firewall
 	rules written on the assumption that the incoming packets are going
 	to create a state in the state table.</p>
 	<h1>Note:</h1>
 	<p>This advisory introduced additional issues that were addressed by
 	FreeBSD-EN-24:16.pf.  Please refer to that erratum for additional
 	fixes.</p>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-6640</cvename>
       <freebsdsa>SA-24:05.pf</freebsdsa>
       <url>https://www.freebsd.org/security/advisories/FreeBSD-EN-24:16.pf.asc</url>
     </references>
     <dates>
       <discovery>2024-08-07</discovery>
       <entry>2024-09-20</entry>
     </dates>
   </vuln>
 
   <vuln vid="93c12fe5-7716-11ef-9a62-002590c1f29c">
     <topic>FreeBSD -- Integer overflow in libnv</topic>
     <affects>
       <package>
 	<name>FreeBSD-kernel</name>
 	<range><ge>14.1</ge><lt>14.1_5</lt></range>
 	<range><ge>14.0</ge><lt>14.0_11</lt></range>
 	<range><ge>13.4</ge><lt>13.4_1</lt></range>
 	<range><ge>13.3</ge><lt>13.3_7</lt></range>
       </package>
       <package>
 	<name>FreeBSD</name>
 	<range><ge>14.1</ge><lt>14.1_5</lt></range>
 	<range><ge>14.0</ge><lt>14.0_11</lt></range>
 	<range><ge>13.4</ge><lt>13.4_1</lt></range>
 	<range><ge>13.3</ge><lt>13.3_7</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<h1>Problem Description:</h1>
 	<p>A malicious value of size in a structure of packed libnv can
 	cause an integer overflow, leading to the allocation of a smaller
 	buffer than required for the parsed data.  The introduced check was
 	incorrect, as it took into account the size of the pointer, not the
 	structure.  This vulnerability affects both kernel and userland.</p>
 	<p>This issue was originally intended to be addressed as part of
 	FreeBSD-SA-24:09.libnv, but due to a logic issue, this issue was
 	not properly addressed.</p>
 	<h1>Impact:</h1>
 	<p>It is possible for an attacker to overwrite portions of memory
 	(in userland or the kernel) as the allocated buffer might be smaller
 	than the data received from a malicious process.  This vulnerability
 	could result in privilege escalation or cause a system panic.</p>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-45287</cvename>
       <freebsdsa>SA-24:16.libnv</freebsdsa>
     </references>
     <dates>
       <discovery>2024-09-19</discovery>
       <entry>2024-09-20</entry>
     </dates>
   </vuln>
 
   <vuln vid="1febd09b-7716-11ef-9a62-002590c1f29c">
     <topic>FreeBSD -- bhyve(8) out-of-bounds read access via XHCI emulation</topic>
     <affects>
       <package>
 	<name>FreeBSD</name>
 	<range><ge>14.1</ge><lt>14.1_5</lt></range>
 	<range><ge>14.0</ge><lt>14.0_11</lt></range>
 	<range><ge>13.4</ge><lt>13.4_1</lt></range>
 	<range><ge>13.3</ge><lt>13.3_7</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<h1>Problem Description:</h1>
 	<p>bhyve can be configured to emulate devices on a virtual USB
 	controller (XHCI), such as USB tablet devices.  An insufficient
 	boundary validation in the USB code could lead to an out-of-bounds read
 	on the heap, which could potentially lead to an arbitrary write and
 	remote code execution.</p>
 	<h1>Impact:</h1>
 	<p>A malicious, privileged software running in a guest VM can exploit
 	the vulnerability to crash the hypervisor process or potentially achieve
 	code execution on the host in the bhyve userspace process, which
 	typically runs as root.  Note that bhyve runs in a Capsicum sandbox, so
 	malicious code is constrained by the capabilities available to the bhyve
 	process.</p>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-41721</cvename>
       <freebsdsa>SA-24:15.bhyve</freebsdsa>
     </references>
     <dates>
       <discovery>2024-09-19</discovery>
       <entry>2024-09-20</entry>
     </dates>
   </vuln>
 
   <vuln vid="3e738678-7582-11ef-bece-2cf05da270f3">
     <topic>Gitlab -- vulnerabilities</topic>
     <affects>
       <package>
 	<name>gitlab-ce</name>
 	<name>gitlab-ee</name>
 	<range><ge>17.3.0</ge><lt>17.3.3</lt></range>
 	<range><ge>17.2.0</ge><lt>17.2.7</lt></range>
 	<range><ge>0</ge><lt>17.1.8</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Gitlab reports:</p>
 	<blockquote cite="https://about.gitlab.com/releases/2024/09/17/patch-release-gitlab-17-3-3-released/">
 	  <p>SAML authentication bypass</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-45409</cvename>
       <url>https://about.gitlab.com/releases/2024/09/17/patch-release-gitlab-17-3-3-released/</url>
     </references>
     <dates>
       <discovery>2024-09-17</discovery>
       <entry>2024-09-18</entry>
     </dates>
   </vuln>
 
   <vuln vid="58750d49-7302-11ef-8c95-195d300202b3">
     <topic>OpenSSH -- Pre-authentication async signal safety issue</topic>
     <affects>
       <package>
 	<name>openssh-portable</name>
 	<range><lt>9.8.p1_1,1</lt></range>
       </package>
       <package>
 	<name>FreeBSD</name>
 	<range><ge>14.1</ge><lt>14.1_3</lt></range>
 	<range><ge>14.0</ge><lt>14.0_9</lt></range>
 	<range><ge>13.3</ge><lt>13.3_5</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The FreeBSD Project reports:</p>
 	<blockquote cite="https://www.freebsd.org/security/advisories/FreeBSD-SA-24:08.openssh.asc">
 	  <p>
 	    A signal handler in sshd(8) may call a logging function that is not async-
 	    signal-safe. The signal handler is invoked when a client does not
 	    authenticate within the LoginGraceTime seconds (120 by default).
 	    This signal handler executes in the context of the sshd(8)'s privileged
 	    code, which is not sandboxed and runs with full root privileges.</p>
 	    <p>This issue is another instance of the problem in CVE-2024-6387 addressed by
 	    FreeBSD-SA-24:04.openssh.  The faulty code in this case is from the
 	    integration of blacklistd in OpenSSH in FreeBSD.
 	  </p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-7589</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-7589</url>
       <freebsdsa>SA-24:08.openssh</freebsdsa>
     </references>
     <dates>
       <discovery>2024-08-06</discovery>
       <entry>2024-09-15</entry>
       <modified>2024-09-20</modified>
     </dates>
   </vuln>
 
   <vuln vid="bd940aba-7467-11ef-a5c4-08002784c58d">
     <topic>SnappyMail -- multiple mXSS in HTML sanitizer</topic>
     <affects>
       <package>
 	<name>snappymail-php81</name>
 	<name>snappymail-php82</name>
 	<name>snappymail-php83</name>
 	<name>snappymail-php84</name>
 	<range><lt>2.38.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Oskar reports:</p>
 	<blockquote cite="https://github.com/the-djmaze/snappymail/security/advisories/GHSA-2rq7-79vp-ffxm">
 	  <p>
 	    SnappyMail uses the `cleanHtml()` function to cleanup HTML
 	    and CSS in emails. Research discovered that the function
 	    has a few bugs which cause an mXSS exploit. Because the
 	    function allowed too many (invalid) HTML elements, it was
 	    possible (with incorrect markup) to trick the browser to
 	    "fix" the broken markup into valid markup. As a result a
 	    motivated attacker may be able to inject javascript.
 	  </p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-45800</cvename>
       <url>https://github.com/the-djmaze/snappymail/security/advisories/GHSA-2rq7-79vp-ffxm</url>
     </references>
     <dates>
       <discovery>2024-09-16</discovery>
       <entry>2024-09-16</entry>
     </dates>
   </vuln>
 
   <vuln vid="e464f777-719e-11ef-8a0f-a8a1599412c6">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>128.0.6613.137</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>128.0.6613.137</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2024/09/stable-channel-update-for-desktop_10.html">
 	 <p>This update includes 4 security fixes:</p>
 	 <ul>
 	    <li>[361461526] High CVE-2024-8636: Heap buffer overflow in Skia. Reported by Renan Rios (@hyhy_100) on 2024-08-22</li>
 	    <li>[361784548] High CVE-2024-8637: Use after free in Media Router. Reported by lime(@limeSec_) from TIANGONG Team of Legendsec at QI-ANXIN Group on 2024-08-23</li>
 	    <li>[362539773] High CVE-2024-8638: Type Confusion in V8. Reported by Zhenghang Xiao (@Kipreyyy) on 2024-08-28</li>
 	    <li>[362658609] High CVE-2024-8639: Use after free in Autofill. Reported by lime(@limeSec_) from TIANGONG Team of Legendsec at QI-ANXIN Group on 2024-08-28</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-8636</cvename>
       <cvename>CVE-2024-8637</cvename>
       <cvename>CVE-2024-8638</cvename>
       <cvename>CVE-2024-8639</cvename>
       <url>https://chromereleases.googleblog.com/2024/09/stable-channel-update-for-desktop_10.html</url>
     </references>
     <dates>
       <discovery>2024-09-10</discovery>
       <entry>2024-09-13</entry>
     </dates>
   </vuln>
 
   <vuln vid="bcc8b21e-7122-11ef-bece-2cf05da270f3">
     <topic>Gitlab -- vulnerabilities</topic>
     <affects>
       <package>
 	<name>gitlab-ce</name>
 	<name>gitlab-ee</name>
 	<range><ge>17.3.0</ge><lt>17.3.2</lt></range>
 	<range><ge>17.2.0</ge><lt>17.2.5</lt></range>
 	<range><ge>8.14.0</ge><lt>17.1.7</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Gitlab reports:</p>
 	<blockquote cite="https://about.gitlab.com/releases/2024/09/11/patch-release-gitlab-17-3-2-released/">
 	  <p>Execute environment stop actions as the owner of the stop action job</p>
 	  <p>Prevent code injection in Product Analytics funnels YAML</p>
 	  <p>SSRF via Dependency Proxy</p>
 	  <p>Denial of Service via sending a large glm_source parameter</p>
 	  <p>CI_JOB_TOKEN can be used to obtain GitLab session token</p>
 	  <p>Variables from settings are not overwritten by PEP if a template is included</p>
 	  <p>Guests can disclose the full source code of projects using custom group-level templates</p>
 	  <p>IdentitiesController allows linking of arbitrary unclaimed provider identities</p>
 	  <p>Open redirect in repo/tree/:id endpoint can lead to account takeover through broken OAuth flow</p>
 	  <p>Open redirect in release permanent links can lead to account takeover through broken OAuth flow</p>
 	  <p>Guest user with Admin group member permission can edit custom role to gain other permissions</p>
 	  <p>Exposure of protected and masked CI/CD variables by abusing on-demand DAST</p>
 	  <p>Credentials disclosed when repository mirroring fails</p>
 	  <p>Commit information visible through release atom endpoint for guest users</p>
 	  <p>Dependency Proxy Credentials are Logged in Plaintext in graphql Logs</p>
 	  <p>User Application can spoof the redirect url</p>
 	  <p>Group Developers can view group runners information</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-6678</cvename>
       <cvename>CVE-2024-8640</cvename>
       <cvename>CVE-2024-8635</cvename>
       <cvename>CVE-2024-8124</cvename>
       <cvename>CVE-2024-8641</cvename>
       <cvename>CVE-2024-8311</cvename>
       <cvename>CVE-2024-4660</cvename>
       <cvename>CVE-2024-4283</cvename>
       <cvename>CVE-2024-4612</cvename>
       <cvename>CVE-2024-8631</cvename>
       <cvename>CVE-2024-2743</cvename>
       <cvename>CVE-2024-5435</cvename>
       <cvename>CVE-2024-6389</cvename>
       <cvename>CVE-2024-4472</cvename>
       <cvename>CVE-2024-6446</cvename>
       <cvename>CVE-2024-6685</cvename>
       <url>https://about.gitlab.com/releases/2024/09/11/patch-release-gitlab-17-3-2-released/</url>
     </references>
     <dates>
       <discovery>2024-09-11</discovery>
       <entry>2024-09-12</entry>
     </dates>
   </vuln>
 
   <vuln vid="d5026193-6fa2-11ef-99bc-1c697a616631">
     <topic>Intel CPUs -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>cpu-microcode-intel</name>
 	<range><lt>20241112</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Intel reports:</p>
 	<blockquote cite="https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01103.html">
 	 <p>
 	  A potential security vulnerability in the Running Average Power Limit
 	  (RAPL) interface for some Intel Processors may allow information
 	  disclosure.  Intel has released firmware updates to mitigate this
 	  potential vulnerability.
 	 </p>
 	</blockquote>
 	<blockquote cite="https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01097.html">
 	 <p>
 	  A potential security vulnerability in some Intel Processors may allow
 	  denial of service.  Intel has released firmware updates to mitigate
 	  this potential vulnerability.
 	 </p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-23984</cvename>
       <cvename>CVE-2024-24968</cvename>
       <url>https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases/tag/microcode-20240910</url>
     </references>
     <dates>
       <discovery>2024-09-10</discovery>
       <entry>2024-09-10</entry>
       <modified>2024-11-12</modified>
     </dates>
   </vuln>
 
   <vuln vid="996518f3-6ef9-11ef-b01b-08002784c58d">
     <topic>clamav -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>clamav</name>
 	<range><ge>1.3.0,1</ge><lt>1.3.2,1</lt></range>
 	<range><ge>1.4.0,1</ge><lt>1.4.1,1</lt></range>
       </package>
       <package>
 	<name>clamav-lts</name>
 	<range><ge>1.0.0,1</ge><lt>1.0.6,1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The ClamAV project  reports:</p>
 	<blockquote cite="https://blog.clamav.net/2024/09/clamav-141-132-107-and-010312-security.html">
 	  <dl>
 	    <dt>CVE-2024-20505</dt>
 	    <dd>
 	      A vulnerability in the PDF parsing module of Clam
 	      AntiVirus (ClamAV) could allow an unauthenticated,
 	      remote attacker to cause a denial of service (DoS)
 	      condition on an affected device. The vulnerability is
 	      due to an out of bounds read. An attacker could exploit
 	      this vulnerability by submitting a crafted PDF file to
 	      be scanned by ClamAV on an affected device. An exploit
 	      could allow the attacker to terminate the scanning
 	      process.
 	    </dd>
 	    <dt>CVE-2024-20506</dt>
 	    <dd>
 	      A vulnerability in the ClamD service module of Clam
 	      AntiVirus (ClamAV) could allow an authenticated, local
 	      attacker to corrupt critical system files. The
 	      vulnerability is due to allowing the ClamD process to
 	      write to its log file while privileged without checking
 	      if the logfile has been replaced with a symbolic
 	      link. An attacker could exploit this vulnerability if
 	      they replace the ClamD log file with a symlink to a
 	      critical system file and then find a way to restart the
 	      ClamD process. An exploit could allow the attacker to
 	      corrupt a critical system file by appending ClamD log
 	      messages after restart.
 	    </dd>
 	  </dl>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-20505</cvename>
       <cvename>CVE-2024-20506</cvename>
       <url>https://blog.clamav.net/2024/09/clamav-141-132-107-and-010312-security.html</url>
     </references>
     <dates>
       <discovery>2024-09-04</discovery>
       <entry>2024-09-09</entry>
     </dates>
   </vuln>
 
   <vuln vid="8fbe81f7-6eb5-11ef-b7bd-00505632d232">
     <topic>netatalk3 -- multiple WolfSSL vulnerabilities</topic>
     <affects>
       <package>
 	<name>netatalk3</name>
 	<range><lt>3.2.8,1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Netatalk release reports:</p>
 	<blockquote cite="https://github.com/Netatalk/netatalk/releases/tag/netatalk-3-2-8">
 	  <p>WolfSSL 5.7.0 (included in netatalk) includes multiple security vulnerabilities.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-1544</cvename>
       <cvename>CVE-2024-5288</cvename>
       <cvename>CVE-2024-5991</cvename>
       <cvename>CVE-2024-5814</cvename>
     </references>
     <dates>
       <discovery>2024-09-08</discovery>
       <entry>2024-09-09</entry>
     </dates>
   </vuln>
 
   <vuln vid="80fbe184-2358-11ef-996e-40b034455553">
     <topic>minio -- unintentional information disclosure</topic>
     <affects>
       <package>
 	<name>minio</name>
 	<range><lt>2024.05.27.19.17.46</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Minio security advisory GHSA-95fr-cm4m-q5p9 reports:</p>
 	<blockquote cite="https://github.com/minio/minio/security/advisories/GHSA-95fr-cm4m-q5p9">
 	  <p>when used with anonymous requests by sending a random
 	    object name requests you can figure out if the object
 	  exists or not on the server on a specific bucket and also
 	  gain access to some amount of information.
 	</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-36107</cvename>
       <url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-36107</url>
     </references>
     <dates>
       <discovery>2024-05-28</discovery>
       <entry>2024-06-05</entry>
     </dates>
   </vuln>
 
   <vuln vid="144836e3-2358-11ef-996e-40b034455553">
     <topic>minio -- privilege escalation via permissions inheritance</topic>
     <affects>
       <package>
 	<name>minio</name>
 	<range><lt>2024.01.31.20.20.33</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Minio security advisory GHSA-xx8w-mq23-29g4 ports:</p>
 	<blockquote cite="https://github.com/minio/minio/security/advisories/GHSA-xx8w-mq23-29g4">
 	<p>
 	  When someone creates an access key, it inherits the
 	  permissions of the parent key. Not only for s3:* actions,
 	  but also admin:* actions. Which means unless somewhere
 	  above in the access-key hierarchy, the admin rights are
 	  denied, access keys will be able to simply override their
 	  own s3 permissions to something more permissive.
 	</p>
 	</blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-24747</cvename>
       <url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-24747</url>
     </references>
     <dates>
       <discovery>2024-01-31</discovery>
       <entry>2024-06-05</entry>
     </dates>
   </vuln>
 
   <vuln vid="7ade3c38-6d1f-11ef-ae11-b42e991fc52e">
     <topic>firefox -- Potential memory corruption and exploitable crash</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>128.0,2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1901411">
 	  <p>An error in the ECMA-262 specification relating to Async Generators
 	could have resulted in a type confusion, potentially leading to
 	memory corruption and an exploitable crash.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-7652</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-7652</url>
     </references>
     <dates>
       <discovery>2024-09-06</discovery>
       <entry>2024-09-07</entry>
     </dates>
   </vuln>
 
   <vuln vid="3e44c35f-6cf4-11ef-b813-4ccc6adda413">
     <topic>exiv2 -- Out-of-bounds read in AsfVideo::streamProperties</topic>
     <affects>
       <package>
 	<name>exiv2</name>
 	<range><ge>0.28.0,1</ge><lt>0.28.3,1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Kevin Backhouse reports:</p>
 	<blockquote cite="https://github.com/Exiv2/exiv2/security/advisories/GHSA-38rv-8x93-pvrh">
 	  <p>An out-of-bounds read was found in Exiv2 version v0.28.2. The vulnerability
 	   is in the parser for the ASF video format, which was a new feature in v0.28.0,
 	   so Exiv2 versions before v0.28 are not affected. The out-of-bounds read is
 	   triggered when Exiv2 is used to read the metadata of a crafted video file.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-39695</cvename>
       <url>https://github.com/Exiv2/exiv2/security/advisories/GHSA-38rv-8x93-pvrh</url>
     </references>
     <dates>
       <discovery>2024-04-21</discovery>
       <entry>2024-09-07</entry>
     </dates>
   </vuln>
 
   <vuln vid="a5e13973-6c75-11ef-858b-23eeba13701a">
     <topic>forgejo -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>forgejo</name>
 	<range><lt>8.0.3</lt></range>
       </package>
       <package>
 	<name>forgejo7</name>
 	<range><lt>7.0.9</lt></range>
       </package>
     </affects>
     <description>
        <body xmlns="http://www.w3.org/1999/xhtml">
        <h1>Problem Description:</h1>
        <ul>
        <li>Replace v-html with v-text in search inputbox</li>
        <li>Upgrade webpack to v5.94.0 as a precaution to mitigate
        CVE-2024-43788, although we were not yet able to confirm that this
        can be exploited in Forgejo.</li>
        </ul>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-43788</cvename>
       <url>https://codeberg.org/forgejo/forgejo/milestone/8231</url>
     </references>
     <dates>
       <discovery>2024-09-03</discovery>
       <entry>2024-09-06</entry>
     </dates>
   </vuln>
 
   <vuln vid="943f8915-6c5d-11ef-810a-f8b46a88f42c">
     <topic>binutils -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>binutils</name>
 	<range><lt>2.43,1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>alster@vinterdalen.se reports PR/281070:</p>
 	<blockquote cite="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281070">
 	  <p>A new version of devel/binutils has been released fixing
 	     CVE-2023-1972, CVE-2023-25585, CVE-2023-25586, and
 	     CVE-2023-25588.
 	  </p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-1972</cvename>
       <cvename>CVE-2023-25585</cvename>
       <cvename>CVE-2023-25586</cvename>
       <cvename>CVE-2023-25588</cvename>
     </references>
     <dates>
       <discovery>2024-08-25</discovery>
       <entry>2024-09-06</entry>
     </dates>
   </vuln>
 
   <vuln vid="f5d0cfe7-6ba6-11ef-858b-23eeba13701a">
     <topic>gitea -- multiple issues</topic>
     <affects>
       <package>
 	<name>gitea</name>
 	<range><lt>1.22.2</lt></range>
       </package>
     </affects>
     <description>
        <body xmlns="http://www.w3.org/1999/xhtml">
        <h1>Problem Description:</h1>
        <ul>
        <li>Replace v-html with v-text in search inputbox</li>
        <li>Fix nuget/conan/container packages upload bugs</li>
        </ul>
       </body>
     </description>
     <references>
       <url>https://github.com/go-gitea/gitea/releases/tag/v1.22.2</url>
     </references>
     <dates>
       <discovery>2024-09-03</discovery>
       <entry>2024-09-05</entry>
     </dates>
   </vuln>
 
   <vuln vid="66907dab-6bb2-11ef-b813-4ccc6adda413">
     <topic>qt5-webengine -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>qt5-webengine</name>
 	<range><lt>5.15.17.p3</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<blockquote cite="https://code.qt.io/cgit/qt/qtwebengine-chromium.git/log/?h=87-based">
 	  <p>Backports for 6 security bugs in Chromium:</p>
 	  <ul>
 	    <li>CVE-2024-5496: Use after free in Media Session</li>
 	    <li>CVE-2024-5846: Use after free in PDFium</li>
 	    <li>CVE-2024-6291: Use after free in Swiftshader</li>
 	    <li>CVE-2024-6989: Use after free in Loader</li>
 	    <li>CVE-2024-6996: Race in Frames</li>
 	    <li>CVE-2024-7536: Use after free in WebAudio</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-5496</cvename>
       <cvename>CVE-2024-5846</cvename>
       <cvename>CVE-2024-6291</cvename>
       <cvename>CVE-2024-6989</cvename>
       <cvename>CVE-2024-6996</cvename>
       <cvename>CVE-2024-7536</cvename>
       <url>https://code.qt.io/cgit/qt/qtwebengine-chromium.git/log/?h=87-based</url>
     </references>
     <dates>
       <discovery>2024-08-05</discovery>
       <entry>2024-09-05</entry>
     </dates>
   </vuln>
 
   <vuln vid="a3a1caf5-6ba1-11ef-b9e8-b42e991fc52e">
     <topic>firefox -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>130.0_1,2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1908496">
 	<p>This entry contains 8 vulnerabilities:</p>
 	<ul>
 	<li>CVE-2024-8381: A potentially exploitable type
 	confusion could be triggered when looking up a property
 	name on an object being used as the `with` environment.</li>
 	<li>CVE-2024-8382: Internal browser event interfaces were
 	exposed to web content when privileged EventHandler listener
 	callbacks ran for those events. Web content that tried to
 	use those interfaces would not be able to use them with
 	elevated privileges, but their presence would indicate
 	certain browser features had been used, such as when a user
 	opened the Dev Tools console.</li>
 	<li>CVE-2024-8383: Firefox normally asks for confirmation
 	before asking the operating system to find an application to
 	handle a scheme that the browser does not support. It did not
 	ask before doing so for the Usenet-related schemes news: and
 	snews:.  Since most operating systems don&apos;t have a
 	trusted newsreader installed by default, an unscrupulous
 	program that the user downloaded could register itself as a
 	handler. The website that served the application download
 	could then launch that application at will.</li>
 	<li>CVE-2024-8384: The JavaScript garbage collector could
 	mis-color cross-compartment objects if OOM conditions were
 	detected at the right point between two passes. This could have
 	led to memory corruption.</li>
 	<li>CVE-2024-8385: A difference in the handling of
 	StructFields and ArrayTypes in WASM could be used to trigger
 	an exploitable type confusion vulnerability.</li>
 	<li>CVE-2024-8386: If a site had been granted the permission
 	to open popup windows, it could cause Select elements to
 	appear on top of another site to perform a spoofing attack.</li>
 	<li>CVE-2024-8387: Memory safety bugs present in Firefox 129,
 	Firefox ESR 128.1, and Thunderbird 128.1. Some of these bugs
 	showed evidence of memory corruption and we presume that with
 	enough effort some of these could have been exploited to run
 	arbitrary code.</li>
 	<li>CVE-2024-8389: Memory safety bugs present in Firefox 129.
 	Some of these bugs showed evidence of memory corruption and we
 	presume that with enough effort some of these could have been
 	exploited to run arbitrary code.</li>
   </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-8381</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-8381</url>
       <cvename>CVE-2024-8382</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-8382</url>
       <cvename>CVE-2024-8383</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-8383</url>
       <cvename>CVE-2024-8384</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-8384</url>
       <cvename>CVE-2024-8385</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-8385</url>
       <cvename>CVE-2024-8386</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-8386</url>
       <cvename>CVE-2024-8387</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-8387</url>
       <cvename>CVE-2024-8389</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-8389</url>
     </references>
     <dates>
       <discovery>2024-09-03</discovery>
       <entry>2024-09-05</entry>
     </dates>
   </vuln>
 
   <vuln vid="7e079ce2-6b51-11ef-9a62-002590c1f29c">
     <topic>FreeBSD -- umtx Kernel panic or Use-After-Free</topic>
     <affects>
       <package>
 	<name>FreeBSD</name>
 	<range><ge>14.1</ge><lt>14.1_4</lt></range>
 	<range><ge>14.0</ge><lt>14.0_10</lt></range>
 	<range><ge>13.3</ge><lt>13.3_6</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<h1>Problem Description:</h1>
 	<p>Concurrent removals of such a mapping by using the UMTX_SHM_DESTROY
 	sub-request of UMTX_OP_SHM can lead to decreasing the reference
 	count of the object representing the mapping too many times, causing
 	it to be freed too early.</p>
 	<h1>Impact:</h1>
 	<p>A malicious code exercizing the UMTX_SHM_DESTROY sub-request
 	in parallel can panic the kernel or enable further Use-After-Free
 	attacks, potentially including code execution or Capsicum sandbox
 	escape.</p>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-43102</cvename>
       <freebsdsa>SA-24:14.umtx</freebsdsa>
     </references>
     <dates>
       <discovery>2024-09-04</discovery>
       <entry>2024-09-05</entry>
     </dates>
   </vuln>
 
   <vuln vid="4edaa9f4-6b51-11ef-9a62-002590c1f29c">
     <topic>FreeBSD -- bhyve(8) privileged guest escape via USB controller</topic>
     <affects>
       <package>
 	<name>FreeBSD</name>
 	<range><ge>14.1</ge><lt>14.1_4</lt></range>
 	<range><ge>14.0</ge><lt>14.0_10</lt></range>
 	<range><ge>13.3</ge><lt>13.3_6</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<h1>Problem Description:</h1>
 	<p>bhyve can be configured to emulate devices on a virtual USB
 	controller (XHCI), such as USB tablet devices.  An insufficient
 	boundary validation in the USB code could lead to an out-of-bounds
 	write on the heap, with data controlled by the caller.</p>
 	<h1>Impact:</h1>
 	<p>A malicious, privileged software running in a guest VM can
 	exploit the vulnerability to achieve code execution on the host in
 	the bhyve userspace process, which typically runs as root.  Note
 	that bhyve runs in a Capsicum sandbox, so malicious code is constrained
 	by the capabilities available to the bhyve process.</p>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-32668</cvename>
       <freebsdsa>SA-24:12.bhyve</freebsdsa>
     </references>
     <dates>
       <discovery>2024-09-04</discovery>
       <entry>2024-09-05</entry>
     </dates>
   </vuln>
 
   <vuln vid="9bd5e47b-6b50-11ef-9a62-002590c1f29c">
     <topic>FreeBSD -- Multiple issues in ctl(4) CAM Target Layer</topic>
     <affects>
       <package>
 	<name>FreeBSD-kernel</name>
 	<range><ge>14.1</ge><lt>14.1_4</lt></range>
 	<range><ge>14.0</ge><lt>14.0_10</lt></range>
 	<range><ge>13.3</ge><lt>13.3_6</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<h1>Problem Description:</h1>
 	<p>Several vulnerabilities were found in the ctl subsystem.</p>
 	<p>The function ctl_write_buffer incorrectly set a flag which resulted
 	in a kernel Use-After-Free when a command finished processing
 	(CVE-2024-45063).  The ctl_write_buffer and ctl_read_buffer functions
 	allocated memory to be returned to userspace, without initializing
 	it (CVE-2024-8178).  The ctl_report_supported_opcodes function did
 	not sufficiently validate a field provided by userspace, allowing
 	an arbitrary write to a limited amount of kernel help memory
 	(CVE-2024-42416).  The ctl_request_sense function could expose up
 	to three bytes of the kernel heap to userspace (CVE-2024-43110).</p>
 	<p>Guest virtual machines in the bhyve hypervisor can send SCSI commands
 	to the corresponding kernel driver via the virtio_scsi interface.
 	This provides guests with direct access to the vulnerabilities
 	covered by this advisory.</p>
 	<p>The CAM Target Layer iSCSI target daemon ctld(8) accepts incoming
 	iSCSI connections, performs authentication and passes connections
 	to the kernel ctl(4) target layer.</p>
 	<h1>Impact:</h1>
 	<p>Malicious software running in a guest VM that exposes virtio_scsi
 	can exploit the vulnerabilities to achieve code execution on the
 	host in the bhyve userspace process, which typically runs as root.
 	Note that bhyve runs in a Capsicum sandbox, so malicious code is
 	constrained by the capabilities available to the bhyve process.</p>
 	<p>A malicious iSCSI initiator could achieve remote code execution on
 	the iSCSI target host.</p>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-8178</cvename>
       <cvename>CVE-2024-42416</cvename>
       <cvename>CVE-2024-43110</cvename>
       <freebsdsa>SA-24:11.ctl</freebsdsa>
     </references>
     <dates>
       <discovery>2024-09-04</discovery>
       <entry>2024-09-05</entry>
     </dates>
   </vuln>
 
   <vuln vid="56d76414-6b50-11ef-9a62-002590c1f29c">
     <topic>FreeBSD -- bhyve(8) privileged guest escape via TPM device passthrough</topic>
     <affects>
       <package>
 	<name>FreeBSD</name>
 	<range><ge>14.1</ge><lt>14.1_4</lt></range>
 	<range><ge>14.0</ge><lt>14.0_10</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<h1>Problem Description:</h1>
 	<p>bhyve can be configured to provide access to the host's TPM
 	device, where it passes the communication through an emulated device
 	provided to the guest.  This may be performed on the command-line
 	by starting bhyve with the `-l tpm,passthru,/dev/tpmX` parameters.</p>
 	<p>The MMIO handler for the emulated device did not validate the offset
 	and size of the memory access correctly, allowing guests to read
 	and write memory contents outside of the memory area effectively
 	allocated.</p>
 	<h1>Impact:</h1>
 	<p>Malicious software running in a guest VM can exploit the buffer
 	overflow to achieve code execution on the host in the bhyve userspace
 	process, which typically runs as root.  Note that bhyve runs in a
 	Capsicum sandbox, so malicious code is constrained by the capabilities
 	available to the bhyve process.</p>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-41928</cvename>
       <freebsdsa>SA-24:10.bhyve</freebsdsa>
     </references>
     <dates>
       <discovery>2024-09-04</discovery>
       <entry>2024-09-05</entry>
     </dates>
   </vuln>
 
   <vuln vid="8d1f9adf-6b4f-11ef-9a62-002590c1f29c">
     <topic>FreeBSD -- Multiple vulnerabilities in libnv</topic>
     <affects>
       <package>
 	<name>FreeBSD-kernel</name>
 	<range><ge>14.1</ge><lt>14.1_4</lt></range>
 	<range><ge>14.0</ge><lt>14.0_10</lt></range>
 	<range><ge>13.3</ge><lt>13.3_6</lt></range>
       </package>
       <package>
 	<name>FreeBSD</name>
 	<range><ge>14.1</ge><lt>14.1_4</lt></range>
 	<range><ge>14.0</ge><lt>14.0_10</lt></range>
 	<range><ge>13.3</ge><lt>13.3_6</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<h1>Problem Description:</h1>
 	<p>CVE-2024-45287 is a vulnerability that affects both the kernel
 	and userland.  A malicious value of size in a structure of packed
 	libnv can cause an integer overflow, leading to the allocation of
 	a smaller buffer than required for the parsed data.</p>
 	<p>CVE-2024-45288 is a vulnerability that affects both the kernel and
 	userland.  A missing null-termination character in the last element
 	of an nvlist array string can lead to writing outside the allocated
 	buffer.</p>
 	<h1>Impact:</h1>
 	<p>It is possible for an attacker to overwrite portions of memory
 	(in userland or the kernel) as the allocated buffer might be smaller
 	than the data received from a malicious process.  This vulnerability
 	could result in privilege escalation or cause a system panic.</p>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-45287</cvename>
       <cvename>CVE-2024-45288</cvename>
       <freebsdsa>SA-24:09.libnv</freebsdsa>
     </references>
     <dates>
       <discovery>2024-09-04</discovery>
       <entry>2024-09-05</entry>
     </dates>
   </vuln>
 
   <vuln vid="21f505f4-6a1c-11ef-b611-84a93843eb75">
     <topic>OpenSSL -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>openssl</name>
 	<range><lt>3.0.15,1</lt></range>
       </package>
       <package>
 	<name>openssl31</name>
 	<range><lt>3.1.7</lt></range>
       </package>
       <package>
 	<name>openssl32</name>
 	<range><lt>3.2.3</lt></range>
       </package>
       <package>
 	<name>openssl33</name>
 	<range><lt>3.3.2</lt></range>
       </package>
       <package>
 	<name>openssl-quictls</name>
 	<range><lt>3.0.15</lt></range>
       </package>
       <package>
 	<name>openssl31-quictls</name>
 	<range><lt>3.1.7</lt></range>
       </package>
       <package>
 	<name>FreeBSD</name>
 	<range><ge>14.1</ge><lt>14.1_4</lt></range>
 	<range><ge>14.0</ge><lt>14.0_10</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The OpenSSL project reports:</p>
 	<blockquote cite="https://openssl-library.org/news/secadv/20240903.txt">
 	  <p>Possible denial of service in X.509 name checks [Moderate severity]
 	    Applications performing certificate name checks (e.g., TLS clients
 	    checking server certificates) may attempt to read an invalid
 	    memory address resulting in abnormal termination of the application
 	    process.</p>
 	  <p>SSL_select_next_proto buffer overread [Low severity]
 	    Calling the OpenSSL API function SSL_select_next_proto with an empty
 	    supported client protocols buffer may cause a crash or memory
 	    contents to be sent to the peer.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-5535</cvename>
       <cvename>CVE-2024-6119</cvename>
       <url>https://openssl-library.org/news/secadv/20240627.txt</url>
       <url>https://openssl-library.org/news/secadv/20240903.txt</url>
       <freebsdsa>SA-24:13.openssl</freebsdsa>
     </references>
     <dates>
       <discovery>2024-09-03</discovery>
       <entry>2024-09-03</entry>
       <modified>2024-09-05</modified>
     </dates>
   </vuln>
 
   <vuln vid="26125e09-69ca-11ef-8a0f-a8a1599412c6">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>128.0.6613.119</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>128.0.6613.119</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2024/09/stable-channel-update-for-desktop.html">
 	 <p>This update includes 4 security fixes:</p>
 	 <ul>
 	    <li>[357391257] High CVE-2024-8362: Use after free in WebAudio. Reported by Cassidy Kim(@cassidy6564) on 2024-08-05</li>
 	    <li>[358485426] High CVE-2024-7970: Out of bounds write in V8. Reported by Cassidy Kim(@cassidy6564) on 2024-08-09</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-8362</cvename>
       <cvename>CVE-2024-7970</cvename>
       <url>https://chromereleases.googleblog.com/2024/09/stable-channel-update-for-desktop.html</url>
     </references>
     <dates>
       <discovery>2024-09-02</discovery>
       <entry>2024-09-03</entry>
     </dates>
   </vuln>
 
   <vuln vid="eb437e17-66a1-11ef-ac08-75165d18d8d2">
     <topic>forgejo -- The scope of application tokens was not verified when writing containers or Conan packages.</topic>
     <affects>
       <package>
 	<name>forgejo</name>
 	<range><lt>8.0.2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The forgejo team reports:</p>
 	<blockquote cite="https://codeberg.org/forgejo/forgejo/milestone/7728">
 	<p>The scope of application tokens was not verified when writing
 	containers or Conan packages.  This is of no consequence when the
 	user associated with the application token does not have write
 	access to packages.  If the user has write access to packages, such
 	a token can be used to write containers and Conan packages.  An
 	application token that was used to write containers or Conan
 	packages without the package:write scope will now fail with an
 	unauthorized error.  It must be re-created to include the
 	package:write scope.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <url>https://codeberg.org/forgejo/forgejo/pulls/5149</url>
     </references>
     <dates>
       <discovery>2024-08-26</discovery>
       <entry>2024-08-30</entry>
     </dates>
   </vuln>
 
   <vuln vid="7e9cc7fd-6b3e-46c5-ad6d-409d90d41bbf">
     <topic>RabbitMQ-C -- auth credentials visible in commandline tool options</topic>
     <affects>
       <package>
 	<name>rabbitmq-c</name>
 	<range><lt>0.14.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>hadmut reports:</p>
 	<blockquote cite="https://nvd.nist.gov/vuln/detail/CVE-2023-35789">
 		<p>This C library includes 2 command-line tools that can take
 		credentials as command-line options. The credentials are exposed
 		as plain-text in the process list. This could allow an attacker
 		with access to the process list to see the credentials.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-35789</cvename>
 	  <url>https://nvd.nist.gov/vuln/detail/CVE-2023-35789</url>
     </references>
     <dates>
       <discovery>2019-09-19</discovery>
       <entry>2024-08-30</entry>
     </dates>
   </vuln>
 
   <vuln vid="5e4d7172-66b8-11ef-b104-b42e991fc52e">
     <topic>firefox -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>129.0,2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1909241">
 	  <ul>
 	    <li>Firefox adds web-compatibility shims in place of some
 	      tracking scripts blocked by Enhanced Tracking Protection.
 	      On a site protected by Content Security Policy in
 	      &quot;strict-dynamic&quot; mode, an attacker able to
 	      inject an HTML element could have used a DOM
 	      Clobbering attack on some of the shims and achieved XSS,
 	      bypassing the CSP strict-dynamic protection.</li>
 	    <li>Form validation popups could capture escape key presses.
 	      Therefore, spamming form validation messages could be used
 	      to prevent users from exiting full-screen mode.</li>
 	    <li>When almost out-of-memory an elliptic curve key which
 	      was never allocated could have been freed again. </li>
 	    <li>It was possible to move the cursor using pointerlock
 	      from an iframe.  This allowed moving the cursor outside
 	      of the viewport and the Firefox window.</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-7524</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-7524</url>
       <cvename>CVE-2024-6610</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-6610</url>
       <cvename>CVE-2024-6609</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-6609</url>
       <cvename>CVE-2024-6608</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-6608</url>
     </references>
     <dates>
       <discovery>2024-08-06</discovery>
       <entry>2024-08-30</entry>
     </dates>
   </vuln>
 
   <vuln vid="6f2545bb-65e8-11ef-8a0f-a8a1599412c6">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>128.0.6613.113</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>128.0.6613.113</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2024/08/stable-channel-update-for-desktop_28.html">
 	 <p>This update includes 4 security fixes:</p>
 	 <ul>
 	    <li>[351865302] High CVE-2024-7969: Type Confusion in V8. Reported by CFF of Topsec Alpha Team on 2024-07-09</li>
 	    <li>[360265320] High CVE-2024-8193: Heap buffer overflow in Skia. Reported by Renan Rios (@hyhy_100) on 2024-08-16</li>
 	    <li>[360533914] High CVE-2024-8194: Type Confusion in V8. Reported by Seunghyun Lee (@0x10n) on 2024-08-18</li>
 	    <li>[360758697] High CVE-2024-8198: Heap buffer overflow in Skia. Reported by Renan Rios (@hyhy_100) on 2024-08-19</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-7969</cvename>
       <cvename>CVE-2024-8193</cvename>
       <cvename>CVE-2024-8194</cvename>
       <cvename>CVE-2024-8198</cvename>
       <url>https://chromereleases.googleblog.com/2024/08/stable-channel-update-for-desktop_28.html</url>
     </references>
     <dates>
       <discovery>2024-08-28</discovery>
       <entry>2024-08-29</entry>
     </dates>
   </vuln>
 
   <vuln vid="46419e8c-65d9-11ef-ac06-b0416f0c4c67">
     <topic>Configobj -- Regular Expression Denial of Service attack</topic>
     <affects>
       <package>
 	<name>py38-configobj</name>
 	<name>py39-configobj</name>
 	<name>py310-configobj</name>
 	<name>py311-configobj</name>
 	<range><le>5.0.8</le></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>report@snyk.io reports:</p>
 	<blockquote cite="https://github.com/DiffSK/configobj/issues/232">
 	  <p>All versions of the package configobj are vulnerable to Regular
 	Expression Denial of Service (ReDoS) via the validate function,
 	using (.+?)\((.*)\).**Note:** This is only exploitable in the case
 	of a developer putting the offending value in a server side
 	configuration file.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-26112</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2023-26112</url>
     </references>
     <dates>
       <discovery>2023-04-03</discovery>
       <entry>2024-08-29</entry>
     </dates>
   </vuln>
 
   <vuln vid="49ef501c-62b6-11ef-bba5-2cf05da270f3">
     <topic>Gitlab -- vulnerabilities</topic>
     <affects>
       <package>
 	<name>gitlab-ce</name>
 	<name>gitlab-ee</name>
 	<range><ge>17.3.0</ge><lt>17.3.1</lt></range>
 	<range><ge>17.2.0</ge><lt>17.2.4</lt></range>
 	<range><ge>8.2.0</ge><lt>17.1.6</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Gitlab reports:</p>
 	<blockquote cite="https://about.gitlab.com/releases/2024/08/21/patch-release-gitlab-17-3-1-released/">
 	  <p>The GitLab Web Interface Does Not Guarantee Information Integrity When Downloading Source Code from Releases</p>
 	  <p>Denial of Service by importing maliciously crafted GitHub repository</p>
 	  <p>Prompt injection in "Resolve Vulnerabilty" results in arbitrary command execution in victim's pipeline</p>
 	  <p>An unauthorized user can perform certain actions through GraphQL after a group owner enables IP restrictions</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-6502</cvename>
       <cvename>CVE-2024-8041</cvename>
       <cvename>CVE-2024-7110</cvename>
       <cvename>CVE-2024-3127</cvename>
       <url>https://about.gitlab.com/releases/2024/08/21/patch-release-gitlab-17-3-1-released/</url>
     </references>
     <dates>
       <discovery>2024-08-21</discovery>
       <entry>2024-08-25</entry>
     </dates>
   </vuln>
 
   <vuln vid="7e6e932f-617b-11ef-8a7d-b42e991fc52e">
     <topic>firefox -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>127,2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1414937">
 	  <ul>
 	    <li>CVE-2024-5697: A website was able to detect when a
 	      user took a screenshot of a page using the built-in
 	      Screenshot functionality in Firefox.</li>
 	    <li>CVE-2024-5698: By manipulating the fullscreen
 	      feature while opening a data-list, an attacker could
 	      have overlaid a text box over the address bar. This
 	      could have led to user confusion and possible spoofing
 	      attacks.
 	    </li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-5697</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-5697</url>
       <cvename>CVE-2024-5698</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-5698</url>
     </references>
     <dates>
       <discovery>2024-06-11</discovery>
       <entry>2024-08-23</entry>
     </dates>
   </vuln>
 
   <vuln vid="6e8b9c75-6179-11ef-8a7d-b42e991fc52e">
     <topic>mcpp -- Heap-based buffer overflow</topic>
     <affects>
       <package>
 	<name>mcpp</name>
 	<range><lt>2.7.2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>cve@mitre.org reports:</p>
 	<blockquote cite="http://lists.opensuse.org/opensuse-security-announce/2020-03/msg00032.html">
 	  <p>MCPP 2.7.2 has a heap-based buffer overflow in the do_msg() function
 	in support.c.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2019-14274</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2019-14274</url>
     </references>
     <dates>
       <discovery>2019-07-26</discovery>
       <entry>2024-08-23</entry>
     </dates>
   </vuln>
 
   <vuln vid="f2b1da2e-6178-11ef-8a7d-b42e991fc52e">
     <topic>md4c -- DoS attack</topic>
     <affects>
       <package>
 	<name>md4c</name>
 	<range><lt>0.4.7</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>cve@mitre.org reports:</p>
 	<blockquote cite="https://github.com/mity/md4c/commit/4fc808d8fe8d8904f8525bb4231d854f45e23a19">
 	  <p>md_analyze_line in md4c.c in md4c 0.4.7 allows attackers
 	  to trigger use of uninitialized memory, and cause a denial
 	  of service via a malformed Markdown document.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2021-30027</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2021-30027</url>
     </references>
     <dates>
       <discovery>2021-04-29</discovery>
       <entry>2024-08-23</entry>
     </dates>
   </vuln>
 
   <vuln vid="b339992e-6059-11ef-8a0f-a8a1599412c6">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>128.0.6613.84</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>128.0.6613.84</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2024/08/stable-channel-update-for-desktop_21.html">
 	 <p>This update includes 38 security fixes:</p>
 	 <ul>
 	    <li>[358296941] High CVE-2024-7964: Use after free in Passwords. Reported by Anonymous on 2024-08-08</li>
 	    <li>[356196918] High CVE-2024-7965: Inappropriate implementation in V8. Reported by TheDog on 2024-07-30</li>
 	    <li>[355465305] High CVE-2024-7966: Out of bounds memory access in Skia. Reported by Renan Rios (@HyHy100) on 2024-07-25</li>
 	    <li>[355731798] High CVE-2024-7967: Heap buffer overflow in Fonts. Reported by Tashita Software Security on 2024-07-27</li>
 	    <li>[349253666] High CVE-2024-7968: Use after free in Autofill. Reported by Han Zheng (HexHive) on 2024-06-25</li>
 	    <li>[351865302] High CVE-2024-7969: Type Confusion in V8. Reported by CFF of Topsec Alpha Team on 2024-07-09</li>
 	    <li>[360700873] High CVE-2024-7971: Type confusion in V8. Reported by Microsoft Threat Intelligence Center (MSTIC), Microsoft Security Response Center (MSRC) on 2024-08-19</li>
 	    <li>[345960102] Medium CVE-2024-7972: Inappropriate implementation in V8. Reported by Simon Gerst (intrigus-lgtm) on 2024-06-10</li>
 	    <li>[345518608] Medium CVE-2024-7973: Heap buffer overflow in PDFium. Reported by soiax on 2024-06-06</li>
 	    <li>[339141099] Medium CVE-2024-7974: Insufficient data validation in V8 API. Reported by bowu(@gocrashed) on 2024-05-07</li>
 	    <li>[347588491] Medium CVE-2024-7975: Inappropriate implementation in Permissions. Reported by Thomas Orlita on 2024-06-16</li>
 	    <li>[339654392] Medium CVE-2024-7976: Inappropriate implementation in FedCM. Reported by Alesandro Ortiz on 2024-05-10</li>
 	    <li>[324770940] Medium CVE-2024-7977: Insufficient data validation in Installer. Reported by Kim Dong-uk (@justlikebono) on 2024-02-11</li>
 	    <li>[40060358] Medium CVE-2024-7978: Insufficient policy enforcement in Data Transfer. Reported by NDevTK on 2022-07-21</li>
 	    <li>[356064205] Medium CVE-2024-7979: Insufficient data validation in Installer. Reported by VulnNoob on 2024-07-29</li>
 	    <li>[356328460] Medium CVE-2024-7980: Insufficient data validation in Installer. Reported by VulnNoob on 2024-07-30</li>
 	    <li>[40067456] Low CVE-2024-7981: Inappropriate implementation in Views. Reported by Thomas Orlita on 2023-07-14</li>
 	    <li>[350256139] Low CVE-2024-8033: Inappropriate implementation in WebApp Installs. Reported by Lijo A.T on 2024-06-30</li>
 	    <li>[353858776] Low CVE-2024-8034: Inappropriate implementation in Custom Tabs. Reported by Bharat (mrnoob) on 2024-07-18</li>
 	    <li>[40059470] Low CVE-2024-8035: Inappropriate implementation in Extensions. Reported by Microsoft on 2022-04-26</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-7964</cvename>
       <cvename>CVE-2024-7965</cvename>
       <cvename>CVE-2024-7966</cvename>
       <cvename>CVE-2024-7967</cvename>
       <cvename>CVE-2024-7968</cvename>
       <cvename>CVE-2024-7969</cvename>
       <cvename>CVE-2024-7971</cvename>
       <cvename>CVE-2024-7972</cvename>
       <cvename>CVE-2024-7973</cvename>
       <cvename>CVE-2024-7974</cvename>
       <cvename>CVE-2024-7975</cvename>
       <cvename>CVE-2024-7976</cvename>
       <cvename>CVE-2024-7977</cvename>
       <cvename>CVE-2024-7978</cvename>
       <cvename>CVE-2024-7979</cvename>
       <cvename>CVE-2024-7980</cvename>
       <cvename>CVE-2024-7981</cvename>
       <cvename>CVE-2024-8033</cvename>
       <cvename>CVE-2024-8034</cvename>
       <cvename>CVE-2024-8035</cvename>
       <url>https://chromereleases.googleblog.com/2024/08/stable-channel-update-for-desktop_21.html</url>
     </references>
     <dates>
       <discovery>2024-08-21</discovery>
       <entry>2024-08-22</entry>
     </dates>
   </vuln>
 
   <vuln vid="addc71b8-6024-11ef-86a1-8c164567ca3c">
     <topic>nginx -- Vulnerability in the ngx_http_mp4_module</topic>
     <affects>
       <package>
 	<name>nginx-devel</name>
 	<range><ge>1.5.13,3</ge><lt>1.27.1,3</lt></range>
       </package>
       <package>
 	<name>nginx</name>
 	<range><ge>1.6.0,3</ge><lt>1.26.2,3</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The nginx development team reports:</p>
 	<blockquote cite="http://nginx.org/en/security_advisories.html">
 	  <p>This update fixes the buffer overread vulnerability in the
 	ngx_http_mp4_module.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-7347</cvename>
     </references>
     <dates>
       <discovery>2024-08-14</discovery>
       <entry>2024-08-22</entry>
     </dates>
   </vuln>
 
   <vuln vid="04c9c3f8-5ed3-11ef-8262-b0416f0c4c67">
     <topic>Jinja2 -- Vulnerable to HTML attribute injection when passing user input as keys to xmlattr filter</topic>
     <affects>
       <package>
 	<name>py38-Jinja2</name>
 	<name>py39-Jinja2</name>
 	<name>py310-Jinja2</name>
 	<name>py311-Jinja2</name>
 	<range><lt>3.1.4</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security-advisories@github.com reports:</p>
 	<blockquote cite="https://github.com/pallets/jinja/commit/0668239dc6b44ef38e7a6c9f91f312fd4ca581cb">
 	  <p>Jinja is an extensible templating engine.  The `xmlattr` filter in
 	affected versions of Jinja accepts keys containing non-attribute
 	characters.  XML/HTML attributes cannot contain spaces, `/`, `&gt;`,
 	or `=`, as each would then be interpreted as starting a separate
 	attribute.  If an application accepts keys (as opposed to only
 	values) as user input, and renders these in pages that other users
 	see as well, an attacker could use this to inject other attributes
 	and perform XSS.  The fix for CVE-2024-22195 only addressed spaces
 	but not other characters.  Accepting keys as user input is now
 	explicitly considered an unintended use case of the `xmlattr` filter,
 	and code that does so without otherwise validating the input should
 	be flagged as insecure, regardless of Jinja version.  Accepting
 	_values_ as user input continues to be safe.  This vulnerability
 	is fixed in 3.1.4.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-34064</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-34064</url>
     </references>
     <dates>
       <discovery>2024-05-06</discovery>
       <entry>2024-08-20</entry>
     </dates>
   </vuln>
 
   <vuln vid="d0ac9a17-5e68-11ef-b8cc-b42e991fc52e">
     <topic>mozilla products -- spoofing attack</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>129,2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1875354">
 	  <p>Select options could obscure the fullscreen notification dialog.
 	This could be used by a malicious site to perform a spoofing attack.
 	This vulnerability affects Firefox &lt; 129, Firefox ESR &lt; 128.1,
 	and Thunderbird &lt; 128.1.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-7518</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-7518</url>
     </references>
     <dates>
       <discovery>2024-08-06</discovery>
       <entry>2024-08-19</entry>
     </dates>
   </vuln>
 
   <vuln vid="e61af8f4-455d-4f99-8d81-fbb004929dab">
     <topic>electron31 -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>electron31</name>
 	<range><lt>31.4.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Electron developers report:</p>
 	<blockquote cite="https://github.com/electron/electron/releases/tag/v31.4.0">
 	  <p>This update fixes the following vulnerabilities:</p>
 	  <ul>
 	    <li>Security: backported fix for CVE-2024-6989.</li>
 	    <li>Security: backported fix for CVE-2024-6991.</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-6989</cvename>
       <url>https://github.com/advisories/GHSA-32j6-235r-7fmm</url>
       <cvename>CVE-2024-6991</cvename>
       <url>https://github.com/advisories/GHSA-3v8g-fm64-g4mc</url>
     </references>
     <dates>
       <discovery>2024-08-15</discovery>
       <entry>2024-08-18</entry>
     </dates>
   </vuln>
 
   <vuln vid="ac025402-4cbc-4177-bd99-c20c03a07f23">
     <topic>electron{29,30} -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>electron29</name>
 	<range><lt>29.4.6</lt></range>
       </package>
       <package>
 	<name>electron30</name>
 	<range><lt>30.4.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Electron developers report:</p>
 	<blockquote cite="https://github.com/electron/electron/releases/tag/v29.4.6">
 	  <p>This update fixes the following vulnerabilities:</p>
 	  <ul>
 	    <li>Security: backported fix for CVE-2024-6776.</li>
 	    <li>Security: backported fix for CVE-2024-6778.</li>
 	    <li>Security: backported fix for CVE-2024-6777.</li>
 	    <li>Security: backported fix for CVE-2024-6773.</li>
 	    <li>Security: backported fix for CVE-2024-6774.</li>
 	    <li>Security: backported fix for CVE-2024-6772.</li>
 	    <li>Security: backported fix for CVE-2024-6775.</li>
 	    <li>Security: backported fix for CVE-2024-6779.</li>
 	    <li>Security: backported fix for CVE-2024-6989.</li>
 	    <li>Security: backported fix for CVE-2024-6991.</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-6776</cvename>
       <url>https://github.com/advisories/GHSA-7hjm-9cg2-rcg6</url>
       <cvename>CVE-2024-6778</cvename>
       <url>https://github.com/advisories/GHSA-9m98-937v-r97x</url>
       <cvename>CVE-2024-6777</cvename>
       <url>https://github.com/advisories/GHSA-w2v8-c457-cjvf</url>
       <cvename>CVE-2024-6773</cvename>
       <url>https://github.com/advisories/GHSA-7gj8-545r-5295</url>
       <cvename>CVE-2024-6774</cvename>
       <url>https://github.com/advisories/GHSA-cgm7-mqr6-f7vg</url>
       <cvename>CVE-2024-6772</cvename>
       <url>https://github.com/advisories/GHSA-cc8c-62x7-qwjr</url>
       <cvename>CVE-2024-6775</cvename>
       <url>https://github.com/advisories/GHSA-mxwm-jm3p-mh5m</url>
       <cvename>CVE-2024-6779</cvename>
       <url>https://github.com/advisories/GHSA-v4v9-v4wf-9c86</url>
       <cvename>CVE-2024-6989</cvename>
       <url>https://github.com/advisories/GHSA-32j6-235r-7fmm</url>
       <cvename>CVE-2024-6991</cvename>
       <url>https://github.com/advisories/GHSA-3v8g-fm64-g4mc</url>
     </references>
     <dates>
       <discovery>2024-08-16</discovery>
       <entry>2024-08-18</entry>
     </dates>
   </vuln>
 
   <vuln vid="6a6ad6cb-5c6c-11ef-b456-001e676bf734">
     <topic>Dovecot -- DoS</topic>
     <affects>
       <package>
 	<name>dovecot</name>
 	<range><lt>2.3.21.1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Dovecot reports:</p>
 	<blockquote cite="https://dovecot.org/mailman3/hyperkitty/list/dovecot-news@dovecot.org/thread/2CSVL56LFPAXVLWMGXEIWZL736PSYHP5/">
 	  <p>A DoS is possible with a large number of address headers or abnormally large email headers.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-23184</cvename>
       <cvename>CVE-2024-23185</cvename>
       <url>https://dovecot.org/mailman3/hyperkitty/list/dovecot-news@dovecot.org/thread/2CSVL56LFPAXVLWMGXEIWZL736PSYHP5/</url>
     </references>
     <dates>
       <discovery>2024-08-14</discovery>
       <entry>2024-08-16</entry>
     </dates>
   </vuln>
 
   <vuln vid="9d8e9952-5a42-11ef-a219-1c697a616631">
     <topic>Intel CPUs -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>cpu-microcode-intel</name>
 	<range><lt>20240813</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Intel reports:</p>
 	<blockquote cite="https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01083.html">
 	 <p>
 	  A potential security vulnerability in SMI Transfer monitor (STM) may
 	  allow escalation of privilege.  Intel has released microcode updates
 	  to mitigate this potential vulnerability.
 	 </p>
 	</blockquote>
 	<blockquote cite="https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01118.html">
 	 <p>
 	  A potential security vulnerability in some 3rd Generation Intel Xeon
 	  Scalable Processors may allow denial of service.  Intel has released
 	  microcode updates to mitigate this potential vulnerability.
 	 </p>
 	</blockquote>
 	<blockquote cite="https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01100.html">
 	 <p>
 	  A potential security vulnerability in some 3rd, 4th, and 5th
 	  Generation Intel Xeon Processors may allow escalation of privilege.
 	  Intel has released firmware updates to mitigate this potential
 	  vulnerability.
 	 </p>
 	</blockquote>
 	<blockquote cite="https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01038.html">
 	 <p>
 	  A potential security vulnerability in the Intel Core Ultra Processor
 	  stream cache mechanism may allow escalation of privilege.  Intel has
 	  released microcode updates to mitigate this potential vulnerability.
 	 </p>
 	</blockquote>
 	<blockquote cite="https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01046.html">
 	 <p>
 	  A potential security vulnerability in some Intel Processor stream
 	  cache mechanisms may allow escalation of privilege.  Intel has
 	  released microcode updates to mitigate this potential vulnerability.
 	 </p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-24853</cvename>
       <cvename>CVE-2024-25939</cvename>
       <cvename>CVE-2024-24980</cvename>
       <cvename>CVE-2023-42667</cvename>
       <cvename>CVE-2023-49141</cvename>
       <url>https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases/tag/microcode-20240813</url>
     </references>
     <dates>
       <discovery>2024-08-13</discovery>
       <entry>2024-08-14</entry>
     </dates>
   </vuln>
 
   <vuln vid="5d7939f6-5989-11ef-9793-b42e991fc52e">
     <topic>firefox -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>129.0,2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1905691">
 	<ul>
 	<li>
 	  CVE-2024-7531: Calling `PK11_Encrypt()` in NSS using
 	  CKM_CHACHA20 and the same buffer for input and output can
 	  result in plaintext on an Intel Sandy Bridge processor. In
 	  Firefox this only affects the QUIC header protection
 	  feature when the connection is using the ChaCha20-Poly1305
 	  cipher suite. The most likely outcome is connection
 	  failure, but if the connection persists despite the high
 	  packet loss it could be possible for a network observer to
 	  identify packets as coming from the same source despite a
 	  network path change. This vulnerability affects Firefox
 	  &lt; 129, Firefox ESR &lt; 115.14, and Firefox ESR &lt;
 	  128.1.
 	</li>
 	<li>
 	  CVE-2024-7529: The date picker could partially obscure
 	  security prompts. This could be used by a malicious site
 	  to trick a user into granting permissions. This
 	  vulnerability affects Firefox &lt; 129, Firefox ESR &lt;
 	  115.14, Firefox ESR &lt; 128.1, Thunderbird &lt; 128.1,
 	  and Thunderbird &lt; 115.14.
 	</li>
 	<li>
 	  CVE-2024-7525: It was possible for a web extension with
 	  minimal permissions to create a `StreamFilter` which could
 	  be used to read and modify the response body of requests
 	  on any site. This vulnerability affects Firefox &lt; 129,
 	  Firefox ESR &lt; 115.14, Firefox ESR &lt; 128.1,
 	  Thunderbird &lt; 128.1, and Thunderbird &lt; 115.14.
 	</li>
 	<li>
 	  CVE-2024-7522: Editor code failed to check an attribute
 	  value. This could have led to an out-of-bounds read. This
 	  vulnerability affects Firefox &lt; 129, Firefox ESR &lt;
 	  115.14, Firefox ESR &lt; 128.1, Thunderbird &lt; 128.1, and
 	  Thunderbird &lt; 115.14.
 	</li>
 	<li>
 	  CVE-2024-7520: A type confusion bug in WebAssembly could
 	  be leveraged by an attacker to potentially achieve code
 	  execution. This vulnerability affects Firefox &lt; 129,
 	  Firefox ESR &lt; 128.1, and Thunderbird &lt; 128.1.
 	</li>
 	<li>
 	  CVE-2024-7521: Incomplete WebAssembly exception handing
 	  could have led to a use-after-free. This vulnerability
 	  affects Firefox &lt; 129, Firefox ESR &lt; 115.14,
 	  Firefox ESR &lt; 128.1, Thunderbird &lt; 128.1, and
 	  Thunderbird &lt; 115.14.
 	</li>
 	<li>
 	  CVE-2024-7530: Incorrect garbage collection interaction
 	  could have led to a use-after-free. This vulnerability
 	  affects Firefox &lt; 129.
 	</li>
 	<li>
 	  CVE-2024-7528: Incorrect garbage collection interaction in
 	  IndexedDB could have led to a use-after-free. This
 	  vulnerability affects Firefox &lt; 129,
 	  Firefox ESR &lt; 128.1, and Thunderbird &lt; 128.1.
 	</li>
 	<li>
 	  CVE-2024-7527: Unexpected marking work at the start of
 	  sweeping could have led to a use-after-free. This
 	  vulnerability affects Firefox &lt; 129,
 	  Firefox ESR &lt; 115.14, Firefox ESR &lt; 128.1,
 	  Thunderbird &lt; 128.1, and Thunderbird &lt; 115.14.
 	</li>
 	</ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-7531</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-7531</url>
       <cvename>CVE-2024-7529</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-7529</url>
       <cvename>CVE-2024-7525</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-7525</url>
       <cvename>CVE-2024-7522</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-7522</url>
       <cvename>CVE-2024-7520</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-7520</url>
       <cvename>CVE-2024-7521</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-7521</url>
       <cvename>CVE-2024-7530</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-7530</url>
       <cvename>CVE-2024-7528</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-7528</url>
       <cvename>CVE-2024-7527</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-7527</url>
     </references>
     <dates>
       <discovery>2024-08-06</discovery>
       <entry>2024-08-13</entry>
     </dates>
   </vuln>
 
   <vuln vid="587ed8ac-5957-11ef-854a-001e676bf734">
     <topic>OpenHAB CometVisu addon -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>openhab-addons</name>
 	<range><lt>4.2.1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>OpenHAB reports:</p>
 	<blockquote cite="https://github.com/openhab/openhab-distro/releases/tag/4.2.1">
 	  <p>This patch release addresses the following security advisories:</p>
 <ul>
 <li>SSRF/XSS (CometVisu) - <a href="https://github.com/openhab/openhab-webui/security/advisories/GHSA-v7gr-mqpj-wwh3">GHSA-v7gr-mqpj-wwh3</a></li>
 <li>Sensitive information disclosure (CometVisu) - <a href="https://github.com/openhab/openhab-webui/security/advisories/GHSA-3g4c-hjhr-73rj">GHSA-3g4c-hjhr-73rj</a></li>
 <li>RCE through path traversal (CometVisu) - <a href="https://github.com/openhab/openhab-webui/sec
 urity/advisories/GHSA-f729-58x4-gqgf">GHSA-f729-58x4-gqgf</a></li>
 <li>Path traversal (CometVisu) - <a href="https://github.com/openhab/openhab-webui/security/advisories/GHSA-pcwp-26pw-j98w">GHSA-pcwp-26pw-j98w</a></li>
 </ul>
 <p>
 All of these are related to the CometVisu add-on for openHAB - if you are a user of CometVisu, we strongly recommend to upgrade your system to openHAB 4.2.1 in order to fix those vulnerabilities.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <url>https://github.com/openhab/openhab-distro/releases/tag/4.2.1</url>
       <url>https://github.com/openhab/openhab-webui/security/advisories/GHSA-v7gr-mqpj-wwh3</url>
       <url>https://github.com/openhab/openhab-webui/security/advisories/GHSA-3g4c-hjhr-73rj</url>
       <url>https://github.com/openhab/openhab-webui/security/advisories/GHSA-f729-58x4-gqgf</url>
       <url>https://github.com/openhab/openhab-webui/security/advisories/GHSA-pcwp-26pw-j98w</url>
     </references>
     <dates>
       <discovery>2024-08-09</discovery>
       <entry>2024-08-09</entry>
     </dates>
   </vuln>
 
   <vuln vid="d2723b0f-58d9-11ef-b611-84a93843eb75">
     <topic>Vaultwarden -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>vaultwarden</name>
 	<range><lt>1.32.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>SO-AND-SO reports:</p>
 	<blockquote cite="https://github.com/dani-garcia/vaultwarden/releases/tag/1.32.0">
 	  <p>This release has several CVE Reports fixed and we recommend
 	    everybody to update to the latest version as soon as possible.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-39924</cvename>
       <cvename>CVE-2024-39925</cvename>
       <cvename>CVE-2024-39926</cvename>
       <url>https://github.com/dani-garcia/vaultwarden/releases/tag/1.32.0</url>
     </references>
     <dates>
       <discovery>2024-08-11</discovery>
       <entry>2024-08-12</entry>
     </dates>
   </vuln>
 
   <vuln vid="7d631146-5769-11ef-b618-1c697a616631">
     <topic>AMD CPUs -- Guest Memory Vulnerabilities</topic>
     <affects>
       <package>
 	<name>cpu-microcode-amd</name>
 	<range><lt>20240810</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>AMD reports:</p>
 	<blockquote cite="https://www.amd.com/en/resources/product-security/bulletin/amd-sb-7014.html">
 	  <p>
 	   Researchers from IOActive have reported that it may be possible for
 	   an attacker with ring 0 access to modify the configuration of System
 	   Management Mode (SMM) even when SMM Lock is enabled.  Improper
 	   validation in a model specific register (MSR) could allow a malicious
 	   program with ring0 access to modify SMM configuration while SMI lock
 	   is enabled, potentially leading to arbitrary code execution.
 	  </p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-31315</cvename>
       <url>https://www.amd.com/en/resources/product-security/bulletin/amd-sb-7014.html</url>
     </references>
     <dates>
       <discovery>2024-08-09</discovery>
       <entry>2024-08-10</entry>
     </dates>
   </vuln>
 
   <vuln vid="5776cc4f-5717-11ef-b611-84a93843eb75">
     <topic>Roundcube -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>roundcube</name>
 	<range><lt>1.6.8,1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The Roundcube project reports:</p>
 	<blockquote cite="https://roundcube.net/news/2024/08/04/security-updates-1.6.8-and-1.5.8">
 	  <p>XSS vulnerability in post-processing of sanitized HTML content [CVE-2024-42009]</p>
 	  <p>XSS vulnerability in serving of attachments other than HTML or SVG [CVE-2024-42008]</p>
 	  <p>information leak (access to remote content) via insufficient CSS filtering [CVE-2024-42010]</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-42009</cvename>
       <cvename>CVE-2024-42008</cvename>
       <cvename>CVE-2024-42010</cvename>
       <url>https://roundcube.net/news/2024/08/04/security-updates-1.6.8-and-1.5.8</url>
     </references>
     <dates>
       <discovery>2024-08-04</discovery>
       <entry>2024-08-10</entry>
     </dates>
   </vuln>
 
   <vuln vid="aa1c7af9-570e-11ef-a43e-b42e991fc52e">
     <topic>mozilla firefox -- protocol information guessing</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>127.0,2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1883693">
 	  <p>By monitoring the time certain operations take, an attacker could
 	have guessed which external protocol handlers were functional on a
 	user&apos;s system.  This vulnerability affects Firefox &lt; 127,
 	Firefox ESR &lt; 115.12, and Thunderbird &lt; 115.12.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-5690</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-5690</url>
     </references>
     <dates>
       <discovery>2024-06-11</discovery>
       <entry>2024-08-10</entry>
     </dates>
   </vuln>
 
   <vuln vid="8c342a6c-563f-11ef-a77e-901b0e9408dc">
     <topic>soft-serve -- Remote code execution vulnerability</topic>
     <affects>
       <package>
 	<name>soft-serve</name>
 	<range><lt>0.7.5</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>soft-serve team reports:</p>
 	<blockquote cite="https://github.com/charmbracelet/soft-serve/security/advisories/GHSA-m445-w3xr-vp2f">
 	  <p>Arbitrary code execution by crafting git ssh requests</p>
 	  <p>It is possible for a user who can commit files to a
 	  repository hosted by Soft Serve to execute arbitrary code
 	  via environment manipulation and Git.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-41956</cvename>
       <url>https://github.com/charmbracelet/soft-serve/security/advisories/GHSA-m445-w3xr-vp2f</url>
     </references>
     <dates>
       <discovery>2024-08-01</discovery>
       <entry>2024-08-09</entry>
     </dates>
   </vuln>
 
   <vuln vid="48e6d514-5568-11ef-af48-6cc21735f730">
     <topic>PostgreSQL -- Prevent unauthorized code execution during pg_dump</topic>
     <affects>
       <package>
 	<name>postgresql12-client</name>
 	<range><lt>12.20</lt></range>
       </package>
       <package>
 	<name>postgresql13-client</name>
 	<range><lt>13.16</lt></range>
       </package>
       <package>
 	<name>postgresql14-client</name>
 	<range><lt>14.13</lt></range>
       </package>
       <package>
 	<name>postgresql15-client</name>
 	<range><lt>15.8</lt></range>
       </package>
       <package>
 	<name>postgresql16-client</name>
 	<range><lt>16.4</lt></range>
       </package>
       <package>
 	<name>postgresql12-server</name>
 	<range><lt>12.20</lt></range>
       </package>
       <package>
 	<name>postgresql13-server</name>
 	<range><lt>13.16</lt></range>
       </package>
       <package>
 	<name>postgresql14-server</name>
 	<range><lt>14.13</lt></range>
       </package>
       <package>
 	<name>postgresql15-server</name>
 	<range><lt>15.8</lt></range>
       </package>
       <package>
 	<name>postgresql16-server</name>
 	<range><lt>16.4</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>PostgreSQL project reports:</p>
 	<blockquote cite="https://www.postgresql.org/support/security/CVE-2024-7348/">
 	   <p>
 	     An attacker able to create and drop non-temporary objects could
 	     inject SQL code that would be executed by a concurrent pg_dump
 	     session with the privileges of the role running pg_dump
 	     (which is often a superuser). The attack involves replacing a
 	     sequence or similar object with a view or foreign table that will
 	     execute malicious code. To prevent this, introduce a new server
 	     parameter restrict_nonsystem_relation_kind that can disable
 	     expansion of non-builtin views as well as access to foreign
 	     tables, and teach pg_dump to set it when available. Note that the
 	     attack is prevented only if both pg_dump and the server it is
 	     dumping from are new enough to have this fix.
 	   </p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-7348</cvename>
       <url>https://www.postgresql.org/support/security/CVE-2024-7348/</url>
     </references>
     <dates>
       <discovery>2024-08-08</discovery>
       <entry>2024-08-08</entry>
     </dates>
   </vuln>
 
   <vuln vid="db8fa362-0ccb-4aa8-9220-72b7763e9a4a">
     <topic>jenkins -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>jenkins</name>
 	<range><lt>2.471</lt></range>
       </package>
       <package>
 	<name>jenkins-lts</name>
 	<range><lt>2.462.1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Jenkins Security Advisory:</p>
 	<blockquote cite="https://www.jenkins.io/security/advisory/2024-08-07/">
 	  <h1>Description</h1>
 	  <h5>(Critical) SECURITY-3430 / CVE-2024-43044</h5>
 	  <p>Arbitrary file read vulnerability through agent connections can lead to RCE</p>
 	  <h1>Description</h1>
 	  <h5>(Medium) SECURITY-3349 / CVE-2024-43045</h5>
 	  <p>Missing permission check allows accessing other users' "My Views"</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-43044</cvename>
       <cvename>CVE-2024-43045</cvename>
       <url>https://www.jenkins.io/security/advisory/2024-08-07/</url>
     </references>
     <dates>
       <discovery>2024-08-07</discovery>
       <entry>2024-08-07</entry>
     </dates>
   </vuln>
 
   <vuln vid="729008b9-54bf-11ef-a61b-2cf05da270f3">
     <topic>Gitlab -- Vulnerabilities</topic>
     <affects>
       <package>
 	<name>gitlab-ce</name>
 	<name>gitlab-ee</name>
 	<range><ge>17.2.0</ge><lt>17.2.2</lt></range>
 	<range><ge>17.1.0</ge><lt>17.1.4</lt></range>
 	<range><ge>12.0.0</ge><lt>17.0.6</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Gitlab reports:</p>
 	<blockquote cite="https://about.gitlab.com/releases/2024/08/07/patch-release-gitlab-17-2-2-released/">
 	  <p>Privilege Escalation via LFS Tokens Granting Unrestricted Repository Access</p>
 	  <p>Cross project access of Security policy bot</p>
 	  <p>Advanced search ReDOS in highlight for code results</p>
 	  <p>Denial of Service via banzai pipeline</p>
 	  <p>Denial of service using adoc files</p>
 	  <p>ReDoS in RefMatcher when matching branch names using wildcards</p>
 	  <p>Path encoding can cause the Web interface to not render diffs correctly</p>
 	  <p>XSS while viewing raw XHTML files through API</p>
 	  <p>Ambiguous tag name exploitation</p>
 	  <p>Logs disclosings potentially sensitive data in query params</p>
 	  <p>Password bypass on approvals using policy projects</p>
 	  <p>ReDoS when parsing git push</p>
 	  <p>Webhook deletion audit log can preserve auth credentials</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-3035</cvename>
       <cvename>CVE-2024-6356</cvename>
       <cvename>CVE-2024-5423</cvename>
       <cvename>CVE-2024-4210</cvename>
       <cvename>CVE-2024-2800</cvename>
       <cvename>CVE-2024-6329</cvename>
       <cvename>CVE-2024-4207</cvename>
       <cvename>CVE-2024-3958</cvename>
       <cvename>CVE-2024-4784</cvename>
       <cvename>CVE-2024-3114</cvename>
       <cvename>CVE-2024-7586</cvename>
       <url>https://about.gitlab.com/releases/2024/08/07/patch-release-gitlab-17-2-2-released/</url>
     </references>
     <dates>
       <discovery>2024-08-07</discovery>
       <entry>2024-08-07</entry>
     </dates>
   </vuln>
 
   <vuln vid="94d441d2-5497-11ef-9d2f-080027836e8b">
     <topic>Django -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>py39-django42</name>
 	<name>py310-django42</name>
 	<name>py311-django42</name>
 	<range><lt>4.2.15</lt></range>
       </package>
       <package>
 	<name>py310-django50</name>
 	<name>py311-django50</name>
 	<range><lt>5.0.8</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Django reports:</p>
 	<blockquote cite="https://www.djangoproject.com/weblog/2024/aug/06/security-releases/">
 	  <p>CVE-2024-41989: Memory exhaustion in django.utils.numberformat.floatformat().</p>
 	  <p>CVE-2024-41990: Potential denial-of-service in django.utils.html.urlize().</p>
 	  <p>CVE-2024-41991: Potential denial-of-service vulnerability in
 	    django.utils.html.urlize() and AdminURLFieldWidget.</p>
 	  <p>CVE-2024-42005: Potential SQL injection in QuerySet.values() and values_list().</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-41989</cvename>
       <cvename>CVE-2024-41990</cvename>
       <cvename>CVE-2024-41991</cvename>
       <cvename>CVE-2024-42005</cvename>
       <url>https://www.djangoproject.com/weblog/2024/aug/06/security-releases/</url>
     </references>
     <dates>
       <discovery>2024-08-01</discovery>
       <entry>2024-08-07</entry>
     </dates>
   </vuln>
 
   <vuln vid="05cd9f82-5426-11ef-8a0f-a8a1599412c6">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>127.0.6533.99</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>127.0.6533.99</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2024/08/stable-channel-update-for-desktop.html">
 	 <p>This update includes 5 security fixes:</p>
 	 <ul>
 	    <li>[350528343] Critical CVE-2024-7532: Out of bounds memory access in ANGLE. Reported by wgslfuzz on 2024-07-02</li>
 	    <li>[353552540] High CVE-2024-7533: Use after free in Sharing. Reported by lime(@limeSec_) from TIANGONG Team of Legendsec at QI-ANXIN Group on 2024-07-17</li>
 	    <li>[355256380] High CVE-2024-7550: Type Confusion in V8. Reported by Zhenghang Xiao (@Kipreyyy) on 2024-07-25</li>
 	    <li>[352467338] High CVE-2024-7534: Heap buffer overflow in Layout. Reported by Tashita Software Security on 2024-07-11</li>
 	    <li>[352690885] High CVE-2024-7535: Inappropriate implementation in V8. Reported by Tashita Software Security on 2024-07-12</li>
 	    <li>[354847246] High CVE-2024-7536: Use after free in WebAudio. Reported by Cassidy Kim(@cassidy6564) on 2024-07-23</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-7532</cvename>
       <cvename>CVE-2024-7550</cvename>
       <cvename>CVE-2024-7534</cvename>
       <cvename>CVE-2024-7535</cvename>
       <cvename>CVE-2024-7536</cvename>
       <url>https://chromereleases.googleblog.com/2024/08/stable-channel-update-for-desktop.html</url>
     </references>
     <dates>
       <discovery>2024-08-06</discovery>
       <entry>2024-08-06</entry>
     </dates>
   </vuln>
 
   <vuln vid="15d398ea-4f73-11ef-8a0f-a8a1599412c6">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>127.0.6533.88</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>127.0.6533.88</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2024/07/stable-channel-update-for-desktop_30.html">
 	 <p>This update includes 3 security fixes:</p>
 	 <ul>
 	    <li>[353034820] Critical CVE-2024-6990: Uninitialized Use in Dawn. Reported by gelatin dessert on 2024-07-15</li>
 	    <li>[352872238] High CVE-2024-7255: Out of bounds read in WebTransport. Reported by Marten Richter on 2024-07-13</li>
 	    <li>[354748060] High CVE-2024-7256: Insufficient data validation in Dawn. Reported by gelatin dessert on 2024-07-23</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-6990</cvename>
       <cvename>CVE-2024-7255</cvename>
       <cvename>CVE-2024-7256</cvename>
       <url>https://chromereleases.googleblog.com/2024/07/stable-channel-update-for-desktop_30.html</url>
     </references>
     <dates>
       <discovery>2024-07-30</discovery>
       <entry>2024-07-31</entry>
     </dates>
   </vuln>
 
   <vuln vid="fb0b5574-4e64-11ef-8a0f-a8a1599412c6">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>127.0.6533.72</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>127.0.6533.72</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2024/07/stable-channel-update-for-desktop_23.html">
 	 <p>This update includes 22 security fixes:</p>
 	 <ul>
 	    <li>[349198731] High CVE-2024-6988: Use after free in Downloads. Reported by lime(@limeSec_) from TIANGONG Team of Legendsec at QI-ANXIN Group on 2024-06-25</li>
 	    <li>[349342289] High CVE-2024-6989: Use after free in Loader. Reported by Anonymous on 2024-06-25</li>
 	    <li>[346618785] High CVE-2024-6991: Use after free in Dawn. Reported by wgslfuzz on 2024-06-12</li>
 	    <li>[339686368] Medium CVE-2024-6994: Heap buffer overflow in Layout. Reported by Huang Xilin of Ant Group Light-Year Security Lab on 2024-05-10</li>
 	    <li>[343938078] Medium CVE-2024-6995: Inappropriate implementation in Fullscreen. Reported by Alesandro Ortiz on 2024-06-01</li>
 	    <li>[333708039] Medium CVE-2024-6996: Race in Frames. Reported by Louis Jannett (Ruhr University Bochum) on 2024-04-10</li>
 	    <li>[325293263] Medium CVE-2024-6997: Use after free in Tabs. Reported by Sven Dysthe (@svn-dys) on 2024-02-15</li>
 	    <li>[340098902] Medium CVE-2024-6998: Use after free in User Education. Reported by Sven Dysthe (@svn-dys) on 2024-05-13</li>
 	    <li>[340893685] Medium CVE-2024-6999: Inappropriate implementation in FedCM. Reported by Alesandro Ortiz on 2024-05-15</li>
 	    <li>[339877158] Medium CVE-2024-7000: Use after free in CSS. Reported by Anonymous on 2024-05-11</li>
 	    <li>[347509736] Medium CVE-2024-7001: Inappropriate implementation in HTML. Reported by Jake Archibald on 2024-06-17</li>
 	    <li>[338233148] Low CVE-2024-7003: Inappropriate implementation in FedCM. Reported by Alesandro Ortiz on 2024-05-01</li>
 	    <li>[40063014] Low CVE-2024-7004: Insufficient validation of untrusted input in Safe Browsing. Reported by Anonymous on 2023-02-10</li>
 	    <li>[40068800] Low CVE-2024-7005: Insufficient validation of untrusted input in Safe Browsing. Reported by Umar Farooq on 2023-08-04</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-6988</cvename>
       <cvename>CVE-2024-6989</cvename>
       <cvename>CVE-2024-6991</cvename>
       <cvename>CVE-2024-6994</cvename>
       <cvename>CVE-2024-6995</cvename>
       <cvename>CVE-2024-6996</cvename>
       <cvename>CVE-2024-6997</cvename>
       <cvename>CVE-2024-6998</cvename>
       <cvename>CVE-2024-6999</cvename>
       <cvename>CVE-2024-7000</cvename>
       <cvename>CVE-2024-7001</cvename>
       <cvename>CVE-2024-7003</cvename>
       <cvename>CVE-2024-7004</cvename>
       <cvename>CVE-2024-7005</cvename>
       <url>https://chromereleases.googleblog.com/2024/07/stable-channel-update-for-desktop_23.html</url>
     </references>
     <dates>
       <discovery>2024-07-23</discovery>
       <entry>2024-07-30</entry>
     </dates>
   </vuln>
 
   <vuln vid="8057d198-4d26-11ef-8e64-641c67a117d8">
     <topic>znc -- remote code execution vulnerability</topic>
     <affects>
       <package>
 	<name>znc</name>
 	<range><lt>1.9.1</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Mitre reports:</p>
 	<blockquote cite="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-39844">
 	  <p>In ZNC before 1.9.1, remote code execution can occur in modtcl via a KICK.</p>
 	</blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-39844</cvename>
       <url>https://wiki.znc.in/ChangeLog/1.9.1</url>
       <url>https://www.openwall.com/lists/oss-security/2024/07/03/9</url>
     </references>
     <dates>
       <discovery>2024-07-03</discovery>
       <entry>2024-07-28</entry>
     </dates>
   </vuln>
 
   <vuln vid="3e917407-4b3f-11ef-8e49-001999f8d30b">
     <topic>Mailpit -- Content Security Policy XSS</topic>
     <affects>
       <package>
 	<name>mailpit</name>
 	<range><lt>1.19.3</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Mailpit developer reports:</p>
 	<blockquote cite="https://github.com/axllent/mailpit/releases/tag/v1.19.3">
 	  <p>A vulnerability was discovered which allowed a bad
 	  actor with SMTP access to Mailpit to bypass the Content
 	  Security Policy headers using a series of crafted HTML
 	  messages which could result in a stored XSS attack via
 	  the web UI.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <url>https://github.com/axllent/mailpit/releases/tag/v1.19.3</url>
     </references>
     <dates>
       <discovery>2024-07-26</discovery>
       <entry>2024-07-26</entry>
     </dates>
   </vuln>
 
   <vuln vid="24c88add-4a3e-11ef-86d7-001b217b3468">
     <topic>Gitlab -- Vulnerabilities</topic>
     <affects>
       <package>
 	<name>gitlab-ce</name>
 	<name>gitlab-ee</name>
 	<range><ge>17.2.0</ge><lt>17.2.1</lt></range>
 	<range><ge>17.1.0</ge><lt>17.1.3</lt></range>
 	<range><ge>12.0.0</ge><lt>17.0.5</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Gitlab reports:</p>
 	<blockquote cite="https://about.gitlab.com/releases/2024/07/24/patch-release-gitlab-17-2-1-released/">
 	  <p>XSS via the Maven Dependency Proxy</p>
 	  <p>Project level analytics settings leaked in DOM</p>
 	  <p>Reports can access and download job artifacts despite use of settings to prevent it</p>
 	  <p>Direct Transfer - Authorised project/group exports are accessible to other users</p>
 	  <p>Bypassing tag check and branch check through imports</p>
 	  <p>Project Import/Export - Make project/group export files hidden to everyone except user who initiated it</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-5067</cvename>
       <cvename>CVE-2024-7057</cvename>
       <cvename>CVE-2024-0231</cvename>
       <url>https://about.gitlab.com/releases/2024/07/24/patch-release-gitlab-17-2-1-released/</url>
     </references>
     <dates>
       <discovery>2024-07-24</discovery>
       <entry>2024-07-25</entry>
     </dates>
   </vuln>
 
   <vuln vid="574028b4-a181-455b-a78b-ec5c62781235">
     <topic>electron29 -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>electron29</name>
 	<range><lt>29.4.5</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Electron developers report:</p>
 	<blockquote cite="https://github.com/electron/electron/releases/tag/v29.4.5">
 	  <p>This update fixes the following vulnerabilities:</p>
 	  <ul>
 	    <li>Security: backported fix for CVE-2024-6291.</li>
 	    <li>Security: backported fix for CVE-2024-6293.</li>
 	    <li>Security: backported fix for CVE-2024-6290.</li>
 	    <li>Security: backported fix for CVE-2024-6292.</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-6291</cvename>
       <url>https://github.com/advisories/GHSA-rpvg-h6p6-42qj</url>
       <cvename>CVE-2024-6293</cvename>
       <url>https://github.com/advisories/GHSA-9f8f-453p-rg87</url>
       <cvename>CVE-2024-6290</cvename>
       <url>https://github.com/advisories/GHSA-r5mh-qgc2-26p2</url>
       <cvename>CVE-2024-6292</cvename>
       <url>https://github.com/advisories/GHSA-m848-8f5r-6j4g</url>
     </references>
     <dates>
       <discovery>2024-07-17</discovery>
       <entry>2024-07-19</entry>
     </dates>
   </vuln>
 
   <vuln vid="088b8b7d-446c-11ef-b611-84a93843eb75">
     <topic>Apache httpd -- Source code disclosure with handlers configured via AddType</topic>
     <affects>
       <package>
 	<name>apache24</name>
 	<range><ge>2.4.60</ge><lt>2.4.62</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The Apache httpd project reports:</p>
 	<blockquote cite="https://httpd.apache.org/security/vulnerabilities_24.html">
 	  <p>source code disclosure with handlers configured via AddType
 	    (CVE-2024-40725) (Important): A partial fix for CVE-2024-39884
 	    in the core of Apache HTTP Server 2.4.61 ignores some use of the
 	    legacy content-type based configuration of handlers. "AddType"
 	    and similar configuration, under some circumstances where files
 	    are requested indirectly, result in source code disclosure of
 	    local content. For example, PHP scripts may be served instead
 	    of interpreted.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-40725</cvename>
       <url>https://httpd.apache.org/security/vulnerabilities_24.html</url>
     </references>
     <dates>
       <discovery>2024-07-17</discovery>
       <entry>2024-07-17</entry>
     </dates>
   </vuln>
 
   <vuln vid="3b018063-4358-11ef-b611-84a93843eb75">
     <topic>MySQL -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>mysql80-client</name>
 	<range><lt>8.0.38</lt></range>
       </package>
       <package>
 	<name>mysql80-server</name>
 	<range><lt>8.0.38</lt></range>
       </package>
       <package>
 	<name>mysql81-client</name>
 	<range><lt>8.1.1</lt></range>
       </package>
       <package>
 	<name>mysql81-server</name>
 	<range><lt>8.1.1</lt></range>
       </package>
       <package>
 	<name>mysql84-client</name>
 	<range><lt>8.4.1</lt></range>
       </package>
       <package>
 	<name>mysql84-server</name>
 	<range><lt>8.4.1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Oracle reports:</p>
 	<blockquote cite="https://www.oracle.com/security-alerts/cpujul2024.html#MySQL">
 	  <p>36 new security patches for Oracle MySQL. 11 of these vulnerabilities
 	    may be remotely exploitable without authentication, i.e., may be
 	    exploited over a network without requiring user credentials.
 	    The highest CVSS v3.1 Base Score of vulnerabilities affecting Oracle
 	    MySQL is 9.8.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <url>https://www.oracle.com/security-alerts/cpujul2024.html#MySQL</url>
     </references>
     <dates>
       <discovery>2024-07-16</discovery>
       <entry>2024-07-16</entry>
     </dates>
   </vuln>
 
   <vuln vid="6091d1d8-4347-11ef-a4d4-080027957747">
     <topic>GLPI -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>glpi</name>
 	<range><lt>10.0.16,1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>GLPI team reports:</p>
 	<blockquote cite="https://github.com/glpi-project/glpi/releases/tag/10.0.16">
 	  <p>GLPI 10.0.16 Changelog</p>
 	  <ul>
 	    <li>[SECURITY - high] Account takeover via SQL Injection in AJAX scripts (CVE-2024-37148)</li>
 	    <li>[SECURITY - high] Remote code execution through the plugin loader (CVE-2024-37149)</li>
 	    <li>[SECURITY - moderate] Authenticated file upload to restricted tickets (CVE-2024-37147)</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-37148</cvename>
       <url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-37148</url>
       <cvename>CVE-2024-37149</cvename>
       <url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-37149</url>
       <cvename>CVE-2024-37147</cvename>
       <url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-37147</url>
       <url>https://github.com/glpi-project/glpi/releases/tag/10.0.16</url>
     </references>
     <dates>
       <discovery>2024-06-03</discovery>
       <entry>2024-07-16</entry>
     </dates>
   </vuln>
 
   <vuln vid="6410f91d-1214-4f92-b7e0-852e39e265f9">
     <topic>electron30 -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>electron30</name>
 	<range><lt>30.2.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Electron developers report:</p>
 	<blockquote cite="https://github.com/electron/electron/releases/tag/v30.2.0">
 	  <p>This update fixes the following vulnerabilities:</p>
 	  <ul>
 	    <li>Security: backported fix for CVE-2024-5493.</li>
 	    <li>Security: backported fix for CVE-2024-5831.</li>
 	    <li>Security: backported fix for CVE-2024-5832.</li>
 	    <li>Security: backported fix for CVE-2024-6100.</li>
 	    <li>Security: backported fix for CVE-2024-6101.</li>
 	    <li>Security: backported fix for CVE-2024-6103.</li>
 	    <li>Security: backported fix for CVE-2024-6291.</li>
 	    <li>Security: backported fix for CVE-2024-6293.</li>
 	    <li>Security: backported fix for CVE-2024-6290.</li>
 	    <li>Security: backported fix for CVE-2024-6292.</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-5493</cvename>
       <url>https://github.com/advisories/GHSA-f6rr-qfxh-hcf9</url>
       <cvename>CVE-2024-5831</cvename>
       <url>https://github.com/advisories/GHSA-9pmm-wf44-xjqc</url>
       <cvename>CVE-2024-5832</cvename>
       <url>https://github.com/advisories/GHSA-rw9q-cwc5-qqp5</url>
       <cvename>CVE-2024-6100</cvename>
       <url>https://github.com/advisories/GHSA-g779-vpj7-v6c4</url>
       <cvename>CVE-2024-6101</cvename>
       <url>https://github.com/advisories/GHSA-rg42-f9ww-x3w7</url>
       <cvename>CVE-2024-6103</cvename>
       <url>https://github.com/advisories/GHSA-ph5m-227m-fc5g</url>
       <cvename>CVE-2024-6291</cvename>
       <url>https://github.com/advisories/GHSA-rpvg-h6p6-42qj</url>
       <cvename>CVE-2024-6293</cvename>
       <url>https://github.com/advisories/GHSA-9f8f-453p-rg87</url>
       <cvename>CVE-2024-6290</cvename>
       <url>https://github.com/advisories/GHSA-r5mh-qgc2-26p2</url>
       <cvename>CVE-2024-6292</cvename>
       <url>https://github.com/advisories/GHSA-m848-8f5r-6j4g</url>
     </references>
     <dates>
       <discovery>2024-07-10</discovery>
       <entry>2024-07-13</entry>
     </dates>
   </vuln>
 
   <vuln vid="55d4a92f-c75f-43e8-ab1f-4a0efc9795c4">
     <topic>electron29 -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>electron29</name>
 	<range><lt>29.4.4</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Electron developers report:</p>
 	<blockquote cite="https://github.com/electron/electron/releases/tag/v29.4.4">
 	  <p>This update fixes the following vulnerabilities:</p>
 	  <ul>
 	    <li>Security: backported fix for CVE-2024-6291.</li>
 	    <li>Security: backported fix for CVE-2024-6293.</li>
 	    <li>Security: backported fix for CVE-2024-6290.</li>
 	    <li>Security: backported fix for CVE-2024-6292.</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-6291</cvename>
       <url>https://github.com/advisories/GHSA-rpvg-h6p6-42qj</url>
       <cvename>CVE-2024-6293</cvename>
       <url>https://github.com/advisories/GHSA-9f8f-453p-rg87</url>
       <cvename>CVE-2024-6290</cvename>
       <url>https://github.com/advisories/GHSA-r5mh-qgc2-26p2</url>
       <cvename>CVE-2024-6292</cvename>
       <url>https://github.com/advisories/GHSA-m848-8f5r-6j4g</url>
     </references>
     <dates>
       <discovery>2024-07-11</discovery>
       <entry>2024-07-13</entry>
     </dates>
   </vuln>
 
   <vuln vid="acb4eab6-3f6d-11ef-8657-001b217b3468">
     <topic>Gitlab -- vulnerabilities</topic>
     <affects>
       <package>
 	<name>gitlab-ce</name>
 	<name>gitlab-ee</name>
 	<range><ge>17.1.0</ge><lt>17.1.2</lt></range>
 	<range><ge>17.0.0</ge><lt>17.0.4</lt></range>
 	<range><ge>11.8.0</ge><lt>16.11.6</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Gitlab reports:</p>
 	<blockquote cite="https://about.gitlab.com/releases/2024/07/10/patch-release-gitlab-17-1-2-released/">
 	  <p>An attacker can run pipeline jobs as an arbitrary user</p>
 	  <p>Developer user with admin_compliance_framework permission can change group URL</p>
 	  <p>Admin push rules custom role allows creation of project level deploy token</p>
 	  <p>Package registry vulnerable to manifest confusion</p>
 	  <p>User with admin_group_member permission can ban group members</p>
 	  <p>Subdomain takeover in GitLab Pages</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-6385</cvename>
       <cvename>CVE-2024-5257</cvename>
       <cvename>CVE-2024-5470</cvename>
       <cvename>CVE-2024-6595</cvename>
       <cvename>CVE-2024-2880</cvename>
       <cvename>CVE-2024-5528</cvename>
       <url>https://about.gitlab.com/releases/2024/07/10/patch-release-gitlab-17-1-2-released/</url>
     </references>
     <dates>
       <discovery>2024-07-10</discovery>
       <entry>2024-07-11</entry>
     </dates>
   </vuln>
 
   <vuln vid="171afa61-3eba-11ef-a58f-080027836e8b">
     <topic>Django -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>py39-django42</name>
 	<name>py310-django42</name>
 	<name>py311-django42</name>
 	<range><lt>4.2.14</lt></range>
       </package>
       <package>
 	<name>py310-django50</name>
 	<name>py311-django50</name>
 	<range><lt>5.0.7</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Django reports:</p>
 	<blockquote cite="https://www.djangoproject.com/weblog/2024/jul/09/security-releases/">
 	  <p>CVE-2024-38875: Potential denial-of-service in django.utils.html.urlize().</p>
 	  <p>CVE-2024-39329: Username enumeration through timing difference for users with unusable passwords.</p>
 	  <p>CVE-2024-39330: Potential directory-traversal in django.core.files.storage.Storage.save().</p>
 	  <p>CVE-2024-39614: Potential denial-of-service in django.utils.translation.get_supported_language_variant().</p>
 	</blockquote>
 	</body>
     </description>
     <references>
 	<cvename>CVE-2024-38875</cvename>
 	<cvename>CVE-2024-39329</cvename>
 	<cvename>CVE-2024-39330</cvename>
 	<cvename>CVE-2024-39614</cvename>
 	<url>https://www.djangoproject.com/weblog/2024/jul/09/security-releases/</url>
     </references>
     <dates>
 	<discovery>2024-07-01</discovery>
 	<entry>2024-07-10</entry>
     </dates>
   </vuln>
 
   <vuln vid="767dfb2d-3c9e-11ef-a829-5404a68ad561">
     <topic>traefik -- Bypassing IP allow-lists via HTTP/3 early data requests</topic>
     <affects>
       <package>
 	<name>traefik</name>
 	<range><lt>2.11.6</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The traefik authors report:</p>
 	<blockquote cite="https://github.com/traefik/traefik/security/advisories/GHSA-gxrv-wf35-62w9">
 		<p>There is a vulnerability in Traefik that allows bypassing IP allow-lists via HTTP/3 early
 		   data requests in QUIC 0-RTT handshakes sent with spoofed IP addresses.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-39321</cvename>
       <url>https://github.com/traefik/traefik/security/advisories/GHSA-gxrv-wf35-62w9</url>
     </references>
     <dates>
       <discovery>2024-07-02</discovery>
       <entry>2024-07-07</entry>
     </dates>
   </vuln>
 
   <vuln vid="5d921a8c-3a43-11ef-b611-84a93843eb75">
     <topic>Apache httpd -- source code disclosure</topic>
     <affects>
       <package>
 	<name>apache24</name>
 	<range><ge>2.4.60</ge><lt>2.4.61</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The Apache httpd project reports:</p>
 	<blockquote cite="https://httpd.apache.org/security/vulnerabilities_24.html">
 	  <p>isource code disclosure with handlers configured via AddType
 	    (CVE-2024-39884) (Important). A regression in the core of Apache HTTP
 	    Server 2.4.60 ignores some use of the legacy content-type based
 	    configuration of handlers. "AddType" and similar configuration,
 	    under some circumstances where files are requested indirectly, result
 	    in source code disclosure of local content. For example, PHP scripts
 	    may be served instead of interpreted.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-39884</cvename>
       <url>https://httpd.apache.org/security/vulnerabilities_24.html</url>
     </references>
     <dates>
       <discovery>2024-07-04</discovery>
       <entry>2024-07-04</entry>
     </dates>
   </vuln>
 
   <vuln vid="51498ee4-39a1-11ef-b609-002590c1f29c">
     <topic>Request Tracker -- information exposure vulnerability</topic>
     <affects>
       <package>
        <name>rt50</name>
        <range><lt>5.0.6</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Request Tracker reports:</p>
 	<p>CVE-2024-3262 describes previously viewed pages being stored in the
 	browser cache, which is the typical default behavior of most browsers to
 	enable the "back" button. Someone who gains access to a host computer could
 	potentially view ticket data using the back button, even after logging out
 	of RT. The CVE specifically references RT version 4.4.1, but this behavior
 	is present in most browsers viewing all versions of RT before 5.0.6.</p>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-3262</cvename>
       <url>https://github.com/advisories/GHSA-6426-p644-ffcf</url>
     </references>
     <dates>
       <discovery>2024-04-04</discovery>
       <entry>2024-07-04</entry>
     </dates>
   </vuln>
 
   <vuln vid="b0374722-3912-11ef-a77e-901b0e9408dc">
     <topic>go -- net/http: denial of service due to improper 100-continue handling</topic>
     <affects>
       <package>
 	<name>go122</name>
 	<range><lt>1.22.5</lt></range>
       </package>
       <package>
 	<name>go121</name>
 	<range><lt>1.21.12</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The Go project reports:</p>
 	<blockquote cite="https://go.dev/issue/67555">
 	  <p>net/http: denial of service due to improper 100-continue handling</p>
 	  <p>The net/http HTTP/1.1 client mishandled the case where a
 	  server responds to a request with an "Expect: 100-continue"
 	  header with a non-informational (200 or higher) status. This
 	  mishandling could leave a client connection in an invalid
 	  state, where the next request sent on the connection will
 	  fail.</p>
 	  <p>An attacker sending a request to a
 	  net/http/httputil.ReverseProxy proxy can exploit this
 	  mishandling to cause a denial of service by sending "Expect:
 	  100-continue" requests which elicit a non-informational
 	  response from the backend. Each such request leaves the
 	  proxy with an invalid connection, and causes one subsequent
 	  request using that connection to fail.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-24791</cvename>
       <url>https://go.dev/issue/67555</url>
     </references>
     <dates>
       <discovery>2024-07-02</discovery>
       <entry>2024-07-03</entry>
     </dates>
   </vuln>
 
   <vuln vid="d7efc2ad-37af-11ef-b611-84a93843eb75">
     <topic>Apache httpd -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>apache24</name>
 	<range><lt>2.4.60</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The Apache httpd project reports:</p>
 	<blockquote cite="https://httpd.apache.org/security/vulnerabilities_24.html">
 	  <p>DoS by Null pointer in websocket over HTTP/2 (CVE-2024-36387) (Low).
 	    Serving WebSocket protocol upgrades over a HTTP/2 connection could
 	    result in a Null Pointer dereference, leading to a crash of the server
 	    process, degrading performance.</p>
 	  <p>Proxy encoding problem (CVE-2024-38473) (Moderate).
 	    Encoding problem in mod_proxy in Apache HTTP Server 2.4.59 and earlier
 	    allows request URLs with incorrect encoding to be sent to backend
 	    services, potentially bypassing authentication via crafted requests.</p>
 	  <p>Weakness with encoded question marks in backreferences
 	    (CVE-2024-38474) (Important). Substitution encoding issue in
 	    mod_rewrite in Apache HTTP Server 2.4.59 and earlier allows attacker
 	    to execute scripts in directories permitted by the configuration but
 	    not directly reachable by any URL or source disclosure of scripts
 	    meant to only to be executed as CGI.</p>
 	  <p>Weakness in mod_rewrite when first segment of substitution matches
 	    filesystem path (CVE-2024-38475) (Important). Improper escaping of
 	    output in mod_rewrite in Apache HTTP Server 2.4.59 and earlier allows
 	    an attacker to map URLs to filesystem locations that are permitted to
 	    be served by the server but are not intentionally/directly reachable
 	    by any URL, resulting in code execution or source code disclosure.
 	    Substitutions in server context that use a backreferences or variables
 	    as the first segment of the substitution are affected. Some unsafe
 	    RewiteRules will be broken by this change and the rewrite flag
 	    "UnsafePrefixStat" can be used to opt back in once ensuring the
 	    substitution is appropriately constrained.</p>
 	  <p>may use exploitable/malicious backend application output to run local
 	    handlers via internal redirect (CVE-2024-38476) (Important).
 	    Vulnerability in core of Apache HTTP Server 2.4.59 and earlier are
 	    vulnerable to information disclosure, SSRF or local script execution
 	    via backend applications whose response headers are malicious or
 	    exploitable.</p>
 	  <p>Crash resulting in Denial of Service in mod_proxy via a malicious
 	    request (CVE-2024-38477) (Important). Null pointer dereference in
 	    mod_proxy in Apache HTTP Server 2.4.59 and earlier allows an attacker
 	    to crash the server via a malicious request.</p>
 	  <p>mod_rewrite proxy handler substitution (CVE-2024-39573) (Moderate).
 	    Potential SSRF in mod_rewrite in Apache HTTP Server 2.4.59 and earlier
 	    allows an attacker to cause unsafe RewriteRules to unexpectedly setup
 	    URL's to be handled by mod_proxy.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-36387</cvename>
       <cvename>CVE-2024-38473</cvename>
       <cvename>CVE-2024-38474</cvename>
       <cvename>CVE-2024-38475</cvename>
       <cvename>CVE-2024-38476</cvename>
       <cvename>CVE-2024-38477</cvename>
       <cvename>CVE-2024-39573</cvename>
       <url>https://httpd.apache.org/security/vulnerabilities_24.html</url>
     </references>
     <dates>
       <discovery>2024-07-01</discovery>
       <entry>2024-07-01</entry>
     </dates>
   </vuln>
 
   <vuln vid="f1a00122-3797-11ef-b611-84a93843eb75">
     <topic>OpenSSH -- Race condition resulting in potential remote code execution</topic>
     <affects>
       <package>
 	<name>openssh-portable</name>
 	<range><lt>9.7.p1_2,1</lt></range>
       </package>
       <package>
 	<name>FreeBSD</name>
 	<range><ge>14.1</ge><lt>14.1_2</lt></range>
 	<range><ge>14.0</ge><lt>14.0_8</lt></range>
 	<range><ge>13.3</ge><lt>13.3_4</lt></range>
 	<range><ge>13.2</ge><lt>13.2_12</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The OpenSSH project reports:</p>
 	<blockquote cite="https://www.openssh.com/security.html">
 	  <p>A race condition in sshd(8) could allow remote code execution as root on non-OpenBSD systems.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-6387</cvename>
       <url>https://www.openssh.com/security.html</url>
       <freebsdsa>SA-24:04.openssh</freebsdsa>
     </references>
     <dates>
       <discovery>2024-07-01</discovery>
       <entry>2024-07-01</entry>
       <modified>2024-09-20</modified>
     </dates>
   </vuln>
 
   <vuln vid="c742dbe8-3704-11ef-9e6e-b42e991fc52e">
     <topic>netatalk3 -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>netatalk3</name>
 	<range><lt>3.2.1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>cve@mitre.org reports:</p>
 	<blockquote cite="https://github.com/Netatalk/netatalk/blob/90d91a9ac9a7d6132ab7620d31c8c23400949206/etc/afpd/directory.c#L2333">
 	  <p>This entry documents the following three vulnerabilities:</p>
 	  <ul>
 	    <li>Netatalk before 3.2.1 has an off-by-one error and resultant heap-based
 	buffer overflow because of setting ibuf[len] to &apos;\0&apos; in
 	FPMapName in afp_mapname in etc/afpd/directory.c.  2.4.1 and 3.1.19
 	are also fixed versions.</li>
 	    <li>Netatalk before 3.2.1 has an off-by-one error, and resultant
 	heap-based buffer overflow and segmentation violation, because of
 	incorrectly using FPLoginExt in BN_bin2bn in etc/uams/uams_dhx_pam.c.
 	The original issue 1097 report stated: &apos;The latest version of
 	Netatalk (v3.2.0) contains a security vulnerability.  This vulnerability
 	arises due to a lack of validation for the length field after parsing
 	user-provided data, leading to an out-of-bounds heap write of one
 	byte (\0).  Under specific configurations, this can result in reading
 	metadata of the next heap block, potentially causing a Denial of
 	Service (DoS) under certain heap layouts or with ASAN enabled.  ...
 	    </li>
 	    <li>Netatalk before 3.2.1 has an off-by-one error and resultant heap-based
 	buffer overflow because of setting ibuf[PASSWDLEN] to &apos;\0&apos;
 	in FPLoginExt in login in etc/uams/uams_pam.c.  2.4.1 and 3.1.19
 	are also fixed versions.
 	    </li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-38440</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-38440</url>
       <cvename>CVE-2024-38441</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-38441</url>
       <cvename>CVE-2024-38439</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-38439</url>
     </references>
     <dates>
       <discovery>2024-06-16</discovery>
       <entry>2024-06-30</entry>
     </dates>
   </vuln>
 
   <vuln vid="0e73964d-053a-481a-bf1c-202948d68484">
     <topic>electron29 -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>electron29</name>
 	<range><lt>29.4.3</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Electron developers report:</p>
 	<blockquote cite="https://github.com/electron/electron/releases/tag/v29.4.3">
 	  <p>This update fixes the following vulnerabilities:</p>
 	  <ul>
 	    <li>Security: backported fix for CVE-2024-5499.</li>
 	    <li>Security: backported fix for CVE-2024-5493.</li>
 	    <li>Security: backported fix for CVE-2024-5494.</li>
 	    <li>Security: backported fix for CVE-2024-5495.</li>
 	    <li>Security: backported fix for CVE-2024-5496.</li>
 	    <li>Security: backported fix for CVE-2024-5158.</li>
 	    <li>Security: backported fix for CVE-2024-5160.</li>
 	    <li>Security: backported fix for CVE-2024-5157.</li>
 	    <li>Security: backported fix for CVE-2024-5159.</li>
 	    <li>Security: backported fix for CVE-2024-5831.</li>
 	    <li>Security: backported fix for CVE-2024-5832.</li>
 	    <li>Security: backported fix for CVE-2024-6100.</li>
 	    <li>Security: backported fix for CVE-2024-6101.</li>
 	    <li>Security: backported fix for CVE-2024-6103.</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-5499</cvename>
       <url>https://github.com/advisories/GHSA-hqfv-mf6j-g3j6</url>
       <cvename>CVE-2024-5493</cvename>
       <url>https://github.com/advisories/GHSA-f6rr-qfxh-hcf9</url>
       <cvename>CVE-2024-5494</cvename>
       <url>https://github.com/advisories/GHSA-fv2x-w8xf-gxpq</url>
       <cvename>CVE-2024-5495</cvename>
       <url>https://github.com/advisories/GHSA-wrxh-8wc3-33rm</url>
       <cvename>CVE-2024-5496</cvename>
       <url>https://github.com/advisories/GHSA-8xgv-q88p-ghq4</url>
       <cvename>CVE-2024-5158</cvename>
       <url>https://github.com/advisories/GHSA-4433-jwm9-48r5</url>
       <cvename>CVE-2024-5160</cvename>
       <url>https://github.com/advisories/GHSA-c24q-2hx9-mjpc</url>
       <cvename>CVE-2024-5157</cvename>
       <url>https://github.com/advisories/GHSA-w7g4-69hj-jcrq</url>
       <cvename>CVE-2024-5159</cvename>
       <url>https://github.com/advisories/GHSA-qmp7-vwf7-6g2g</url>
       <cvename>CVE-2024-5831</cvename>
       <url>https://github.com/advisories/GHSA-9pmm-wf44-xjqc</url>
       <cvename>CVE-2024-5832</cvename>
       <url>https://github.com/advisories/GHSA-rw9q-cwc5-qqp5</url>
       <cvename>CVE-2024-6100</cvename>
       <url>https://github.com/advisories/GHSA-g779-vpj7-v6c4</url>
       <cvename>CVE-2024-6101</cvename>
       <url>https://github.com/advisories/GHSA-rg42-f9ww-x3w7</url>
       <cvename>CVE-2024-6103</cvename>
       <url>https://github.com/advisories/GHSA-ph5m-227m-fc5g</url>
     </references>
     <dates>
       <discovery>2024-06-27</discovery>
       <entry>2024-06-28</entry>
     </dates>
   </vuln>
 
   <vuln vid="07f0ea8c-356a-11ef-ac6d-a0423f48a938">
     <topic>frr - Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>frr9</name>
 	<range><lt>9.1.1</lt></range>
       </package>
       <package>
       <name>frr8</name>
       <range><lt>8.5.5</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>cve@mitre.org reports:</p>
 	<blockquote cite="https://frrouting.org/release/9.1.1/">
 	  <p>In FRRouting (FRR) through 9.1, there are multiples vulnerabilities.</p>
 	<ul>
 	 <li>CVE-2024-31950: buffer overflow and daemon crash in ospf_te_parse_ri for OSPF LSA packets</li>
 	 <li>CVE-2024-31951: buffer overflow and daemon crash in ospf_te_parse_ext_link for OSPF LSA packets</li>
 	</ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-31950</cvename>
       <cvename>CVE-2024-31951</cvename>
       <url>https://frrouting.org/release/9.1.1/</url>
     </references>
     <dates>
       <discovery>2024-04-07</discovery>
       <entry>2024-06-28</entry>
     </dates>
   </vuln>
 
   <vuln vid="589de937-343f-11ef-8a7b-001b217b3468">
     <topic>Gitlab -- Vulnerabilities</topic>
     <affects>
       <package>
 	<name>gitlab-ce</name>
 	<name>gitlab-ee</name>
 	<range><ge>17.1.0</ge><lt>17.1.1</lt></range>
 	<range><ge>17.0.0</ge><lt>17.0.3</lt></range>
 	<range><ge>1.0.0</ge><lt>16.11.5</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Gitlab reports:</p>
 	<blockquote cite="https://about.gitlab.com/releases/2024/06/26/patch-release-gitlab-17-1-1-released/">
 	  <p>Run pipelines as any user</p>
 	  <p>Stored XSS injected in imported project's commit notes</p>
 	  <p>CSRF on GraphQL API IntrospectionQuery</p>
 	  <p>Remove search results from public projects with unauthorized repos</p>
 	  <p>Cross window forgery in user application OAuth flow</p>
 	  <p>Project maintainers can bypass group's merge request approval policy</p>
 	  <p>ReDoS via custom built markdown page</p>
 	  <p>Private job artifacts can be accessed by any user</p>
 	  <p>Security fixes for banzai pipeline</p>
 	  <p>ReDoS in dependency linker</p>
 	  <p>Denial of service using a crafted OpenAPI file</p>
 	  <p>Merge request title disclosure</p>
 	  <p>Access issues and epics without having an SSO session</p>
 	  <p>Non project member can promote key results to objectives</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-5655</cvename>
       <cvename>CVE-2024-4901</cvename>
       <cvename>CVE-2024-4994</cvename>
       <cvename>CVE-2024-6323</cvename>
       <cvename>CVE-2024-2177</cvename>
       <cvename>CVE-2024-5430</cvename>
       <cvename>CVE-2024-4025</cvename>
       <cvename>CVE-2024-3959</cvename>
       <cvename>CVE-2024-4557</cvename>
       <cvename>CVE-2024-1493</cvename>
       <cvename>CVE-2024-1816</cvename>
       <cvename>CVE-2024-2191</cvename>
       <cvename>CVE-2024-3115</cvename>
       <cvename>CVE-2024-4011</cvename>
       <url>https://about.gitlab.com/releases/2024/06/26/patch-release-gitlab-17-1-1-released/</url>
     </references>
     <dates>
       <discovery>2024-06-26</discovery>
       <entry>2024-06-27</entry>
     </dates>
   </vuln>
 
   <vuln vid="2b68c86a-32d5-11ef-8a0f-a8a1599412c6">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>126.0.6478.126</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>126.0.6478.126</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2024/06/stable-channel-update-for-desktop_24.html">
 	 <p>This update includes 5 security fixes:</p>
 	 <ul>
 	    <li>[342428008] High CVE-2024-6290: Use after free in Dawn. Reported by wgslfuzz on 2024-05-23</li>
 	    <li>[40942995] High CVE-2024-6291: Use after free in Swiftshader. Reported by Cassidy Kim(@cassidy6564) on 2023-11-15</li>
 	    <li>[342545100] High CVE-2024-6292: Use after free in Dawn. Reported by wgslfuzz on 2024-05-24</li>
 	    <li>[345993680] High CVE-2024-6293: Use after free in Dawn. Reported by wgslfuzz on 2024-06-09</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-6290</cvename>
       <cvename>CVE-2024-6291</cvename>
       <cvename>CVE-2024-6292</cvename>
       <cvename>CVE-2024-6293</cvename>
       <url>https://chromereleases.googleblog.com/2024/06/stable-channel-update-for-desktop_24.html</url>
     </references>
     <dates>
       <discovery>2024-06-24</discovery>
       <entry>2024-06-25</entry>
     </dates>
   </vuln>
 
   <vuln vid="4f6c4c07-3179-11ef-9da5-1c697a616631">
     <topic>emacs -- Arbitrary shell code evaluation vulnerability</topic>
     <affects>
       <package>
        <name>emacs</name>
        <name>emacs-canna</name>
        <name>emacs-nox</name>
        <name>emacs-wayland</name>
        <range><lt>29.3_3,3</lt></range>
       </package>
       <package>
        <name>emacs-devel</name>
        <name>emacs-devel-nox</name>
        <range><lt>30.0.50.20240615_1,3</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>GNU Emacs developers report:</p>
 	<blockquote cite="https://lists.gnu.org/archive/html/info-gnu-emacs/2024-06/msg00000.html">
 	  <p>Emacs 29.4 is an emergency bugfix release intended to fix a security vulnerability.  Arbitrary shell commands are no longer run when turning on Org mode in order to avoid running malicious code.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <url>https://seclists.org/oss-sec/2024/q2/296</url>
     </references>
     <dates>
       <discovery>2024-06-22</discovery>
       <entry>2024-06-23</entry>
     </dates>
   </vuln>
 
   <vuln vid="82830965-3073-11ef-a17d-5404a68ad561">
     <topic>traefik -- Azure Identity Libraries Elevation of Privilege Vulnerability</topic>
     <affects>
       <package>
 	<name>traefik</name>
 	<range><lt>2.11.5</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The traefik authors report:</p>
 	<blockquote cite="https://github.com/traefik/traefik/security/advisories/GHSA-rvj4-q8q5-8grf">
 		<p>There is a vulnerability in Azure Identity Libraries and
 		   Microsoft Authentication Library Elevation of Privilege Vulnerability.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-35255</cvename>
       <url>https://github.com/traefik/traefik/security/advisories/GHSA-rvj4-q8q5-8grf</url>
     </references>
     <dates>
       <discovery>2024-06-11</discovery>
       <entry>2024-06-22</entry>
     </dates>
   </vuln>
 
   <vuln vid="aa2b65e4-2f63-11ef-9cab-4ccc6adda413">
     <topic>qt5-webengine -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>qt5-webengine</name>
 	<range><lt>5.15.17.p2_1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<blockquote cite="https://code.qt.io/cgit/qt/qtwebengine-chromium.git/log/?h=87-based">
 	  <p>Backports for 5 security bugs in Chromium:</p>
 	  <ul>
 	    <li>CVE-2024-3837: Use after free in QUIC</li>
 	    <li>CVE-2024-3839: Out of bounds read in Fonts</li>
 	    <li>CVE-2024-3914: Use after free in V8</li>
 	    <li>CVE-2024-4058: Type confusion in ANGLE</li>
 	    <li>CVE-2024-4558: Use after free in ANGLE</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-3837</cvename>
       <cvename>CVE-2024-3839</cvename>
       <cvename>CVE-2024-3914</cvename>
       <cvename>CVE-2024-4058</cvename>
       <cvename>CVE-2024-4558</cvename>
       <url>https://code.qt.io/cgit/qt/qtwebengine-chromium.git/log/?h=87-based</url>
     </references>
     <dates>
       <discovery>2024-05-31</discovery>
       <entry>2024-06-20</entry>
     </dates>
   </vuln>
 
   <vuln vid="c5415838-2f52-11ef-9cab-4ccc6adda413">
     <topic>qt6-webengine -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>qt6-webengine</name>
 	<range><lt>6.7.2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Qt qtwebengine-chromium repo reports:</p>
 	<blockquote cite="https://code.qt.io/cgit/qt/qtwebengine-chromium.git/log/?h=118-based">
 	  <p>Backports for 7 security bugs in Chromium:</p>
 	  <ul>
 	    <li>CVE-2024-4948: Use after free in Dawn</li>
 	    <li>CVE-2024-5274: Type Confusion in V8</li>
 	    <li>CVE-2024-5493: Heap buffer overflow in WebRTC</li>
 	    <li>CVE-2024-5494: Use after free in Dawn</li>
 	    <li>CVE-2024-5495: Use after free in Dawn</li>
 	    <li>CVE-2024-5496: Use after free in Media Session</li>
 	    <li>CVE-2024-5499: Out of bounds write in Streams API</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-4948</cvename>
       <cvename>CVE-2024-5274</cvename>
       <cvename>CVE-2024-5493</cvename>
       <cvename>CVE-2024-5494</cvename>
       <cvename>CVE-2024-5495</cvename>
       <cvename>CVE-2024-5496</cvename>
       <cvename>CVE-2024-5499</cvename>
       <url>https://code.qt.io/cgit/qt/qtwebengine-chromium.git/log/?h=118-based</url>
     </references>
     <dates>
       <discovery>2024-05-31</discovery>
       <entry>2024-06-20</entry>
     </dates>
   </vuln>
 
   <vuln vid="142c538e-b18f-40a1-afac-c479effadd5c">
     <topic>openvpn -- two security fixes</topic>
     <affects>
       <package>
 	<name>openvpn</name>
 	<range><lt>2.6.11</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Gert Doering reports that OpenVPN 2.6.11 fixes two security bugs (three on Windows):</p>
 	<blockquote cite="https://github.com/OpenVPN/openvpn/blob/v2.6.11/Changes.rst#security-fixes">
 	  <p>CVE-2024-5594: control channel: refuse control channel messages with nonprintable characters in them. Security scope: a malicious openvpn peer can send garbage to openvpn log, or cause high CPU load. (Reynir Björnsson)</p>
 	  <p>CVE-2024-28882: only call schedule_exit() once (on a given peer). Security scope: an authenticated client can make the server "keep the session" even when the server has been told to disconnect this client. (Reynir Björnsson)</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-5594</cvename>
       <cvename>CVE-2024-28882</cvename>
       <url>https://github.com/OpenVPN/openvpn/blob/v2.6.11/Changes.rst#security-fixes</url>
     </references>
     <dates>
       <discovery>2024-05-16</discovery>
       <entry>2024-06-20</entry>
     </dates>
   </vuln>
 
   <vuln vid="007e7e77-2f06-11ef-8a0f-a8a1599412c6">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>126.0.6478.114</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>126.0.6478.114</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2024/06/stable-channel-update-for-desktop_18.html">
 	 <p>This update includes 6 security fixes:</p>
 	 <ul>
 	    <li>[344608204] High CVE-2024-6100: Type Confusion in V8. Reported by Seunghyun Lee (@0x10n) participating in SSD Secure Disclosure's TyphoonPWN 2024 on 2024-06-04</li>
 	    <li>[343748812] High CVE-2024-6101: Inappropriate implementation in WebAssembly. Reported by @ginggilBesel on 2024-05-31</li>
 	    <li>[339169163] High CVE-2024-6102: Out of bounds memory access in Dawn. Reported by wgslfuzz on 2024-05-07</li>
 	    <li>[344639860] High CVE-2024-6103: Use after free in Dawn. Reported by wgslfuzz on 2024-06-04</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-6100</cvename>
       <cvename>CVE-2024-6101</cvename>
       <cvename>CVE-2024-6102</cvename>
       <cvename>CVE-2024-6103</cvename>
       <url>https://chromereleases.googleblog.com/2024/06/stable-channel-update-for-desktop_18.html</url>
     </references>
     <dates>
       <discovery>2024-06-18</discovery>
       <entry>2024-06-20</entry>
     </dates>
   </vuln>
 
   <vuln vid="453aa0fc-2d91-11ef-8a0f-a8a1599412c6">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>126.0.6478.54</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>126.0.6478.54</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2024/06/stable-channel-update-for-desktop.html">
 	 <p>This update includes 21 security fixes:</p>
 	 <ul>
 	    <li>[342456991] High CVE-2024-5830: Type Confusion in V8. Reported by Man Yue Mo of GitHub Security Lab on 2024-05-24</li>
 	    <li>[339171223] High CVE-2024-5831: Use after free in Dawn. Reported by wgslfuzz on 2024-05-07</li>
 	    <li>[340196361] High CVE-2024-5832: Use after free in Dawn. Reported by wgslfuzz on 2024-05-13</li>
 	    <li>[342602616] High CVE-2024-5833: Type Confusion in V8. Reported by @ginggilBesel on 2024-05-24</li>
 	    <li>[342840932] High CVE-2024-5834: Inappropriate implementation in Dawn. Reported by gelatin dessert on 2024-05-26</li>
 	    <li>[341991535] High CVE-2024-5835: Heap buffer overflow in Tab Groups. Reported by Weipeng Jiang (@Krace) of VRI on 2024-05-22</li>
 	    <li>[341875171] High CVE-2024-5836: Inappropriate Implementation in DevTools. Reported by Allen Ding on 2024-05-21</li>
 	    <li>[342415789] High CVE-2024-5837: Type Confusion in V8. Reported by Anonymous on 2024-05-23</li>
 	    <li>[342522151] High CVE-2024-5838: Type Confusion in V8. Reported by Zhenghang Xiao (@Kipreyyy) on 2024-05-24</li>
 	    <li>[340122160] Medium CVE-2024-5839: Inappropriate Implementation in Memory Allocator. Reported by Micky on 2024-05-13</li>
 	    <li>[41492103] Medium CVE-2024-5840: Policy Bypass in CORS. Reported by Matt Howard on 2024-01-17</li>
 	    <li>[326765855] Medium CVE-2024-5841: Use after free in V8. Reported by Cassidy Kim(@cassidy6564) on 2024-02-26</li>
 	    <li>[40062622] Medium CVE-2024-5842: Use after free in Browser UI. Reported by Sven Dysthe (@svn_dy) on 2023-01-12</li>
 	    <li>[333940412] Medium CVE-2024-5843: Inappropriate implementation in Downloads. Reported by hjy79425575 on 2024-04-12</li>
 	    <li>[331960660] Medium CVE-2024-5844: Heap buffer overflow in Tab Strip. Reported by Sri on 2024-04-01</li>
 	    <li>[340178596] Medium CVE-2024-5845: Use after free in Audio. Reported by anonymous on 2024-05-13</li>
 	    <li>[341095523] Medium CVE-2024-5846: Use after free in PDFium. Reported by Han Zheng (HexHive) on 2024-05-16</li>
 	    <li>[341313077] Medium CVE-2024-5847: Use after free in PDFium. Reported by Han Zheng (HexHive) on 2024-05-18</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-5830</cvename>
       <cvename>CVE-2024-5831</cvename>
       <cvename>CVE-2024-5832</cvename>
       <cvename>CVE-2024-5833</cvename>
       <cvename>CVE-2024-5834</cvename>
       <cvename>CVE-2024-5835</cvename>
       <cvename>CVE-2024-5836</cvename>
       <cvename>CVE-2024-5837</cvename>
       <cvename>CVE-2024-5838</cvename>
       <cvename>CVE-2024-5839</cvename>
       <cvename>CVE-2024-5840</cvename>
       <cvename>CVE-2024-5841</cvename>
       <cvename>CVE-2024-5842</cvename>
       <cvename>CVE-2024-5843</cvename>
       <cvename>CVE-2024-5844</cvename>
       <cvename>CVE-2024-5845</cvename>
       <cvename>CVE-2024-5846</cvename>
       <cvename>CVE-2024-5847</cvename>
       <url>https://chromereleases.googleblog.com/2024/06/stable-channel-update-for-desktop.html</url>
     </references>
     <dates>
       <discovery>2024-06-11</discovery>
       <entry>2024-06-18</entry>
     </dates>
   </vuln>
 
   <vuln vid="f0ba7008-2bbd-11ef-b4ca-814a3d504243">
     <topic>forgejo -- multiple issues</topic>
     <affects>
       <package>
 	<name>forgejo</name>
 	<range><lt>7.0.4</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The forgejo team reports:</p>
 	<blockquote cite="https://codeberg.org/forgejo/forgejo/src/branch/forgejo/RELEASE-NOTES.md#7-0-4">
 	<p><a href="https://pkg.go.dev/vuln/GO-2024-2888">CVE-2024-24789</a>:
 	The archive/zip package's handling of certain types of invalid
 	zip files differs from the behavior of most zip implementations.
 	This misalignment could be exploited to create an zip file with
 	contents that vary depending on the implementation reading the
 	file.</p>
 	<p>The OAuth2 implementation does not always require authentication
 	for public clients, a requirement of RFC 6749 Section 10.2. A
 	malicious client can impersonate another client and obtain access
 	to protected resources if the impersonated client fails to, or is
 	unable to, keep its client credentials confidential.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-24789</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-24789</url>
     </references>
     <dates>
       <discovery>2024-04-04</discovery>
       <entry>2024-04-11</entry>
     </dates>
   </vuln>
 
   <vuln vid="219aaa1e-2aff-11ef-ab37-5404a68ad561">
     <topic>traefik -- Unexpected behavior with IPv4-mapped IPv6 addresses</topic>
     <affects>
       <package>
 	<name>traefik</name>
 	<range><lt>2.11.4</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The traefik authors report:</p>
 	<blockquote cite="https://github.com/traefik/traefik/security/advisories/GHSA-7jmw-8259-q9jx">
 	  <p>There is a vulnerability in Go managing various Is methods
 	     (IsPrivate, IsLoopback, etc) for IPv4-mapped IPv6 addresses.
 	     They didn't work as expected returning false for addresses
 	     which would return true in their traditional IPv4 forms.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-24790</cvename>
       <url>https://github.com/traefik/traefik/security/advisories/GHSA-7jmw-8259-q9jx</url>
     </references>
     <dates>
       <discovery>2024-06-05</discovery>
        <entry>2024-06-15</entry>
     </dates>
   </vuln>
 
   <vuln vid="a5c64f6f-2af3-11ef-a77e-901b0e9408dc">
     <topic>go -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>go122</name>
 	<range><lt>1.22.4</lt></range>
       </package>
       <package>
 	<name>go121</name>
 	<range><lt>1.21.11</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The Go project reports:</p>
 	<blockquote cite="https://go.dev/issue/66869">
 	  <p>archive/zip: mishandling of corrupt central directory record</p>
 	  <p>The archive/zip package's handling of certain types of
 	  invalid zip files differed from the behavior of most zip
 	  implementations. This misalignment could be exploited to
 	  create an zip file with contents that vary depending on the
 	  implementation reading the file. The archive/zip package now
 	  rejects files containing these errors.</p>
 	</blockquote>
 	<blockquote cite="https://go.dev/issue/67680">
 	  <p>net/netip: unexpected behavior from Is methods for
 	  IPv4-mapped IPv6 addresses</p>
 	  <p>The various Is methods (IsPrivate, IsLoopback, etc) did
 	  not work as expected for IPv4-mapped IPv6 addresses,
 	  returning false for addresses which would return true in
 	  their traditional IPv4 forms.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-24789</cvename>
       <cvename>CVE-2024-24790</cvename>
       <url>https://groups.google.com/g/golang-announce/c/XbxouI9gY7k/m/TuoGEhxIEwAJ</url>
     </references>
     <dates>
       <discovery>2024-06-04</discovery>
       <entry>2024-06-15</entry>
     </dates>
   </vuln>
 
   <vuln vid="92cd1c03-2940-11ef-bc02-001b217b3468">
     <topic>Gitlab -- Vulnerabilities</topic>
     <affects>
       <package>
 	<name>gitlab-ce</name>
 	<name>gitlab-ee</name>
 	<range><ge>17.0.0</ge><lt>17.0.2</lt></range>
 	<range><ge>16.11.0</ge><lt>16.11.4</lt></range>
 	<range><ge>5.1</ge><lt>16.10.7</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Gitlab reports:</p>
 	<blockquote cite="https://about.gitlab.com/releases/2024/06/12/patch-release-gitlab-17-0-2-released/">
 	  <p>ReDoS in gomod dependency linker</p>
 	  <p>ReDoS in CI interpolation (fix bypass)</p>
 	  <p>ReDoS in Asana integration issue mapping when webhook is called</p>
 	  <p>XSS and content injection when viewing raw XHTML files on iOS devices</p>
 	  <p>Missing agentk request validation could cause KAS to panic</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-1495</cvename>
       <cvename>CVE-2024-1736</cvename>
       <cvename>CVE-2024-1963</cvename>
       <cvename>CVE-2024-4201</cvename>
       <cvename>CVE-2024-5469</cvename>
       <url>https://about.gitlab.com/releases/2024/06/12/patch-release-gitlab-17-0-2-released/</url>
     </references>
     <dates>
       <discovery>2024-06-12</discovery>
       <entry>2024-06-13</entry>
     </dates>
   </vuln>
 
   <vuln vid="479df73e-2838-11ef-9cab-4ccc6adda413">
     <topic>plasma[56]-plasma-workspace -- Unauthorized users can access session manager</topic>
     <affects>
       <package>
 	<name>plasma5-plasma-workspace</name>
 	<range><lt>5.27.11.1</lt></range>
       </package>
       <package>
 	<name>plasma6-plasma-workspace</name>
 	<range><lt>6.0.4_2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>David Edmundson reports:</p>
 	<blockquote cite="https://kde.org/info/security/advisory-20240531-1.txt">
 	  <p>KSmserver, KDE's XSMP manager, incorrectly allows connections via ICE
 	    based purely on the host, allowing all local connections. This allows
 	    another user on the same machine to gain access to the session
 	    manager.</p>
 	  <p>A well crafted client could use the session restore feature to execute
 	    arbitrary code as the user on the next boot.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-36041</cvename>
       <url>https://kde.org/info/security/advisory-20240531-1.txt</url>
     </references>
     <dates>
       <discovery>2024-05-31</discovery>
       <entry>2024-06-11</entry>
     </dates>
   </vuln>
 
   <vuln vid="5f608c68-276c-11ef-8caa-0897988a1c07">
     <topic>Composer -- Multiple command injections via malicious git/hg branch names</topic>
     <affects>
       <package>
 	<name>php81-composer</name>
 	<range><lt>2.7.7</lt></range>
       </package>
       <package>
 	<name>php82-composer</name>
 	<range><lt>2.7.7</lt></range>
       </package>
       <package>
 	<name>php83-composer</name>
 	<range><lt>2.7.7</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Composer project reports:</p>
 	<blockquote cite="https://github.com/composer/composer/security/advisories/GHSA-47f6-5gq3-vx9c">
 	  <p>The status, reinstall and remove commands with packages
 	  installed from source via git containing specially crafted
 	  branch names in the repository can be used to execute
 	  code.</p>
 	</blockquote>
 	<blockquote cite="https://github.com/composer/composer/security/advisories/GHSA-v9qv-c7wm-wgmf">
 	  <p>The composer install command running inside a git/hg
 	  repository which has specially crafted branch names can
 	  lead to command injection. So this requires cloning
 	  untrusted repositories.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-35241</cvename>
       <url>https://github.com/composer/composer/security/advisories/GHSA-47f6-5gq3-vx9c</url>
       <cvename>CVE-2024-35242</cvename>
       <url>https://github.com/composer/composer/security/advisories/GHSA-v9qv-c7wm-wgmf</url>
     </references>
     <dates>
       <discovery>2024-06-10</discovery>
       <entry>2024-06-10</entry>
     </dates>
   </vuln>
 
   <vuln vid="91929399-249e-11ef-9296-b42e991fc52e">
     <topic>kanboard -- Project Takeover via IDOR in ProjectPermissionController</topic>
     <affects>
       <package>
 	<name>kanboard</name>
 	<range><lt>1.2.37</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security-advisories@github.com reports:</p>
 	<blockquote cite="https://github.com/kanboard/kanboard/commit/b6703688aac8187f5ea4d4d704fc7afeeffeafa7">
 	  <p>Kanboard is project management software that focuses on the Kanban
 	methodology.  The vuln is in app/Controller/ProjectPermissionController.php
 	function addUser().  The users permission to add users to a project
 	only get checked on the URL parameter project_id.  If the user is
 	authorized to add users to this project the request gets processed.
 	The users permission for the POST BODY parameter project_id does
 	not get checked again while processing.  An attacker with the
 	&apos;Project Manager&apos; on a single project may take over any
 	other project.  The vulnerability is fixed in 1.2.37.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-36399</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-36399</url>
     </references>
     <dates>
       <discovery>2024-06-06</discovery>
       <entry>2024-06-07</entry>
     </dates>
   </vuln>
 
   <vuln vid="14908bda-232b-11ef-b621-00155d645102">
     <topic>cyrus-imapd -- unbounded memory allocation</topic>
     <affects>
       <package>
 	<name>cyrus-imapd38</name>
 	<range><lt>3.8.2_1</lt></range>
       </package>
       <package>
 	<name>cyrus-imapd36</name>
 	<range><lt>3.6.4_1</lt></range>
       </package>
       <package>
 	<name>cyrus-imapd34</name>
 	<range><lt>3.4.7_1</lt></range>
       </package>
       <package>
 	<name>cyrus-imapd32</name>
 	<name>cyrus-imapd30</name>
 	<name>cyrus-imapd25</name>
 	<range><gt>0</gt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Cyrus IMAP 3.8.3 Release Notes states:</p>
 	<blockquote cite="https://www.cyrusimap.org/3.8/imap/download/release-notes/3.8/x/3.8.3.html">
 	  <p>Fixed CVE-2024-34055: Cyrus-IMAP through 3.8.2 and 3.10.0-beta2 allow authenticated attackers to cause unbounded memory allocation by sending many LITERALs in a single command.</p>
 	  <p>The IMAP protocol allows for command arguments to be LITERALs of negotiated length, and for these the server allocates memory to receive the content before instructing the client to proceed. The allocated memory is released when the whole command has been received and processed.</p>
 	  <p>The IMAP protocol has a number commands that specify an unlimited number of arguments, for example SEARCH. Each of these arguments can be a LITERAL, for which memory will be allocated and not released until the entire command has been received and processed. This can run a server out of memory, with varying consequences depending on the server's OOM policy.</p>
 	</blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-34055</cvename>
       <url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-34055</url>
     </references>
     <dates>
       <discovery>2024-04-30</discovery>
       <entry>2024-06-05</entry>
     </dates>
   </vuln>
 
   <vuln vid="b058380e-21a4-11ef-8a0f-a8a1599412c6">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>125.0.6422.141</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>125.0.6422.141</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2024/05/stable-channel-update-for-desktop_30.html">
 	 <p>This update includes 11 security fixes:</p>
 	 <ul>
 	    <li>[339877165] High CVE-2024-5493: Heap buffer overflow in WebRTC. Reported by Cassidy Kim(@cassidy6564) on 2024-05-11</li>
 	    <li>[338071106] High CVE-2024-5494: Use after free in Dawn. Reported by wgslfuzz on 2024-05-01</li>
 	    <li>[338103465] High CVE-2024-5495: Use after free in Dawn. Reported by wgslfuzz on 2024-05-01</li>
 	    <li>[338929744] High CVE-2024-5496: Use after free in Media Session. Reported by Cassidy Kim(@cassidy6564) on 2024-05-06</li>
 	    <li>[339061099] High CVE-2024-5497: Out of bounds memory access in Keyboard Inputs. Reported by zh1x1an1221 of Ant Group Tianqiong Security Lab on 2024-05-07</li>
 	    <li>[339588211] High CVE-2024-5498: Use after free in Presentation API. Reported by anymous on 2024-05-09</li>
 	    <li>[339877167] High CVE-2024-5499: Out of bounds write in Streams API. Reported by anonymous on 2024-05-11</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-5493</cvename>
       <cvename>CVE-2024-5494</cvename>
       <cvename>CVE-2024-5495</cvename>
       <cvename>CVE-2024-5496</cvename>
       <cvename>CVE-2024-5497</cvename>
       <cvename>CVE-2024-5498</cvename>
       <cvename>CVE-2024-5499</cvename>
       <url>https://chromereleases.googleblog.com/2024/05/stable-channel-update-for-desktop_30.html</url>
     </references>
     <dates>
       <discovery>2024-05-30</discovery>
       <entry>2024-06-03</entry>
     </dates>
   </vuln>
 
   <vuln vid="320a19f7-1ddd-11ef-a2ae-8c164567ca3c">
     <topic>nginx -- Multiple Vulnerabilities in HTTP/3</topic>
     <affects>
       <package>
 	<name>nginx-devel</name>
 	<range><ge>1.25.0</ge><lt>1.27.0</lt></range>
       </package>
       <package>
 	<name>nginx</name>
 	<range><ge>1.26.0</ge><lt>1.26.1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The nginx development team reports:</p>
 	<blockquote cite="http://nginx.org/en/security_advisories.html">
 	  <p>This update fixes the following vulnerabilities:</p>
 	  <ul>
 	    <li>Stack overflow and use-after-free in HTTP/3</li>
 	    <li>Buffer overwrite in HTTP/3</li>
 	    <li>Memory disclosure in HTTP/3</li>
 	    <li>NULL pointer dereference in HTTP/3</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-31079</cvename>
       <cvename>CVE-2024-32760</cvename>
       <cvename>CVE-2024-34161</cvename>
       <cvename>CVE-2024-35200</cvename>
     </references>
     <dates>
       <discovery>2024-05-29</discovery>
       <entry>2024-05-29</entry>
     </dates>
   </vuln>
 
   <vuln vid="6926d038-1db4-11ef-9f97-a8a1599412c6">
     <topic>chromium -- security fix</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>125.0.6422.112</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>125.0.6422.112</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2024/05/stable-channel-update-for-desktop_23.html">
 	 <p>This update includes 1 security fix:</p>
 	 <ul>
 	    <li>[341663589] High CVE-2024-5274: Type Confusion in V8. Reported by Clément Lecigne of Google's Threat Analysis Group and Brendon Tiszka of Chrome Security on 2024-05-20</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-5274</cvename>
       <url>https://chromereleases.googleblog.com/2024/05/stable-channel-update-for-desktop_23.html</url>
     </references>
     <dates>
       <discovery>2024-05-23</discovery>
       <entry>2024-05-29</entry>
     </dates>
   </vuln>
 
   <vuln vid="73a697d7-1d0f-11ef-a490-84a93843eb75">
     <topic>OpenSSL -- Use after free vulnerability</topic>
     <affects>
       <package>
 	<name>openssl</name>
 	<range><lt>3.0.13_5,1</lt></range>
       </package>
       <package>
 	<name>openssl31</name>
 	<range><lt>3.1.5_5</lt></range>
       </package>
       <package>
 	<name>openssl32</name>
 	<range><lt>3.2.1_5</lt></range>
       </package>
       <package>
 	<name>openssl33</name>
 	<range><lt>3.3.0_2</lt></range>
       </package>
       <package>
 	<name>openssl-quictls</name>
 	<range><lt>3.0.13_5</lt></range>
       </package>
       <package>
 	<name>openssl31-quictls</name>
 	<range><lt>3.1.5_5</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The OpenSSL project reports:</p>
 	<blockquote cite="https://www.openssl.org/news/secadv/20240528.txt">
 	  <p>Use After Free with SSL_free_buffers (low).</p>
 	  <p>Calling the OpenSSL API function SSL_free_buffers may cause
 	    memory to be accessed that was previously freed in some situations</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-4741</cvename>
       <url>https://www.openssl.org/news/secadv/20240528.txt</url>
     </references>
     <dates>
       <discovery>2024-05-28</discovery>
       <entry>2024-05-28</entry>
     </dates>
   </vuln>
 
   <vuln vid="04e78f32-04b2-4c23-bfae-72600842d317">
     <topic>electron29 -- use after free in Dawn</topic>
     <affects>
       <package>
 	<name>electron29</name>
 	<range><lt>29.4.1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Electron developers report:</p>
 	<blockquote cite="https://github.com/electron/electron/releases/tag/v29.4.1">
 	  <p>This update fixes the following vulnerability:</p>
 	  <ul>
 	    <li>Security: backported fix for CVE-2024-4948.</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-4948</cvename>
       <url>https://github.com/advisories/GHSA-xvp9-87cv-m4fv</url>
     </references>
     <dates>
       <discovery>2024-05-22</discovery>
       <entry>2024-05-25</entry>
     </dates>
   </vuln>
 
   <vuln vid="43d1c381-a3e5-4a1d-b3ed-f37b61a451af">
     <topic>electron28 -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>electron28</name>
 	<range><lt>28.3.2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Electron developers report:</p>
 	<blockquote cite="https://github.com/electron/electron/releases/tag/v28.3.2">
 	  <p>This update fixes the following vulnerabilities:</p>
 	  <ul>
 	    <li>Security: backported fix for CVE-2024-4948.</li>
 	    <li>Security: backported fix for CVE-2024-3914.</li>
 	    <li>Security: backported fix for CVE-2024-4060.</li>
 	    <li>Security: backported fix for CVE-2024-4058.</li>
 	    <li>Security: backported fix for CVE-2024-4558.</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-4948</cvename>
       <url>https://github.com/advisories/GHSA-xvp9-87cv-m4fv</url>
       <cvename>CVE-2024-3914</cvename>
       <url>https://github.com/advisories/GHSA-jv87-hfr8-8j2r</url>
       <cvename>CVE-2024-4060</cvename>
       <url>https://github.com/advisories/GHSA-4qw6-vwc8-mh38</url>
       <cvename>CVE-2024-4058</cvename>
       <url>https://github.com/advisories/GHSA-23rw-79p3-xgcm</url>
       <cvename>CVE-2024-4558</cvename>
       <url>https://github.com/advisories/GHSA-r4j8-j63p-24j8</url>
     </references>
     <dates>
       <discovery>2024-05-22</discovery>
       <entry>2024-05-25</entry>
     </dates>
   </vuln>
 
   <vuln vid="f5fa174d-19de-11ef-83d8-4ccc6adda413">
     <topic>QtNetworkAuth -- predictable seeding of PRNG in QAbstractOAuth</topic>
     <affects>
       <package>
 	<name>qt5-networkauth</name>
 	<range><lt>5.15.13_1</lt></range>
       </package>
       <package>
 	<name>qt6-networkauth</name>
 	<range><lt>6.7.1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Andy Shaw reports:</p>
 	<blockquote cite="https://www.qt.io/blog/security-advisory-qstringconverter-0">
 	  <p>The OAuth1 implementation in QtNetworkAuth created nonces using
 	    a PRNG that was seeded with a predictable seed.</p>
 	  <p>This means that an attacker that can somehow control the time of
 	    the first OAuth1 flow of the process has a high chance of predicting
 	    the nonce used in said OAuth flow.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-36048</cvename>
       <url>https://www.qt.io/blog/security-advisory-qstringconverter-0</url>
       <url>https://codereview.qt-project.org/c/qt/qtnetworkauth/+/560317</url>
     </references>
     <dates>
       <discovery>2024-05-08</discovery>
       <entry>2024-05-24</entry>
     </dates>
   </vuln>
 
   <vuln vid="f848ef90-1848-11ef-9850-001b217b3468">
     <topic>Gitlab -- Vulnerabilities</topic>
     <affects>
       <package>
 	<name>gitlab-ce</name>
 	<name>gitlab-ee</name>
 	<range><ge>17.0.0</ge><lt>17.0.1</lt></range>
 	<range><ge>16.11.0</ge><lt>16.11.3</lt></range>
 	<range><ge>11.11</ge><lt>16.10.6</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Gitlab reports:</p>
 	<blockquote cite="https://about.gitlab.com/releases/2024/05/22/patch-release-gitlab-17-0-1-released/">
 	  <p>1-click account takeover via XSS in the code editor in gitlab.com</p>
 	  <p>A DOS vulnerability in the 'description' field of the runner</p>
 	  <p>CSRF via K8s cluster-integration</p>
 	  <p>Using Set Pipeline Status of a Commit API incorrectly create a new pipeline when SHA and pipeline_id did not match</p>
 	  <p>Redos on wiki render API/Page</p>
 	  <p>Resource exhaustion and denial of service with test_report API calls</p>
 	  <p>Guest user can view dependency lists of private projects through job artifacts</p>
 	  <p>Stored XSS via PDFjs</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-4835</cvename>
       <cvename>CVE-2024-2874</cvename>
       <cvename>CVE-2023-7045</cvename>
       <cvename>CVE-2023-6502</cvename>
       <cvename>CVE-2024-1947</cvename>
       <cvename>CVE-2024-4367</cvename>
       <url>https://about.gitlab.com/releases/2024/05/22/patch-release-gitlab-17-0-1-released/</url>
     </references>
     <dates>
       <discovery>2024-05-22</discovery>
       <entry>2024-05-22</entry>
     </dates>
   </vuln>
 
   <vuln vid="8247af0d-183b-11ef-9f97-a8a1599412c6">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>125.0.6422.76</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>125.0.6422.76</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2024/05/stable-channel-update-for-desktop_21.html">
 	 <p>This update includes 15 security fixes:</p>
 	 <ul>
 	    <li>[336012573] High CVE-2024-5157: Use after free in Scheduling. Reported by Looben Yang on 2024-04-21</li>
 	    <li>[338908243] High CVE-2024-5158: Type Confusion in V8. Reported by Zhenghang Xiao (@Kipreyyy) on 2024-05-06</li>
 	    <li>[335613092] High CVE-2024-5159: Heap buffer overflow in ANGLE. Reported by David Sievers (@loknop) on 2024-04-18</li>
 	    <li>[338161969] High CVE-2024-5160: Heap buffer overflow in Dawn. Reported by wgslfuzz on 2024-05-01</li>
 	    <li>[340221135] High CVE-2024-4947: Type Confusion in V8. Reported by Vasily Berdnikov (@vaber_b) and Boris Larin (@oct0xor) of Kaspersky on 2024-05-13</li>
 	    <li>[333414294] High CVE-2024-4948: Use after free in Dawn. Reported by wgslfuzz on 2024-04-09</li>
 	    <li>[326607001] Medium CVE-2024-4949: Use after free in V8. Reported by Ganjiang Zhou(@refrain_areu) of ChaMd5-H1 team on 2024-02-24</li>
 	    <li>[40065403] Low CVE-2024-4950: Inappropriate implementation in Downloads. Reported by Shaheen Fazim on 2023-06-06</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-5157</cvename>
       <cvename>CVE-2024-5158</cvename>
       <cvename>CVE-2024-5159</cvename>
       <cvename>CVE-2024-5160</cvename>
       <cvename>CVE-2024-4947</cvename>
       <cvename>CVE-2024-4948</cvename>
       <cvename>CVE-2024-4949</cvename>
       <cvename>CVE-2024-4950</cvename>
       <url>https://chromereleases.googleblog.com/2024/05/stable-channel-update-for-desktop_21.html</url>
     </references>
     <dates>
       <discovery>2024-05-21</discovery>
       <entry>2024-05-22</entry>
     </dates>
   </vuln>
 
   <vuln vid="9bcff2c4-1779-11ef-b489-b42e991fc52e">
     <topic>Openfire administration console authentication bypass</topic>
     <affects>
       <package>
 	<name>openfire</name>
 	<range><lt>4.6.8</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security-advisories@github.com reports:</p>
 	<blockquote cite="http://packetstormsecurity.com/files/173607/Openfire-Authentication-Bypass-Remote-Code-Execution.html">
 	  <p>Openfire&apos;s administrative console, a web-based
 	application, was found to be vulnerable to a path traversal attack
 	via the setup environment.  This permitted an unauthenticated user
 	to use the unauthenticated Openfire Setup Environment in an already
 	configured Openfire environment to access restricted pages in the
 	Openfire Admin Console reserved for administrative users.  This
 	vulnerability affects all versions of Openfire that have been
 	released since April 2015, starting with version 3.10.0.  The problem
 	has been patched in Openfire release 4.7.5 and 4.6.8, and further
 	improvements will be included in the yet-to-be released first version
 	on the 4.8 branch (which is expected to be version 4.8.0).  Users
 	are advised to upgrade.  If an Openfire upgrade isnt available for
 	a specific release, or isnt quickly actionable, users may see the
 	linked github advisory (GHSA-gw42-f939-fhvm) for mitigation advice.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-32315</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2023-32315</url>
     </references>
     <dates>
       <discovery>2023-05-26</discovery>
       <entry>2024-05-21</entry>
     </dates>
   </vuln>
 
   <vuln vid="e020b0fd-1751-11ef-a490-84a93843eb75">
     <topic>Roundcube -- Cross-site scripting vulnerabilities</topic>
     <affects>
       <package>
 	<name>roundcube</name>
 	<range><lt>1.6.7,1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The Roundcube project reports:</p>
 	<blockquote cite="https://roundcube.net/news/2024/05/19/security-updates-1.6.7-and-1.5.7">
 	  <p>cross-site scripting (XSS) vulnerability in handling SVG
 	    animate attributes.</p>
 	  <p>cross-site scripting (XSS) vulnerability in handling list
 	    columns from user preferences.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <url>https://roundcube.net/news/2024/05/19/security-updates-1.6.7-and-1.5.7</url>
     </references>
     <dates>
       <discovery>2024-05-19</discovery>
       <entry>2024-05-21</entry>
     </dates>
   </vuln>
 
   <vuln vid="d58455cc-159e-11ef-83d8-4ccc6adda413">
     <topic>qt5-webengine -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>qt5-webengine</name>
 	<range><lt>5.15.16.p9_2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<blockquote cite="https://code.qt.io/cgit/qt/qtwebengine-chromium.git/log/?h=87-based">
 	  <p>Backports for 2 security bugs in Chromium:</p>
 	  <ul>
 	    <li>CVE-2024-3157: Out of bounds write in Compositing</li>
 	    <li>CVE-2024-3516: Heap buffer overflow in ANGLE</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-3157</cvename>
       <cvename>CVE-2024-3516</cvename>
       <url>https://code.qt.io/cgit/qt/qtwebengine-chromium.git/log/?h=87-based</url>
     </references>
     <dates>
       <discovery>2024-04-16</discovery>
       <entry>2024-05-19</entry>
     </dates>
   </vuln>
 
   <vuln vid="f393b5a7-1535-11ef-8064-c5610a6efffb">
     <topic>Arti -- Security issues related to circuit construction</topic>
     <affects>
       <package>
 	<name>arti</name>
 	<range><lt>1.2.3</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Tor Project reports:</p>
 	<blockquote cite="https://blog.torproject.org/arti_1_2_3_released/">
 		<p>
 			When building anonymizing circuits to or from an onion
 			service with 'lite' vanguards (the default) enabled, the
 			circuit manager code would build the circuits with one
 			hop too few.
 		</p>
 		<p>
 			When 'full' vanguards are enabled, some circuits are
 			supposed to be built with an extra hop to minimize the
 			linkability of the guard nodes. In some circumstances,
 			the circuit manager would build circuits with one hop
 			too few, making it easier for an adversary to discover
 			the L2 and L3 guards of the affected clients and
 			services.
 		</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-35313</cvename>
       <url>https://gitlab.torproject.org/tpo/core/arti/-/issues/1400</url>
       <cvename>CVE-2024-35312</cvename>
       <url>https://gitlab.torproject.org/tpo/core/arti/-/issues/1409</url>
     </references>
     <dates>
       <discovery>2024-05-14</discovery>
       <entry>2024-05-18</entry>
     </dates>
   </vuln>
 
   <vuln vid="b88aa380-1442-11ef-a490-84a93843eb75">
     <topic>OpenSSL -- Denial of Service vulnerability</topic>
     <affects>
       <package>
 	<name>openssl</name>
 	<range><lt>3.0.13_4,1</lt></range>
       </package>
       <package>
 	<name>openssl31</name>
 	<range><lt>3.1.5_4</lt></range>
       </package>
       <package>
 	<name>openssl32</name>
 	<range><lt>3.2.1_4</lt></range>
       </package>
       <package>
 	<name>openssl33</name>
 	<range><lt>3.3.0_1</lt></range>
       </package>
       <package>
 	<name>openssl-quictls</name>
 	<range><lt>3.0.13_4</lt></range>
       </package>
       <package>
 	<name>openssl31-quictls</name>
 	<range><lt>3.1.5_4</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The OpenSSL project reports:</p>
 	<blockquote cite="https://www.openssl.org/news/secadv/20240516.txt">
 	  <p>Excessive time spent checking DSA keys and parameters (Low)</p>
 	  <p>Checking excessively long DSA keys or parameters may be very
 	    slow.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-4603</cvename>
       <url>https://www.openssl.org/news/secadv/20240516.txt</url>
     </references>
     <dates>
       <discovery>2024-05-16</discovery>
       <entry>2024-05-17</entry>
     </dates>
   </vuln>
 
   <vuln vid="a431676c-f86c-4371-b48a-b7d2b0bec3a3">
     <topic>electron29 -- setuid() does not affect libuv's internal io_uring</topic>
     <affects>
       <package>
 	<name>electron29</name>
 	<range><lt>29.4.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Electron developers report:</p>
 	<blockquote cite="https://github.com/electron/electron/releases/tag/v29.4.0">
 	  <p>This update fixes the following vulnerability:</p>
 	  <ul>
 	    <li>Backported fix for CVE-2024-22017.</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-22017</cvename>
       <url>https://github.com/advisories/GHSA-vr4q-vx84-9g5x</url>
     </references>
     <dates>
       <discovery>2024-05-15</discovery>
       <entry>2024-05-17</entry>
     </dates>
   </vuln>
 
   <vuln vid="c6f03ea6-12de-11ef-83d8-4ccc6adda413">
     <topic>qt6-webengine -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>qt6-webengine</name>
 	<range><lt>6.7.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Qt qtwebengine-chromium repo reports:</p>
 	<blockquote cite="https://code.qt.io/cgit/qt/qtwebengine-chromium.git/log/?h=118-based">
 	  <p>Backports for 16 security bugs in Chromium:</p>
 	  <ul>
 	    <li>CVE-2024-2625: Object lifecycle issue in V8</li>
 	    <li>CVE-2024-2626: Out of bounds read in Swiftshader</li>
 	    <li>CVE-2024-2885: Use after free in Dawn</li>
 	    <li>CVE-2024-2887: Type Confusion in WebAssembly</li>
 	    <li>CVE-2024-3157: Out of bounds write in Compositing</li>
 	    <li>CVE-2024-3159: Out of bounds memory access in V8</li>
 	    <li>CVE-2024-3516: Heap buffer overflow in ANGLE</li>
 	    <li>CVE-2024-3837: Use after free in QUIC</li>
 	    <li>CVE-2024-3839: Out of bounds read in Fonts</li>
 	    <li>CVE-2024-3914: Use after free in V8</li>
 	    <li>CVE-2024-3840: Insufficient policy enforcement in Site Isolation</li>
 	    <li>CVE-2024-4058: Type Confusion in ANGLE</li>
 	    <li>CVE-2024-4060: Use after free in Dawn</li>
 	    <li>CVE-2024-4331: Use after free in Picture In Picture</li>
 	    <li>CVE-2024-4368: Use after free in Dawn</li>
 	    <li>CVE-2024-4671: Use after free in Visuals</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-2625</cvename>
       <cvename>CVE-2024-2626</cvename>
       <cvename>CVE-2024-2885</cvename>
       <cvename>CVE-2024-2887</cvename>
       <cvename>CVE-2024-3157</cvename>
       <cvename>CVE-2024-3159</cvename>
       <cvename>CVE-2024-3516</cvename>
       <cvename>CVE-2024-3837</cvename>
       <cvename>CVE-2024-3839</cvename>
       <cvename>CVE-2024-3914</cvename>
       <cvename>CVE-2024-3840</cvename>
       <cvename>CVE-2024-4058</cvename>
       <cvename>CVE-2024-4060</cvename>
       <cvename>CVE-2024-4331</cvename>
       <cvename>CVE-2024-4368</cvename>
       <cvename>CVE-2024-4671</cvename>
       <url>https://code.qt.io/cgit/qt/qtwebengine-chromium.git/log/?h=118-based</url>
     </references>
     <dates>
       <discovery>2024-04-03</discovery>
       <entry>2024-05-15</entry>
     </dates>
   </vuln>
 
   <vuln vid="e79cc4e2-12d7-11ef-83d8-4ccc6adda413">
     <topic>qt6-base (core module) -- Invalid pointer in QStringConverter</topic>
     <affects>
       <package>
 	<name>qt6-base</name>
 	<range><ge>6.5.0</ge><le>6.5.5</le></range>
 	<range><ge>6.6.0</ge><lt>6.7.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Andy Shaw reports:</p>
 	<blockquote cite="https://www.qt.io/blog/security-advisory-qstringconverter">
 	  <p>QStringConverter has an invalid pointer being passed as a callback
 	    which can allow modification of the stack. Qt itself is not vulnerable
 	    to remote attack however an application using QStringDecoder either
 	    directly or indirectly can be vulnerable.</p>
 	  <p>This requires:</p>
 	  <ol>
 	    <li>the attacker be able to tell the application a specific codec to use</li>
 	    <li>the attacker be able to feed the application data in a specific way to cause the desired modification</li>
 	    <li>the attacker what in the stack will get modified, which requires knowing the build of the application (and not all builds will be vulnerable)</li>
 	    <li>the modification do anything in particular that is useful to the attacker, besides maybe crashing the application</li>
 	  </ol>
 	  <p>Qt does not automatically use any of those codecs, so this needs the application
 	    to implement something using QStringDecoder to be vulnerable.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-33861</cvename>
       <url>https://www.qt.io/blog/security-advisory-qstringconverter</url>
     </references>
     <dates>
       <discovery>2024-05-02</discovery>
       <entry>2024-05-15</entry>
     </dates>
   </vuln>
 
   <vuln vid="f2d8342f-1134-11ef-8791-6805ca2fa271">
     <topic>dnsdist -- Transfer requests received over DoH can lead to a denial of service</topic>
     <affects>
       <package>
 	<name>dnsdist</name>
 	<range><lt>1.9.4</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>PowerDNS Security Advisory reports:</p>
 	<blockquote cite="https://dnsdist.org/security-advisories/index.html">
 	  <p>When incoming DNS over HTTPS support is enabled using the nghttp2 provider,
 	    and queries are routed to a tcp-only or DNS over TLS backend, an attacker can
 	    trigger an assertion failure in DNSdist by sending a request for a zone transfer (AXFR
 	    or IXFR) over DNS over HTTPS, causing the process to stop and thus leading to a
 	    Denial of Service. DNS over HTTPS is not enabled by default, and backends are using
 	    plain DNS (Do53) by default.
 	  </p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-25581</cvename>
       <url>https://dnsdist.org/security-advisories/powerdns-advisory-for-dnsdist-2024-03.html</url>
     </references>
     <dates>
       <discovery>2024-05-13</discovery>
       <entry>2024-05-13</entry>
     </dates>
   </vuln>
 
   <vuln vid="5afd64ae-122a-11ef-8eed-1c697a616631">
     <topic>Intel CPUs -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>cpu-microcode-intel</name>
 	<range><lt>20240514</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Intel reports:</p>
 	<blockquote cite="https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01036.html">
 	 <p>
 	  Potential security vulnerabilities in some Intel Trust Domain
 	  Extensions (TDX) module software may allow escalation of
 	  privilege. Improper input validation in some Intel TDX module
 	  software before version 1.5.05.46.698 may allow a privileged user to
 	  potentially enable escalation of privilege via local access.  Intel
 	  is releasing firmware updates to mitigate these potential
 	  vulnerabilities.
 	 </p>
 	</blockquote>
 	<blockquote cite="https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01051.html">
 	 <p>
 	  A potential security vulnerability in some Intel Processors may
 	  allow information disclosure.  Hardware logic contains race
 	  conditions in some Intel Processors that may allow an authenticated
 	  user to potentially enable partial information disclosure via local
 	  access. Intel is releasing microcode updates to mitigate this
 	  potential vulnerability.
 	 </p>
 	</blockquote>
 	<blockquote cite="https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01052.html">
 	 <p>
 	  A potential security vulnerability in Intel Core Ultra Processors
 	  may allow denial of service.  Sequence of processor instructions
 	  leads to unexpected behavior in Intel Core Ultra Processors may
 	  allow an authenticated user to potentially enable denial of service
 	  via local access.  Intel is releasing microcode updates to mitigate
 	  this potential vulnerability.
 	 </p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-45745</cvename>
       <cvename>CVE-2023-45733</cvename>
       <cvename>CVE-2023-46103</cvename>
       <url>https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases/tag/microcode-20240514</url>
     </references>
     <dates>
       <discovery>2024-05-14</discovery>
       <entry>2024-05-14</entry>
     </dates>
   </vuln>
 
   <vuln vid="8e0e8b56-11c6-11ef-9f97-a8a1599412c6">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>124.0.6367.207</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>124.0.6367.207</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2024/05/stable-channel-update-for-desktop_13.html">
 	 <p>This update includes 1 security fix:</p>
 	 <ul>
 	    <li>[339458194] High CVE-2024-4761: Out of bounds write in V8. Reported by Anonymous on 2024-05-09</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-4761</cvename>
       <url>https://chromereleases.googleblog.com/2024/05/stable-channel-update-for-desktop_13.html</url>
     </references>
     <dates>
       <discovery>2024-05-13</discovery>
       <entry>2024-05-14</entry>
     </dates>
   </vuln>
 
   <vuln vid="d3847eba-114b-11ef-9c21-901b0e9408dc">
     <topic>go -- net: malformed DNS message can cause infinite loop</topic>
     <affects>
       <package>
 	<name>go122</name>
 	<range><lt>1.22.3</lt></range>
       </package>
       <package>
 	<name>go121</name>
 	<range><lt>1.21.10</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The Go project reports:</p>
 	<blockquote cite="https://go.dev/issue/66754">
 	  <p>net: malformed DNS message can cause infinite loop</p>
 	  <p>A malformed DNS message in response to a query can cause
 	  the Lookup functions to get stuck in an infinite loop.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-24788</cvename>
       <url>https://go.dev/issue/66754</url>
     </references>
     <dates>
       <discovery>2024-04-25</discovery>
       <entry>2024-05-13</entry>
     </dates>
   </vuln>
 
   <vuln vid="3cf8ea44-1029-11ef-9f97-a8a1599412c6">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>124.0.6367.201</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>124.0.6367.201</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2024/05/stable-channel-update-for-desktop_9.html">
 	 <p>This update includes 1 security fix:</p>
 	 <ul>
 	    <li>[339266700] High CVE-2024-4671: Use after free in Visuals. Reported by Anonymous on 2024-05-07</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-4671</cvename>
       <url>https://chromereleases.googleblog.com/2024/05/stable-channel-update-for-desktop_9.html</url>
     </references>
     <dates>
       <discovery>2024-05-09</discovery>
       <entry>2024-05-12</entry>
     </dates>
   </vuln>
 
   <vuln vid="d53c30c1-0d7b-11ef-ba02-6cc21735f730">
     <topic>PostgreSQL server -- Potentially allowing authenicated database users to see data that they shouldn't.</topic>
     <affects>
       <package>
 	<name>postgresql-server</name>
 	<range><lt>16.3</lt></range>
 	<range><lt>15.7</lt></range>
 	<range><lt>14.12</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>PostgreSQL project reports:</p>
 	<blockquote cite="https://www.postgresql.org/support/security/CVE-2024-4317/">
 	  <p>
 	    A security vulnerability was found in the system views pg_stats_ext
 	    and pg_stats_ext_exprs, potentially allowing authenticated database
 	    users to see data they shouldn't.  If this is of concern in your
 	    installation, run the SQL script /usr/local/share/postgresql/fix-CVE-2024-4317.sql
 	    for each of your databases. See the link for details.
 	  </p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-4317</cvename>
       <url>https://www.postgresql.org/support/security/CVE-2024-4317/</url>
     </references>
     <dates>
       <discovery>2024-05-09</discovery>
       <entry>2024-05-09</entry>
     </dates>
   </vuln>
 
   <vuln vid="ee6936da-0ddd-11ef-9c21-901b0e9408dc">
     <topic>tailscale -- Insufficient inbound packet filtering in subnet routers and exit nodes</topic>
     <affects>
       <package>
 	<name>tailscale</name>
 	<range><lt>1.66.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Tailscale team reports:</p>
 	<blockquote cite="https://tailscale.com/security-bulletins#ts-2024-005">
 	  <p>In Tailscale versions earlier than 1.66.0, exit nodes,
 	  subnet routers, and app connectors, could allow inbound
 	  connections to other tailnet nodes from their local area
 	  network (LAN). This vulnerability only affects Linux exit
 	  nodes, subnet routers, and app connectors in tailnets where
 	  ACLs allow "src": "*", such as with default ACLs.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <url>https://tailscale.com/security-bulletins#ts-2024-005</url>
     </references>
     <dates>
       <discovery>2024-05-08</discovery>
       <entry>2024-05-09</entry>
     </dates>
   </vuln>
 
   <vuln vid="ec994672-5284-49a5-a7fc-93c02126e5fb">
     <topic>electron29 -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>electron29</name>
 	<range><lt>29.3.3</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Electron developers report:</p>
 	<blockquote cite="https://github.com/electron/electron/releases/tag/v29.3.3">
 	  <p>This update fixes the following vulnerabilities:</p>
 	  <ul>
 	    <li>Security: backported fix for CVE-2024-3914.</li>
 	    <li>Security: backported fix for CVE-2024-4558.</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-3914</cvename>
       <url>https://github.com/advisories/GHSA-jv87-hfr8-8j2r</url>
       <cvename>CVE-2024-4558</cvename>
       <url>https://github.com/advisories/GHSA-r4j8-j63p-24j8</url>
     </references>
     <dates>
       <discovery>2024-05-09</discovery>
       <entry>2024-05-09</entry>
     </dates>
   </vuln>
 
   <vuln vid="fbc2c629-0dc5-11ef-9850-001b217b3468">
     <topic>Gitlab -- vulnerabilities</topic>
     <affects>
       <package>
 	<name>gitlab-ce</name>
 	<name>gitlab-ee</name>
 	<range><ge>16.11.0</ge><lt>16.11.2</lt></range>
 	<range><ge>16.10.0</ge><lt>16.10.5</lt></range>
 	<range><ge>10.6.0</ge><lt>16.9.7</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Gitlab reports:</p>
 	<blockquote cite="https://about.gitlab.com/releases/2024/05/08/patch-release-gitlab-16-11-2-released/">
 	  <p>ReDoS in branch search when using wildcards</p>
 	  <p>ReDoS in markdown render pipeline</p>
 	  <p>Redos on Discord integrations</p>
 	  <p>Redos on Google Chat Integration</p>
 	  <p>Denial of Service Attack via Pin Menu</p>
 	  <p>DoS by filtering tags and branches via the API</p>
 	  <p>MR approval via CSRF in SAML SSO</p>
 	  <p>Banned user from groups can read issues updates via the api</p>
 	  <p>Require confirmation before linking JWT identity</p>
 	  <p>View confidential issues title and description of any public project via export</p>
 	  <p>SSRF via Github importer</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-2878</cvename>
       <cvename>CVE-2024-2651</cvename>
       <cvename>CVE-2023-6682</cvename>
       <cvename>CVE-2023-6688</cvename>
       <cvename>CVE-2024-2454</cvename>
       <cvename>CVE-2024-4539</cvename>
       <cvename>CVE-2024-4597</cvename>
       <cvename>CVE-2024-1539</cvename>
       <cvename>CVE-2024-1211</cvename>
       <cvename>CVE-2024-3976</cvename>
       <cvename>CVE-2023-6195</cvename>
       <url>https://about.gitlab.com/releases/2024/05/08/patch-release-gitlab-16-11-2-released/</url>
     </references>
     <dates>
       <discovery>2024-05-08</discovery>
       <entry>2024-05-09</entry>
     </dates>
   </vuln>
 
   <vuln vid="059a99a9-45e0-492b-b9f9-5a79573c8eb6">
     <topic>electron29 -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>electron29</name>
 	<range><lt>29.3.2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Electron developers report:</p>
 	<blockquote cite="https://github.com/electron/electron/releases/tag/v29.3.2">
 	  <p>This update fixes the following vulnerabilities:</p>
 	  <ul>
 	    <li>Security: backported fix for CVE-2024-4060.</li>
 	    <li>Security: backported fix for CVE-2024-4058.</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-4060</cvename>
       <url>https://github.com/advisories/GHSA-4qw6-vwc8-mh38</url>
       <cvename>CVE-2024-4058</cvename>
       <url>https://github.com/advisories/GHSA-23rw-79p3-xgcm</url>
     </references>
     <dates>
       <discovery>2024-05-03</discovery>
       <entry>2024-05-08</entry>
     </dates>
   </vuln>
 
   <vuln vid="f69415aa-086e-11ef-9f97-a8a1599412c6">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>124.0.6367.118</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>124.0.6367.118</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2024/04/stable-channel-update-for-desktop_30.html">
 	 <p>This update includes 2 security fixes:</p>
 	 <ul>
 	    <li>[335003891] High CVE-2024-4331: Use after free in Picture In Picture. Reported by Zhenghang Xiao (@Kipreyyy) on 2024-04-16</li>
 	    <li>[333508731] High CVE-2024-4368: Use after free in Dawn. Reported by wgslfuzz on 2024-04-09</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-4058</cvename>
       <cvename>CVE-2024-4059</cvename>
       <cvename>CVE-2024-4060</cvename>
       <url>https://chromereleases.googleblog.com/2024/04/stable-channel-update-for-desktop_30.html</url>
     </references>
     <dates>
       <discovery>2024-04-30</discovery>
       <entry>2024-05-02</entry>
     </dates>
   </vuln>
 
   <vuln vid="4a1e2bad-0836-11ef-9fd2-1c697a616631">
     <topic>R -- arbitrary code execution vulnerability</topic>
     <affects>
       <package>
 	<name>R</name>
 	<range><lt>4.4.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>HiddenLayer Research reports:</p>
 	<blockquote cite="https://hiddenlayer.com/research/r-bitrary-code-execution/">
 	  <p>Deserialization of untrusted data can occur in the R statistical programming language, enabling a maliciously crafted RDS (R Data Serialization) formatted file or R package to run arbitrary code on an end user's system.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-27322</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-27322</url>
     </references>
     <dates>
       <discovery>2024-04-29</discovery>
       <entry>2024-05-02</entry>
     </dates>
   </vuln>
 
   <vuln vid="da4adc02-07f4-11ef-960d-5404a68ad561">
     <topic>hcode -- buffer overflow in mail.c</topic>
     <affects>
       <package>
 	<name>ko-hcode</name>
 	<range><lt>2.1.3_2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The openSUSE project reports:</p>
 	<blockquote cite="https://bugzilla.suse.com/show_bug.cgi?id=1223534">
 	  <p>The problematic function in question is putSDN() in mail.c. The static variable `cp` is used as an index for a fixed-sized buffer `ibuf`. There is a range check: `if ( cp >= HDR_BUF_LEN ) ...` but under certain circumstances, cp can be incremented beyond the buffer size, leading to a buffer overwrite</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-34020</cvename>
       <url>https://bugzilla.suse.com/show_bug.cgi?id=1223534</url>
     </references>
     <dates>
       <discovery>2024-04-29</discovery>
       <entry>2024-05-01</entry>
     </dates>
   </vuln>
 
   <vuln vid="5da8b1e6-0591-11ef-9e00-080027957747">
     <topic>GLPI -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>glpi</name>
 	<range><lt>10.0.15,1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>GLPI team reports:</p>
 	<blockquote cite="https://github.com/glpi-project/glpi/releases/tag/10.0.15">
 	  <p>GLPI 10.0.15 Changelog</p>
 	  <ul>
 	    <li>[SECURITY - high] Authenticated SQL injection from map search (CVE-2024-31456)</li>
 	    <li>[SECURITY - high] Account takeover via SQL Injection in saved searches feature (CVE-2024-29889)</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-31456</cvename>
       <cvename>CVE-2024-29889</cvename>
       <url>https://github.com/glpi-project/glpi/releases/tag/10.0.15</url>
     </references>
     <dates>
       <discovery>2024-04-03</discovery>
       <entry>2024-04-28</entry>
     </dates>
   </vuln>
 
   <vuln vid="b3affee8-04d1-11ef-8928-901b0ef714d4">
     <topic>py-social-auth-app-django -- Improper Handling of Case Sensitivity</topic>
     <affects>
       <package>
 	<name>py38-social-auth-app-django</name>
 	<name>py39-social-auth-app-django</name>
 	<name>py310-social-auth-app-django</name>
 	<name>py311-social-auth-app-django</name>
 	<range><lt>5.4.1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>GitHub Advisory Database:</p>
 	<blockquote cite="https://nvd.nist.gov/vuln/detail/CVE-2024-32879">
 	  <p>Python Social Auth is a social authentication/registration mechanism. Prior to version 5.4.1, due to default case-insensitive collation in MySQL or MariaDB databases, third-party authentication user IDs are not case-sensitive and could cause different IDs to match. This issue has been addressed by a fix released in version 5.4.1. An immediate workaround would be to change collation of the affected field.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-32879</cvename>
       <url>https://github.com/python-social-auth/social-app-django/security/advisories/GHSA-2gr8-3wc7-xhj3</url>
     </references>
     <dates>
       <discovery>2024-04-24</discovery>
       <entry>2024-04-28</entry>
     </dates>
   </vuln>
 
   <vuln vid="7a42852d-0347-11ef-9f97-a8a1599412c6">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>124.0.6367.78</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>124.0.6367.78</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2024/04/stable-channel-update-for-desktop_24.html">
 	 <p>This update includes 4 security fixes:</p>
 	 <ul>
 	    <li>[332546345] Critical CVE-2024-4058: Type Confusion in ANGLE. Reported by Toan (suto) Pham and Bao (zx) Pham of Qrious Secure on 2024-04-02</li>
 	    <li>[333182464] High CVE-2024-4059: Out of bounds read in V8 API. Reported by Eirik on 2024-04-08</li>
 	    <li>[333420620] High CVE-2024-4060: Use after free in Dawn. Reported by wgslfuzz on 2024-04-09</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-4058</cvename>
       <cvename>CVE-2024-4059</cvename>
       <cvename>CVE-2024-4060</cvename>
       <url>https://chromereleases.googleblog.com/2024/04/stable-channel-update-for-desktop_24.html</url>
     </references>
     <dates>
       <discovery>2024-04-24</discovery>
       <entry>2024-04-25</entry>
     </dates>
   </vuln>
 
   <vuln vid="10e86b16-6836-11ee-b06f-0050569ceb3a">
     <topic>Unallowed PHP script execution in GLPI</topic>
     <affects>
       <package>
 	<name>glpi</name>
 	<range><lt>10.0.10,1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>From the GLPI 10.0.10 Changelog:</p>
 	<blockquote
 	cite="https://github.com/glpi-project/glpi/releases/tag/10.0.10">
 	<p>You will find below security issues fixed in this bugfixes version:
 	[SECURITY - Critical] Unallowed PHP script execution (CVE-2023-42802).</p>
 	</blockquote>
 	<p>The mentioned CVE is invalid</p>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-42802</cvename>
       <url>https://github.com/glpi-project/glpi/releases/tag/10.0.10</url>
     </references>
     <dates>
       <discovery>2023-09-27</discovery>
       <entry>2023-10-11</entry>
     </dates>
   </vuln>
 
   <vuln vid="894f2491-6834-11ee-b06f-0050569ceb3a">
     <topic>glpi-project -- SQL injection in ITIL actors in GLPI</topic>
     <affects>
       <package>
 	<name>glpi</name>
 	<range><ge>10.0.8,1</ge><lt>10.0.10,1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security-advisories@github.com reports:</p>
 	<blockquote cite="https://github.com/glpi-project/glpi/security/advisories/GHSA-x3jp-69f2-p84w">
 	  <p>GLPI stands for Gestionnaire Libre de Parc Informatique is a Free
 	Asset and IT Management Software package, that provides ITIL Service
 	Desk features, licenses tracking and software auditing.  The ITIL
 	actors input field from the Ticket form can be used to perform a
 	SQL injection.  Users are advised to upgrade to version 10.0.10.
 	There are no known workarounds for this vulnerability.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-42461</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2023-42461</url>
     </references>
     <dates>
       <discovery>2023-09-27</discovery>
       <entry>2023-10-11</entry>
     </dates>
   </vuln>
 
   <vuln vid="54e5573a-6834-11ee-b06f-0050569ceb3a">
     <topic>Phishing through a login page malicious URL in GLPI</topic>
     <affects>
       <package>
 	<name>glpi</name>
 	<range><ge>10.0.8,1</ge><lt>10.0.10,1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security-advisories@github.com reports:</p>
 	<blockquote cite="https://github.com/glpi-project/glpi/security/advisories/GHSA-2hcg-75jj-hghp">
 	  <p>GLPI stands for Gestionnaire Libre de Parc Informatique is a Free
 	Asset and IT Management Software package, that provides ITIL Service
 	Desk features, licenses tracking and software auditing.  The lack
 	of path filtering on the GLPI URL may allow an attacker to transmit
 	a malicious URL of login page that can be used to attempt a phishing
 	attack on user credentials.  Users are advised to upgrade to version
 	10.0.10.  There are no known workarounds for this vulnerability.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-41888</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2023-41888</url>
     </references>
     <dates>
       <discovery>2023-09-27</discovery>
       <entry>2023-10-11</entry>
     </dates>
   </vuln>
 
   <vuln vid="20302cbc-6834-11ee-b06f-0050569ceb3a">
     <topic>Users login enumeration by unauthenticated user in GLPI</topic>
     <affects>
       <package>
 	<name>glpi</name>
 	<range><lt>10.0.10,1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security-advisories@github.com reports:</p>
 	<blockquote cite="https://github.com/glpi-project/glpi/security/advisories/GHSA-5cf4-6q6r-49x9">
 	  <p>GLPI stands for Gestionnaire Libre de Parc Informatique is a Free
 	Asset and IT Management Software package, that provides ITIL Service
 	Desk features, licenses tracking and software auditing.  An
 	unauthenticated user can enumerate users logins.  Users are advised
 	to upgrade to version 10.0.10.  There are no known workarounds for
 	this vulnerability.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-41323</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2023-41323</url>
     </references>
     <dates>
       <discovery>2023-09-27</discovery>
       <entry>2023-10-11</entry>
     </dates>
   </vuln>
 
   <vuln vid="ae8b1445-6833-11ee-b06f-0050569ceb3a">
     <topic>Privilege Escalation from technician to super-admin in GLPI</topic>
     <affects>
       <package>
 	<name>glpi</name>
 	<range><ge>9.1.0,1</ge><lt>10.0.10,1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security-advisories@github.com reports:</p>
 	<blockquote cite="https://github.com/glpi-project/glpi/security/advisories/GHSA-9j8m-7563-8xvr">
 	  <p>GLPI stands for Gestionnaire Libre de Parc Informatique is a Free
 	Asset and IT Management Software package, that provides ITIL Service
 	Desk features, licenses tracking and software auditing.  A user
 	with write access to another user can make requests to change the
 	latter&apos;s password and then take control of their account.
 	Users are advised to upgrade to version 10.0.10.  There are no known
 	work around for this vulnerability.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-41322</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2023-41322</url>
     </references>
     <dates>
       <discovery>2023-09-27</discovery>
       <entry>2023-10-11</entry>
     </dates>
   </vuln>
 
   <vuln vid="6851f3bb-6833-11ee-b06f-0050569ceb3a">
     <topic>Sensitive fields enumeration through API in GLPI</topic>
     <affects>
       <package>
 	<name>glpi</name>
 	<range><ge>9.1.1,1</ge><lt>10.0.10,1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security-advisories@github.com reports:</p>
 	<blockquote cite="https://github.com/glpi-project/glpi/security/advisories/GHSA-3fxw-j5rj-w836">
 	  <p>GLPI stands for Gestionnaire Libre de Parc Informatique is a Free
 	Asset and IT Management Software package, that provides ITIL Service
 	Desk features, licenses tracking and software auditing.  An API
 	user can enumerate sensitive fields values on resources on which
 	he has read access.  Users are advised to upgrade to version 10.0.10.
 	There are no known workarounds for this vulnerability.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-41321</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2023-41321</url>
     </references>
     <dates>
       <discovery>2023-09-27</discovery>
       <entry>2023-10-11</entry>
     </dates>
   </vuln>
 
   <vuln vid="df71f5aa-6831-11ee-b06f-0050569ceb3a">
     <topic>File deletion through document upload process in GLPI</topic>
     <affects>
       <package>
 	<name>glpi</name>
 	<range><ge>10.0.0,1</ge><lt>10.0.10,1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security-advisories@github.com reports:</p>
 	<blockquote cite="https://github.com/glpi-project/glpi/security/advisories/GHSA-hm76-jh96-7j75">
 	  <p>GLPI stands for Gestionnaire Libre de Parc Informatique is a Free
 	Asset and IT Management Software package, that provides ITIL Service
 	Desk features, licenses tracking and software auditing.  The document
 	upload process can be diverted to delete some files.  Users are
 	advised to upgrade to version 10.0.10.  There are no known workarounds
 	for this vulnerability.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-42462</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2023-42462</url>
     </references>
     <dates>
       <discovery>2023-09-27</discovery>
       <entry>2023-10-11</entry>
     </dates>
   </vuln>
 
   <vuln vid="95c4ec45-6831-11ee-b06f-0050569ceb3a">
     <topic>Account takeover through API in GLPI</topic>
     <affects>
       <package>
 	<name>glpi</name>
 	<range><ge>9.3.0,1</ge><lt>10.0.10,1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security-advisories@github.com reports:</p>
 	<blockquote cite="https://github.com/glpi-project/glpi/security/advisories/GHSA-58wj-8jhx-jpm3">
 	  <p>GLPI stands for Gestionnaire Libre de Parc Informatique is a Free
 	Asset and IT Management Software package, that provides ITIL Service
 	Desk features, licenses tracking and software auditing.  An API
 	user that have read access on users resource can steal accounts of
 	other users.  Users are advised to upgrade to version 10.0.10.
 	There are no known workarounds for this vulnerability.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-41324</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2023-41324</url>
     </references>
     <dates>
       <discovery>2023-09-27</discovery>
       <entry>2023-10-11</entry>
     </dates>
   </vuln>
 
   <vuln vid="040e69f1-6831-11ee-b06f-0050569ceb3a">
     <topic>Account takeover via Kanban feature in GLPI</topic>
     <affects>
       <package>
 	<name>glpi</name>
 	<range><ge>9.5.0,1</ge><lt>10.0.10,1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security-advisories@github.com reports:</p>
 	<blockquote cite="https://github.com/glpi-project/glpi/security/advisories/GHSA-5wj6-hp4c-j5q9">
 	  <p>GLPI stands for Gestionnaire Libre de Parc Informatique is a Free
 	Asset and IT Management Software package, that provides ITIL Service
 	Desk features, licenses tracking and software auditing.  A logged
 	user from any profile can hijack the Kanban feature to alter any
 	user field, and end-up with stealing its account.  Users are advised
 	to upgrade to version 10.0.10.  There are no known workarounds for
 	this vulnerability.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-41326</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2023-41326</url>
     </references>
     <dates>
       <discovery>2023-09-27</discovery>
       <entry>2023-10-11</entry>
     </dates>
   </vuln>
 
   <vuln vid="6f6518ab-6830-11ee-b06f-0050569ceb3a">
     <topic>Account takeover via SQL Injection in UI layout preferences in GLPI</topic>
     <affects>
       <package>
 	<name>glpi</name>
 	<range><ge>10.0.0,1</ge><lt>10.0.10,1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security-advisories@github.com reports:</p>
 	<blockquote cite="https://github.com/glpi-project/glpi/security/advisories/GHSA-mv2r-gpw3-g476">
 	  <p>GLPI stands for Gestionnaire Libre de Parc Informatique is a Free
 	Asset and IT Management Software package, that provides ITIL Service
 	Desk features, licenses tracking and software auditing.  UI layout
 	preferences management can be hijacked to lead to SQL injection.
 	This injection can be use to takeover an administrator account.
 	Users are advised to upgrade to version 10.0.10.  There are no known
 	workarounds for this vulnerability.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-41320</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2023-41320</url>
     </references>
     <dates>
       <discovery>2023-09-27</discovery>
       <entry>2023-10-11</entry>
     </dates>
   </vuln>
 
   <vuln vid="257e1bf0-682f-11ee-b06f-0050569ceb3a">
     <topic>GLPI vulnerable to SQL injection via dashboard administration</topic>
     <affects>
       <package>
 	<name>glpi</name>
 	<range><ge>9.5.0,1</ge><lt>10.0.9,1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security-advisories@github.com reports:</p>
 	<blockquote cite="https://github.com/glpi-project/glpi/releases/tag/10.0.9">
 	  <p>GLPI is a Free Asset and IT Management Software package, Data center
 	management, ITIL Service Desk, licenses tracking and software
 	auditing.  An administrator can trigger SQL injection via dashboards
 	administration.  This vulnerability has been patched in version
 	10.0.9.
 	</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-37278</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2023-37278</url>
     </references>
     <dates>
       <discovery>2023-07-13</discovery>
       <entry>2023-10-11</entry>
     </dates>
   </vuln>
 
   <vuln vid="40173815-6827-11ee-b06f-0050569ceb3a">
     <topic>GLPI vulnerable to unauthorized access to User data</topic>
     <affects>
       <package>
 	<name>glpi</name>
 	<range><lt>10.0.8,1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security-advisories@github.com reports:</p>
 	<blockquote cite="https://github.com/glpi-project/glpi/releases/tag/10.0.8">
 	  <p>GLPI is a free asset and IT management software package.  Versions
 	of the software starting with 0.68 and prior to 10.0.8 have an
 	incorrect rights check on a on a file accessible by an authenticated
 	user.  This allows access to the list of all users and their personal
 	information.  Users should upgrade to version 10.0.8 to receive a
 	patch.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-34106</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2023-34106</url>
     </references>
     <dates>
       <discovery>2023-07-05</discovery>
       <entry>2023-10-11</entry>
     </dates>
   </vuln>
 
   <vuln vid="1fe40200-6823-11ee-b06f-0050569ceb3a">
     <topic>GLPI vulnerable to unauthorized access to KnowbaseItem data</topic>
     <affects>
       <package>
 	<name>glpi</name>
 	<range><ge>9.2.0,1</ge><lt>10.0.8,1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security-advisories@github.com reports:</p>
 	<blockquote cite="https://github.com/glpi-project/glpi/releases/tag/10.0.8">
 	  <p>GLPI is a free asset and IT management software package.  Versions
 	of the software starting with 9.2.0 and prior to 10.0.8 have an
 	incorrect rights check on a on a file accessible by an authenticated
 	user, allows access to the view all KnowbaseItems.  Version 10.0.8
 	has a patch for this issue.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-34107</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2023-34107</url>
     </references>
     <dates>
       <discovery>2023-07-05</discovery>
       <entry>2023-10-11</entry>
     </dates>
   </vuln>
 
   <vuln vid="b14a6ddc-6821-11ee-b06f-0050569ceb3a">
     <topic>GLPI vulnerable to reflected XSS in search pages</topic>
     <affects>
       <package>
 	<name>glpi</name>
 	<range><ge>9.4.0,1</ge><lt>10.0.8,1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security-advisories@github.com reports:</p>
 	<blockquote cite="https://github.com/glpi-project/glpi/releases/tag/10.0.8">
 	  <p>GLPI is a free asset and IT management software package.  Starting
 	in version 9.4.0 and prior to version 10.0.8, a malicious link can
 	be crafted by an unauthenticated user that can exploit a reflected
 	XSS in case any authenticated user opens the crafted link.  Users
 	should upgrade to version 10.0.8 to receive a patch.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-34244</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2023-34244</url>
     </references>
     <dates>
       <discovery>2023-07-05</discovery>
       <entry>2023-10-11</entry>
     </dates>
   </vuln>
 
   <vuln vid="95fde6bc-6821-11ee-b06f-0050569ceb3a">
     <topic>GLPI vulnerable to unauthenticated access to Dashboard data</topic>
     <affects>
       <package>
 	<name>glpi</name>
 	<range><ge>9.5.0,1</ge><lt>10.0.8,1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security-advisories@github.com reports:</p>
 	<blockquote cite="https://github.com/glpi-project/glpi/releases/tag/10.0.8">
 	  <p>GLPI is a free asset and IT management software package.  Starting
 	in version 9.5.0 and prior to version 10.0.8, an incorrect rights
 	check on a file allows an unauthenticated user to be able to access
 	dashboards data.  Version 10.0.8 contains a patch for this issue.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-35940</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2023-35940</url>
     </references>
     <dates>
       <discovery>2023-07-05</discovery>
       <entry>2023-10-11</entry>
     </dates>
   </vuln>
 
   <vuln vid="717efd8a-6821-11ee-b06f-0050569ceb3a">
     <topic>GLPI vulnerable to unauthorized access to Dashboard data</topic>
     <affects>
       <package>
 	<name>glpi</name>
 	<range><ge>9.5.0,1</ge><lt>10.0.8,1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security-advisories@github.com reports:</p>
 	<blockquote cite="https://github.com/glpi-project/glpi/releases/tag/10.0.8">
 	  <p>GLPI is a free asset and IT management software package.  Starting
 	in version 9.5.0 and prior to version 10.0.8, an incorrect rights
 	check on a on a file accessible by an authenticated user (or not
 	for certain actions), allows a threat actor to interact, modify,
 	or see Dashboard data.  Version 10.0.8 contains a patch for this
 	issue.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-35939</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2023-35939</url>
     </references>
     <dates>
       <discovery>2023-07-05</discovery>
       <entry>2023-10-11</entry>
     </dates>
   </vuln>
 
   <vuln vid="548a4163-6821-11ee-b06f-0050569ceb3a">
     <topic>GLPI vulnerable to SQL injection through Computer Virtual Machine information</topic>
     <affects>
       <package>
 	<name>glpi</name>
 	<range><lt>10.0.8,1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security-advisories@github.com reports:</p>
 	<blockquote cite="https://github.com/glpi-project/glpi/releases/tag/10.0.8">
 	  <p>GLPI is a free asset and IT management software package.  Starting
 	in version 0.80 and prior to version 10.0.8, Computer Virtual Machine
 	form and GLPI inventory request can be used to perform a SQL injection
 	attack.  Version 10.0.8 has a patch for this issue.  As a workaround,
 	one may disable native inventory.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-36808</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2023-36808</url>
     </references>
     <dates>
       <discovery>2023-07-05</discovery>
       <entry>2023-10-11</entry>
     </dates>
   </vuln>
 
   <vuln vid="e44e5ace-6820-11ee-b06f-0050569ceb3a">
     <topic>GLPI vulnerable to SQL injection via inventory agent request</topic>
     <affects>
       <package>
 	<name>glpi</name>
 	<range><ge>10.0.0,1</ge><lt>10.0.8,1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security-advisories@github.com reports:</p>
 	<blockquote cite="https://github.com/glpi-project/glpi/releases/tag/10.0.8">
 	  <p>GLPI is a free asset and IT management software package.  Starting
 	in version 10.0.0 and prior to version 10.0.8, GLPI inventory
 	endpoint can be used to drive a SQL injection attack.  By default,
 	GLPI inventory endpoint requires no authentication.  Version 10.0.8
 	has a patch for this issue.  As a workaround, one may disable native
 	inventory.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-35924</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2023-35924</url>
     </references>
     <dates>
       <discovery>2023-07-05</discovery>
       <entry>2023-10-11</entry>
     </dates>
   </vuln>
 
   <vuln vid="bdfa6c04-027a-11ef-9c21-901b0e9408dc">
     <topic>py-matrix-synapse -- weakness in auth chain indexing allows DoS</topic>
     <affects>
       <package>
 	<name>py38-matrix-synapse</name>
 	<name>py39-matrix-synapse</name>
 	<name>py310-matrix-synapse</name>
 	<name>py311-matrix-synapse</name>
 	<range><lt>1.105.1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Matrix developers report:</p>
 	<blockquote cite="https://element.io/blog/security-release-synapse-1-105-1/">
 	  <p>Weakness in auth chain indexing allows DoS from remote
 	  room members through disk fill and high CPU usage. (High severity)</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-31208</cvename>
       <url>https://element.io/blog/security-release-synapse-1-105-1/</url>
       <url>https://github.com/element-hq/synapse/security/advisories/GHSA-3h7q-rfh9-xm4v</url>
     </references>
     <dates>
       <discovery>2024-04-23</discovery>
       <entry>2024-04-24</entry>
     </dates>
   </vuln>
 
   <vuln vid="b857606c-0266-11ef-8681-001b217b3468">
     <topic>Gitlab -- vulnerabilities</topic>
     <affects>
       <package>
 	<name>gitlab-ce</name>
 	<name>gitlab-ee</name>
 	<range><ge>16.11.0</ge><lt>16.11.1</lt></range>
 	<range><ge>16.10.0</ge><lt>16.10.4</lt></range>
 	<range><ge>7.8.0</ge><lt>16.9.6</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Gitlab reports:</p>
 	<blockquote cite="https://about.gitlab.com/releases/2024/04/24/patch-release-gitlab-16-11-1-released/">
 	  <p>GitLab account takeover, under certain conditions, when using Bitbucket as an OAuth provider</p>
 	  <p>Path Traversal leads to DoS and Restricted File Read</p>
 	  <p>Unauthenticated ReDoS in FileFinder when using wildcard filters in project file search</p>
 	  <p>Personal Access Token scopes not honoured by GraphQL subscriptions</p>
 	  <p>Domain based restrictions bypass using a crafted email address</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-4024</cvename>
       <cvename>CVE-2024-2434</cvename>
       <cvename>CVE-2024-2829</cvename>
       <cvename>CVE-2024-4006</cvename>
       <cvename>CVE-2024-1347</cvename>
       <url>https://about.gitlab.com/releases/2024/04/24/patch-release-gitlab-16-11-1-released/</url>
     </references>
     <dates>
       <discovery>2024-04-24</discovery>
       <entry>2024-04-24</entry>
     </dates>
   </vuln>
 
   <vuln vid="1af16f2b-023c-11ef-8791-6805ca2fa271">
     <topic>powerdns-recursor -- denial of service</topic>
     <affects>
       <package>
 	<name>powerdns-recursor</name>
 	<range><lt>5.0.4</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>PowerDNS Team reports:</p>
 	<blockquote cite="https://blog.powerdns.com/2024/04/24/powerdns-recursor-4-8-8-4-9-5-5-0-4-released">
 	  <p>PowerDNS Security Advisory 2024-02: if recursive forwarding is configured,
 	   crafted responses can lead to a denial of service in Recursor</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-25583</cvename>
       <url>https://docs.powerdns.com/recursor/security-advisories/powerdns-advisory-2024-02.html</url>
     </references>
     <dates>
       <discovery>2024-04-24</discovery>
       <entry>2024-04-24</entry>
     </dates>
   </vuln>
 
   <vuln vid="bb49f1fa-00da-11ef-92b7-589cfc023192">
     <topic>GLPI -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>glpi</name>
 	<range><lt>10.0.13,1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>GLPI team reports:</p>
 	<blockquote cite="https://github.com/glpi-project/glpi/releases/tag/10.0.13">
 	  <p>GLPI 10.0.13 Changelog</p>
 	  <ul>
 	    <li>[SECURITY - high] SQL Injection in through the search engine (CVE-2024-27096)</li>
 	    <li>[SECURITY - moderate] Blind SSRF using Arbitrary Object Instantiation (CVE-2024-27098)</li>
 	    <li>[SECURITY - moderate] Stored XSS in dashboards (CVE-2024-27104)</li>
 	    <li>[SECURITY - moderate] Reflected XSS in debug mode (CVE-2024-27914)</li>
 	    <li>[SECURITY - moderate] Sensitive fields access through dropdowns (CVE-2024-27930)</li>
 	    <li>[SECURITY - moderate] Users emails enumeration (CVE-2024-27937)</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-27096</cvename>
       <cvename>CVE-2024-27098</cvename>
       <cvename>CVE-2024-27104</cvename>
       <cvename>CVE-2024-27914</cvename>
       <cvename>CVE-2024-27930</cvename>
       <cvename>CVE-2024-27937</cvename>
       <url>https://github.com/glpi-project/glpi/releases/tag/10.0.13</url>
     </references>
     <dates>
       <discovery>2024-03-13</discovery>
       <entry>2024-04-22</entry>
     </dates>
   </vuln>
 
   <vuln vid="faccf131-00d9-11ef-92b7-589cfc023192">
     <topic>GLPI -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>glpi</name>
 	<range><lt>10.0.12,1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>GLPI team reports:</p>
 	<blockquote cite="https://github.com/glpi-project/glpi/releases/tag/10.0.12">
 	  <p>GLPI 10.0.12 Changelog</p>
 	  <ul>
 	    <li>[SECURITY - moderate] Reflected XSS in reports pages (CVE-2024-23645)</li>
 	    <li>[SECURITY - moderate] LDAP Injection during authentication (CVE-2023-51446)</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-23645</cvename>
       <cvename>CVE-2023-51446</cvename>
       <url>https://github.com/glpi-project/glpi/releases/tag/10.0.12</url>
     </references>
     <dates>
       <discovery>2024-02-01</discovery>
       <entry>2024-04-22</entry>
     </dates>
   </vuln>
 
   <vuln vid="ed688880-00c4-11ef-92b7-589cfc023192">
     <topic>GLPI -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>glpi</name>
 	<range><lt>10.0.11,1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>GLPI team reports:</p>
 	<blockquote cite="https://github.com/glpi-project/glpi/releases/tag/10.0.11">
 	  <p>GLPI 10.0.11 Changelog</p>
 	  <ul>
 	    <li>[SECURITY - moderate] Authenticated SQL Injection (CVE-2023-43813)</li>
 	    <li>[SECURITY - high] SQL injection through inventory agent request (CVE-2023-46727)</li>
 	    <li>[SECURITY - high] Remote code execution from LDAP server configuration form on PHP 7.4 (CVE-2023-46726)</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-43813</cvename>
       <cvename>CVE-2023-46727</cvename>
       <cvename>CVE-2023-46726</cvename>
       <url>https://github.com/glpi-project/glpi/releases/tag/10.0.11</url>
     </references>
     <dates>
       <discovery>2023-12-13</discovery>
       <entry>2024-04-22</entry>
     </dates>
   </vuln>
 
   <vuln vid="2ce1a2f1-0177-11ef-a45e-08002784c58d">
     <topic>ruby -- Arbitrary memory address read vulnerability with Regex search</topic>
     <affects>
       <package>
 	<name>ruby</name>
 	<range><ge>3.1.0,1</ge><lt>3.1.5,1</lt></range>
 	<range><ge>3.2.0,1</ge><lt>3.2.4,1</lt></range>
 	<range><ge>3.3.0,1</ge><lt>3.3.1,1</lt></range>
       </package>
       <package>
 	<name>ruby31</name>
 	<range><ge>3.1.0,1</ge><lt>3.1.5,1</lt></range>
       </package>
       <package>
 	<name>ruby32</name>
 	<range><ge>3.2.0,1</ge><lt>3.2.4,1</lt></range>
       </package>
       <package>
 	<name>ruby33</name>
 	<range><ge>3.3.0,1</ge><lt>3.3.1,1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>sp2ip reports:</p>
 	<blockquote cite="https://www.ruby-lang.org/en/news/2024/04/23/arbitrary-memory-address-read-regexp-cve-2024-27282/">
 	  <p>
 	    If attacker-supplied data is provided to the Ruby regex
 	    compiler, it is possible to extract arbitrary heap data
 	    relative to the start of the text, including pointers and
 	    sensitive strings.
 	  </p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-27282</cvename>
       <url>https://www.ruby-lang.org/en/news/2024/04/23/arbitrary-memory-address-read-regexp-cve-2024-27282/</url>
     </references>
     <dates>
       <discovery>2024-04-23</discovery>
       <entry>2024-04-23</entry>
     </dates>
   </vuln>
 
   <vuln vid="304d92c3-00c5-11ef-bd52-080027bff743">
 	<topic>sdl2_sound -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>sdl2_sound</name>
 	<range><lt>2.0.2_1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>GitHub Security Lab reports:</p>
 	<blockquote cite="https://securitylab.github.com/advisories/GHSL-2023-145_GHSL-2023-151_stb_image_h/">
 	  <p>stb_image.h and stb_vorbis libraries contain several memory access violations of different severity</p>
 	  <ol>
 		<li>Wild address read in stbi__gif_load_next (GHSL-2023-145).</li>
 		<li>Multi-byte read heap buffer overflow in stbi__vertical_flip (GHSL-2023-146).</li>
 		<li>Disclosure of uninitialized memory in stbi__tga_load (GHSL-2023-147).</li>
 		<li>Double-free in stbi__load_gif_main_outofmem (GHSL-2023-148).</li>
 		<li>Null pointer dereference in stbi__convert_format (GHSL-2023-149).</li>
 		<li>Possible double-free or memory leak in stbi__load_gif_main (GHSL-2023-150).</li>
 		<li>Null pointer dereference because of an uninitialized variable (GHSL-2023-151).</li>
 		<li>0 byte write heap buffer overflow in start_decoder (GHSL-2023-165)</li>
 		<li>Multi-byte write heap buffer overflow in start_decoder (GHSL-2023-166)</li>
 		<li>Heap buffer out of bounds write in start_decoder (GHSL-2023-167)</li>
 		<li>Off-by-one heap buffer write in start_decoder (GHSL-2023-168)</li>
 		<li>Attempt to free an uninitialized memory pointer in vorbis_deinit (GHSL-2023-169)</li>
 		<li>Null pointer dereference in vorbis_deinit (GHSL-2023-170)</li>
 		<li>Out of bounds heap buffer write (GHSL-2023-171)</li>
 		<li>Wild address read in vorbis_decode_packet_rest (GHSL-2023-172)</li>
 	  </ol>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-45676</cvename>
       <cvename>CVE-2023-45677</cvename>
       <cvename>CVE-2023-45680</cvename>
       <cvename>CVE-2023-45681</cvename>
       <cvename>CVE-2023-45682</cvename>
 	  <url>https://securitylab.github.com/advisories/GHSL-2023-145_GHSL-2023-151_stb_image_h/</url>
     </references>
     <dates>
       <discovery>2023-10-20</discovery>
       <entry>2024-04-22</entry>
     </dates>
   </vuln>
 
   <vuln vid="9bed230f-ffc8-11ee-8e76-a8a1599412c6">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>124.0.6367.60</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>124.0.6367.60</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2024/04/stable-channel-update-for-desktop_16.html">
 	 <p>This update includes 23 security fixes:</p>
 	 <ul>
 	    <li>[331358160] High CVE-2024-3832: Object corruption in V8. Reported by Man Yue Mo of GitHub Security Lab on 2024-03-27</li>
 	    <li>[331383939] High CVE-2024-3833: Object corruption in WebAssembly. Reported by Man Yue Mo of GitHub Security Lab on 2024-03-27</li>
 	    <li>[330759272] High CVE-2024-3914: Use after free in V8. Reported by Seunghyun Lee (@0x10n) of KAIST Hacking Lab, via Pwn2Own 2024 on 2024-03-21</li>
 	    <li>[326607008] High CVE-2024-3834: Use after free in Downloads. Reported by ChaobinZhang on 2024-02-24</li>
 	    <li>[41491379] Medium CVE-2024-3837: Use after free in QUIC. Reported by {rotiple, dch3ck} of CW Research Inc. on 2024-01-15</li>
 	    <li>[328278717] Medium CVE-2024-3838: Inappropriate implementation in Autofill. Reported by Ardyan Vicky Ramadhan on 2024-03-06</li>
 	    <li>[41491859] Medium CVE-2024-3839: Out of bounds read in Fonts. Reported by Ronald Crane (Zippenhop LLC) on 2024-01-16</li>
 	    <li>[41493458] Medium CVE-2024-3840: Insufficient policy enforcement in Site Isolation. Reported by Ahmed ElMasry on 2024-01-22</li>
 	    <li>[330376742] Medium CVE-2024-3841: Insufficient data validation in Browser Switcher. Reported by Oleg on 2024-03-19</li>
 	    <li>[41486690] Medium CVE-2024-3843: Insufficient data validation in Downloads. Reported by Azur on 2023-12-24</li>
 	    <li>[40058873] Low CVE-2024-3844: Inappropriate implementation in Extensions. Reported by Alesandro Ortiz on 2022-02-23</li>
 	    <li>[323583084] Low CVE-2024-3845: Inappropriate implementation in Network. Reported by Daniel Baulig on 2024-02-03</li>
 	    <li>[40064754] Low CVE-2024-3846: Inappropriate implementation in Prompts. Reported by Ahmed ElMasry on 2023-05-23</li>
 	    <li>[328690293] Low CVE-2024-3847: Insufficient policy enforcement in WebUI. Reported by Yan Zhu on 2024-03-08</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-3832</cvename>
       <cvename>CVE-2024-3833</cvename>
       <cvename>CVE-2024-3914</cvename>
       <cvename>CVE-2024-3834</cvename>
       <cvename>CVE-2024-3837</cvename>
       <cvename>CVE-2024-3838</cvename>
       <cvename>CVE-2024-3839</cvename>
       <cvename>CVE-2024-3840</cvename>
       <cvename>CVE-2024-3841</cvename>
       <cvename>CVE-2024-3843</cvename>
       <cvename>CVE-2024-3844</cvename>
       <cvename>CVE-2024-3845</cvename>
       <cvename>CVE-2024-3846</cvename>
       <cvename>CVE-2024-3847</cvename>
       <url>https://chromereleases.googleblog.com/2024/04/stable-channel-update-for-desktop_16.html</url>
     </references>
     <dates>
       <discovery>2024-04-16</discovery>
       <entry>2024-04-21</entry>
     </dates>
   </vuln>
 
   <vuln vid="ecafc4af-fe8a-11ee-890c-08002784c58d">
     <topic>clamav -- Possible crash in the HTML file parser that could cause a denial-of-service (DoS) condition</topic>
     <affects>
       <package>
 	<name>clamav</name>
 	<range><ge>1.3.0,1</ge><lt>1.3.1,1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Błażej Pawłowski reports:</p>
 	<blockquote cite="https://blog.clamav.net/2024/04/clamav-131-123-106-patch-versions.html">
 	  <p>
 	    A vulnerability in the HTML parser of ClamAV could allow
 	    an unauthenticated, remote attacker to cause a denial of
 	    service (DoS) condition on an affected device. The
 	    vulnerability is due to an issue in the C to Rust foreign
 	    function interface. An attacker could exploit this
 	    vulnerability by submitting a crafted file containing HTML
 	    content to be scanned by ClamAV on an affected device. An
 	    exploit could allow the attacker to cause the ClamAV
 	    scanning process to terminate, resulting in a DoS
 	    condition on the affected software.
 	  </p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-20380</cvename>
       <url>https://blog.clamav.net/2024/04/clamav-131-123-106-patch-versions.html</url>
     </references>
     <dates>
       <discovery>2024-04-17</discovery>
       <entry>2024-04-19</entry>
     </dates>
   </vuln>
 
   <vuln vid="4ebdd56b-fe72-11ee-bc57-00e081b7aa2d">
     <topic>jenkins -- Terrapin SSH vulnerability in Jenkins CLI client</topic>
     <affects>
       <package>
 	<name>jenkins</name>
 	<range><lt>2.452</lt></range>
       </package>
       <package>
 	<name>jenkins-lts</name>
 	<range><lt>2.440.3</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Jenkins Security Advisory:</p>
 	<blockquote cite="https://www.jenkins.io/security/advisory/2024-04-17/">
 	  <h1>Description</h1>
 	  <h5>(Medium) SECURITY-3386 / CVE-2023-48795</h5>
 	  <p>Terrapin SSH vulnerability in Jenkins CLI client</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-48795</cvename>
       <url>https://www.jenkins.io/security/advisory/2024-04-17/</url>
     </references>
     <dates>
       <discovery>2024-04-17</discovery>
       <entry>2024-04-19</entry>
     </dates>
   </vuln>
 
   <vuln vid="f90bf863-e43c-4db3-b5a8-d9603684657a">
     <topic>electron{27,28,29} -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>electron27</name>
 	<range><lt>27.3.11</lt></range>
       </package>
       <package>
 	<name>electron28</name>
 	<range><lt>28.3.1</lt></range>
       </package>
       <package>
 	<name>electron29</name>
 	<range><lt>29.3.1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Electron develpers report:</p>
 	<blockquote cite="https://github.com/electron/electron/releases/tag/v27.3.11">
 	  <p>This update fixes the following vulnerabilities:</p>
 	  <ul>
 	    <li>Security: backported fix for CVE-2024-3515.</li>
 	    <li>Security: backported fix for CVE-2024-3516.</li>
 	    <li>Security: backported fix for CVE-2024-3157.</li>
 	    <li>Security: backported fix for CVE-2024-1580.</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-3515</cvename>
       <url>https://github.com/advisories/GHSA-x6cj-gx36-vcxv</url>
       <cvename>CVE-2024-3516</cvename>
       <url>https://github.com/advisories/GHSA-jf9g-42gm-v87w</url>
       <cvename>CVE-2024-3157</cvename>
       <url>https://github.com/advisories/GHSA-4m4g-p795-cmq7</url>
       <cvename>CVE-2024-1580</cvename>
       <url>https://github.com/advisories/GHSA-3p7f-4r2q-wxmm</url>
     </references>
     <dates>
       <discovery>2024-04-16</discovery>
       <entry>2024-04-18</entry>
     </dates>
   </vuln>
 
   <vuln vid="6d82c5e9-fc24-11ee-a689-04421a1baf97">
     <topic>php -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>php81</name>
 	<range><lt>8.1.28</lt></range>
       </package>
       <package>
 	<name>php82</name>
 	<range><lt>8.2.18</lt></range>
       </package>
       <package>
 	<name>php83</name>
 	<range><lt>8.3.6</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>This update includes 3 security fixes:</p>
     <blockquote cite="https://seclists.org/oss-sec/2024/q2/113/">
 	 <ul>
 	   <li>High CVE-2024-1874: Command injection via array-ish $command parameter of proc_open even if bypass_shell option enabled on Windows</li>
 	   <li>High CVE-2024-1874: Command injection via array-ish $command parameter of proc_open even if bypass_shell option enabled on Windows</li>
        <li>Medium CVE-2024-2756: __Host-/__Secure- cookie bypass due to partial CVE-2022-31629 fix</li>
        <li>High CVE-2024-2757: mb_encode_mimeheader runs endlessly for some inputs</li>
 	 </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-1874</cvename>
       <url>https://github.com/php/php-src/security/advisories/GHSA-pc52-254m-w9w7</url>
       <cvename>CVE-2024-2756</cvename>
       <url>https://github.com/php/php-src/security/advisories/GHSA-wpj3-hf5j-x4v4</url>
       <cvename>CVE-2024-3096</cvename>
       <url>https://github.com/php/php-src/security/advisories/GHSA-h746-cjrr-wfmr</url>
       <cvename>CVE-2024-2757</cvename>
       <url>https://github.com/php/php-src/security/advisories/GHSA-fjp9-9hwx-59fq</url>
     </references>
     <dates>
       <discovery>2024-04-11</discovery>
       <entry>2024-04-16</entry>
     </dates>
   </vuln>
 
   <vuln vid="cdb5e0e3-fafc-11ee-9c21-901b0e9408dc">
     <topic>go -- http2: close connections when receiving too many headers</topic>
     <affects>
       <package>
 	<name>go122</name>
 	<range><lt>1.22.2</lt></range>
       </package>
       <package>
 	<name>go121</name>
 	<range><lt>1.21.9</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The Go project reports:</p>
 	<blockquote cite="https://go.dev/issue/65051">
 	  <p>http2: close connections when receiving too many headers</p>
 	  <p>Maintaining HPACK state requires that we parse and
 	  process all HEADERS and CONTINUATION frames on a
 	  connection. When a request's headers exceed MaxHeaderBytes,
 	  we don't allocate memory to store the excess headers but we
 	  do parse them. This permits an attacker to cause an HTTP/2
 	  endpoint to read arbitrary amounts of header data, all
 	  associated with a request which is going to be
 	  rejected. These headers can include Huffman-encoded data
 	  which is significantly more expensive for the receiver to
 	  decode than for an attacker to send.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-45288</cvename>
       <url>https://groups.google.com/g/golang-announce/c/YgW0sx8mN3M/m/khALNYGdAAAJ</url>
     </references>
     <dates>
       <discovery>2024-04-03</discovery>
       <entry>2024-04-15</entry>
     </dates>
   </vuln>
 
   <vuln vid="7314942b-0889-46f0-b02b-2c60aabe4a82">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>123.0.6312.122</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>123.0.6312.122</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2024/04/stable-channel-update-for-desktop_10.html">
 	 <p>This update includes 3 security fixes:</p>
 	 <ul>
 	    <li>[331237485] High CVE-2024-3157: Out of bounds write in Compositing. Reported by DarkNavy on 2024-03-26</li>
 	    <li>[328859176] High CVE-2024-3516: Heap buffer overflow in ANGLE. Reported by Bao (zx) Pham and Toan (suto) Pham of Qrious Secure on 2024-03-09</li>
 	    <li>[331123811] High CVE-2024-3515: Use after free in Dawn. Reported by wgslfuzz on 2024-03-25</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-3157</cvename>
       <cvename>CVE-2024-3516</cvename>
       <cvename>CVE-2024-3515</cvename>
       <url>https://chromereleases.googleblog.com/2024/04/stable-channel-update-for-desktop_10.html</url>
     </references>
     <dates>
       <discovery>2024-04-10</discovery>
       <entry>2024-04-12</entry>
     </dates>
   </vuln>
 
   <vuln vid="080936ba-fbb7-11ee-abc8-6960f2492b1d">
     <topic>PuTTY and embedders (f.i., filezilla) -- biased RNG with NIST P521/ecdsa-sha2-nistp521 signatures permits recovering private key</topic>
     <affects>
       <package>
 	<name>putty</name>
 	<range><ge>0.68</ge><lt>0.81</lt></range>
       </package>
       <package>
 	<name>putty-nogtk</name>
 	<range><ge>0.68</ge><lt>0.81</lt></range>
       </package>
       <package>
 	<name>filezilla</name>
 	<range><lt>3.67.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Simon Tatham reports:</p>
 	<blockquote cite="https://lists.tartarus.org/pipermail/putty-announce/2024/000038.html">
 	  <p>ECDSA signatures using 521-bit keys (the NIST P521 curve,
 	    otherwise known as ecdsa-sha2-nistp521) were generated with biased
 	    random numbers. This permits an attacker in possession of a few
 	    dozen signatures to RECOVER THE PRIVATE KEY.</p>
 	  <p>Any 521-bit ECDSA private key that PuTTY or Pageant has used to
 	    sign anything should be considered compromised.</p>
 	  <p>Additionally, if you have any 521-bit ECDSA private keys that
 	    you've used with PuTTY, you should consider them to be
 	    compromised: generate new keys, and remove the old public keys
 	    from any authorized_keys files.</p>
 	</blockquote>
 	<blockquote cite="https://nvd.nist.gov/vuln/detail/CVE-2024-31497">
 	  <p>
 	    A second, independent scenario is that the adversary is an operator
 	    of an SSH server to which the victim authenticates (for remote login
 	    or file copy), [...] and the victim uses the same private key for
 	    SSH connections to other services operated by other entities. Here,
 	    the rogue server operator (who would otherwise have no way to
 	    determine the victim's private key) can derive the victim's private
 	    key, and then use it for unauthorized access to those other
 	    services. If the other services include Git services, then again it
 	    may be possible to conduct supply-chain attacks on software
 	    maintained in Git. This also affects, for example, FileZilla before
 	    3.67.0, WinSCP before 6.3.3, TortoiseGit before 2.15.0.1, and
 	    TortoiseSVN through 1.14.6.
 	  </p>
 	</blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-31497</cvename>
       <url>https://lists.tartarus.org/pipermail/putty-announce/2024/000038.html</url>
       <url>https://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/vuln-p521-bias.html</url>
       <url>https://git.tartarus.org/?h=c193fe9848f50a88a4089aac647fecc31ae96d27&amp;p=simon/putty.git</url>
       <url>https://filezilla-project.org/versions.php</url>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-31497</url>
     </references>
     <dates>
       <discovery>2024-04-01</discovery> <!-- see git.tartarus.org link to commit c193fe9848f -->
       <entry>2024-04-16</entry>
     </dates>
   </vuln>
 
   <vuln vid="31617e47-7eec-4c60-9fdf-8aee61622bab">
     <topic>electron{27,28} -- Out of bounds memory access in V8</topic>
     <affects>
       <package>
 	<name>electron27</name>
 	<range><lt>27.3.10</lt></range>
       </package>
       <package>
 	<name>electron28</name>
 	<range><lt>28.3.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Electron developers report:</p>
 	<blockquote cite="https://github.com/electron/electron/releases/tag/v27.3.10">
 	  <p>This update fixes the following vulnerability:</p>
 	  <ul>
 	    <li>Security: backported fix for CVE-2024-3159.</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-3159</cvename>
       <url>https://github.com/advisories/GHSA-mh2p-2x66-3hr4</url>
     </references>
     <dates>
       <discovery>2024-04-10</discovery>
       <entry>2024-04-11</entry>
     </dates>
   </vuln>
 
   <vuln vid="7c217849-f7d7-11ee-a490-84a93843eb75">
     <topic>OpenSSL -- Unbounded memory growth with session handling in TLSv1.3</topic>
     <affects>
       <package>
 	<name>openssl</name>
 	<range><lt>3.0.13_3,1</lt></range>
       </package>
       <package>
 	<name>openssl31</name>
 	<range><lt>3.1.5_3</lt></range>
       </package>
       <package>
 	<name>openssl32</name>
 	<range><lt>3.2.1_2</lt></range>
       </package>
       <package>
 	<name>openssl-quictls</name>
 	<range><lt>3.0.13_3</lt></range>
       </package>
       <package>
 	<name>openssl31-quictls</name>
 	<range><lt>3.1.5_1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The OpenSSL project reports:</p>
 	<blockquote cite="https://www.openssl.org/news/secadv/20240408.txt">
 	  <p>Some non-default TLS server configurations can cause unbounded
 	    memory growth when processing TLSv1.3 sessions</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-2511</cvename>
       <url>https://www.openssl.org/news/secadv/20240408.txt</url>
     </references>
     <dates>
       <discovery>2024-04-08</discovery>
       <entry>2024-04-11</entry>
     </dates>
   </vuln>
 
   <vuln vid="c092be0e-f7cc-11ee-aa6b-b42e991fc52e">
     <topic>forgejo -- HTTP/2 CONTINUATION flood in net/http</topic>
     <affects>
       <package>
 	<name>forgejo</name>
 	<range><lt>1.21.8</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@golang.org reports:</p>
 	<blockquote cite="https://go.dev/cl/576155">
 	  <p>An attacker may cause an HTTP/2 endpoint to read arbitrary amounts
 	of header data by sending an excessive number of CONTINUATION frames.
 	Maintaining HPACK state requires parsing and processing all HEADERS
 	and CONTINUATION frames on a connection.  When a request&apos;s
 	headers exceed MaxHeaderBytes, no memory is allocated to store the
 	excess headers, but they are still parsed.  This permits an attacker
 	to cause an HTTP/2 endpoint to read arbitrary amounts of header
 	data, all associated with a request which is going to be rejected.
 	These headers can include Huffman-encoded data which is significantly
 	more expensive for the receiver to decode than for an attacker to
 	send.  The fix sets a limit on the amount of excess header frames
 	we will process before closing a connection.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-45288</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2023-45288</url>
     </references>
     <dates>
       <discovery>2024-04-04</discovery>
       <entry>2024-04-11</entry>
     </dates>
   </vuln>
 
   <vuln vid="02be46c1-f7cc-11ee-aa6b-b42e991fc52e">
     <topic>jose -- DoS vulnerability</topic>
     <affects>
       <package>
 	<name>jose</name>
 	<range><lt>13</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>cve@mitre.org reports:</p>
 	<blockquote cite="https://github.com/P3ngu1nW/CVE_Request/blob/main/latch-jose.md">
 	<p>
 	  latchset jose through version 11 allows attackers to cause
 	  a denial of service (CPU consumption) via a large p2c (aka
 	  PBES2 Count) value.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-50967</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2023-50967</url>
     </references>
     <dates>
       <discovery>2024-03-20</discovery>
       <entry>2024-04-11</entry>
     </dates>
   </vuln>
 
   <vuln vid="dad6294c-f7c1-11ee-bb77-001b217b3468">
     <topic>Gitlab -- Patch Release: 16.10.2, 16.9.4, 16.8.6</topic>
     <affects>
       <package>
 	<name>gitlab-ce</name>
 	<range><ge>16.10.0</ge><lt>16.10.2</lt></range>
 	<range><ge>16.9.0</ge><lt>16.9.4</lt></range>
 	<range><lt>16.8.6</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Gitlab reports:</p>
 	<blockquote cite="https://about.gitlab.com/releases/2024/04/10/patch-release-gitlab-16-10-2-released/">
 	  <p>Stored XSS injected in diff viewer</p>
 	  <p>Stored XSS via autocomplete results</p>
 	  <p>Redos on Integrations Chat Messages</p>
 	  <p>Redos During Parse Junit Test Report</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-3092</cvename>
       <cvename>CVE-2024-2279</cvename>
       <cvename>CVE-2023-6489</cvename>
       <cvename>CVE-2023-6678</cvename>
       <url>https://about.gitlab.com/releases/2024/04/10/patch-release-gitlab-16-10-2-released/</url>
     </references>
     <dates>
       <discovery>2024-04-10</discovery>
       <entry>2024-04-11</entry>
     </dates>
   </vuln>
 
   <vuln vid="ea4a2dfc-f761-11ee-af2c-589cfc0f81b0">
     <topic>wordpress -- XSS</topic>
     <affects>
       <package>
 	<name>wordpress</name>
 	<name>fr-wordpress-fr_FR</name>
 	<range><ge>6.5.0,1</ge><lt>6.5.1,1</lt></range>
 	<range><lt>6.4.4,1</lt></range>
       </package>
       <package>
 	<name>ru-wordpress-ru_RU</name>
 	<name>ja-wordpress-ja</name>
 	<name>zh-wordpress-zh_CN</name>
 	<name>zh-wordpress-zh_TW</name>
 	<name>de-wordpress-de_DE</name>
 	<range><ge>6.5.0</ge><lt>6.5.1</lt></range>
 	<range><lt>6.4.4</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The Wordpress team reports:</p>
 	<blockquote cite="https://wordpress.org/documentation/wordpress-version/version-6-4-4/">
 	  <p>A cross-site scripting (XSS) vulnerability affecting the Avatar block type</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <url>https://wordpress.org/documentation/wordpress-version/version-6-4-4/</url>
     </references>
     <dates>
       <discovery>2024-04-09</discovery>
       <entry>2024-04-10</entry>
     </dates>
   </vuln>
 
   <vuln vid="8e6f684b-f333-11ee-a573-84a93843eb75">
     <topic>Apache httpd -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>apache24</name>
 	<range><lt>2.4.59</lt></range>
       </package>
       <package>
 	<name>mod_http2</name>
 	<range><lt>2.0.27</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The Apache httpd project reports:</p>
 	<blockquote cite="https://downloads.apache.org/httpd/CHANGES_2.4.59">
 	  <p>HTTP/2 DoS by memory exhaustion on endless continuation frames</p>
 	  <p>HTTP Response Splitting in multiple modules</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-27316</cvename>
       <cvename>CVE-2024-24795</cvename>
       <cvename>CVE-2024-38709</cvename>
       <url>https://downloads.apache.org/httpd/CHANGES_2.4.59</url>
     </references>
     <dates>
       <discovery>2024-04-04</discovery>
       <entry>2024-04-05</entry>
     </dates>
   </vuln>
 
   <vuln vid="c2431c4e-622c-4d92-996d-d8b5258ae8c9">
     <topic>electron{27,28} -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>electron27</name>
 	<range><lt>27.3.9</lt></range>
       </package>
       <package>
 	<name>electron28</name>
 	<range><lt>28.2.10</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Electron developers report:</p>
 	<blockquote cite="https://github.com/electron/electron/releases/tag/v27.3.9">
 	  <p>This update fixes the following vulnerabilities:</p>
 	  <ul>
 	    <li>Security: backported fix for CVE-2024-2885.</li>
 	    <li>Security: backported fix for CVE-2024-2883.</li>
 	    <li>Security: backported fix for CVE-2024-2887.</li>
 	    <li>Security: backported fix for CVE-2024-2886.</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-2885</cvename>
       <url>https://github.com/advisories/GHSA-qccw-wmvp-8pv9</url>
       <cvename>CVE-2024-2883</cvename>
       <url>https://github.com/advisories/GHSA-gg9c-7j6m-3qq2</url>
       <cvename>CVE-2024-2887</cvename>
       <url>https://github.com/advisories/GHSA-q75f-2pp5-9phj</url>
       <cvename>CVE-2024-2886</cvename>
       <url>https://github.com/advisories/GHSA-5pj4-f8gh-j3mr</url>
     </references>
     <dates>
       <discovery>2024-04-03</discovery>
       <entry>2024-04-05</entry>
     </dates>
   </vuln>
 
   <vuln vid="4a026b6c-f2b8-11ee-8e76-a8a1599412c6">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>123.0.6312.105</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>123.0.6312.105</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2024/04/stable-channel-update-for-desktop.html">
 	 <p>This update includes 3 security fixes:</p>
 	 <ul>
 	    <li>[329130358] High CVE-2024-3156: Inappropriate implementation in V8. Reported by Zhenghang Xiao (@Kipreyyy) on 2024-03-12</li>
 	    <li>[329965696] High CVE-2024-3158: Use after free in Bookmarks. Reported by undoingfish on 2024-03-17</li>
 	    <li>[330760873] High CVE-2024-3159: Out of bounds memory access in V8. Reported by Edouard Bochin (@le_douds) and Tao Yan (@Ga1ois) of Palo Alto Networks, via Pwn2Own 2024 on 2024-03-22</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-3156</cvename>
       <cvename>CVE-2024-3158</cvename>
       <cvename>CVE-2024-3159</cvename>
       <url>https://chromereleases.googleblog.com/2024/04/stable-channel-update-for-desktop.html</url>
     </references>
     <dates>
       <discovery>2024-04-02</discovery>
       <entry>2024-04-04</entry>
     </dates>
   </vuln>
 
   <vuln vid="57561cfc-f24b-11ee-9730-001fc69cd6dc">
     <topic>xorg server -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>xorg-server</name>
 	<name>xephyr</name>
 	<name>xorg-vfbserver</name>
 	<range><lt>21.1.12,1</lt></range>
       </package>
       <package>
 	<name>xorg-nextserver</name>
 	<range><lt>21.1.12,2</lt></range>
       </package>
       <package>
 	<name>xwayland</name>
 	<range><lt>23.2.5</lt></range>
       </package>
       <package>
 	<name>xwayland-devel</name>
 	<range><ge>21.0.99.1.672</ge><lt>21.0.99.1.841_1</lt></range>
 	<range><lt>21.0.99.1.671_1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The X.Org project reports:</p>
 	<blockquote cite="https://lists.x.org/archives/xorg-announce/2024-April/003497.html">
 	  <ul>
 	    <li>
 	      CVE-2024-31080: Heap buffer overread/data leakage in
 	      ProcXIGetSelectedEvents
 
 	      <p>The ProcXIGetSelectedEvents() function uses the byte-swapped
 	      length of the return data for the amount of data to return to
 	      the client, if the client has a different endianness than
 	      the X server.</p>
 	    </li>
 	    <li>CVE-2024-31081: Heap buffer overread/data leakage in
 	    ProcXIPassiveGrabDevice
 
 	    <p>The ProcXIPassiveGrabDevice() function uses the byte-swapped
 	    length of the return data for the amount of data to return to
 	    the client, if the client has a different endianness than
 	    the X server.</p>
 	    </li>
 
 	    <li>CVE-2024-31083: User-after-free in ProcRenderAddGlyphs
 
 	    <p>The ProcRenderAddGlyphs() function calls the AllocateGlyph()
 	    function to store new glyphs sent by the client to the X server.
 	    AllocateGlyph() would return a new glyph with refcount=0 and
 	    a re-used glyph would end up not changing the refcount at all.
 	    The resulting glyph_new array would thus have multiple entries
 	    pointing to the same non-refcounted glyphs.
 
 	    ProcRenderAddGlyphs() may free a glyph, resulting in a
 	    use-after-free when the same glyph pointer is then later used.</p>
 	    </li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-31080</cvename>
       <cvename>CVE-2024-31081</cvename>
       <cvename>CVE-2024-31083</cvename>
       <url>https://lists.x.org/archives/xorg-announce/2024-April/003497.html</url>
     </references>
     <dates>
       <discovery>2024-04-03</discovery>
       <entry>2024-04-04</entry>
     </dates>
   </vuln>
 
   <vuln vid="2e3bea0c-f110-11ee-bc57-00e081b7aa2d">
     <topic>jenkins -- HTTP/2 denial of service vulnerability in bundled Jetty</topic>
     <affects>
       <package>
 	<name>jenkins</name>
 	<range><lt>2.444</lt></range>
       </package>
       <package>
 	<name>jenkins-lts</name>
 	<range><lt>2.440.2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Jenkins Security Advisory:</p>
 	<blockquote cite="https://www.jenkins.io/security/advisory/2024-03-20/">
 	  <h1>Description</h1>
 	  <h5>(High) SECURITY-3379 / CVE-2024-22201</h5>
 	  <p>HTTP/2 denial of service vulnerability in bundled Jetty</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-22201</cvename>
       <url>https://www.jenkins.io/security/advisory/2024-03-20/</url>
     </references>
     <dates>
       <discovery>2024-03-20</discovery>
       <entry>2024-04-02</entry>
     </dates>
   </vuln>
 
   <vuln vid="d58726ff-ef5e-11ee-8d8e-080027a5b8e9">
     <topic>mediawiki -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>mediawiki139</name>
 	<range><lt>1.39.7</lt></range>
       </package>
       <package>
 	<name>mediawiki140</name>
 	<range><lt>1.40.3</lt></range>
       </package>
       <package>
 	<name>mediawiki141</name>
 	<range><lt>1.41.1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Mediawiki reports:</p>
 	<blockquote cite="https://lists.wikimedia.org/hyperkitty/list/mediawiki-announce@lists.wikimedia.org/message/V3WXEPXV2DU6WTVEKK4XHW4QXD5OFKD7/">
 	  <p>(T355538, CVE-2024-PENDING) SECURITY: XSS in edit summary parser.</p>
 	  <p>(T357760, CVE-2024-PENDING) SECURITY: Denial of service vector via GET
 	    request to Special:MovePage on pages with thousands of subpages.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <url>https://lists.wikimedia.org/hyperkitty/list/mediawiki-announce@lists.wikimedia.org/message/V3WXEPXV2DU6WTVEKK4XHW4QXD5OFKD7/</url>
     </references>
     <dates>
       <discovery>2024-03-15</discovery>
       <entry>2024-03-31</entry>
     </dates>
   </vuln>
 
   <vuln vid="bdcd041e-5811-4da3-9243-573a9890fdb1">
     <topic>electron{27,28} -- Object lifecycle issue in V8</topic>
     <affects>
       <package>
 	<name>electron27</name>
 	<range><lt>27.3.8</lt></range>
       </package>
       <package>
 	<name>electron28</name>
 	<range><lt>28.2.9</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Electron developers report:</p>
 	<blockquote cite="https://github.com/electron/electron/releases/tag/v27.3.8">
 	  <p>This update fixes the following vulnerability:</p>
 	  <ul>
 	    <li>Security: backported fix for CVE-2024-2625.</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-2625</cvename>
       <url>https://github.com/advisories/GHSA-j7h3-fcrw-g6j8</url>
     </references>
     <dates>
       <discovery>2024-03-28</discovery>
       <entry>2024-03-29</entry>
     </dates>
   </vuln>
 
   <vuln vid="d2992bc2-ed18-11ee-96dc-001b217b3468">
     <topic>Gitlab -- vulnerabilities</topic>
     <affects>
       <package>
 	<name>gitlab-ce</name>
 	<range><ge>16.10.0</ge><lt>16.10.1</lt></range>
 	<range><ge>16.9.0</ge><lt>16.9.3</lt></range>
 	<range><lt>16.8.5</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Gitlab reports:</p>
 	<blockquote cite="https://about.gitlab.com/releases/2024/03/27/security-release-gitlab-16-10-1-released/">
 	  <p>Stored-XSS injected in Wiki page via Banzai pipeline</p>
 	  <p>DOS using crafted emojis</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-6371</cvename>
       <cvename>CVE-2024-2818</cvename>
       <url>https://about.gitlab.com/releases/2024/03/27/security-release-gitlab-16-10-1-released/</url>
     </references>
     <dates>
       <discovery>2024-03-27</discovery>
       <entry>2024-03-28</entry>
     </dates>
   </vuln>
 
   <vuln vid="814af1be-ec63-11ee-8e76-a8a1599412c6">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>123.0.6312.86</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>123.0.6312.86</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2024/03/stable-channel-update-for-desktop_26.html">
 	 <p>This update includes 7 security fixes:</p>
 	 <ul>
 	    <li>[327807820] Critical CVE-2024-2883: Use after free in ANGLE. Reported by Cassidy Kim(@cassidy6564) on 2024-03-03</li>
 	    <li>[328958020] High CVE-2024-2885: Use after free in Dawn. Reported by wgslfuzz on 2024-03-11</li>
 	    <li>[330575496] High CVE-2024-2886: Use after free in WebCodecs. Reported by Seunghyun Lee (@0x10n) of KAIST Hacking Lab, via Pwn2Own 2024 on 2024-03-21</li>
 	    <li>[330588502] High CVE-2024-2887: Type Confusion in WebAssembly. Reported by Manfred Paul, via Pwn2Own 2024 on 2024-03-21</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-2883</cvename>
       <cvename>CVE-2024-2885</cvename>
       <cvename>CVE-2024-2886</cvename>
       <cvename>CVE-2024-2887</cvename>
       <url>https://chromereleases.googleblog.com/2024/03/stable-channel-update-for-desktop_26.html</url>
     </references>
     <dates>
       <discovery>2024-03-26</discovery>
       <entry>2024-03-27</entry>
     </dates>
   </vuln>
 
   <vuln vid="8b3be705-eba7-11ee-99b3-589cfc0f81b0">
     <topic>phpmyfaq -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>phpmyfaq-php81</name>
 	<name>phpmyfaq-php82</name>
 	<name>phpmyfaq-php83</name>
 	<range><lt>3.2.6</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>phpMyFAQ team reports:</p>
 	<blockquote cite="https://www.phpmyfaq.de/security/advisory-2024-03-25">
 	  <p>The phpMyFAQ Team has learned of multiple security issues that'd
 	    been discovered in phpMyFAQ 3.2.5 and earlier. phpMyFAQ contains
 	    cross-site scripting (XSS), SQL injection and bypass
 	    vulnerabilities.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <url>https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-mmh6-5cpf-2c72</url>
       <url>https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-hm8r-95g3-5hj9</url>
       <url>https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-48vw-jpf8-hwqh</url>
       <url>https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-2grw-mc9r-822r</url>
       <url>https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-6p68-36m6-392r</url>
       <url>https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-pwh2-fpfr-x5gf</url>
       <url>https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-q7g6-xfh2-vhpx</url>
       <url>https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-qgxx-4xv5-6hcw</url>
     </references>
     <dates>
       <discovery>2024-03-25</discovery>
       <entry>2024-03-26</entry>
     </dates>
   </vuln>
 
   <vuln vid="f661184a-eb90-11ee-92fc-1c697a616631">
     <topic>emacs -- multiple vulnerabilities</topic>
     <affects>
       <package>
        <name>emacs</name>
        <name>emacs-canna</name>
        <name>emacs-nox</name>
        <range><lt>29.3,3</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>GNU Emacs developers report:</p>
 	<blockquote cite="https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS?h=emacs-29.3">
 	  <p>Emacs 29.3 is an emergency bugfix release intended to fix several security vulnerabilities.</p>
 	<ul>
 	  <li>Arbitrary Lisp code is no longer evaluated as part of turning on Org mode.  This is for security reasons, to avoid evaluating malicious Lisp code.</li>
 	  <li>New buffer-local variable 'untrusted-content'.  When this is non-nil, Lisp programs should treat buffer contents with extra caution.</li>
 	  <li>Gnus now treats inline MIME contents as untrusted.  To get back previous insecure behavior, 'untrusted-content' should be reset to nil in the buffer.</li>
 	  <li>LaTeX preview is now by default disabled for email attachments.  To get back previous insecure behavior, set the variable 'org--latex-preview-when-risky' to a non-nil value.</li>
 	  <li>Org mode now considers contents of remote files to be untrusted.  Remote files are recognized by calling 'file-remote-p'.</li>
 	</ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-30202</cvename>
       <cvename>CVE-2024-30203</cvename>
       <cvename>CVE-2024-30204</cvename>
       <cvename>CVE-2024-30205</cvename>
       <url>https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS?h=emacs-29.3</url>
     </references>
     <dates>
       <discovery>2024-03-24</discovery>
       <entry>2024-03-26</entry>
     </dates>
   </vuln>
 
   <vuln vid="34f98d06-eb56-11ee-8007-6805ca2fa271">
     <topic>quiche -- Multiple Vulnerabilities</topic>
     <affects>
       <package>
        <name>quiche</name>
        <range><lt>0.20.1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Quiche Releases reports:</p>
 	<blockquote cite="https://github.com/cloudflare/quiche/releases/tag/0.20.1">
 	 <p>This release includes 2 security fixes:</p>
 	 <ul>
 	  <li>
 		CVE-2024-1410: Unbounded storage of information related to
 		connection ID retirement, in quiche. Reported by Marten
 		Seeman (@marten-seeman)
 	  </li>
 	  <li>
 		CVE-2024-1765: Unlimited resource allocation by QUIC
 		CRYPTO frames flooding in quiche. Reported by Marten
 		Seeman (@marten-seeman)
 	  </li>
 	 </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-1410</cvename>
       <cvename>CVE-2024-1765</cvename>
       <url>https://github.com/cloudflare/quiche/releases/tag/0.20.1</url>
     </references>
     <dates>
       <discovery>2024-03-12</discovery>
       <entry>2024-03-26</entry>
     </dates>
   </vuln>
 
   <vuln vid="80815c47-e84f-11ee-8e76-a8a1599412c6">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>123.0.6312.58</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>123.0.6312.58</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2024/03/stable-channel-update-for-desktop_19.html">
 	 <p>This update includes 12 security fixes:</p>
 	 <ul>
 	    <li>[327740539] High CVE-2024-2625: Object lifecycle issue in V8. Reported by Ganjiang Zhou(@refrain_areu) of ChaMd5-H1 team on 2024-03-01</li>
 	    <li>[40945098] Medium CVE-2024-2626: Out of bounds read in Swiftshader. Reported by Cassidy Kim(@cassidy6564) on 2023-11-22</li>
 	    <li>[41493290] Medium CVE-2024-2627: Use after free in Canvas. Reported by Anonymous on 2024-01-21</li>
 	    <li>[41487774] Medium CVE-2024-2628: Inappropriate implementation in Downloads. Reported by Ath3r1s on 2024-01-03</li>
 	    <li>[41487721] Medium CVE-2024-2629: Incorrect security UI in iOS. Reported by Muneaki Nishimura (nishimunea) on 2024-01-02</li>
 	    <li>[41481877] Medium CVE-2024-2630: Inappropriate implementation in iOS. Reported by James Lee (@Windowsrcer) on 2023-12-07</li>
 	    <li>[41495878] Low CVE-2024-2631: Inappropriate implementation in iOS. Reported by Ramit Gangwar on 2024-01-29</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-2625</cvename>
       <cvename>CVE-2024-2626</cvename>
       <cvename>CVE-2024-2627</cvename>
       <cvename>CVE-2024-2628</cvename>
       <cvename>CVE-2024-2629</cvename>
       <cvename>CVE-2024-2630</cvename>
       <cvename>CVE-2024-2631</cvename>
       <url>https://chromereleases.googleblog.com/2024/03/stable-channel-update-for-desktop_19.html</url>
     </references>
     <dates>
       <discovery>2024-03-19</discovery>
       <entry>2024-03-22</entry>
     </dates>
   </vuln>
 
   <vuln vid="7a7129ef-e790-11ee-a1c0-0050569f0b83">
     <topic>security/shibboleth-idp -- CAS service SSRF</topic>
     <affects>
       <package>
 	<name>shibboleth-idp</name>
 	<range><ge>4.3.0</ge><lt>4.3.2</lt></range>
 	<range><ge>5.0.0</ge><lt>5.1.1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Shibboleth Developers report:</p>
 	<blockquote cite="https://shibboleth.net/community/advisories/secadv_20240320.txt">
 	  <p>The Identity Provider's CAS support relies on a function in the
 	     Spring Framework to parse CAS service URLs and append the ticket
 	     parameter.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <url>https://shibboleth.net/community/advisories/secadv_20240320.txt</url>
     </references>
     <dates>
       <discovery>2024-03-20</discovery>
       <entry>2024-03-21</entry>
     </dates>
   </vuln>
 
   <vuln vid="a8448963-e6f5-11ee-a784-dca632daf43b">
     <topic>databases/mongodb* -- Improper Certificate Validation</topic>
     <affects>
       <package>
 	<name>mongodb44</name>
 	<range><lt>4.4.29</lt></range>
       </package>
       <package>
 	<name>mongodb50</name>
 	<range><lt>5.0.25</lt></range>
       </package>
       <package>
 	<name>mongodb60</name>
 	<range><lt>6.0.14</lt></range>
       </package>
       <package>
 	<name>mongodb70</name>
 	<range><lt>7.0.6</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>MongoDB, Inc. reports:</p>
 	<blockquote cite="https://jira.mongodb.org/browse/SERVER-72839">
 	  <p>A security vulnerability was found where a server process
 	  running MongoDB 3.2.6 or later will allow incoming connections
 	  to skip peer certificate validation if the server process was
 	  started with TLS enabled (net.tls.mode set to allowTLS,
 	  preferTLS, or requireTLS) and without a net.tls.CAFile
 	  configured (CVE-2024-1351).</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-1351</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-1351</url>
     </references>
     <dates>
       <discovery>2024-03-07</discovery>
       <entry>2024-03-20</entry>
     </dates>
   </vuln>
 
   <vuln vid="05b7180b-e571-11ee-a1c0-0050569f0b83">
     <topic>www/varnish7 -- Denial of Service</topic>
     <affects>
       <package>
 	<name>varnish7</name>
 	<range><lt>7.4.3</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The Varnish Development Team reports:</p>
 	<blockquote cite="https://varnish-cache.org/security/VSV00014.html#vsv00014">
 	<p>A denial of service attack can be performed on Varnish Cacher servers
 	   that have the HTTP/2 protocol turned on. An attacker can let the
 	   servers HTTP/2 connection control flow window run out of credits
 	   indefinitely and prevent progress in the processing of streams,
 	   retaining the associated resources.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-43622</cvename>
       <url>https://varnish-cache.org/security/VSV00014.html#vsv00014</url>
     </references>
     <dates>
       <discovery>2019-04-19</discovery>
       <entry>2024-03-18</entry>
     </dates>
   </vuln>
 
   <vuln vid="0a48e552-e470-11ee-99b3-589cfc0f81b0">
     <topic>amavisd-new -- multipart boundary confusion</topic>
     <affects>
       <package>
 	<name>amavisd-new</name>
 	<range><lt>2.12.3</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The Amavis project reports:</p>
 	<blockquote cite="https://gitlab.com/amavis/amavis/-/raw/v2.12.3/README_FILES/README.CVE-2024-28054">
 	  <p>Emails which consist of multiple parts (`Content-Type: multipart/*`)
 	  incorporate boundary information stating at which point one part ends and the
 	  next part begins.</p>
 	  <p>A boundary is announced by an Content-Type header's `boundary` parameter. To
 	  our current knowledge, RFC2046 and RFC2045 do not explicitly specify how a
 	  parser should handle multiple boundary parameters that contain conflicting
 	  values. As a result, there is no canonical choice which of the values should or
 	  should not be used for mime part decomposition.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-28054</cvename>
       <url>https://gitlab.com/amavis/amavis/-/raw/v2.12.3/README_FILES/README.CVE-2024-28054</url>
     </references>
     <dates>
       <discovery>2024-03-14</discovery>
       <entry>2024-03-17</entry>
     </dates>
   </vuln>
 
   <vuln vid="1ad3d264-e36b-11ee-9c27-40b034429ecf">
     <topic>typo3-{11,12} -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>typo3-11</name>
 	<range><lt>11.5.35</lt></range>
       </package>
       <package>
 	<name>typo3-12</name>
 	<range><lt>12.4.11</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Typo3 developers reports:</p>
 	<blockquote cite="https://typo3.org/article/typo3-1301-12411-and-11535-security-releases-published">
 	  <p>All versions are security releases and contain important security fixes - read the corresponding security advisories here:</p>
 	<ul>
 	  <li>Path Traversal in TYPO3 File Abstraction Layer Storages CVE-2023-30451</li>
 	  <li>Code Execution in TYPO3 Install Tool CVE-2024-22188</li>
 	  <li>Information Disclosure of Hashed Passwords in TYPO3 Backend Forms CVE-2024-25118</li>
 	  <li>Information Disclosure of Encryption Key in TYPO3 Install Tool CVE-2024-25119</li>
 	  <li>Improper Access Control of Resources Referenced by t3:// URI Scheme CVE-2024-25120</li>
 	  <li>Improper Access Control Persisting File Abstraction Layer Entities via Data Handler CVE-2024-25121</li>
 	</ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-30451</cvename>
       <cvename>CVE-2024-22188</cvename>
       <cvename>CVE-2024-25118</cvename>
       <cvename>CVE-2024-25119</cvename>
       <cvename>CVE-2024-25120</cvename>
       <cvename>CVE-2024-25121</cvename>
       <url>https://typo3.org/article/typo3-1301-12411-and-11535-security-releases-published</url>
     </references>
     <dates>
       <discovery>2024-02-13</discovery>
       <entry>2024-03-16</entry>
     </dates>
   </vuln>
 
   <vuln vid="49dd9362-4473-48ae-8fac-e1b69db2dedf">
     <topic>electron{27,28} -- Out of bounds memory access in V8</topic>
     <affects>
       <package>
 	<name>electron27</name>
 	<range><lt>27.3.6</lt></range>
       </package>
       <package>
 	<name>electron28</name>
 	<range><lt>28.2.7</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Electron developers report:</p>
 	<blockquote cite="https://github.com/electron/electron/releases/tag/v27.3.6">
 	  <p>This update fixes the following vulnerability:</p>
 	  <ul>
 	    <li>Security: backported fix for CVE-2024-2173.</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-2173</cvename>
       <url>https://github.com/advisories/GHSA-6hhg-hj7x-7qv8</url>
     </references>
     <dates>
       <discovery>2024-03-13</discovery>
       <entry>2024-03-14</entry>
     </dates>
   </vuln>
 
   <vuln vid="b6dd9d93-e09b-11ee-92fc-1c697a616631">
     <topic>Intel CPUs -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>cpu-microcode-intel</name>
 	<range><lt>20240312</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Intel reports:</p>
 	<blockquote cite="https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00972.html">
 	  <p>2024.1 IPU - Intel Processor Bus Lock Advisory</p>
 
 	  <p>A potential security vulnerability in the bus lock regulator
 	  mechanism for some Intel Processors may allow denial of service. Intel
 	  is releasing firmware updates to mitigate this potential
 	  vulnerability.</p>
 	</blockquote>
 	<blockquote cite="https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00982.html">
 	  <p>2024.1 IPU - Intel Processor Return Predictions Advisory</p>
 
 	  <p>A potential security vulnerability in some Intel Processors may
 	  allow information disclosure.</p>
 	</blockquote>
 	<blockquote cite="https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00898.html">
 	  <p>2024.1 IPU - Intel Atom Processor Advisory</p>
 
 	  <p>A potential security vulnerability in some Intel Atom Processors
 	  may allow information disclosure.</p>
 	</blockquote>
 	<blockquote cite="https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00960.html">
 	  <p>2024.1 IPU - Intel Xeon Processor Advisory</p>
 
 	  <p>A potential security vulnerability in some 3rd and 4th Generation
 	  Intel Xeon Processors when using Intel Software Guard Extensions (SGX)
 	  or Intel Trust Domain Extensions (TDX) may allow escalation of
 	  privilege.</p>
 	</blockquote>
 	<blockquote cite="https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01045.html">
 	  <p>2024.1 IPU OOB - Intel Xeon D Processor Advisory</p>
 
 	  <p>A potential security vulnerability in some Intel Xeon D Processors
 	  with Intel Software Guard Extensions (SGX) may allow information
 	  disclosure.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-39368</cvename>
       <cvename>CVE-2023-38575</cvename>
       <cvename>CVE-2023-28746</cvename>
       <cvename>CVE-2023-22655</cvename>
       <cvename>CVE-2023-43490</cvename>
       <url>https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases/tag/microcode-20240312</url>
     </references>
     <dates>
       <discovery>2023-03-12</discovery>
       <entry>2024-03-12</entry>
     </dates>
   </vuln>
 
   <vuln vid="6d31ef38-df85-11ee-abf1-6c3be5272acd">
     <topic>Grafana -- Data source permission escalation</topic>
     <affects>
       <package>
 	<name>grafana</name>
 	<range><ge>8.5.0</ge><lt>9.5.17</lt></range>
 	<range><ge>10.0.0</ge><lt>10.0.12</lt></range>
 	<range><ge>10.1.0</ge><lt>10.1.8</lt></range>
 	<range><ge>10.2.0</ge><lt>10.2.5</lt></range>
 	<range><ge>10.3.0</ge><lt>10.3.4</lt></range>
       </package>
       <package>
 	<name>grafana9</name>
 	<range><lt>9.5.17</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Grafana Labs reports:</p>
 	<blockquote cite="https://grafana.com/blog/2024/03/07/grafana-security-release-medium-severity-security-fix-for-cve-2024-1442/">
 	  <p>The vulnerability impacts Grafana Cloud and Grafana Enterprise instances,
 	  and it is exploitable if a user who should not be able to access all data
 	  sources is granted permissions to create a data source.</p>
 	  <p>By default, only organization Administrators are allowed to create a data
 	  source and have full access to all data sources. All other users need to be
 	  explicitly granted permission to create a data source, which then means they
 	  could exploit this vulnerability.</p>
 	  <p>When a user creates a data source via the
 	  <a href="https://grafana.com/docs/grafana/latest/developers/http_api/data_source/#create-a-data-source">API</a>,
 	  they can specify data source UID. If the UID is set to an asterisk (*),
 	  the user gains permissions to query, update, and delete all data sources
 	  in the organization. The exploit, however, does not stretch across
 	  organizations — to exploit the vulnerability in several organizations, a user
 	  would need permissions to create data sources in each organization.</p>
 	  <p>The vulnerability comes from a lack of UID validation. When evaluating
 	  permissions, we interpret an asterisk (*) as a wild card for all resources.
 	  Therefore, we should treat it as a reserved value, and not allow the creation
 	  of a resource with the UID set to an asterisk.</p>
 	  <p>The CVSS score for this vulnerability is
 	  <a href="https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:L&amp;version=3.1">6 Medium</a>.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-1442</cvename>
       <url>https://grafana.com/security/security-advisories/cve-2024-1442/</url>
     </references>
     <dates>
       <discovery>2024-02-12</discovery>
       <entry>2024-03-11</entry>
       <modified>2024-03-26</modified>
     </dates>
   </vuln>
 
   <vuln vid="c2ad8700-de25-11ee-9190-84a93843eb75">
     <topic>Unbound -- Denial-of-Service vulnerability</topic>
     <affects>
       <package>
 	<name>unbound</name>
 	<range><gt>1.18.0</gt><lt>1.19.2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>NLNet Labs reports:</p>
 	<blockquote cite="https://www.nlnetlabs.nl/downloads/unbound/CVE-2024-1931.txt">
 	  <p>Unbound 1.18.0 introduced a feature that removes EDE records from
 	    responses with size higher than the client's advertised buffer size.
 	    Before removing all the EDE records however, it would try to see if
 	    trimming the extra text fields on those records would result in an
 	    acceptable size while still retaining the EDE codes. Due to an
 	    unchecked condition, the code that trims the text of the EDE records
 	    could loop indefinitely. This happens when Unbound would reply with
 	    attached EDE information on a positive reply and the client's buffer
 	    size is smaller than the needed space to include EDE records.
 
 	    The vulnerability can only be triggered when the 'ede: yes' option
 	    is used; non default configuration.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-1931</cvename>
       <url>https://www.nlnetlabs.nl/downloads/unbound/CVE-2024-1931.txt</url>
     </references>
     <dates>
       <discovery>2024-03-07</discovery>
       <entry>2024-03-09</entry>
     </dates>
   </vuln>
 
   <vuln vid="e74da31b-276a-4a22-9772-17dd42b97559">
     <topic>electron{27,28} -- vulnerability in libxml2</topic>
     <affects>
       <package>
 	<name>electron27</name>
 	<range><lt>27.3.5</lt></range>
       </package>
       <package>
 	<name>electron28</name>
 	<range><lt>28.2.6</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Electron developers report:</p>
 	<blockquote cite="https://github.com/electron/electron/releases/tag/v27.3.5">
 	  <p>This update fixes the following vulnerability:</p>
 	  <ul>
 	    <li>Security: backported fix for CVE-2024-25062.</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-25062</cvename>
       <url>https://github.com/advisories/GHSA-x77r-6xxm-wjmx</url>
     </references>
     <dates>
       <discovery>2024-03-06</discovery>
       <entry>2024-03-07</entry>
     </dates>
   </vuln>
 
   <vuln vid="b2caae55-dc38-11ee-96dc-001b217b3468">
     <topic>Gitlab -- Vulnerabilities</topic>
     <affects>
       <package>
 	<name>gitlab-ce</name>
 	<range><ge>16.9.0</ge><lt>16.9.2</lt></range>
 	<range><ge>16.8.0</ge><lt>16.8.4</lt></range>
 	<range><ge>11.3.0</ge><lt>16.7.7</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Gitlab reports:</p>
 	<blockquote cite="https://about.gitlab.com/releases/2024/03/06/security-release-gitlab-16-9-2-released/">
 	  <p>Bypassing CODEOWNERS approval allowing to steal protected variables</p>
 	  <p>Guest with manage group access tokens can rotate and see group access token with owner permissions</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-0199</cvename>
       <cvename>CVE-2024-1299</cvename>
       <url>https://about.gitlab.com/releases/2024/03/06/security-release-gitlab-16-9-2-released/</url>
     </references>
     <dates>
       <discovery>2024-03-06</discovery>
       <entry>2024-03-07</entry>
     </dates>
   </vuln>
 
   <vuln vid="b1b039ec-dbfc-11ee-9165-901b0e9408dc">
     <topic>go -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>go122</name>
 	<range><lt>1.22.1</lt></range>
       </package>
       <package>
 	<name>go121</name>
 	<range><lt>1.21.8</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The Go project reports reports:</p>
 	<blockquote cite="https://go.dev/issue/65390">
 	  <p>crypto/x509: Verify panics on certificates with an
 	  unknown public key algorithm</p>
 	  <p>Verifying a certificate chain which contains a
 	  certificate with an unknown public key algorithm will
 	  cause Certificate.Verify to panic.</p>
 	</blockquote>
 	<blockquote cite="https://go.dev/issue/65383">
 	  <p>net/http: memory exhaustion in Request.ParseMultipartForm</p>
 	  <p>When parsing a multipart form (either explicitly with
 	  Request.ParseMultipartForm or implicitly with Request.FormValue,
 	  Request.PostFormValue, or Request.FormFile), limits on the total
 	  size of the parsed form were not applied to the memory consumed
 	  while reading a single form line. This permitted a maliciously
 	  crafted input containing very long lines to cause allocation of
 	  arbitrarily large amounts of memory, potentially leading to memory
 	  exhaustion.</p>
 	</blockquote>
 	<blockquote cite="https://go.dev/issue/65065">
 	  <p>net/http, net/http/cookiejar: incorrect forwarding
 	  of sensitive headers and cookies on HTTP redirect</p>
 	  <p>When following an HTTP redirect to a domain which
 	  is not a subdomain match or exact match of the initial
 	  domain, an http.Client does not forward sensitive headers
 	  such as "Authorization" or "Cookie". For example, a
 	  redirect from foo.com to www.foo.com will forward the
 	  Authorization header, but a redirect to bar.com will not.</p>
 	</blockquote>
 	<blockquote cite="https://go.dev/issue/65697">
 	  <p>html/template: errors returned from MarshalJSON methods
 	  may break template escaping</p>
 	  <p>If errors returned from MarshalJSON methods contain user
 	  controlled data, they may be used to break the contextual
 	  auto-escaping behavior of the html/template package, allowing
 	  for subsequent actions to inject unexpected content into
 	  templates.</p>
 	</blockquote>
 	<blockquote cite="https://go.dev/issue/65083">
 	  <p>net/mail: comments in display names are incorrectly handled</p>
 	  <p>The ParseAddressList function incorrectly handles comments
 	  (text within parentheses) within display names. Since this is a
 	  misalignment with conforming address parsers, it can result in
 	  different trust decisions being made by programs using different
 	  parsers.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-45289</cvename>
       <cvename>CVE-2023-45290</cvename>
       <cvename>CVE-2024-24783</cvename>
       <cvename>CVE-2024-24784</cvename>
       <cvename>CVE-2024-24785</cvename>
       <url>https://groups.google.com/g/golang-announce/c/5pwGVUPoMbg/m/46oA5yPABQAJ</url>
     </references>
     <dates>
       <discovery>2024-03-05</discovery>
       <entry>2024-03-06</entry>
     </dates>
   </vuln>
 
   <vuln vid="fd3401a1-b6df-4577-917a-2c22fee99d34">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>122.0.6261.111</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>122.0.6261.111</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2024/03/stable-channel-update-for-desktop.html">
 	 <p>This update includes 3 security fixes:</p>
 	 <ul>
 	    <li>[325893559] High CVE-2024-2173: Out of bounds memory access in V8. Reported by 5fceb6172bbf7e2c5a948183b53565b9 on 2024-02-19</li>
 	    <li>[325866363] High CVE-2024-2174: Inappropriate implementation in V8. Reported by 5f46f4ee2e17957ba7b39897fb376be8 on 2024-02-19</li>
 	    <li>[325936438] High CVE-2024-2176: Use after free in FedCM. Reported by Anonymous on 2024-02-20</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-2173</cvename>
       <cvename>CVE-2024-2174</cvename>
       <cvename>CVE-2024-2176</cvename>
       <url>https://chromereleases.googleblog.com/2024/03/stable-channel-update-for-desktop.html</url>
     </references>
     <dates>
       <discovery>2024-03-05</discovery>
       <entry>2024-03-06</entry>
     </dates>
   </vuln>
 
   <vuln vid="0ef3398e-da21-11ee-b23a-080027a5b8e9">
     <topic>Django -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>py39-django32</name>
 	<name>py310-django32</name>
 	<name>py311-django32</name>
 	<range><lt>3.2.25</lt></range>
       </package>
       <package>
 	<name>py39-django42</name>
 	<name>py310-django42</name>
 	<name>py311-django42</name>
 	<range><lt>4.2.11</lt></range>
       </package>
       <package>
 	<name>py310-django50</name>
 	<name>py311-django50</name>
 	<range><lt>5.0.3</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Django reports:</p>
 	<blockquote cite="https://www.djangoproject.com/weblog/2024/mar/04/security-releases/">
 	  <p>CVE-2024-27351: Potential regular expression denial-of-service in
 	    django.utils.text.Truncator.words().</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-27351</cvename>
       <url>https://www.djangoproject.com/weblog/2024/mar/04/security-releases/</url>
     </references>
     <dates>
       <discovery>2024-02-25</discovery>
       <entry>2024-03-04</entry>
     </dates>
   </vuln>
 
   <vuln vid="77a6f1c9-d7d2-11ee-bb12-001b217b3468">
     <topic>NodeJS -- Vulnerabilities</topic>
     <affects>
       <package>
 	<name>node</name>
 	<range><ge>21.0.0</ge><lt>21.6.2</lt></range>
 	<range><ge>20.0.0</ge><lt>20.11.1</lt></range>
 	<range><ge>18.0.0</ge><lt>18.19.1</lt></range>
 	<range><ge>16.0.0</ge><lt>16.20.3</lt></range>
       </package>
       <package>
 	<name>node16</name>
 	<range><ge>16.0.0</ge><lt>16.20.3</lt></range>
       </package>
       <package>
 	<name>node18</name>
 	<range><ge>18.0.0</ge><lt>18.19.1</lt></range>
       </package>
       <package>
 	<name>node20</name>
 	<range><ge>20.0.0</ge><lt>20.11.1</lt></range>
       </package>
       <package>
 	<name>node21</name>
 	<range><ge>21.0.0</ge><lt>21.6.2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Node.js reports:</p>
 	<blockquote cite="https://github.com/nodejs/node/blob/main/doc/changelogs/CHANGELOG_V20.md#2024-02-14-version-20111-iron-lts-rafaelgss-prepared-by-marco-ippolito">
 	  <p>Code injection and privilege escalation through Linux capabilities- (High)</p>
 	  <p>http: Reading unprocessed HTTP request with unbounded chunk extension allows DoS attacks- (High)</p>
 	  <p>Path traversal by monkey-patching Buffer internals- (High)</p>
 	  <p>setuid() does not drop all privileges due to io_uring - (High)</p>
 	  <p>Node.js is vulnerable to the Marvin Attack (timing variant of the Bleichenbacher attack against PKCS#1 v1.5 padding) - (Medium)</p>
 	  <p>Multiple permission model bypasses due to improper path traversal sequence sanitization - (Medium)</p>
 	  <p>Improper handling of wildcards in --allow-fs-read and --allow-fs-write (Medium)</p>
 	  <p>Denial of Service by resource exhaustion in fetch() brotli decoding - (Medium)</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-21892</cvename>
       <cvename>CVE-2024-22019</cvename>
       <cvename>CVE-2024-21896</cvename>
       <cvename>CVE-2024-22017</cvename>
       <cvename>CVE-2023-46809</cvename>
       <cvename>CVE-2024-21891</cvename>
       <cvename>CVE-2024-21890</cvename>
       <cvename>CVE-2024-22025</cvename>
       <url>https://github.com/nodejs/node/blob/main/doc/changelogs/CHANGELOG_V20.md#2024-02-14-version-20111-iron-lts-rafaelgss-prepared-by-marco-ippolito</url>
     </references>
     <dates>
       <discovery>2024-02-14</discovery>
       <entry>2024-03-01</entry>
     </dates>
   </vuln>
 
   <vuln vid="3567456a-6b17-41f7-ba7f-5cd3efb2b7c9">
     <topic>electron{27,28} -- Use after free in Mojo</topic>
     <affects>
       <package>
 	<name>electron27</name>
 	<range><lt>27.3.4</lt></range>
       </package>
       <package>
 	<name>electron28</name>
 	<range><lt>28.2.5</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Electron developers report:</p>
 	<blockquote cite="https://github.com/electron/electron/releases/tag/v27.3.4">
 	  <p>This update fixes the following vulnerability:</p>
 	  <ul>
 	    <li>Security: backported fix for CVE-2024-1670.</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-1670</cvename>
       <url>https://github.com/advisories/GHSA-wjv4-j3hc-gxvv</url>
     </references>
     <dates>
       <discovery>2024-02-28</discovery>
       <entry>2024-02-29</entry>
     </dates>
   </vuln>
 
   <vuln vid="31bb1b8d-d6dc-11ee-86bb-a8a1599412c6">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>122.0.6261.94</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>122.0.6261.94</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2024/02/stable-channel-update-for-desktop_27.html">
 	 <p>This update includes 4 security fixes:</p>
 	 <ul>
 	    <li>[324596281] High CVE-2024-1938: Type Confusion in V8. Reported by 5f46f4ee2e17957ba7b39897fb376be8 on 2024-02-11</li>
 	    <li>[323694592] High CVE-2024-1939: Type Confusion in V8. Reported by Bohan Liu (@P4nda20371774) of Tencent Security Xuanwu Lab on 2024-02-05</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-1938</cvename>
       <cvename>CVE-2024-1939</cvename>
       <url>https://chromereleases.googleblog.com/2024/02/stable-channel-update-for-desktop_27.html</url>
     </references>
     <dates>
       <discovery>2024-02-27</discovery>
       <entry>2024-02-29</entry>
     </dates>
   </vuln>
 
   <vuln vid="3dada2d5-4e17-4e39-97dd-14fdbd4356fb">
     <topic>null -- Routinator terminates when RTR connection is reset too quickly after opening</topic>
     <affects>
       <package>
        <name>null</name>
        <range><lt>null</lt></range>
       </package>
     </affects>
     <description>
        <body xmlns="http://www.w3.org/1999/xhtml">
        <p>sep@nlnetlabs.nl reports:</p>
        <blockquote cite="https://www.nlnetlabs.nl/downloads/routinator/CVE-2024-1622.txt">
        <p>Due to a mistake in error checking, Routinator will terminate when
        an incoming RTR connection is reset by the peer too quickly after
        opening.</p>
        </blockquote>
        </body>
     </description>
     <references>
       <cvename>CVE-2024-1622</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-1622</url>
     </references>
     <dates>
       <discovery>2024-02-26</discovery>
       <entry>2024-02-28</entry>
     </dates>
   </vuln>
 
   <vuln vid="02e33cd1-c655-11ee-8613-08002784c58d">
     <topic>curl -- OCSP verification bypass with TLS session reuse</topic>
     <affects>
       <package>
 	<name>curl</name>
 	<range><lt>8.6.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Hiroki Kurosawa reports:</p>
 	<blockquote cite="https://curl.se/docs/CVE-2024-0853.html">
 	  <p>
 	    curl inadvertently kept the SSL session ID for connections
 	    in its cache even when the verify status (OCSP stapling)
 	    test failed. A subsequent transfer to the same hostname
 	    could then succeed if the session ID cache was still
 	    fresh, which then skipped the verify status check.
 	  </p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-0853</cvename>
       <url>https://curl.se/docs/CVE-2024-0853.html</url>
     </references>
     <dates>
       <discovery>2024-01-31</discovery>
       <entry>2024-02-28</entry>
     </dates>
   </vuln>
 
   <vuln vid="5ecfb588-d2f4-11ee-ad82-dbdfaa8acfc2">
     <topic>gitea -- Fix XSS vulnerabilities</topic>
     <affects>
       <package>
 	<name>gitea</name>
 	<range><lt>1.21.6</lt></range>
       </package>
     </affects>
     <description>
        <body xmlns="http://www.w3.org/1999/xhtml">
        <h1>Problem Description:</h1>
        <ul>
        <li>The Wiki page did not sanitize author name</li>
        <li>the reviewer name on a "dismiss review" comment is also affected</li>
        <li>the migration page has some spots</li>
        </ul>
       </body>
     </description>
     <references>
       <url>https://blog.gitea.com/release-of-1.21.6/</url>
     </references>
     <dates>
       <discovery>2024-02-23</discovery>
       <entry>2024-02-24</entry>
     </dates>
   </vuln>
 
   <vuln vid="2a470712-d351-11ee-86bb-a8a1599412c6">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>122.0.6261.57</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>122.0.6261.57</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2024/02/stable-channel-update-for-desktop_20.html">
 	 <p>This update includes 12 security fixes:</p>
 	 <ul>
 	    <li>[41495060] High CVE-2024-1669: Out of bounds memory access in Blink. Reported by Anonymous on 2024-01-26</li>
 	    <li>[41481374] High CVE-2024-1670: Use after free in Mojo. Reported by Cassidy Kim(@cassidy6564) on 2023-12-06</li>
 	    <li>[41487933] Medium CVE-2024-1671: Inappropriate implementation in Site Isolation. Reported by Harry Chen on 2024-01-03</li>
 	    <li>[41485789] Medium CVE-2024-1672: Inappropriate implementation in Content Security Policy. Reported by Georg Felber (TU Wien) &amp; Marco Squarcina (TU Wien) on 2023-12-19</li>
 	    <li>[41490491] Medium CVE-2024-1673: Use after free in Accessibility. Reported by Weipeng Jiang (@Krace) of VRI on 2024-01-11</li>
 	    <li>[40095183] Medium CVE-2024-1674: Inappropriate implementation in Navigation. Reported by David Erceg on 2019-05-27</li>
 	    <li>[41486208] Medium CVE-2024-1675: Insufficient policy enforcement in Download. Reported by Bartłomiej Wacko on 2023-12-21</li>
 	    <li>[40944847] Low CVE-2024-1676: Inappropriate implementation in Navigation. Reported by Khalil Zhani on 2023-11-21</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <url>https://chromereleases.googleblog.com/2024/02/stable-channel-update-for-desktop_20.html</url>
     </references>
     <dates>
       <discovery>2024-02-20</discovery>
       <entry>2024-02-24</entry>
     </dates>
   </vuln>
 
   <vuln vid="6a851dc0-cfd2-11ee-ac09-6c3be5272acd">
     <topic>Grafana -- Email verification is not required after email change</topic>
     <affects>
       <package>
 	<name>grafana</name>
 	<range><lt>9.5.16</lt></range>
 	<range><ge>10.0.0</ge><lt>10.0.11</lt></range>
 	<range><ge>10.1.0</ge><lt>10.1.7</lt></range>
 	<range><ge>10.2.0</ge><lt>10.2.4</lt></range>
 	<range><ge>10.3.0</ge><lt>10.3.3</lt></range>
       </package>
       <package>
 	<name>grafana9</name>
 	<range><lt>9.5.16</lt></range>
       </package>
       <package>
 	<name>grafana10</name>
 	<range><lt>10.0.11</lt></range>
 	<range><ge>10.1.0</ge><lt>10.1.7</lt></range>
 	<range><ge>10.2.0</ge><lt>10.2.4</lt></range>
 	<range><ge>10.3.0</ge><lt>10.3.3</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Grafana Labs reports:</p>
 	<blockquote cite="https://grafana.com/blog/2024/02/14/grafana-security-release-medium-severity-security-fix-for-cve-2023-6152/">
 	  <p>The vulnerability impacts instances where
 	  <a href="https://grafana.com/docs/grafana/latest/setup-grafana/configure-security/configure-authentication/grafana/">
 	  Grafana basic authentication</a> is enabled.</p>
 	  <p>Grafana has a
 	  <a href="https://grafana.com/docs/grafana/latest/setup-grafana/configure-grafana/#verify_email_enabled">
 	  verify_email_enabled</a> configuration option. When this option is enabled,
 	  users are required to confirm their email addresses before the sign-up process
 	  is complete. However, the email is only checked at the time of the sign-up.
 	  No further verification is carried out if a user’s email address is updated
 	  after the initial sign-up. Moreover, Grafana allows using an email address
 	  as the user’s login name, and no verification is ever carried out for this email
 	  address.</p>
 	  <p>This means that even if the
 	  <a href="https://grafana.com/docs/grafana/latest/setup-grafana/configure-grafana/#verify_email_enabled">
 	  verify_email_enabled</a> configuration option is enabled, users can use
 	  unverified email addresses to log into Grafana if the email address
 	  has been changed after the sign up, or if an email address is set as the login
 	  name.</p>
 	  <p>The CVSS score for this vulnerability is [5.4 Medium] (CVSS).</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-6152</cvename>
       <url>https://grafana.com/security/security-advisories/cve-2023-6152/</url>
     </references>
     <dates>
       <discovery>2023-11-10</discovery>
       <entry>2024-02-20</entry>
     </dates>
   </vuln>
 
   <vuln vid="255bf44c-d298-11ee-9c27-40b034429ecf">
     <topic>dns/c-ares -- malformatted file causes application crash</topic>
     <affects>
       <package>
 	<name>c-ares</name>
 	<range><lt>1.27.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>c-ares project reports:</p>
 	<blockquote cite="https://c-ares.org/changelog.html">
 	  <p>Reading malformatted /etc/resolv.conf, /etc/nsswitch.conf or the HOSTALIASES file could result in a crash.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-25629</cvename>
       <url>https://github.com/c-ares/c-ares/security/advisories/GHSA-mg26-v6qh-x48q</url>
     </references>
     <dates>
       <discovery>2024-02-23</discovery>
       <entry>2024-02-23</entry>
     </dates>
   </vuln>
 
   <vuln vid="979dc373-d27d-11ee-8b84-b42e991fc52e">
     <topic>suricata -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>suricata</name>
 	<range><lt>7.0.3</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Suricata team reports:</p>
 	<blockquote cite="https://suricata.io/2024/02/08/suricata-7-0-3-and-6-0-16-released/">
 	  <p>Multiple vulnerabilities fixed in the last release of suricata.</p>
 	</blockquote>
 	<p>No details have been disclosed yet</p>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-23839</cvename>
       <cvename>CVE-2024-23836</cvename>
       <cvename>CVE-2024-23835</cvename>
       <cvename>CVE-2024-24568</cvename>
       <cvename>CVE-2024-23837</cvename>
     </references>
     <dates>
       <discovery>2024-01-22</discovery>
       <entry>2024-02-23</entry>
     </dates>
   </vuln>
 
   <vuln vid="80ad6d6c-b398-457f-b88f-bf6be0bbad44">
     <topic>electron27 -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>electron27</name>
 	<range><lt>27.3.3</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Electron developers report:</p>
 	<blockquote cite="https://github.com/electron/electron/releases/tag/v27.3.3">
 	  <p>This update fixes the following vulnerability:</p>
 	  <ul>
 	    <li>Security: backported fix for CVE-2024-1283.</li>
 	    <li>Security: backported fix for CVE-2024-1284.</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-1283</cvename>
       <url>https://github.com/advisories/GHSA-7mgj-p9v3-3vxr</url>
       <cvename>CVE-2024-1284</cvename>
       <url>https://github.com/advisories/GHSA-pf89-rhhw-xmhp</url>
     </references>
     <dates>
       <discovery>2024-02-21</discovery>
       <entry>2024-02-23</entry>
     </dates>
   </vuln>
 
   <vuln vid="03bf5157-d145-11ee-acee-001b217b3468">
     <topic>Gitlab -- Vulnerabilities</topic>
     <affects>
       <package>
 	<name>gitlab-ce</name>
 	<range><ge>16.9.0</ge><lt>16.9.1</lt></range>
 	<range><ge>16.8.0</ge><lt>16.8.3</lt></range>
 	<range><ge>11.3.0</ge><lt>16.7.6</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Gitlab reports:</p>
 	<blockquote cite="https://about.gitlab.com/releases/2024/02/21/security-release-gitlab-16-9-1-released/">
 	  <p>Stored-XSS in user's profile page</p>
 	  <p>User with "admin_group_members" permission can invite other groups to gain owner access</p>
 	  <p>ReDoS issue in the Codeowners reference extractor</p>
 	  <p>LDAP user can reset password using secondary email and login using direct authentication</p>
 	  <p>Bypassing group ip restriction settings to access environment details of projects through Environments/Operations Dashboard</p>
 	  <p>Users with the Guest role can change Custom dashboard projects settings for projects in the victim group</p>
 	  <p>Group member with sub-maintainer role can change title of shared private deploy keys</p>
 	  <p>Bypassing approvals of CODEOWNERS</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-1451</cvename>
       <cvename>CVE-2023-6477</cvename>
       <cvename>CVE-2023-6736</cvename>
       <cvename>CVE-2024-1525</cvename>
       <cvename>CVE-2023-4895</cvename>
       <cvename>CVE-2024-0861</cvename>
       <cvename>CVE-2023-3509</cvename>
       <cvename>CVE-2024-0410</cvename>
       <url>https://about.gitlab.com/releases/2024/02/21/security-release-gitlab-16-9-1-released/</url>
     </references>
     <dates>
       <discovery>2024-02-21</discovery>
       <entry>2024-02-22</entry>
     </dates>
   </vuln>
 
   <vuln vid="e15ba624-cca8-11ee-84ca-b42e991fc52e">
     <topic>powerdns-recursor -- Multiple Vulnerabilities</topic>
     <affects>
       <package>
 	<name>powerdns-recursor</name>
 	<range><lt>5.0.2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>cve@mitre.org reports:</p>
 	<blockquote cite="https://access.redhat.com/security/cve/CVE-2023-50868">
 	  <p>CVE-2023-50868: The Closest Encloser Proof aspect of the DNS protocol (in RFC 5155
 	  when RFC 9276 guidance is skipped) allows remote attackers to cause
 	  a denial of service (CPU consumption for SHA-1 computations) via
 	    DNSSEC responses in a random subdomain attack, aka the &quot;NSEC3&quot;
 	  issue.  The RFC 5155 specification implies that an algorithm must
 	  perform thousands of iterations of a hash function in certain
 	situations.</p>
       <p>CVE-2023-50387: Certain DNSSEC aspects of the DNS protocol (in RFC 4033, 4034, 4035,
       6840, and related RFCs) allow remote attackers to cause a denial
       of service (CPU consumption) via one or more DNSSEC responses, aka
       the &quot;KeyTrap&quot; issue.  One of the concerns is that, when
       there is a zone with many DNSKEY and RRSIG records, the protocol
       specification implies that an algorithm must evaluate all combinations
 	of DNSKEY and RRSIG records.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-50868</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2023-50868</url>
       <cvename>CVE-2023-50387</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2023-50387</url>
     </references>
     <dates>
       <discovery>2024-02-14</discovery>
       <entry>2024-02-16</entry>
     </dates>
   </vuln>
 
   <vuln vid="c97a4ecf-cc25-11ee-b0ee-0050569f0b83">
     <topic>nginx-devel -- Multiple Vulnerabilities in HTTP/3</topic>
     <affects>
       <package>
 	<name>nginx-devel</name>
 	<range><ge>1.25.0</ge><lt>1.25.4</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The nginx development team reports:</p>
 	<blockquote cite="http://nginx.org/en/security_advisories.html">
 	  <p>When using HTTP/3 a segmentation fault might occur in a
 	  worker process while processing a specially crafted QUIC session.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-24989</cvename>
       <cvename>CVE-2024-24990</cvename>
     </references>
     <dates>
       <discovery>2024-02-14</discovery>
       <entry>2024-02-15</entry>
     </dates>
   </vuln>
 
   <vuln vid="46a29f83-cb47-11ee-b609-002590c1f29c">
     <topic>FreeBSD -- jail(2) information leak</topic>
     <affects>
       <package>
 	<name>FreeBSD-kernel</name>
 	<range><ge>14.0</ge><lt>14.0_5</lt></range>
 	<range><ge>13.2</ge><lt>13.2_10</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<h1>Problem Description:</h1>
 	<p>The jail(2) system call has not limited a visiblity of allocated
 	TTYs (the kern.ttys sysctl).  This gives rise to an information
 	leak about processes outside the current jail.</p>
 	<h1>Impact:</h1>
 	<p>Attacker can get information about TTYs allocated on the host
 	or in other jails.  Effectively, the information printed by "pstat
 	-t" may be leaked.</p>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-25941</cvename>
       <freebsdsa>SA-24:02.tty</freebsdsa>
     </references>
     <dates>
       <discovery>2024-02-14</discovery>
       <entry>2024-02-14</entry>
     </dates>
   </vuln>
 
   <vuln vid="c62285cb-cb46-11ee-b609-002590c1f29c">
     <topic>FreeBSD -- bhyveload(8) host file access</topic>
     <affects>
       <package>
 	<name>FreeBSD</name>
 	<range><ge>14.0</ge><lt>14.0_5</lt></range>
 	<range><ge>13.2</ge><lt>13.2_10</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<h1>Problem Description:</h1>
 	<p>`bhyveload -h &lt;host-path&gt;` may be used to grant loader access
 	to the &lt;host-path&gt; directory tree on the host.  Affected versions
 	of bhyveload(8) do not make any attempt to restrict loader's access
 	to &lt;host-path&gt;, allowing the loader to read any file the host user
 	has access to.</p>
 	<h1>Impact:</h1>
 	<p>In the bhyveload(8) model, the host supplies a userboot.so to
 	boot with, but the loader scripts generally come from the guest
 	image.  A maliciously crafted script could be used to exfiltrate
 	sensitive data from the host accessible to the user running
 	bhyhveload(8), which is often the system root.</p>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-25940</cvename>
       <freebsdsa>SA-24:01.bhyveload</freebsdsa>
     </references>
     <dates>
       <discovery>2024-02-14</discovery>
       <entry>2024-02-14</entry>
     </dates>
   </vuln>
 
   <vuln vid="4edbea45-cb0c-11ee-86bb-a8a1599412c6">
     <topic>chromium -- security fix</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>121.0.6167.184</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>121.0.6167.184</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2024/02/stable-channel-update-for-desktop_13.html">
 	 <p>This update includes 1 security fix.</p>
        </blockquote>
       </body>
     </description>
     <references>
       <url>https://chromereleases.googleblog.com/2024/02/stable-channel-update-for-desktop_13.html</url>
     </references>
     <dates>
       <discovery>2024-02-13</discovery>
       <entry>2024-02-14</entry>
     </dates>
   </vuln>
 
   <vuln vid="21a854cc-cac1-11ee-b7a7-353f1e043d9a">
     <topic>DNSSEC validators -- denial-of-service/CPU exhaustion from KeyTrap and NSEC3 vulnerabilities</topic>
     <affects>
       <package>
 	<name>bind916</name>
 	<range><lt>9.16.48</lt></range>
       </package>
       <package>
 	<name>bind918</name>
 	<range><lt>9.18.24</lt></range>
       </package>
       <package>
 	<name>bind9-devel</name>
 	<range><lt>9.19.21</lt></range>
       </package>
       <package>
 	<name>dnsmasq</name>
 	<range><lt>2.90</lt></range>
       </package>
       <package>
 	<name>dnsmasq-devel</name>
 	<range><lt>2.90</lt></range>
       </package>
       <package>
 	<name>powerdns-recursor</name>
 	<range><lt>5.0.2</lt></range>
       </package>
       <package>
 	<name>unbound</name>
 	<range><lt>1.19.1</lt></range>
       </package>
       <package>
 	<name>FreeBSD</name>
 	<range><ge>14.0</ge><lt>14.0_6</lt></range>
 	<range><ge>13.2</ge><lt>13.2_11</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Simon Kelley reports:</p>
 	<blockquote cite="https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2024q1/017430.html">
 	  <p>If DNSSEC validation is enabled, then an attacker who can force a
 	    DNS server to validate a specially crafted signed domain can use a
 	    lot of CPU in the validator. This only affects dnsmasq installations
 	    with DNSSEC enabled.</p>
 	</blockquote>
 	<p>Stichting NLnet Labs reports:</p>
 	<blockquote cite="https://nlnetlabs.nl/news/2024/Feb/13/unbound-1.19.1-released/">
 	  <p>
 	    The KeyTrap [CVE-2023-50387] vulnerability works by using a
 	    combination of Keys (also colliding Keys), Signatures and number of
 	    RRSETs on a malicious zone. Answers from that zone can force a
 	    DNSSEC validator down a very CPU intensive and time costly
 	    validation path.
 	  </p>
 	  <p>
 	    The NSEC3 [CVE-2023-50868] vulnerability uses specially crafted responses on a
 	    malicious zone with multiple NSEC3 RRSETs to force a DNSSEC
 	    validator down a very CPU intensive and time costly NSEC3 hash
 	    calculation path.
 	  </p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-50387</cvename>
       <cvename>CVE-2023-50868</cvename>
       <url>https://kb.isc.org/docs/cve-2023-50387</url>
       <url>https://kb.isc.org/docs/cve-2023-50868</url>
       <url>https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2024q1/017430.html</url>
       <url>https://blog.powerdns.com/2024/02/13/powerdns-recursor-4-8-6-4-9-3-5-0-2-released</url>
       <url>https://nlnetlabs.nl/news/2024/Feb/13/unbound-1.19.1-released/</url>
       <freebsdsa>SA-24:03.unbound</freebsdsa>
     </references>
     <dates>
       <discovery>2024-02-06</discovery>
       <entry>2024-02-13</entry>
       <modified>2024-04-01</modified>
     </dates>
   </vuln>
 
   <vuln vid="cbfc1591-c8c0-11ee-b45a-589cfc0f81b0">
     <topic>phpmyfaq -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>phpmyfaq-php81</name>
 	<name>phpmyfaq-php82</name>
 	<name>phpmyfaq-php83</name>
 	<range><lt>3.2.5</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>phpMyFAQ team reports:</p>
 	<blockquote cite="https://www.phpmyfaq.de/security/advisory-2024-02-05">
 	  <p>phpMyFAQ doesn't implement sufficient checks to avoid XSS when
 	    storing on attachments filenames. The 'sharing FAQ' functionality
 	    allows any unauthenticated actor to misuse the phpMyFAQ application
 	    to send arbitrary emails to a large range of targets. phpMyFAQ's
 	    user removal page allows an attacker to spoof another user's
 	    detail, and in turn make a compelling phishing case for removing
 	    another user's account.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <url>https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-7m8g-fprr-47fx</url>
       <url>https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-9hhf-xmcw-r3xg</url>
       <url>https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-6648-6g96-mg35</url>
     </references>
     <dates>
       <discovery>2024-02-05</discovery>
       <entry>2024-02-11</entry>
     </dates>
   </vuln>
 
   <vuln vid="f161a5ad-c9bd-11ee-b7a7-353f1e043d9a">
     <topic>openexr -- Heap Overflow in Scanline Deep Data Parsing</topic>
     <affects>
       <package>
 	<name>openexr</name>
 	<range><lt>3.1.12</lt></range>
 	<range><ge>3.2.0</ge><lt>3.2.2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Austin Hackers Anonymous report:</p>
 	<blockquote cite="https://takeonme.org/cves/CVE-2023-5841.html">
 	  <p>Due to a failure in validating the number of scanline samples of a OpenEXR file containing deep scanline data, Academy Software Foundation OpenEXR image parsing library version 3.2.1 and prior is susceptible to a heap-based buffer overflow vulnerability.</p>
 	</blockquote>
 	<blockquote cite="https://github.com/AcademySoftwareFoundation/openexr/releases/tag/v3.2.2">
 	  <p>[...] it is in a routine that is predominantly used for development and
 	    testing. It is not likely to appear in production code.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-5841</cvename>
       <url>https://takeonme.org/cves/CVE-2023-5841.html</url>
       <url>https://github.com/AcademySoftwareFoundation/openexr/releases/tag/v3.2.2</url>
     </references>
     <dates>
       <discovery>2023-10-26</discovery>
       <entry>2024-02-12</entry>
     </dates>
   </vuln>
 
   <vuln vid="388eefc0-c93f-11ee-92ce-4ccc6adda413">
     <topic>readstat -- Heap buffer overflow in readstat_convert</topic>
     <affects>
       <package>
 	<name>readstat</name>
 	<range><lt>1.1.9</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Google reports:</p>
 	<blockquote cite="https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=33991">
 	  <p>A heap buffer overflow exists in readstat_convert.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <url>https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=33991</url>
       <url>https://osv.dev/vulnerability/OSV-2021-732</url>
       <url>https://github.com/WizardMac/ReadStat/issues/285</url>
     </references>
     <dates>
       <discovery>2021-05-05</discovery>
       <entry>2024-02-12</entry>
     </dates>
   </vuln>
 
   <vuln vid="cb22a9a6-c907-11ee-8d1c-40b034429ecf">
     <topic>p5-Spreadsheet-ParseExcel -- Remote Code Execution Vulnerability</topic>
     <affects>
       <package>
 	<name>p5-Spreadsheet-ParseExcel</name>
 	<range><lt>0.66</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Spreadsheet-ParseExcel reports:</p>
 	<blockquote cite="https://nvd.nist.gov/vuln/detail/CVE-2023-7101">
 	  <p>
 	    Spreadsheet::ParseExcel version 0.65 is a Perl module used for parsing Excel files.
 	    Spreadsheet::ParseExcel is vulnerable to an arbitrary code execution (ACE) vulnerability
 	    due to passing unvalidated input from a file into a string-type eval "eval".
 	    Specifically, the issue stems from the evaluation of Number format strings
 	    (not to be confused with printf-style format strings) within the Excel parsing logic.
 	  </p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-7101</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2023-7101</url>
     </references>
     <dates>
       <discovery>2023-12-29</discovery>
       <entry>2024-02-11</entry>
     </dates>
   </vuln>
 
   <vuln vid="19e6dd1b-c6a5-11ee-9cd0-6cc21735f730">
     <topic>postgresql-server -- non-owner REFRESH MATERIALIZED VIEW CONCURRENTLY executes arbitrary SQL</topic>
     <affects>
       <package>
 	<name>postgresql-server</name>
 	<range><lt>15.6</lt></range>
 	<range><lt>14.11</lt></range>
 	<range><lt>13.14</lt></range>
 	<range><lt>12.18</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>PostgreSQL Project reports:</p>
 	<blockquote cite="https://www.postgresql.org/support/security/CVE-2024-0985/">
 	  <p>
 	    One step of a concurrent refresh command was run under
 	    weak security restrictions. If a materialized view's
 	    owner could persuade a superuser or other
 	    high-privileged user to perform a concurrent refresh on
 	    that view, the view's owner could control code executed
 	    with the privileges of the user running REFRESH. The fix
 	    for the vulnerability makes is so that all
 	    user-determined code is run as the view's owner, as
 	    expected.
 	  </p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-0985</cvename>
       <url>https://www.postgresql.org/support/security/CVE-2024-0985/</url>
     </references>
     <dates>
       <discovery>2024-02-08</discovery>
       <entry>2024-02-08</entry>
     </dates>
   </vuln>
 
   <vuln vid="6b2cba6a-c6a5-11ee-97d0-001b217b3468">
     <topic>Gitlab -- vulnerabilities</topic>
     <affects>
       <package>
 	<name>gitlab-ce</name>
 	<range><ge>16.8.0</ge><lt>16.8.2</lt></range>
 	<range><ge>16.7.0</ge><lt>16.7.5</lt></range>
 	<range><ge>13.3.0</ge><lt>16.6.7</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Gitlab reports:</p>
 	<blockquote cite="https://about.gitlab.com/releases/2024/02/07/security-release-gitlab-16-8-2-released/">
 	  <p>Restrict group access token creation for custom roles</p>
 	  <p>Project maintainers can bypass group's scan result policy block_branch_modification setting</p>
 	  <p>ReDoS in CI/CD Pipeline Editor while verifying Pipeline syntax</p>
 	  <p>Resource exhaustion using GraphQL vulnerabilitiesCountByDay</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-1250</cvename>
       <cvename>CVE-2023-6840</cvename>
       <cvename>CVE-2023-6386</cvename>
       <cvename>CVE-2024-1066</cvename>
       <url>https://about.gitlab.com/releases/2024/02/07/security-release-gitlab-16-8-2-released/</url>
     </references>
     <dates>
       <discovery>2024-02-07</discovery>
       <entry>2024-02-08</entry>
     </dates>
   </vuln>
 
   <vuln vid="33ba2241-c68e-11ee-9ef3-001999f8d30b">
     <topic>Composer -- Code execution and possible privilege escalation</topic>
     <affects>
       <package>
 	<name>php81-composer</name>
 	<range><lt>2.7.0</lt></range>
       </package>
       <package>
 	<name>php82-composer</name>
 	<range><lt>2.7.0</lt></range>
       </package>
       <package>
 	<name>php83-composer</name>
 	<range><lt>2.7.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Copmposer reports:</p>
 	<blockquote cite="https://github.com/composer/composer/security/advisories/GHSA-7c6p-848j-wh5h">
 	  <p>Code execution and possible privilege escalation via
 	  compromised InstalledVersions.php or installed.php.</p>
 	  <p>Several files within the local working directory are
 	  included during the invocation of Composer and in the
 	  context of the executing user.</p>
 	  <p>As such, under certain conditions arbitrary code
 	  execution may lead to local privilege escalation, provide
 	  lateral user movement or malicious code execution when
 	  Composer is invoked within a directory with tampered
 	  files.</p>
 	  <p>All Composer CLI commands are affected, including
 	  composer.phar's self-update.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-24821</cvename>
       <url>https://github.com/composer/composer/security/advisories/GHSA-7c6p-848j-wh5h</url>
     </references>
     <dates>
       <discovery>2024-02-08</discovery>
       <entry>2024-02-08</entry>
     </dates>
   </vuln>
 
   <vuln vid="43768ff3-c683-11ee-97d0-001b217b3468">
     <topic>Libgit2 -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>eza</name>
 	<range><lt>0.18.2</lt></range>
       </package>
       <package>
 	<name>libgit2</name>
 	<range><ge>1.7.0</ge><lt>1.7.2</lt></range>
 	<range><lt>1.6.5</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Git community reports:</p>
 	<blockquote cite="https://github.com/libgit2/libgit2/releases/tag/v1.7.2">
 	  <p>A bug in git_revparse_single is fixed that could have caused the function to enter an infinite loop given well-crafted inputs, potentially causing a Denial of Service attack in the calling application</p>
 	  <p>A bug in git_revparse_single is fixed that could have caused the function to enter an infinite loop given well-crafted inputs, potentially causing a Denial of Service attack in the calling application</p>
 	  <p>A bug in the smart transport negotiation could have caused an out-of-bounds read when a remote server did not advertise capabilities</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-24577</cvename>
       <url>https://github.com/libgit2/libgit2/releases/tag/v1.7.2</url>
     </references>
     <dates>
       <discovery>2024-02-06</discovery>
       <entry>2024-02-08</entry>
       <modified>2024-02-14</modified>
     </dates>
   </vuln>
 
   <vuln vid="19047673-c680-11ee-86bb-a8a1599412c6">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>121.0.6167.160</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>121.0.6167.160</lt></range>
       </package>
       <package>
        <name>qt5-webengine</name>
        <range><lt>5.15.16.p5_5</lt></range>
       </package>
       <package>
        <name>qt6-webengine</name>
        <range><lt>6.6.1_5</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2024/02/stable-channel-update-for-desktop.html">
 	 <p>This update includes 3 security fixes:</p>
 	 <ul>
 	    <li>[41494539] High CVE-2024-1284: Use after free in Mojo. Reported by Anonymous on 2024-01-25</li>
 	    <li>[41494860] High CVE-2024-1283: Heap buffer overflow in Skia. Reported by Jorge Buzeti (@r3tr074) on 2024-01-25</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-1284</cvename>
       <cvename>CVE-2024-1283</cvename>
       <url>https://chromereleases.googleblog.com/2024/02/stable-channel-update-for-desktop.html</url>
     </references>
     <dates>
       <discovery>2024-02-06</discovery>
       <entry>2024-02-08</entry>
     </dates>
   </vuln>
 
   <vuln vid="68ae70c5-c5e5-11ee-9768-08002784c58d">
     <topic>clamav -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>clamav</name>
 	<range><lt>1.2.2,1</lt></range>
       </package>
       <package>
 	<name>clamav-lts</name>
 	<range><lt>1.0.5,1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The ClamAV project reports:</p>
 	<blockquote cite="https://blog.clamav.net/2023/11/clamav-130-122-105-released.html">
 	  <dl>
 	    <dt>CVE-2024-20290</dt>
 	    <dd>
 	      A vulnerability in the OLE2 file format parser of ClamAV
 	      could allow an unauthenticated, remote attacker to cause
 	      a denial of service (DoS) condition on an affected
 	      device. This vulnerability is due to an incorrect check
 	      for end-of-string values during scanning, which may
 	      result in a heap buffer over-read. An attacker could
 	      exploit this vulnerability by submitting a crafted file
 	      containing OLE2 content to be scanned by ClamAV on an
 	      affected device. A successful exploit could allow the
 	      attacker to cause the ClamAV scanning process to
 	      terminate, resulting in a DoS condition on the affected
 	      software and consuming available system resources.
 	    </dd>
 	    <dt>CVE-2024-20328</dt>
 	    <dd>
 	      Fixed a possible command injection vulnerability in the
 	      &quot;VirusEvent&quot; feature of ClamAV's ClamD
 	      service. To fix this issue, we disabled the '%f' format
 	      string parameter.	 ClamD administrators may continue to
 	      use the `CLAM_VIRUSEVENT_FILENAME` environment variable,
 	      instead of '%f'. But you should do so only from within
 	      an executable, such as a Python script, and not directly
 	      in the clamd.conf &quot;VirusEvent&quot; command.
 	    </dd>
 	  </dl>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-20290</cvename>
       <cvename>CVE-2024-20328</cvename>
       <url>https://blog.clamav.net/2023/11/clamav-130-122-105-released.html</url>
     </references>
     <dates>
       <discovery>2024-02-07</discovery>
       <entry>2024-02-07</entry>
     </dates>
   </vuln>
 
   <vuln vid="e0f6215b-c59e-11ee-a6db-080027a5b8e9">
     <topic>Django -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>py39-django32</name>
 	<name>py310-django32</name>
 	<name>py311-django32</name>
 	<range><lt>3.2.24</lt></range>
       </package>
       <package>
 	<name>py39-django42</name>
 	<name>py310-django42</name>
 	<name>py311-django42</name>
 	<range><lt>4.2.8</lt></range>
       </package>
       <package>
 	<name>py311-django50</name>
 	<range><lt>5.0.2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Django reports:</p>
 	<blockquote cite="https://www.djangoproject.com/weblog/2024/feb/06/security-releases/">
 	  <p>CVE-2024-24680:Potential denial-of-service in intcomma template filter.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-24680</cvename>
       <url>https://www.djangoproject.com/weblog/2024/feb/06/security-releases/</url>
     </references>
     <dates>
       <discovery>2024-01-09</discovery>
       <entry>2024-02-07</entry>
     </dates>
   </vuln>
 
   <vuln vid="dc9e5237-c197-11ee-86bb-a8a1599412c6">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>121.0.6167.139</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>121.0.6167.139</lt></range>
       </package>
       <package>
        <name>qt5-webengine</name>
        <range><lt>5.15.16.p5_5</lt></range>
       </package>
       <package>
        <name>qt6-webengine</name>
        <range><lt>6.6.1_5</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2024/01/stable-channel-update-for-desktop_30.html">
 	 <p>This update includes 4 security fixes:</p>
 	 <ul>
 	    <li>[1511567] High CVE-2024-1060: Use after free in Canvas. Reported by Anonymous on 2023-12-14</li>
 	    <li>[1514777] High CVE-2024-1059: Use after free in WebRTC. Reported by Cassidy Kim(@cassidy6564) on 2023-12-29</li>
 	    <li>[1511085] High CVE-2024-1077: Use after free in Network. Reported by Microsoft Security Research Center on 2023-12-13</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-1060</cvename>
       <cvename>CVE-2024-1059</cvename>
       <cvename>CVE-2024-1077</cvename>
       <url>https://chromereleases.googleblog.com/2024/01/stable-channel-update-for-desktop_30.html</url>
     </references>
     <dates>
       <discovery>2024-01-30</discovery>
       <entry>2024-02-02</entry>
     </dates>
   </vuln>
 
   <vuln vid="72d6d757-c197-11ee-86bb-a8a1599412c6">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>121.0.6167.85</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>121.0.6167.85</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2024/01/stable-channel-update-for-desktop_23.html">
 	 <p>This update includes 17 security fixes:</p>
 	 <ul>
 	    <li>[1484394] High CVE-2024-0812: Inappropriate implementation in Accessibility. Reported by Anonymous on 2023-09-19</li>
 	    <li>[1504936] High CVE-2024-0808: Integer underflow in WebUI. Reported by Lyra Rebane (rebane2001) on 2023-11-24</li>
 	    <li>[1496250] Medium CVE-2024-0810: Insufficient policy enforcement in DevTools. Reported by Shaheen Fazim on 2023-10-26</li>
 	    <li>[1463935] Medium CVE-2024-0814: Incorrect security UI in Payments. Reported by Muneaki Nishimura (nishimunea) on 2023-07-11</li>
 	    <li>[1477151] Medium CVE-2024-0813: Use after free in Reading Mode. Reported by @retsew0x01 on 2023-08-30</li>
 	    <li>[1505176] Medium CVE-2024-0806: Use after free in Passwords. Reported by 18楼梦想改造家 on 2023-11-25</li>
 	    <li>[1514925] Medium CVE-2024-0805: Inappropriate implementation in Downloads. Reported by Om Apip on 2024-01-01</li>
 	    <li>[1515137] Medium CVE-2024-0804: Insufficient policy enforcement in iOS Security UI. Reported by Narendra Bhati of Suma Soft Pvt. Ltd. Pune (India)  on 2024-01-03</li>
 	    <li>[1494490] Low CVE-2024-0811: Inappropriate implementation in Extensions API. Reported by Jann Horn of Google Project Zero on 2023-10-21</li>
 	    <li>[1497985] Low CVE-2024-0809: Inappropriate implementation in Autofill. Reported by Ahmed ElMasry on 2023-10-31</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-0812</cvename>
       <cvename>CVE-2024-0808</cvename>
       <cvename>CVE-2024-0810</cvename>
       <cvename>CVE-2024-0814</cvename>
       <cvename>CVE-2024-0813</cvename>
       <cvename>CVE-2024-0806</cvename>
       <cvename>CVE-2024-0805</cvename>
       <cvename>CVE-2024-0804</cvename>
       <cvename>CVE-2024-0811</cvename>
       <cvename>CVE-2024-0809</cvename>
       <url>https://chromereleases.googleblog.com/2024/01/stable-channel-update-for-desktop_23.html</url>
     </references>
     <dates>
       <discovery>2024-01-23</discovery>
       <entry>2024-02-02</entry>
     </dates>
   </vuln>
 
   <vuln vid="13a8c4bf-cb2b-48ec-b49c-a3875c72b3e8">
     <topic>electron{26,27,28} -- Use after free in Web Audio</topic>
     <affects>
       <package>
 	<name>electron26</name>
 	<range><lt>26.6.8</lt></range>
       </package>
       <package>
 	<name>electron27</name>
 	<range><lt>27.3.1</lt></range>
       </package>
       <package>
 	<name>electron28</name>
 	<range><lt>28.2.1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Electron developers reports:</p>
 	<blockquote cite="https://github.com/electron/electron/releases/tag/v26.6.8">
 	  <p>This update fixes the following vulnerability:</p>
 	  <ul>
 	    <li>Security: backported fix for CVE-2024-0807.</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-0807</cvename>
       <url>https://github.com/advisories/GHSA-hjm7-v5pw-x89r</url>
     </references>
     <dates>
       <discovery>2024-01-31</discovery>
       <entry>2024-02-01</entry>
     </dates>
   </vuln>
 
   <vuln vid="bbcb1584-c068-11ee-bdd6-4ccc6adda413">
     <topic>qt6-webengine -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>qt5-webengine</name>
 	<range><lt>5.15.16.p5_5</lt></range>
       </package>
       <package>
 	<name>qt6-webengine</name>
 	<range><lt>6.6.1_4</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Qt qtwebengine-chromium repo reports:</p>
 	<blockquote cite="https://code.qt.io/cgit/qt/qtwebengine-chromium.git/log/?h=112-based">
 	  <p>Backports for 3 security bugs in Chromium:</p>
 	  <ul>
 	    <li>[1505080] High CVE-2024-0807: Use after free in WebAudio</li>
 	    <li>[1504936] Critical CVE-2024-0808: Integer underflow in WebUI</li>
 	    <li>[1496250] Medium CVE-2024-0810: Insufficient policy enforcement in DevTools</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-0807</cvename>
       <cvename>CVE-2024-0808</cvename>
       <cvename>CVE-2024-0810</cvename>
       <url>https://code.qt.io/cgit/qt/qtwebengine-chromium.git/log/?h=112-based</url>
     </references>
     <dates>
       <discovery>2024-01-30</discovery>
       <entry>2024-01-31</entry>
     </dates>
   </vuln>
 
   <vuln vid="10dee731-c069-11ee-9190-84a93843eb75">
     <topic>OpenSSL -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>openssl</name>
 	<range><lt>3.0.13,1</lt></range>
       </package>
       <package>
 	<name>openssl-quictls</name>
 	<range><lt>3.0.13</lt></range>
       </package>
       <package>
 	<name>openssl31</name>
 	<range><lt>3.1.5</lt></range>
       </package>
       <package>
 	<name>openssl31-quictls</name>
 	<range><lt>3.1.5</lt></range>
       </package>
       <package>
 	<name>openssl32</name>
 	<range><lt>3.2.1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The OpenSSL project reports:</p>
 	<blockquote cite="https://www.openssl.org/news/secadv/20240125.txt">
 	  <p>Excessive time spent checking invalid RSA public keys (CVE-2023-6237)</p>
 	  <p>PKCS12 Decoding crashes (CVE-2024-0727)</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-0727</cvename>
       <cvename>CVE-2023-6237</cvename>
       <url>https://www.openssl.org/news/secadv/20240125.txt</url>
       <url>https://www.openssl.org/news/secadv/20240115.txt</url>
       <url>https://www.openssl.org/news/openssl-3.0-notes.html</url>
       <url>https://www.openssl.org/news/openssl-3.1-notes.html</url>
       <url>https://www.openssl.org/news/openssl-3.2-notes.html</url>
     </references>
     <dates>
       <discovery>2024-01-30</discovery>
       <entry>2024-01-31</entry>
     </dates>
   </vuln>
 
   <vuln vid="67c2eb06-5579-4595-801b-30355be24654">
     <topic>lizard -- Negative size passed to memcpy resulting in memory corruption</topic>
     <affects>
       <package>
 	<name>lizard</name>
 	<range><lt>1.0_1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>cve@mitre.org reports:</p>
 	<blockquote cite="https://github.com/inikep/lizard/issues/16">
 	  <p>In Lizard v1.0 and LZ5 v2.0 (the prior release, before the product
 	was renamed), there is an unchecked buffer size during a memcpy in
 	the Lizard_decompress_LIZv1 function (lib/lizard_decompress_liz.h).
 	Remote attackers can leverage this vulnerability to cause a denial
 	of service via a crafted input file, as well as achieve remote code
 	execution.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2018-11498</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2018-11498</url>
     </references>
     <dates>
       <discovery>2018-05-26</discovery>
       <entry>2024-01-31</entry>
     </dates>
   </vuln>
 
   <vuln vid="a25b323a-bed9-11ee-bdd6-4ccc6adda413">
     <topic>qt6-webengine -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>qt6-webengine</name>
 	<range><lt>6.6.1_3</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Qt qtwebengine-chromium repo reports:</p>
 	<blockquote cite="https://code.qt.io/cgit/qt/qtwebengine-chromium.git/log/?h=112-based">
 	  <p>Backports for 15 security bugs in Chromium:</p>
 	  <ul>
 	    <li>[1505053] High CVE-2023-6345: Integer overflow in Skia</li>
 	    <li>[1500856] High CVE-2023-6346: Use after free in WebAudio</li>
 	    <li>[1494461] High CVE-2023-6347: Use after free in Mojo</li>
 	    <li>[1501326] High CVE-2023-6702: Type Confusion in V8</li>
 	    <li>[1502102] High CVE-2023-6703: Use after free in Blink</li>
 	    <li>[1505708] High CVE-2023-6705: Use after free in WebRTC</li>
 	    <li>[1500921] High CVE-2023-6706: Use after free in FedCM</li>
 	    <li>[1513170] High CVE-2023-7024: Heap buffer overflow in WebRTC</li>
 	    <li>[1501798] High CVE-2024-0222: Use after free in ANGLE</li>
 	    <li>[1505009] High CVE-2024-0223: Heap buffer overflow in ANGLE</li>
 	    <li>[1505086] High CVE-2024-0224: Use after free in WebAudio</li>
 	    <li>[1506923] High CVE-2024-0225: Use after free in WebGPU</li>
 	    <li>[1513379] High CVE-2024-0333: Insufficient data validation in Extensions</li>
 	    <li>[1507412] High CVE-2024-0518: Type Confusion in V8</li>
 	    <li>[1517354] High CVE-2024-0519: Out of bounds memory access in V8</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-6345</cvename>
       <cvename>CVE-2023-6346</cvename>
       <cvename>CVE-2023-6347</cvename>
       <cvename>CVE-2023-6702</cvename>
       <cvename>CVE-2023-6703</cvename>
       <cvename>CVE-2023-6705</cvename>
       <cvename>CVE-2023-6706</cvename>
       <cvename>CVE-2023-7024</cvename>
       <cvename>CVE-2024-0222</cvename>
       <cvename>CVE-2024-0223</cvename>
       <cvename>CVE-2024-0224</cvename>
       <cvename>CVE-2024-0225</cvename>
       <cvename>CVE-2024-0333</cvename>
       <cvename>CVE-2024-0518</cvename>
       <cvename>CVE-2024-0519</cvename>
       <url>https://code.qt.io/cgit/qt/qtwebengine-chromium.git/log/?h=112-based</url>
     </references>
     <dates>
       <discovery>2024-01-08</discovery>
       <entry>2024-01-29</entry>
     </dates>
   </vuln>
 
   <vuln vid="a11e7dd1-bed4-11ee-bdd6-4ccc6adda413">
     <topic>qt5-webengine -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>qt5-webengine</name>
 	<range><lt>5.15.16.p5_4</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Qt qtwebengine-chromium repo reports:</p>
 	<blockquote cite="https://code.qt.io/cgit/qt/qtwebengine-chromium.git/log/?h=87-based">
 	  <p>Backports for 8 security bugs in Chromium:</p>
 	  <ul>
 	    <li>[1505053] High CVE-2023-6345: Integer overflow in Skia</li>
 	    <li>[1501326] High CVE-2023-6702: Type Confusion in V8</li>
 	    <li>[1513170] High CVE-2023-7024: Heap buffer overflow in WebRTC</li>
 	    <li>[1501798] High CVE-2024-0222: Use after free in ANGLE</li>
 	    <li>[1505086] High CVE-2024-0224: Use after free in WebAudio</li>
 	    <li>[1513379] High CVE-2024-0333: Insufficient data validation in Extensions</li>
 	    <li>[1507412] High CVE-2024-0518: Type Confusion in V8</li>
 	    <li>[1517354] High CVE-2024-0519: Out of bounds memory access in V8</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-6345</cvename>
       <cvename>CVE-2023-6702</cvename>
       <cvename>CVE-2023-7024</cvename>
       <cvename>CVE-2024-0222</cvename>
       <cvename>CVE-2024-0224</cvename>
       <cvename>CVE-2024-0333</cvename>
       <cvename>CVE-2024-0518</cvename>
       <cvename>CVE-2024-0519</cvename>
       <url>https://code.qt.io/cgit/qt/qtwebengine-chromium.git/log/?h=87-based</url>
     </references>
     <dates>
       <discovery>2024-01-08</discovery>
       <entry>2024-01-29</entry>
     </dates>
   </vuln>
 
   <vuln vid="b5e22ec5-bc4b-11ee-b0b5-b42e991fc52e">
     <topic>rclone -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>rclone</name>
 	<range><lt>1.65.1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Multiple vulnerabilities in ssh and golang</p>
 	<blockquote cite="https://github.com/go-resty/resty/commit/577fed8730d79f583eb48dfc81674164e1fc471e">
 	  <ul>
 	    <li>
 	      CVE-2023-45286: HTTP request body disclosure in go-resty
 	      disclosure across requests.
 	    </li>
 	    <li>
 	      CVE-2023-48795: The SSH transport protocol with certain
 	      OpenSSH extensions, found in OpenSSH before 9.6 and
 	      other products, allows remote attackers to bypass
 	      integrity checks.
 	    </li>
 	  </ul>
   </blockquote>
   </body>
     </description>
     <references>
       <cvename>CVE-2023-45286</cvename>
       <cvename>CVE-2023-48795</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2023-45286</url>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2023-48795</url>
     </references>
     <dates>
       <discovery>2023-11-28</discovery>
       <entry>2024-01-26</entry>
     </dates>
   </vuln>
 
   <vuln vid="61fe903b-bc2e-11ee-b06e-001b217b3468">
     <topic>Gitlab -- vulnerabilities</topic>
     <affects>
       <package>
 	<name>gitlab-ce</name>
 	<range><ge>16.8.0</ge><lt>16.8.1</lt></range>
 	<range><ge>16.7.0</ge><lt>16.7.4</lt></range>
 	<range><ge>16.6.0</ge><lt>16.6.6</lt></range>
 	<range><ge>12.7.0</ge><lt>16.5.8</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Gitlab reports:</p>
 	<blockquote cite="https://about.gitlab.com/releases/2024/01/25/critical-security-release-gitlab-16-8-1-released/">
 	  <p>Arbitrary file write while creating workspace</p>
 	  <p>ReDoS in Cargo.toml blob viewer</p>
 	  <p>Arbitrary API PUT requests via HTML injection in user's name</p>
 	  <p>Disclosure of the public email in Tags RSS Feed</p>
 	  <p>Non-Member can update MR Assignees of owned MRs</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-0402</cvename>
       <cvename>CVE-2023-6159</cvename>
       <cvename>CVE-2023-5933</cvename>
       <cvename>CVE-2023-5612</cvename>
       <cvename>CVE-2024-0456</cvename>
       <url>https://about.gitlab.com/releases/2024/01/25/critical-security-release-gitlab-16-8-1-released/</url>
     </references>
     <dates>
       <discovery>2024-01-25</discovery>
       <entry>2024-01-26</entry>
     </dates>
   </vuln>
 
   <vuln vid="8b03d274-56ca-489e-821a-cf32f07643f0">
     <topic>jenkins -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>jenkins</name>
 	<range><lt>2.422</lt></range>
       </package>
       <package>
 	<name>jenkins-lts</name>
 	<range><lt>2.426.3</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Jenkins Security Advisory:</p>
 	<blockquote cite="https://www.jenkins.io/security/advisory/2024-01-24/">
 	  <h1>Description</h1>
 	  <h5>(Critical) SECURITY-3314 / CVE-2024-23897</h5>
 	  <p>Arbitrary file read vulnerability through the CLI can lead to RCE</p>
 	  <h1>Description</h1>
 	  <h5>(High) SECURITY-3315 / CVE-2024-23898</h5>
 	  <p>Cross-site WebSocket hijacking vulnerability in the CLI</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-23897</cvename>
       <cvename>CVE-2024-23898</cvename>
       <url>https://www.jenkins.io/security/advisory/2024-01-24/</url>
     </references>
     <dates>
       <discovery>2024-01-24</discovery>
       <entry>2024-01-24</entry>
     </dates>
   </vuln>
 
   <vuln vid="9532a361-b84d-11ee-b0d7-84a93843eb75">
     <topic>TinyMCE -- mXSS in multiple plugins</topic>
     <affects>
       <package>
 	<name>tinymce</name>
 	<range><lt>6.7.3</lt></range>
       </package>
       <package>
 	<name>roundcube</name>
 	<range><lt>1.6.6,1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>TinyMCE reports:</p>
 	<blockquote cite="https://github.com/tinymce/tinymce/security/advisories/GHSA-v626-r774-j7f8">
 	  <p>Special characters in unescaped text nodes can trigger mXSS
 	    when using TinyMCE undo/redo, getContentAPI, resetContentAPI,
 	    and Autosave plugin</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-48219</cvename>
       <url>https://github.com/tinymce/tinymce/security/advisories/GHSA-v626-r774-j7f8</url>
       <url>https://github.com/roundcube/roundcubemail/releases/tag/1.6.6</url>
     </references>
     <dates>
       <discovery>2023-11-15</discovery>
       <entry>2024-01-23</entry>
     </dates>
   </vuln>
 
   <vuln vid="fedf7e71-61bd-49ec-aaf0-6da14bdbb319">
     <topic>zeek -- potential DoS vulnerability</topic>
     <affects>
       <package>
 	<name>zeek</name>
 	<range><lt>6.0.3</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Tim Wojtulewicz of Corelight reports:</p>
 	<blockquote cite="https://github.com/zeek/zeek/releases/tag/v6.0.3">
 	  <p>A specially-crafted series of packets containing nested
 	  MIME entities can cause Zeek to spend large amounts of
 	  time parsing the entities. </p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <url>https://github.com/zeek/zeek/releases/tag/v6.0.3</url>
     </references>
     <dates>
       <discovery>2024-01-22</discovery>
       <entry>2024-01-22</entry>
     </dates>
   </vuln>
 
   <vuln vid="2264566a-a890-46eb-a895-7881dd220bd0">
     <topic>electron26 -- Out of bounds memory access in V8</topic>
     <affects>
       <package>
 	<name>electron26</name>
 	<range><lt>26.6.7</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Electron developers report:</p>
 	<blockquote cite="https://github.com/electron/electron/releases/tag/v26.6.7">
 	  <p>This update fixes the following vulnerability:</p>
 	  <ul>
 	    <li>Security: backported fix for CVE-2024-0519.</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-0519</cvename>
       <url>https://github.com/advisories/GHSA-vg6w-jr5m-86c8</url>
     </references>
     <dates>
       <discovery>2024-01-18</discovery>
       <entry>2024-01-19</entry>
     </dates>
   </vuln>
 
   <vuln vid="a8326b61-eda0-4c03-9a5b-49ebd8f41c1a">
     <topic>electron{26,27} -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>electron26</name>
 	<range><lt>26.6.6</lt></range>
       </package>
       <package>
 	<name>electron27</name>
 	<range><lt>27.2.4</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Electron developers report:</p>
 	<blockquote cite="https://github.com/electron/electron/releases/tag/v27.2.3">
 	  <p>This update fixes the following vulnerabilities:</p>
 	  <ul>
 	    <li>Security: backported fix for CVE-2024-0518.</li>
 	    <li>Security: backported fix for CVE-2024-0517.</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-0518</cvename>
       <url>https://github.com/advisories/GHSA-4pvg-f3m8-ff3j</url>
       <cvename>CVE-2024-0517</cvename>
       <url>https://github.com/advisories/GHSA-v39r-662x-j524</url>
     </references>
     <dates>
       <discovery>2024-01-17</discovery>
       <entry>2024-01-17</entry>
       <modified>2024-01-18</modified>
     </dates>
   </vuln>
 
   <vuln vid="1bc07be0-b514-11ee-86bb-a8a1599412c6">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>120.0.6099.224</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>120.0.6099.224</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2024/01/stable-channel-update-for-desktop_16.html">
 	 <p>This update includes 4 security fixes:</p>
 	 <ul>
 	    <li>[1515930] High CVE-2024-0517: Out of bounds write in V8. Reported by Toan (suto) Pham of Qrious Secure on 2024-01-06</li>
 	    <li>[1507412] High CVE-2024-0518: Type Confusion in V8. Reported by Ganjiang Zhou(@refrain_areu) of ChaMd5-H1 team on 2023-12-03</li>
 	    <li>[1517354] High CVE-2024-0519: Out of bounds memory access in V8. Reported by Anonymous on 2024-01-11</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-0517</cvename>
       <cvename>CVE-2024-0518</cvename>
       <cvename>CVE-2024-0519</cvename>
       <url>https://chromereleases.googleblog.com/2024/01/stable-channel-update-for-desktop_16.html</url>
     </references>
     <dates>
       <discovery>2024-01-16</discovery>
       <entry>2024-01-17</entry>
     </dates>
   </vuln>
 
   <vuln vid="7467c611-b490-11ee-b903-001fc69cd6dc">
     <topic>xorg server -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>xorg-server</name>
 	<name>xephyr</name>
 	<name>xorg-vfbserver</name>
 	<range><lt>21.1.11,1</lt></range>
       </package>
       <package>
 	<name>xorg-nextserver</name>
 	<range><lt>21.1.11,2</lt></range>
       </package>
       <package>
 	<name>xwayland</name>
 	<range><lt>23.2.4</lt></range>
       </package>
       <package>
 	<name>xwayland-devel</name>
 	<range><lt>21.0.99.1.653</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The X.Org project reports:</p>
 	<blockquote cite="https://lists.x.org/archives/xorg/2024-January/061525.html">
 	  <ul>
 	    <li>CVE-2023-6816: Heap buffer overflow in DeviceFocusEvent
 	    and ProcXIQueryPointer
 
 	    <p>Both DeviceFocusEvent and the XIQueryPointer reply contain a bit
 	    for each logical button currently down. Buttons can be arbitrarily
 	    mapped to any value up to 255 but the X.Org Server was only
 	    allocating space for the device's number of buttons,
 	    leading to a heap overflow if a bigger value was used.</p></li>
 	    <li>CVE-2024-0229: Reattaching to different master device may lead
 	    to out-of-bounds memory access
 
 	    <p>If a device has both a button class and a key class and
 	    numButtons is zero, we can get an out-of-bounds write due
 	    to event under-allocation in the DeliverStateNotifyEvent
 	    function.</p></li>
 
 	    <li>CVE-2024-21885: Heap buffer overflow in
 	    XISendDeviceHierarchyEvent
 
 	    <p>The XISendDeviceHierarchyEvent() function allocates space to
 	    store up to MAXDEVICES (256) xXIHierarchyInfo structures in info.
 	    If a device with a given ID was removed and a new device with
 	    the same ID added both in the same operation,
 	    the single device ID will lead to two info structures being
 	    written to info.
 	    Since this case can occur for every device ID at once,
 	    a total of two times MAXDEVICES info structures might be written
 	    to the allocation, leading to a heap buffer overflow.</p></li>
 
 	    <li>CVE-2024-21886: Heap buffer overflow in DisableDevice
 
 	    <p>The DisableDevice() function is called whenever an enabled device
 	    is disabled and it moves the device from the inputInfo.devices
 	    linked list to the inputInfo.off_devices linked list.
 	    However, its link/unlink operation has an issue during the recursive
 	    call to DisableDevice() due to the prev pointer pointing to a
 	    removed device.
 	    This issue leads to a length mismatch between the total number of
 	    devices and the number of device in the list, leading to a heap
 	    overflow and, possibly, to local privilege escalation.</p></li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-6816</cvename>
       <cvename>CVE-2024-0229</cvename>
       <cvename>CVE-2024-21885</cvename>
       <cvename>CVE-2024-21886</cvename>
       <url>https://lists.x.org/archives/xorg/2024-January/061525.html</url>
     </references>
     <dates>
       <discovery>2024-01-16</discovery>
       <entry>2024-01-16</entry>
     </dates>
   </vuln>
 
   <vuln vid="28b42ef5-80cd-440c-904b-b7fbca74c73d">
     <topic>electron{26,27} -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>electron26</name>
 	<range><lt>26.6.5</lt></range>
       </package>
       <package>
 	<name>electron27</name>
 	<range><lt>27.2.2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Electron developers report:</p>
 	<blockquote cite="https://github.com/electron/electron/releases/tag/v26.6.5">
 	  <p>This update fixes the following vulnerabilities:</p>
 	  <ul>
 	    <li>Security: backported fix for CVE-2024-0224.</li>
 	    <li>Security: backported fix for CVE-2024-0225.</li>
 	    <li>Security: backported fix for CVE-2024-0223.</li>
 	    <li>Security: backported fix for CVE-2024-0222.</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-0224</cvename>
       <url>https://github.com/advisories/GHSA-83wx-v283-85g9</url>
       <cvename>CVE-2024-0225</cvename>
       <url>https://github.com/advisories/GHSA-gqr9-4fcc-c9jq</url>
       <cvename>CVE-2024-0223</cvename>
       <url>https://github.com/advisories/GHSA-w8x8-g534-x4rp</url>
       <cvename>CVE-2024-0222</cvename>
       <url>https://github.com/advisories/GHSA-c87c-56pw-mwgh</url>
     </references>
     <dates>
       <discovery>2024-01-10</discovery>
       <entry>2024-01-12</entry>
     </dates>
   </vuln>
 
   <vuln vid="4c8c2218-b120-11ee-90ec-001b217b3468">
     <topic>Gitlab -- vulnerabilities</topic>
     <affects>
       <package>
 	<name>gitlab-ce</name>
 	<range><ge>16.7.0</ge><lt>16.7.2</lt></range>
 	<range><ge>16.6.0</ge><lt>16.6.4</lt></range>
 	<range><ge>8.13.0</ge><lt>16.5.6</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Gitlab reports:</p>
 	<blockquote cite="https://about.gitlab.com/releases/2024/01/11/critical-security-release-gitlab-16-7-2-released/">
 	  <p>Account Takeover via Password Reset without user interactions</p>
 	  <p>Attacker can abuse Slack/Mattermost integrations to execute slash commands as another user</p>
 	  <p>Bypass CODEOWNERS approval removal</p>
 	  <p>Workspaces able to be created under different root namespace</p>
 	  <p>Commit signature validation ignores headers after signature</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-7028</cvename>
       <cvename>CVE-2023-5356</cvename>
       <cvename>CVE-2023-4812</cvename>
       <cvename>CVE-2023-6955</cvename>
       <cvename>CVE-2023-2030</cvename>
       <url>https://about.gitlab.com/releases/2024/01/11/critical-security-release-gitlab-16-7-2-released/</url>
     </references>
     <dates>
       <discovery>2024-01-11</discovery>
       <entry>2024-01-12</entry>
     </dates>
   </vuln>
 
   <vuln vid="8337251b-b07b-11ee-b0d7-84a93843eb75">
     <topic>OpenSSL -- Vector register corruption on PowerPC</topic>
     <affects>
       <package>
 	<name>openssl</name>
 	<range><lt>3.0.12_2,1</lt></range>
       </package>
       <package>
 	<name>openssl-quictls</name>
 	<range><lt>3.0.12_2</lt></range>
       </package>
       <package>
 	<name>openssl31</name>
 	<range><lt>3.1.4_2</lt></range>
       </package>
       <package>
 	<name>openssl31-quictls</name>
 	<range><lt>3.1.4_2</lt></range>
       </package>
       <package>
 	<name>openssl32</name>
 	<range><lt>3.2.0_1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>SO-AND-SO reports:</p>
 	<blockquote cite="https://www.openssl.org/news/secadv/20240109.txt">
 	  <p>The POLY1305 MAC (message authentication code) implementation
 	    contains a bug that might corrupt the internal state of applications running
 	    on PowerPC CPU based platforms if the CPU provides vector instructions.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-6129</cvename>
       <url>https://www.openssl.org/news/secadv/20240109.txt</url>
     </references>
     <dates>
 	<discovery>2024-01-09</discovery>
       <entry>2024-01-11</entry>
     </dates>
   </vuln>
 
   <vuln vid="ec8e4040-afcd-11ee-86bb-a8a1599412c6">
     <topic>chromium -- security fix</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>120.0.6099.216</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>120.0.6099.216</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2024/01/stable-channel-update-for-desktop_9.html">
 	 <p>This update includes 1 security fix:</p>
 	 <ul>
 	    <li>[1513379] High CVE-2024-0333: Insufficient data validation in Extensions. Reported by Malcolm Stagg (@malcolmst) of SODIUM-24, LLC on 2023-12-20</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-0333</cvename>
       <url>https://chromereleases.googleblog.com/2024/01/stable-channel-update-for-desktop_9.html</url>
     </references>
     <dates>
       <discovery>2024-01-09</discovery>
       <entry>2024-01-10</entry>
     </dates>
   </vuln>
 
   <vuln vid="e2f981f1-ad9e-11ee-8b55-4ccc6adda413">
     <topic>QtNetwork -- potential buffer overflow</topic>
     <affects>
       <package>
 	<name>qt5-network</name>
 	<range><lt>5.15.12p148_1</lt></range>
       </package>
       <package>
 	<name>qt6-base</name>
 	<range><lt>6.6.1_2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Andy Shaw reports:</p>
 	<blockquote cite="https://www.qt.io/blog/security-advisory-potential-integer-overflow-in-qts-http2-implementation">
 	  <p>A potential integer overflow has been discovered in Qt's HTTP2
 	  implementation. If the HTTP2 implementation receives more than 4GiB
 	  in total headers, or more than 2GiB for any given header pair, then
 	  the internal buffers may overflow.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-51714</cvename>
       <url>https://www.qt.io/blog/security-advisory-potential-integer-overflow-in-qts-http2-implementation</url>
     </references>
     <dates>
       <discovery>2023-12-14</discovery>
       <entry>2024-01-07</entry>
     </dates>
   </vuln>
 
   <vuln vid="1f0d0024-ac9c-11ee-8e91-1c697a013f4b">
     <topic>mantis -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>mantis-php74</name>
 	<name>mantis-php80</name>
 	<name>mantis-php81</name>
 	<name>mantis-php82</name>
 	<name>mantis-php83</name>
 	<range><lt>2.25.8,1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Mantis 2.25.8 release reports:</p>
 	<blockquote cite="https://mantisbt.org/bugs/changelog_page.php?version_id=370">
 	  <p>Security and maintenance release</p>
 	  <ul>
 	    <li>0032432: Update guzzlehttp/psr7 to 1.9.1 (CVE-2023-29197)</li>
 	    <li>0032981: Information Leakage on DokuWiki Integration (CVE-2023-44394)</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-29197</cvename>
       <url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-29197</url>
       <cvename>CVE-2023-44394</cvename>
       <url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-44394</url>
     </references>
     <dates>
       <discovery>2023-10-14</discovery>
       <entry>2024-01-06</entry>
     </dates>
   </vuln>
 
   <vuln vid="3ee577a9-aad4-11ee-86bb-a8a1599412c6">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>120.0.6099.199</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>120.0.6099.199</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2024/01/stable-channel-update-for-desktop.html">
 	 <p>This update includes 6 security fixes:</p>
 	 <ul>
 	    <li>[1501798] High CVE-2024-0222: Use after free in ANGLE. Reported by Toan (suto) Pham of Qrious Secure on 2023-11-13</li>
 	    <li>[1505009] High CVE-2024-0223: Heap buffer overflow in ANGLE. Reported by Toan (suto) Pham and Tri Dang of Qrious Secure on 2023-11-24</li>
 	    <li>[1505086] High CVE-2024-0224: Use after free in WebAudio. Reported by Huang Xilin of Ant Group Light-Year Security Lab on 2023-11-25</li>
 	    <li>[1506923] High CVE-2024-0225: Use after free in WebGPU. Reported by Anonymous on 2023-12-01</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-0222</cvename>
       <cvename>CVE-2024-0223</cvename>
       <cvename>CVE-2024-0224</cvename>
       <cvename>CVE-2024-0225</cvename>
       <url>https://chromereleases.googleblog.com/2024/01/stable-channel-update-for-desktop.html</url>
     </references>
     <dates>
       <discovery>2024-01-03</discovery>
       <entry>2024-01-04</entry>
     </dates>
   </vuln>
 
   <vuln vid="d1b20e09-dbdf-432b-83c7-89f0af76324a">
     <topic>electron27 -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>electron27</name>
 	<range><lt>27.2.1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Electron developers report:</p>
 	<blockquote cite="https://github.com/electron/electron/releases/tag/v27.2.1">
 	  <p>This update fixes the following vulnerabilities:</p>
 	  <ul>
 	    <li>Security: backported fix for CVE-2023-6706.</li>
 	    <li>Security: backported fix for CVE-2023-6705.</li>
 	    <li>Security: backported fix for CVE-2023-6703.</li>
 	    <li>Security: backported fix for CVE-2023-6702.</li>
 	    <li>Security: backported fix for CVE-2023-6704.</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-6706</cvename>
       <url>https://github.com/advisories/GHSA-jqrg-rvpw-5fw5</url>
       <cvename>CVE-2023-6705</cvename>
       <url>https://github.com/advisories/GHSA-h27f-fw5q-c2gh</url>
       <cvename>CVE-2023-6703</cvename>
       <url>https://github.com/advisories/GHSA-9v72-359m-2vx4</url>
       <cvename>CVE-2023-6702</cvename>
       <url>https://github.com/advisories/GHSA-7hjc-c62g-4w73</url>
       <cvename>CVE-2023-6704</cvename>
       <url>https://github.com/advisories/GHSA-587x-fmc5-99p9</url>
     </references>
     <dates>
       <discovery>2024-01-04</discovery>
       <entry>2024-01-04</entry>
     </dates>
   </vuln>
 
   <vuln vid="0cee4f9c-5efb-4770-b917-f4e4569e8bec">
     <topic>electron26 -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>electron26</name>
 	<range><lt>26.6.4</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Electron developers report:</p>
 	<blockquote cite="https://github.com/electron/electron/releases/tag/v26.6.4">
 	  <p>This update fixes the following vulnerabilities:</p>
 	  <ul>
 	    <li>Security: backported fix for CVE-2023-6704.</li>
 	    <li>Security: backported fix for CVE-2023-6705.</li>
 	    <li>Security: backported fix for CVE-2023-6703.</li>
 	    <li>Security: backported fix for CVE-2023-6702.</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2023-6704</cvename>
       <url>https://github.com/advisories/GHSA-587x-fmc5-99p9</url>
       <cvename>CVE-2023-6705</cvename>
       <url>https://github.com/advisories/GHSA-h27f-fw5q-c2gh</url>
       <cvename>CVE-2023-6703</cvename>
       <url>https://github.com/advisories/GHSA-9v72-359m-2vx4</url>
       <cvename>CVE-2023-6702</cvename>
       <url>https://github.com/advisories/GHSA-7hjc-c62g-4w73</url>
     </references>
     <dates>
       <discovery>2024-01-04</discovery>
       <entry>2024-01-04</entry>
     </dates>
   </vuln>
 
   <vuln vid="13d83980-9f18-11ee-8e38-002590c1f29c">
     <topic>FreeBSD -- Prefix Truncation Attack in the SSH protocol</topic>
     <affects>
       <package>
 	<name>FreeBSD</name>
 	<range><ge>14.0</ge><lt>14.0_4</lt></range>
 	<range><ge>13.2</ge><lt>13.2_9</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<h1>Problem Description:</h1>
 	<p>The SSH protocol executes an initial handshake between the
 	server and the client.  This protocol handshake includes the
 	possibility of several extensions allowing different options to be
 	selected.  Validation of the packets in the handshake is done through
 	sequence numbers.</p>
 	<h1>Impact:</h1>
 	<p>A man in the middle attacker can silently manipulate handshake
 	messages to truncate extension negotiation messages potentially
 	leading to less secure client authentication algorithms or deactivating
 	keystroke timing attack countermeasures.</p>
       </body>
     </description>
     <references>
       <cvename>CVE-2023-48795</cvename>
       <freebsdsa>SA-23:19.openssh</freebsdsa>
     </references>
     <dates>
       <discovery>2023-12-19</discovery>
       <entry>2024-01-02</entry>
     </dates>
   </vuln>
 
   <vuln vid="bd7592a1-cbfd-11ee-a42a-5404a6f3ca32">
     <topic>gitea -- Prevent anonymous container access</topic>
     <affects>
       <package>
 	<name>gitea</name>
 	<range><lt>1.21.5</lt></range>
       </package>
     </affects>
     <description>
        <body xmlns="http://www.w3.org/1999/xhtml">
        <h1>Problem Description:</h1>
     <p>
       Even with RequireSignInView enabled, anonymous users can use docker pull
       to fetch public images.
     </p>
       </body>
     </description>
     <references>
       <url>https://blog.gitea.com/release-of-1.21.5/</url>
     </references>
     <dates>
       <discovery>2024-01-24</discovery>
       <entry>2024-02-15</entry>
     </dates>
   </vuln>
diff --git a/security/vuxml/vuln/2025.xml b/security/vuxml/vuln/2025.xml
index b8d669821d8b..8f68010d3ba5 100644
--- a/security/vuxml/vuln/2025.xml
+++ b/security/vuxml/vuln/2025.xml
@@ -1,9964 +1,9976 @@
   <vuln vid="f51077bd-6dd7-11f0-9d62-b42e991fc52e">
     <topic>SQLite -- integer overflow in key info allocation</topic>
     <affects>
       <package>
 	<name>sqlite3</name>
-	<range><gt>3.39.2</gt><lt>3.41.1</lt></range>
+	<range><ge>3.39.2,1</ge><lt>3.41.2,1</lt></range>
       </package>
+      <!-- as of 2025-08-01, sqlite in -c7 is 3.7.17 and matched by the <3.50.2 below,
+	   and -rl9 aka linux_base ships 3.34.1 which is outside this range. -->
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>cve-coordination@google.com reports:</p>
 	<blockquote cite="https://sqlite.org/forum/forumpost/16ce2bb7a639e29b">
 	  <p>An integer overflow in the sqlite3KeyInfoFromExprList function in
 	SQLite versions 3.39.2 through 3.41.1 allows an attacker with the
 	ability to execute arbitrary SQL statements to cause a denial of
 	service or disclose sensitive information from process memory via
 	a crafted SELECT statement with a large number of expressions in
 	the ORDER BY clause.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-7458</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-7458</url>
     </references>
     <dates>
       <discovery>2025-07-29</discovery>
       <entry>2025-07-31</entry>
+      <modified>2025-08-01</modified>
     </dates>
   </vuln>
 
   <vuln vid="cd7f969e-6cb4-11f0-97c4-40b034429ecf">
     <topic>p5-Crypt-CBC -- Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)</topic>
     <affects>
       <package>
 	<name>p5-Crypt-CBC</name>
 	<range><lt>3.07</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Lib-Crypt-CBC project reports:</p>
 	<blockquote cite="https://perldoc.perl.org/functions/rand">
 	  <p>
 	  Crypt::CBC versions between 1.21 and 3.05 for Perl may use the rand() function as the default
 	  source of entropy, which is not cryptographically secure, for cryptographic functions.
 	  This issue affects operating systems where "/dev/urandom'" is unavailable.
 	  In that case, Crypt::CBC will fallback to use the insecure rand() function.
 	  </p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-2814</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-2814</url>
     </references>
     <dates>
       <discovery>2025-04-12</discovery>
       <entry>2025-07-29</entry>
     </dates>
   </vuln>
 
   <vuln vid="c37f29ba-6ae3-11f0-b4bf-ecf4bbefc954">
     <topic>viewvc -- Arbitrary server filesystem content</topic>
     <affects>
       <package>
 	<name>viewvc</name>
 	<range><ge>1.1.0</ge><le>1.1.30</le></range>
       </package>
       <package>
 	<name>viewvc</name>
 	<range><ge>1.2.0</ge><le>1.2.3</le></range>
       </package>
       <package>
 	<name>viewvc-devel</name>
 	<range><lt>1.3.0.20250316_1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>cmpilato reports:</p>
 	<blockquote cite="https://github.com/viewvc/viewvc/security/advisories/GHSA-rv3m-76rj-q397">
 	  <p>
 	    The ViewVC standalone web server (standalone.py) is a script provided in the ViewVC
 	    distribution for the purposes of quickly testing a ViewVC configuration. This script
 	    can in particular configurations expose the contents of the host server's filesystem
 	    though a directory traversal-style attack.
 	  </p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-54141</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-54141</url>
     </references>
     <dates>
       <discovery>2025-07-22</discovery>
       <entry>2025-07-25</entry>
     </dates>
   </vuln>
 
   <vuln vid="eed1a411-699b-11f0-91fe-000c295725e4">
     <topic>rubygem-resolv -- Possible denial of service</topic>
     <affects>
       <package>
 	<name>rubygem-resolv</name>
 	<range><lt>0.6.2</lt></range>
       </package>
       <package>
 	<name>ruby</name>
 	<range><ge>3.2.0.p1,1</ge><lt>3.2.9,1</lt></range>
 	<range><ge>3.3.0.p1,1</ge><lt>3.3.9,1</lt></range>
 	<range><ge>3.4.0.p1,1</ge><lt>3.4.5,1</lt></range>
 	<range><ge>3.5.0.p1,1</ge><lt>3.5.0.p2,1</lt></range>
       </package>
       <package>
 	<name>ruby32</name>
 	<range><lt>3.2.9,1</lt></range>
       </package>
       <package>
 	<name>ruby33</name>
 	<range><lt>3.3.9,1</lt></range>
       </package>
       <package>
 	<name>ruby34</name>
 	<range><lt>3.4.5,1</lt></range>
       </package>
       <package>
 	<name>ruby35</name>
 	<range><lt>3.5.0.p2,1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Manu reports:</p>
 	<blockquote cite="https://www.ruby-lang.org/en/news/2025/07/08/dos-resolv-cve-2025-24294/">
 	  <p>
 	    The vulnerability is caused by an insufficient check on
 	    the length of a decompressed domain name within a DNS
 	    packet.
 	  </p>
 	  <p>
 	    An attacker can craft a malicious DNS packet containing a
 	    highly compressed domain name. When the resolv library
 	    parses such a packet, the name decompression process
 	    consumes a large amount of CPU resources, as the library
 	    does not limit the resulting length of the name.
 	  </p>
 	  <p>
 	    This resource consumption can cause the application thread
 	    to become unresponsive, resulting in a Denial of Service
 	    condition.
 	  </p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-24294</cvename>
       <url>https://www.ruby-lang.org/en/news/2025/07/08/dos-resolv-cve-2025-24294/</url>
     </references>
     <dates>
       <discovery>2025-07-08</discovery>
       <entry>2025-07-25</entry>
     </dates>
   </vuln>
 
   <vuln vid="67c6461f-685e-11f0-a12d-b42e991fc52e">
     <topic>Mozilla -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>141.0,2</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>141.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/buglist.cgi?bug_id=1933572%2C1971116">
 	  <p>Memory safety bugs present in Firefox 140 and
 	  Thunderbird 140. Some of these bugs showed evidence of
 	  memory corruption and we presume that with enough effort
 	  some of these could have been exploited to run arbitrary
 	  code.</p>
 	  <p>Focus incorrectly truncated URLs towards the beginning instead of
 	    around the origin.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-8044</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-8044</url>
       <cvename>CVE-2025-8043</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-8043</url>
     </references>
     <dates>
       <discovery>2025-07-22</discovery>
       <entry>2025-07-24</entry>
     </dates>
   </vuln>
 
   <vuln vid="62f1a68f-685e-11f0-a12d-b42e991fc52e">
     <topic>Mozilla -- Memory safety bugs</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>141.0,2</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>140.1</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>141.0</lt></range>
       </package>
       <package>
 	<name>thunderbird-esr</name>
 	<range><lt>140.1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/buglist.cgi?bug_id=1975058%2C1975058%2C1975998%2C1975998">
 	  <p>Memory safety bugs present in Firefox ESR 140.0,
 	  Thunderbird ESR 140.0, Firefox 140 and Thunderbird 140.
 	  Some of these bugs showed evidence of memory corruption and
 	  we presume that with enough effort some of these could have
 	  been exploited to run arbitrary code.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-8040</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-8040</url>
     </references>
     <dates>
       <discovery>2025-07-22</discovery>
       <entry>2025-07-24</entry>
     </dates>
   </vuln>
 
   <vuln vid="6088905c-685e-11f0-a12d-b42e991fc52e">
     <topic>Mozilla -- Persisted search terms in the URL bar</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>141.0,2</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>140.1</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>141.0</lt></range>
       </package>
       <package>
 	<name>thunderbird-esr</name>
 	<range><lt>140.1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1970997">
 	  <p>In some cases search terms persisted in the URL bar even after
 	navigating away from the search page.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-8039</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-8039</url>
     </references>
     <dates>
       <discovery>2025-07-22</discovery>
       <entry>2025-07-24</entry>
     </dates>
   </vuln>
 
   <vuln vid="5d91def0-685e-11f0-a12d-b42e991fc52e">
     <topic>Mozilla -- Ignored paths while checking navigations</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>141.0,2</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>140.1</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>141.0</lt></range>
       </package>
       <package>
 	<name>thunderbird-esr</name>
 	<range><lt>140.1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1808979">
 	  <p>Thunderbird ignored paths when checking the validity of
 	  navigations in a frame.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-8038</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-8038</url>
     </references>
     <dates>
       <discovery>2025-07-22</discovery>
       <entry>2025-07-24</entry>
     </dates>
   </vuln>
 
   <vuln vid="5abc2187-685e-11f0-a12d-b42e991fc52e">
     <topic>Mozilla -- cookie shadowing</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>141.0,2</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>140.1</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>141.0</lt></range>
       </package>
       <package>
 	<name>thunderbird-esr</name>
 	<range><lt>140.1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1964767">
 	  <p>Setting a nameless cookie with an equals sign in the
 	  value shadowed other cookies. Even if the nameless cookie
 	  was set over HTTP and the shadowed cookie included the
 	  `Secure` attribute.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-8037</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-8037</url>
     </references>
     <dates>
       <discovery>2025-07-22</discovery>
       <entry>2025-07-24</entry>
     </dates>
   </vuln>
 
   <vuln vid="58027367-685e-11f0-a12d-b42e991fc52e">
     <topic>Mozilla -- CORS circumvention</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>141.0,2</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>140.1</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>141.0</lt></range>
       </package>
       <package>
 	<name>thunderbird-esr</name>
 	<range><lt>140.1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1960834">
 	  <p>Thunderbird cached CORS preflight responses across IP
 	  address changes. This allowed circumventing CORS with DNS
 	  rebinding.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-8036</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-8036</url>
     </references>
     <dates>
       <discovery>2025-07-22</discovery>
       <entry>2025-07-24</entry>
     </dates>
   </vuln>
 
   <vuln vid="55096bd3-685e-11f0-a12d-b42e991fc52e">
     <topic>Mozilla -- Memory safety bugs</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>141.0,2</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>140.1</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>128.13</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>141.0</lt></range>
       </package>
       <package>
 	<name>thunderbird-esr</name>
 	<range><lt>140.1</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>128.13</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/buglist.cgi?bug_id=1975961%2C1975961%2C1975961">
 	  <p>Memory safety bugs present in Firefox ESR 128.12,
 	  Thunderbird ESR 128.12, Firefox ESR 140.0, Thunderbird ESR
 	  140.0, Firefox 140 and Thunderbird 140. Some of these bugs
 	  showed evidence of memory corruption and we presume that
 	  with enough effort some of these could have been exploited
 	  to run arbitrary code.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-8035</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-8035</url>
     </references>
     <dates>
       <discovery>2025-07-22</discovery>
       <entry>2025-07-24</entry>
     </dates>
   </vuln>
 
   <vuln vid="4faa01cb-685e-11f0-a12d-b42e991fc52e">
     <topic>Mozilla -- Memory safety bugs</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>141.0,2</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>140.1</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>128.13</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>115.26</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>141.0</lt></range>
       </package>
       <package>
 	<name>thunderbird-esr</name>
 	<range><lt>140.1</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>128.13</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/buglist.cgi?bug_id=1970422%2C1970422%2C1970422%2C1970422">
 	  <p>Memory safety bugs present in Firefox ESR 115.25, Firefox
 	  ESR 128.12, Thunderbird ESR 128.12, Firefox ESR 140.0,
 	  Thunderbird ESR 140.0, Firefox 140 and Thunderbird 140. Some
 	  of these bugs showed evidence of memory corruption and we
 	  presume that with enough effort some of these could have
 	  been exploited to run arbitrary code.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-8034</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-8034</url>
     </references>
     <dates>
       <discovery>2025-07-22</discovery>
       <entry>2025-07-24</entry>
     </dates>
   </vuln>
 
   <vuln vid="4d03efe7-685e-11f0-a12d-b42e991fc52e">
     <topic>Mozilla -- nullptr dereference</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>141.0,2</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>140.1</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>128.13</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>115.26</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>141.0</lt></range>
       </package>
       <package>
 	<name>thunderbird-esr</name>
 	<range><lt>140.1</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>128.13</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1973990">
 	  <p>The JavaScript engine did not handle closed generators
 	  correctly and it was possible to resume them leading to a
 	  nullptr deref.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-8033</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-8033</url>
     </references>
     <dates>
       <discovery>2025-07-22</discovery>
       <entry>2025-07-24</entry>
     </dates>
   </vuln>
 
   <vuln vid="4a357f4b-685e-11f0-a12d-b42e991fc52e">
     <topic>Mozilla -- XSLT document CSP bypass</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>141.0,2</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>140.1</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>128.13</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>141.0</lt></range>
       </package>
       <package>
 	<name>thunderbird-esr</name>
 	<range><lt>140.1</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>128.13</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1974407">
 	  <p>XSLT document loading did not correctly propagate the
 	  source document which bypassed its CSP.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-8032</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-8032</url>
     </references>
     <dates>
       <discovery>2025-07-22</discovery>
       <entry>2025-07-24</entry>
     </dates>
   </vuln>
 
   <vuln vid="477e9eb3-685e-11f0-a12d-b42e991fc52e">
     <topic>Mozilla -- HTTP Basic Authentication credentials leak</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>141.0,2</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>140.1</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>128.13</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>141.0</lt></range>
       </package>
       <package>
 	<name>thunderbird-esr</name>
 	<range><lt>140.1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1971719">
 	  <p>The `username:password` part was not correctly stripped
 	  from URLs in CSP reports potentially leaking HTTP Basic
 	  Authentication credentials.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-8031</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-8031</url>
     </references>
     <dates>
       <discovery>2025-07-22</discovery>
       <entry>2025-07-24</entry>
     </dates>
   </vuln>
 
   <vuln vid="44b3048b-685e-11f0-a12d-b42e991fc52e">
     <topic>Mozilla -- Insufficient input escaping</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>141.0,2</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>140.1</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>128.13</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>141.0</lt></range>
       </package>
       <package>
 	<name>thunderbird-esr</name>
 	<range><lt>140.1</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>128.13</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1968414">
 	  <p>Insufficient escaping in the Copy as cURL feature could
 	  potentially be used to trick a user into executing
 	  unexpected code.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-8030</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-8030</url>
     </references>
     <dates>
       <discovery>2025-07-22</discovery>
       <entry>2025-07-24</entry>
     </dates>
   </vuln>
 
   <vuln vid="419bcf99-685e-11f0-a12d-b42e991fc52e">
     <topic>Mozilla -- 'javascript:' URLs execution</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>141.0,2</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>140.1</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>128.13</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>141.0</lt></range>
       </package>
       <package>
 	<name>thunderbird-esr</name>
 	<range><lt>140.1</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>128.13</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1928021">
 	  <p>Thunderbird executed `javascript:` URLs when used in
 	  `object` and `embed` tags.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-8029</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-8029</url>
     </references>
     <dates>
       <discovery>2025-07-22</discovery>
       <entry>2025-07-24</entry>
     </dates>
   </vuln>
 
   <vuln vid="3e9406a7-685e-11f0-a12d-b42e991fc52e">
     <topic>Mozilla -- Incorrect computation of branch address</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>141.0,2</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>140.1</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>128.13</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>115.26</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>141.0</lt></range>
       </package>
       <package>
 	<name>thunderbird-esr</name>
 	<range><lt>140.1</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>128.13</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1971581">
 	  <p>On arm64, a WASM `br_table` instruction with a lot of
 	  entries could lead to the label being too far from the
 	  instruction causing truncation and incorrect computation of
 	  the branch address.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-8028</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-8028</url>
     </references>
     <dates>
       <discovery>2025-07-22</discovery>
       <entry>2025-07-24</entry>
     </dates>
   </vuln>
 
   <vuln vid="3c234220-685e-11f0-a12d-b42e991fc52e">
     <topic>Mozilla -- IonMonkey-JIT bad stack write</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>141.0,2</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>140.1</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>128.13</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>115.26</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>141.0</lt></range>
       </package>
       <package>
 	<name>thunderbird-esr</name>
 	<range><lt>140.1</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>128.13</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1968423">
 	  <p>On 64-bit platforms IonMonkey-JIT only wrote 32 bits of
 	  the 64-bit return value space on the stack. Baseline-JIT,
 	  however, read the entire 64 bits.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-8027</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-8027</url>
     </references>
     <dates>
       <discovery>2025-07-22</discovery>
       <entry>2025-07-24</entry>
     </dates>
   </vuln>
 
   <vuln vid="3d4393b2-68a5-11f0-b2b4-589cfc10832a">
     <topic>gdk-pixbuf2 -- a heap buffer overflow</topic>
     <affects>
       <package>
 	<name>gdk-pixbuf2</name>
 	<range><lt>2.42.12_2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>cve@mitre.org reports:</p>
 	<blockquote cite="https://www.cve.org/CVERecord?id=CVE-2025-7345">
 	  <p>A flaw exists in gdk-pixbuf within the gdk_pixbuf__jpeg_image_load_increment
 	function (io-jpeg.c) and in glib’s g_base64_encode_step (glib/gbase64.c).
 	When processing maliciously crafted JPEG images, a heap buffer overflow can occur
 	during Base64 encoding, allowing out-of-bounds reads from heap memory, potentially
 	causing application crashes or arbitrary code execution.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-7345</cvename>
       <url>https://www.cve.org/CVERecord?id=CVE-2025-7345</url>
     </references>
     <dates>
       <discovery>2025-07-24</discovery>
       <entry>2025-07-24</entry>
     </dates>
   </vuln>
 
   <vuln vid="b3948bf3-685e-11f0-bff5-6805ca2fa271">
     <topic>powerdns-recursor -- cache pollution</topic>
     <affects>
       <package>
 	<name>powerdns-recursor</name>
 	<range><lt>5.2.4</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>PowerDNS Team reports:</p>
 	<blockquote cite="https://blog.powerdns.com/powerdns-security-advisory-2025-04">
 	  <p>An attacker spoofing answers to ECS enabled requests
 	  sent out by the Recursor has a chance of success higher
 	  than non-ECS enabled queries.	The updated version include
 	  various mitigations against spoofing attempts of ECS enabled
 	  queries by chaining ECS enabled requests and enforcing
 	  stricter validation of the received answers. The most strict
 	  mitigation done when the new setting outgoing.edns_subnet_harden
 	  (old style name edns-subnet-harden) is enabled.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-30192</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-30192</url>
    </references>
     <dates>
       <discovery>2025-07-21</discovery>
       <entry>2025-07-24</entry>
     </dates>
   </vuln>
 
   <vuln vid="5683b3a7-683d-11f0-966e-2cf05da270f3">
     <topic>Gitlab -- vulnerabilities</topic>
     <affects>
       <package>
 	<name>gitlab-ce</name>
 	<name>gitlab-ee</name>
 	<range><ge>18.2.0</ge><lt>18.2.1</lt></range>
 	<range><ge>18.1.0</ge><lt>18.1.3</lt></range>
 	<range><ge>15.0.0</ge><lt>18.0.5</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Gitlab reports:</p>
 	<blockquote cite="https://about.gitlab.com/releases/2025/07/23/patch-release-gitlab-18-2-1-released/">
 	  <p>Cross-site scripting issue impacts Kubernetes Proxy in GitLab CE/EE</p>
 	  <p>Cross-site scripting issue impacts Kubernetes Proxy in GitLab CE/EE using CDNs</p>
 	  <p>Exposure of Sensitive Information to an Unauthorized Actor issue impacts GitLab CE/EE</p>
 	  <p>Improper Access Control issue impacts GitLab EE</p>
 	  <p>Exposure of Sensitive Information to an Unauthorized Actor issue impacts GitLab CE/EE</p>
 	  <p>Improper Access Control issue impacts GitLab CE/EE</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-4700</cvename>
       <cvename>CVE-2025-4439</cvename>
       <cvename>CVE-2025-7001</cvename>
       <cvename>CVE-2025-4976</cvename>
       <cvename>CVE-2025-0765</cvename>
       <cvename>CVE-2025-1299</cvename>
       <url>https://about.gitlab.com/releases/2025/07/23/patch-release-gitlab-18-2-1-released/</url>
     </references>
     <dates>
       <discovery>2025-07-23</discovery>
       <entry>2025-07-24</entry>
     </dates>
   </vuln>
 
   <vuln vid="0f5bcba2-67fb-11f0-9ee5-b42e991fc52e">
     <topic>sqlite -- Integer Truncation on SQLite</topic>
     <affects>
       <package>
 	<name>sqlite3</name>
+	<range><lt>3.50.2,1</lt></range>
+      </package>
+      <package>
+	<name>linux-c7-sqlite</name>
 	<range><lt>3.50.2</lt></range>
       </package>
+      <package>
+	<name>linux_base</name>
+	<range><ge>0</ge></range>
+      </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>cve-coordination@google.com reports:</p>
 	<blockquote cite="https://www.sqlite.org/src/info/5508b56fd24016c13981ec280ecdd833007c9d8dd595edb295b984c2b487b5c8">
 	  <p>There exists a vulnerability in SQLite versions before
 	  3.50.2 where the number of aggregate terms could exceed the
 	  number of columns available. This could lead to a memory
 	  corruption issue.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-6965</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-6965</url>
     </references>
     <dates>
       <discovery>2025-07-15</discovery>
       <entry>2025-07-23</entry>
+      <modified>2025-08-01</modified>
     </dates>
   </vuln>
 
   <vuln vid="80411ba2-6729-11f0-a5cb-8c164580114f">
     <topic>7-Zip -- Multi-byte write heap buffer overflow in NCompress::NRar5::CDecoder</topic>
     <affects>
       <package>
 	<name>7-zip</name>
 	<range><lt>25.00</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security-advisories@github.com reports:</p>
 	<blockquote cite="https://securitylab.github.com/advisories/GHSL-2025-058_7-Zip/">
 	  <p>7-Zip is a file archiver with a high compression ratio.  Zeroes
 	written outside heap buffer in RAR5 handler may lead to memory
 	corruption and denial of service in versions of 7-Zip prior to
 	25.0.0.  Version 25.0.0 contains a fix for the issue.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-53816</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-53816</url>
     </references>
     <dates>
       <discovery>2025-07-17</discovery>
       <entry>2025-07-22</entry>
     </dates>
   </vuln>
 
   <vuln vid="605a9d1e-6521-11f0-beb2-ac5afc632ba3">
     <topic>libwasmtime -- host panic with fd_renumber WASIp1 function</topic>
     <affects>
       <package>
 	<name>libwasmtime</name>
 	<range><ge>24.0.0</ge><lt>24.0.4</lt></range>
 	<range><ge>33.0.0</ge><lt>33.0.2</lt></range>
 	<range><ge>34.0.0</ge><lt>34.0.2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>WasmTime development team reports:</p>
 	<blockquote cite="https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-fm79-3f68-h2fc">
 	  <p>A bug in Wasmtime's implementation of the WASIp1 set of import
 	  functions can lead to a WebAssembly guest inducing a panic in the
 	  host (embedder).</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-53901</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-53901</url>
     </references>
     <dates>
       <discovery>2025-07-18</discovery>
       <entry>2025-07-20</entry>
     </dates>
   </vuln>
 
   <vuln vid="e27ee4fc-cdc9-45a1-8242-09898cdbdc91">
     <topic>unbound -- Cache poisoning via the ECS-enabled Rebirthday Attack</topic>
     <affects>
       <package>
 	<name>unbound</name>
 	<range><gt>1.6.1</gt><lt>1.23.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>sep@nlnetlabs.nl reports:</p>
 	<blockquote cite="https://nlnetlabs.nl/downloads/unbound/CVE-2025-5994.txt">
 	  <p>A multi-vendor cache poisoning vulnerability named &apos;Rebirthday
 	Attack&apos; has been discovered in caching resolvers that support
 	EDNS Client Subnet (ECS).  Unbound is also vulnerable when compiled
 	with ECS support, i.e., &apos;--enable-subnet&apos;, AND configured
 	to send ECS information along with queries to upstream name servers,
 	i.e., at least one of the &apos;send-client-subnet&apos;,
 	&apos;client-subnet-zone&apos; or &apos;client-subnet-always-forward&apos;
 	options is used.  Resolvers supporting ECS need to segregate outgoing
 	queries to accommodate for different outgoing ECS information.  This
 	re-opens up resolvers to a birthday paradox attack (Rebirthday
 	Attack) that tries to match the DNS transaction ID in order to cache
 	non-ECS poisonous replies.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-5994</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-5994</url>
     </references>
     <dates>
       <discovery>2025-07-16</discovery>
       <entry>2025-07-18</entry>
     </dates>
   </vuln>
 
   <vuln vid="aeac223e-60e1-11f0-8baa-8447094a420f">
     <topic>liboqs -- Secret-dependent branching in HQC</topic>
     <affects>
       <package>
 	<name>liboqs</name>
 	<range><lt>0.14.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The OpenQuantumSafe project reports:</p>
 	<blockquote cite="https://github.com/open-quantum-safe/liboqs/security/advisories/GHSA-qq3m-rq9v-jfgm">
 	  <p>Secret-dependent branching in HQC reference implementation when compiled with Clang 17-20 for optimizations above -O0</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-52473</cvename>
       <url>https://github.com/open-quantum-safe/liboqs/security/advisories/GHSA-qq3m-rq9v-jfgm</url>
     </references>
     <dates>
       <discovery>2025-07-10</discovery>
       <entry>2025-07-14</entry>
     </dates>
   </vuln>
 
   <vuln vid="c3e1df74-5e73-11f0-95e5-74563cf9e4e9">
     <topic>GnuTLS -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>gnutls</name>
 	<range><lt>3.8.10</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Daiki Ueno  reports:</p>
 	<blockquote cite="https://lists.gnupg.org/pipermail/gnutls-help/2025-July/004883.html">
 	  <ul>
 	    <li>libgnutls: Fix heap read buffer overrun in parsing X.509 SCTS timestamps
 	      Spotted by oss-fuzz and reported by OpenAI Security Research Team,
 	      and fix developed by Andrew Hamilton. [GNUTLS-SA-2025-07-07-1,
 	      CVSS: medium] [CVE-2025-32989]</li>
 	    <li>libgnutls: Fix double-free upon error when exporting otherName in SAN
 	      Reported by OpenAI Security Research Team. [GNUTLS-SA-2025-07-07-2,
 	      CVSS: low] [CVE-2025-32988]</li>
 	    <li>certtool: Fix 1-byte write buffer overrun when parsing template
 	      Reported by David Aitel. [GNUTLS-SA-2025-07-07-3,
 	      CVSS: low] [CVE-2025-32990]</li>
 	    <li>libgnutls: Fix NULL pointer dereference when 2nd Client Hello omits PSK
 	      Reported by Stefan Bühler. [GNUTLS-SA-2025-07-07-4, CVSS: medium]
 	      [CVE-2025-6395]</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-32989</cvename>
       <cvename>CVE-2025-32988</cvename>
       <cvename>CVE-2025-32990</cvename>
       <cvename>CVE-2025-6395</cvename>
       <url>https://lists.gnupg.org/pipermail/gnutls-help/2025-July/004883.html</url>
     </references>
     <dates>
       <discovery>2025-07-09</discovery>
       <entry>2025-07-14</entry>
     </dates>
   </vuln>
 
   <vuln vid="b0a3466f-5efc-11f0-ae84-99047d0a6bcc">
     <topic>libxslt -- unmaintained, with multiple unfixed vulnerabilities</topic>
     <affects>
       <package>
 	<name>libxslt</name>
 	<range><lt>2</lt></range> <!-- adjust should libxslt ever be fixed -->
       </package>
       <package>
 	<name>linux-c7-libxslt</name>
 	<range><lt>2</lt></range> <!-- adjust should libxslt ever be fixed -->
       </package>
       <package>
 	<name>linux-rl9-libxslt</name>
 	<range><lt>2</lt></range> <!-- adjust should libxslt ever be fixed -->
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Alan Coopersmith reports:</p>
 	<blockquote cite="https://www.openwall.com/lists/oss-security/2025/07/11/2">
 	  <p>On 6/16/25 15:12, Alan Coopersmith wrote:</p>
 	  <p><em>
 	    BTW, users of libxml2 may also be using its sibling project, libxslt,
 	    which currently has no active maintainer, but has three unfixed security issues
 	    reported against it according to
 	    <a href="https://gitlab.gnome.org/Teams/Releng/security/-/wikis/2025#libxml2-and-libxslt">
 		https://gitlab.gnome.org/Teams/Releng/security/-/wikis/2025#libxml2-and-libxslt</a>
 	  </em></p>
 	  <p>2 of the 3 have now been disclosed:</p>
 	  <p>(CVE-2025-7424) libxslt: Type confusion in xmlNode.psvi between stylesheet and source nodes<br />
 	    <a href="https://gitlab.gnome.org/GNOME/libxslt/-/issues/139">https://gitlab.gnome.org/GNOME/libxslt/-/issues/139</a>
 	    <a href="https://project-zero.issues.chromium.org/issues/409761909">https://project-zero.issues.chromium.org/issues/409761909</a></p>
 	  <p>(CVE-2025-7425) libxslt: heap-use-after-free in xmlFreeID caused by `atype` corruption<br />
 	    <a href="https://gitlab.gnome.org/GNOME/libxslt/-/issues/140">https://gitlab.gnome.org/GNOME/libxslt/-/issues/140</a><br /><a href="https://project-zero.issues.chromium.org/issues/410569369">https://project-zero.issues.chromium.org/issues/410569369</a></p>
 	  <p>Engineers from Apple &amp; Google have proposed patches in the GNOME gitlab issues,
 	  but neither has had a fix applied to the git repo since there is currently no
 	    maintainer for libxslt.</p>
 	</blockquote>
 	<p>Note that a fourth vulnerability was reported on June 18, 2025, which remains undisclosed to date (GNOME libxslt issue 148, link below), see
 	  <a href="https://gitlab.gnome.org/Teams/Releng/security/-/wikis/2025#libxml2-and-libxslt">
 	    https://gitlab.gnome.org/Teams/Releng/security/-/wikis/2025#libxml2-and-libxslt</a>
 	</p>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-7424</cvename>
       <cvename>CVE-2025-7425</cvename>
       <url>https://gitlab.gnome.org/Teams/Releng/security/-/wikis/2025#libxml2-and-libxslt</url>
       <url>https://gitlab.gnome.org/GNOME/libxslt/-/issues/139</url>
       <url>https://gitlab.gnome.org/GNOME/libxslt/-/issues/140</url>
       <url>https://gitlab.gnome.org/GNOME/libxslt/-/issues/144</url>
       <url>https://gitlab.gnome.org/GNOME/libxslt/-/issues/148</url>
       <url>https://gitlab.gnome.org/GNOME/libxslt/-/commit/923903c59d668af42e3144bc623c9190a0f65988</url>
     </references>
     <dates>
       <discovery>2025-04-10</discovery>
       <entry>2025-07-12</entry>
     </dates>
   </vuln>
 
   <vuln vid="abbc8912-5efa-11f0-ae84-99047d0a6bcc">
     <topic>libxml2 -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>libxml2</name>
 	<range><lt>2.14.5</lt></range>
       </package>
       <package>
 	<name>linux-c7-libxml2</name>
 	<range><lt>2.14.5</lt></range> <!-- needs update once fixed version appears -->
       </package>
       <package>
 	<name>linux-rl9-libxml2</name>
 	<range><lt>2.14.5</lt></range> <!-- needs update once fixed version appears -->
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Alan Coopersmith reports:</p>
 	<blockquote cite="https://www.openwall.com/lists/oss-security/2025/06/16/6">
 	  <p>As discussed in
 	    <a href="https://gitlab.gnome.org/GNOME/libxml2/-/issues/913">https://gitlab.gnome.org/GNOME/libxml2/-/issues/913</a> the
 	  security policy of libxml2 has been changed to disclose vulnerabilities
 	  before fixes are available so that people other than the maintainer can
 	    contribute to fixing security issues in this library.</p>
 	  <p>As part of this, the following 5 CVE's have been disclosed recently:</p>
 	  <p>(CVE-2025-49794) Heap use after free (UAF) leads to Denial of service (DoS)
 	    <a href="https://gitlab.gnome.org/GNOME/libxml2/-/issues/931">https://gitlab.gnome.org/GNOME/libxml2/-/issues/931</a> [...]</p>
 	  <p>(CVE-2025-49795) Null pointer dereference leads to Denial of service (DoS)
 	    <a href="https://gitlab.gnome.org/GNOME/libxml2/-/issues/932">https://gitlab.gnome.org/GNOME/libxml2/-/issues/932</a> [...]</p>
 	  <p>(CVE-2025-49796) Type confusion leads to Denial of service (DoS)
 	    <a href="https://gitlab.gnome.org/GNOME/libxml2/-/issues/933">https://gitlab.gnome.org/GNOME/libxml2/-/issues/933</a> [...]</p>
 	  <p>For all three of the above, note that upstream is considering removing Schematron support completely, as discussed in
 	    <a href="https://gitlab.gnome.org/GNOME/libxml2/-/issues/935">https://gitlab.gnome.org/GNOME/libxml2/-/issues/935</a>.</p>
 	  <p>(CVE-2025-6021) Integer Overflow Leading to Buffer Overflow in xmlBuildQName()
 	    <a href="https://gitlab.gnome.org/GNOME/libxml2/-/issues/926">https://gitlab.gnome.org/GNOME/libxml2/-/issues/926</a> [...]</p>
 	  <p>(CVE-2025-6170) Stack-based Buffer Overflow in xmllint Shell
 	    <a href="https://gitlab.gnome.org/GNOME/libxml2/-/issues/941">https://gitlab.gnome.org/GNOME/libxml2/-/issues/941</a> [...]</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-6021</cvename>
       <cvename>CVE-2025-6170</cvename>
       <cvename>CVE-2025-49794</cvename>
       <cvename>CVE-2025-49795</cvename>
       <cvename>CVE-2025-49795</cvename>
       <url>https://www.openwall.com/lists/oss-security/2025/06/16/6</url>
       <url>https://gitlab.gnome.org/Teams/Releng/security/-/wikis/2025#libxml2-and-libxslt</url>
       <url>https://gitlab.gnome.org/GNOME/libxml2/-/issues/913</url>
       <url>https://gitlab.gnome.org/GNOME/libxml2/-/issues/931</url>
       <url>https://gitlab.gnome.org/GNOME/libxml2/-/issues/932</url>
       <url>https://gitlab.gnome.org/GNOME/libxml2/-/issues/933</url>
       <url>https://gitlab.gnome.org/GNOME/libxml2/-/issues/935</url>
       <url>https://gitlab.gnome.org/GNOME/libxml2/-/issues/926</url>
       <url>https://gitlab.gnome.org/GNOME/libxml2/-/issues/941</url>
     </references>
     <dates>
       <discovery>2025-05-27</discovery>
       <entry>2025-07-12</entry>
       <modified>2025-07-15</modified>
     </dates>
   </vuln>
 
   <vuln vid="61d74f80-5e9e-11f0-8baa-8447094a420f">
     <topic>mod_http2 -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>mod_http2</name>
 	<range><lt>2.0.33</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The mod_http2 project reports:</p>
 	<blockquote cite="https://github.com/icing/mod_h2/releases/tag/v2.0.33">
 	  <p>a client can increase memory consumption for a HTTP/2 connection
 	    via repeated request header names,leading to denial of service</p>
 	  <p>certain proxy configurations whith mod_proxy_http2 as the
 	    backend, an assertion can be triggered by certain requests, leading
 	    to denial of service</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-53020</cvename>
       <cvename>CVE-2025-49630</cvename>
       <url>https://github.com/icing/mod_h2/releases/tag/v2.0.33</url>
     </references>
     <dates>
       <discovery>2025-07-10</discovery>
       <entry>2025-07-11</entry>
     </dates>
   </vuln>
 
   <vuln vid="342f2a0a-5e9b-11f0-8baa-8447094a420f">
     <topic>Apache httpd -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>apache24</name>
 	<range><lt>2.4.64</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The Apache httpd project reports:</p>
 	<blockquote cite="https://httpd.apache.org/security/vulnerabilities_24.html">
 	  <p>moderate: Apache HTTP Server: HTTP response splitting (CVE-2024-42516)</p>
 	  <p>low: Apache HTTP Server: SSRF with mod_headers setting Content-Type header (CVE-2024-43204)</p>
 	  <p>moderate: Apache HTTP Server: SSRF on Windows due to UNC paths (CVE-2024-43394)</p>
 	  <p>low: Apache HTTP Server: mod_ssl error log variable escaping (CVE-2024-47252)</p>
 	  <p>moderate: Apache HTTP Server: mod_ssl access control bypass with session resumption (CVE-2025-23048)</p>
 	  <p>low: Apache HTTP Server: mod_proxy_http2 denial of service (CVE-2025-49630)</p>
 	  <p>moderate: Apache HTTP Server: mod_ssl TLS upgrade attack (CVE-2025-49812)</p>
 	  <p>moderate: Apache HTTP Server: HTTP/2 DoS by Memory Increase (CVE-2025-53020)</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-42516</cvename>
       <cvename>CVE-2024-43204</cvename>
       <cvename>CVE-2024-43394</cvename>
       <cvename>CVE-2024-47252</cvename>
       <cvename>CVE-2025-23048</cvename>
       <cvename>CVE-2025-49630</cvename>
       <cvename>CVE-2025-49812</cvename>
       <cvename>CVE-2025-53020</cvename>
       <url>https://httpd.apache.org/security/vulnerabilities_24.html</url>
     </references>
     <dates>
       <discovery>2025-07-10</discovery>
       <entry>2025-07-11</entry>
     </dates>
   </vuln>
 
   <vuln vid="ef87346f-5dd0-11f0-beb2-ac5afc632ba3">
     <topic>Apache Tomcat -- Multiple Vulnerabilities</topic>
     <affects>
       <package>
 	<name>tomcat110</name>
 	<range><ge>11.0.0</ge><lt>11.0.9</lt></range>
       </package>
       <package>
 	<name>tomcat101</name>
 	<range><ge>10.1.0</ge><lt>10.1.43</lt></range>
       </package>
       <package>
 	<name>tomcat9</name>
 	<range><ge>9.0.0</ge><lt>9.0.107</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@apache.org reports:</p>
 	<blockquote cite="https://www.mail-archive.com/announce@tomcat.apache.org/msg00710.html">
 	  <p>A race condition on connection close could trigger a JVM crash when using the
 	  APR/Native connector leading to a DoS.  This was particularly noticeable with client
 	  initiated closes of HTTP/2 connections.</p>
 	</blockquote>
 	<blockquote cite="https://www.mail-archive.com/announce@tomcat.apache.org/msg00713.html">
 	  <p>An uncontrolled resource consumption vulnerability if an HTTP/2 client did not
 	  acknowledge the initial settings frame that reduces the maximum permitted
 	  concurrent streams could result in a DoS.</p>
 	</blockquote>
 	<blockquote cite="https://www.mail-archive.com/announce@tomcat.apache.org/msg00714.html">
 	  <p>For some unlikely configurations of multipart upload, an Integer Overflow
 	  vulnerability could lead to a DoS via bypassing of size limits.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-52434</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-52434</url>
       <cvename>CVE-2025-52520</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-52520</url>
       <cvename>CVE-2025-53506</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-53506</url>
     </references>
     <dates>
       <discovery>2025-07-10</discovery>
       <entry>2025-07-10</entry>
       <modified>2025-07-15</modified>
     </dates>
   </vuln>
 
   <vuln vid="20823cc0-5d45-11f0-966e-2cf05da270f3">
     <topic>Gitlab -- vulnerabilities</topic>
     <affects>
       <package>
 	<name>gitlab-ce</name>
 	<name>gitlab-ee</name>
 	<range><ge>18.1.0</ge><lt>18.1.2</lt></range>
 	<range><ge>18.0.0</ge><lt>18.0.4</lt></range>
 	<range><ge>13.3.0</ge><lt>17.11.6</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Gitlab reports:</p>
 	<blockquote cite="https://about.gitlab.com/releases/2025/07/09/patch-release-gitlab-18-1-2-released/">
 	  <p>Cross-site scripting issue impacts GitLab CE/EE</p>
 	  <p>Improper authorization issue impacts GitLab CE/EE</p>
 	  <p>Improper authorization issue impacts GitLab EE</p>
 	  <p>Improper authorization issue impacts GitLab EE</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-6948</cvename>
       <cvename>CVE-2025-3396</cvename>
       <cvename>CVE-2025-4972</cvename>
       <cvename>CVE-2025-6168</cvename>
       <url>https://about.gitlab.com/releases/2025/07/09/patch-release-gitlab-18-1-2-released/</url>
     </references>
     <dates>
       <discovery>2025-07-09</discovery>
       <entry>2025-07-10</entry>
     </dates>
   </vuln>
 
   <vuln vid="2a4472ed-5c0d-11f0-b991-291fce777db8">
     <topic>git -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>git</name>
 	<name>git-cvs</name>
 	<name>git-gui</name>
 	<name>git-p4</name>
 	<name>git-svn</name>
 	<range><lt>2.50.1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Git development team reports:</p>
 	<blockquote cite="https://lore.kernel.org/git/xmqq5xg2wrd1.fsf@gitster.g">
 	  <p>CVE-2025-27613: Gitk:
 	     When a user clones an untrusted repository and runs Gitk without
 	     additional command arguments, any writable file can be created and
 	     truncated. The option "Support per-file encoding" must have been
 	     enabled. The operation "Show origin of this line" is affected as
 	     well, regardless of the option being enabled or not.
 	  </p>
 	  <p>CVE-2025-27614: Gitk:
 	    A Git repository can be crafted in such a way that a user who has
 	    cloned the repository can be tricked into running any script
 	    supplied by the attacker by invoking `gitk filename`, where
 	    `filename` has a particular structure.
 	  </p>
 	  <p>CVE-2025-46835: Git GUI:
 	    When a user clones an untrusted repository and is tricked into
 	    editing a file located in a maliciously named directory in the
 	    repository, then Git GUI can create and overwrite any writable
 	    file.
 	  </p>
 	  <p>CVE-2025-48384: Git:
 	    When reading a config value, Git strips any trailing carriage
 	    return and line feed (CRLF). When writing a config entry, values
 	    with a trailing CR are not quoted, causing the CR to be lost when
 	    the config is later read.  When initializing a submodule, if the
 	    submodule path contains a trailing CR, the altered path is read
 	    resulting in the submodule being checked out to an incorrect
 	    location. If a symlink exists that points the altered path to the
 	    submodule hooks directory, and the submodule contains an executable
 	    post-checkout hook, the script may be unintentionally executed
 	    after checkout.
 	  </p>
 	  <p>CVE-2025-48385: Git:
 	    When cloning a repository Git knows to optionally fetch a bundle
 	    advertised by the remote server, which allows the server-side to
 	    offload parts of the clone to a CDN. The Git client does not
 	    perform sufficient validation of the advertised bundles, which
 	    allows the remote side to perform protocol injection.
 	    This protocol injection can cause the client to write the fetched
 	    bundle to a location controlled by the adversary. The fetched
 	    content is fully controlled by the server, which can in the worst
 	    case lead to arbitrary code execution.
 	  </p>
 	  <p>CVE-2025-48386: Git:
 	    The wincred credential helper uses a static buffer (`target`) as a
 	    unique key for storing and comparing against internal storage. This
 	    credential helper does not properly bounds check the available
 	    space remaining in the buffer before appending to it with
 	    `wcsncat()`, leading to potential buffer overflows.
 	  </p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-27613</cvename>
       <url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-27613</url>
       <cvename>CVE-2025-27614</cvename>
       <url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-27614</url>
       <cvename>CVE-2025-46835</cvename>
       <url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-46835</url>
       <cvename>CVE-2025-48384</cvename>
       <url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-48384</url>
       <cvename>CVE-2025-48385</cvename>
       <url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-48385</url>
       <cvename>CVE-2025-48386</cvename>
       <url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-48386</url>
     </references>
     <dates>
       <discovery>2025-04-11</discovery>
       <entry>2025-07-08</entry>
     </dates>
   </vuln>
 
   <vuln vid="79251dc8-5bc5-11f0-834f-b42e991fc52e">
     <topic>MongoDB -- Incorrect Handling of incomplete data may prevent mongoS from Accepting New Connections</topic>
     <affects>
       <package>
 	<name>mongodb60</name>
 	<range><lt>6.0.23</lt></range>
       </package>
       <package>
 	<name>mongodb70</name>
 	<range><lt>7.0.20</lt></range>
       </package>
       <package>
 	<name>mongodb80</name>
 	<range><lt>8.0.9</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>cna@mongodb.com reports:</p>
 	<blockquote cite="https://jira.mongodb.org/browse/SERVER-106753">
 	 <p>MongoDB Server&apos;s mongos component can become
 	unresponsive to new connections due to incorrect handling of
 	incomplete data. This affects MongoDB when configured with
 	load balancer support.
 	Required Configuration:
 	This affects MongoDB sharded clusters when configured with load
 	balancer support for mongos using HAProxy on specified ports.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-6714</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-6714</url>
     </references>
     <dates>
       <discovery>2025-07-07</discovery>
       <entry>2025-07-08</entry>
     </dates>
   </vuln>
 
   <vuln vid="77dc1fc4-5bc5-11f0-834f-b42e991fc52e">
     <topic>MongoDB -- may be susceptible to privilege escalation due to $mergeCursors stage</topic>
     <affects>
       <package>
 	<name>mongodb60</name>
 	<range><lt>6.0.22</lt></range>
       </package>
       <package>
 	<name>mongodb70</name>
 	<range><lt>7.0.20</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>cna@mongodb.com reports:</p>
 	<blockquote cite="https://jira.mongodb.org/browse/SERVER-106752">
 	  <p>An unauthorized user may leverage a specially crafted
 	  aggregation pipeline to access data without proper
 	  authorization due to improper handling of the $mergeCursors
 	  stage in MongoDB Server. This may lead to access to data
 	  without further authorisation.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-6713</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-6713</url>
     </references>
     <dates>
       <discovery>2025-07-07</discovery>
       <entry>2025-07-08</entry>
     </dates>
   </vuln>
 
   <vuln vid="764204eb-5bc5-11f0-834f-b42e991fc52e">
     <topic>MongoDB -- may be susceptible to DoS due to Accumulated Memory Allocation</topic>
     <affects>
       <package>
 	<name>mongodb80</name>
 	<range><lt>8.0.10</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>cna@mongodb.com reports:</p>
 	<blockquote cite="https://jira.mongodb.org/browse/SERVER-106751">
 	  <p>MongoDB Server may be susceptible to disruption caused by
 	  high memory usage, potentially leading to server crash. This
 	  condition is linked to inefficiencies in memory management
 	  related to internal operations. In scenarios where certain
 	  internal processes persist longer than anticipated, memory
 	  consumption can increase, potentially impacting server
 	  stability and availability.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-6712</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-6712</url>
     </references>
     <dates>
       <discovery>2025-07-07</discovery>
       <entry>2025-07-08</entry>
     </dates>
   </vuln>
 
   <vuln vid="72ddee1f-5bc5-11f0-834f-b42e991fc52e">
     <topic>MongoDB -- Incomplete Redaction of Sensitive Information in MongoDB Server Logs</topic>
     <affects>
       <package>
 	<name>mongodb60</name>
 	<range><lt>6.0.21</lt></range>
       </package>
       <package>
 	<name>mongodb70</name>
 	<range><lt>7.0.18</lt></range>
       </package>
       <package>
 	<name>mongodb80</name>
 	<range><lt>8.0.5</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>cna@mongodb.com reports:</p>
 	<blockquote cite="https://jira.mongodb.org/browse/SERVER-98720">
 	  <p>An issue has been identified in MongoDB Server where
 	  unredacted queries may inadvertently appear in server logs
 	  when certain error conditions are encountered.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-6711</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-6711</url>
     </references>
     <dates>
       <discovery>2025-07-07</discovery>
       <entry>2025-07-08</entry>
     </dates>
   </vuln>
 
   <vuln vid="c0f3f54c-5bc4-11f0-834f-b42e991fc52e">
     <topic>ModSecurity -- empty XML tag causes segmentation fault</topic>
     <affects>
       <package>
 	<name>ap24-mod_security</name>
 	<range><lt>2.9.11</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security-advisories@github.com reports:</p>
 	<blockquote cite="https://github.com/owasp-modsecurity/ModSecurity/commit/ecd7b9736836eee391d25f35d5bd06a3ce35a45d">
 	  <p>ModSecurity is an open source, cross platform web application
 	firewall (WAF) engine for Apache, IIS and Nginx.  In versions 2.9.8
 	to before 2.9.11, an empty XML tag can cause a segmentation fault.
 	If SecParseXmlIntoArgs is set to On or OnlyArgs, and the request
 	type is application/xml, and at least one XML tag is empty (eg
 	&lt;foo&gt;&lt;/foo&gt;), then a segmentation fault occurs.  This
 	issue has been patched in version 2.9.11.  A workaround involves
 	setting SecParseXmlIntoArgs to Off.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-52891</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-52891</url>
     </references>
     <dates>
       <discovery>2025-07-02</discovery>
       <entry>2025-07-08</entry>
     </dates>
   </vuln>
 
   <vuln vid="7b3e7f71-5b30-11f0-b507-000c295725e4">
     <topic>redis,valkey -- DoS Vulnerability due to bad connection error handling</topic>
     <affects>
       <package>
 	<name>redis</name>
 	<range><ge>8.0.0</ge><lt>8.0.3</lt></range>
       </package>
       <package>
 	<name>redis74</name>
 	<range><ge>7.4.0</ge><lt>7.4.5</lt></range>
       </package>
       <package>
 	<name>redis72</name>
 	<range><ge>7.2.0</ge><lt>7.2.10</lt></range>
       </package>
       <package>
 	<name>redis62</name>
 	<range><ge>6.2.0</ge><lt>6.2.19</lt></range>
       </package>
       <package>
 	<name>valkey</name>
 	<range><lt>8.1.3</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>@julienperriercornet reports:</p>
 	<blockquote cite="https://github.com/redis/redis/security/advisories/GHSA-4q32-c38c-pwgq">
 	  <p>
 	     An unauthenticated connection can cause repeated IP
 	     protocol errors, leading to client starvation and,
 	     ultimately, a denial of service.
 	  </p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-48367</cvename>
       <url>https://github.com/redis/redis/security/advisories/GHSA-4q32-c38c-pwgq</url>
     </references>
     <dates>
       <discovery>2025-07-06</discovery>
       <entry>2025-07-07</entry>
     </dates>
   </vuln>
 
   <vuln vid="f11d0a69-5b2d-11f0-b507-000c295725e4">
     <topic>redis,valkey -- Out of bounds write in hyperloglog commands leads to RCE</topic>
     <affects>
       <package>
 	<name>redis</name>
 	<range><ge>8.0.0</ge><lt>8.0.3</lt></range>
       </package>
       <package>
 	<name>redis74</name>
 	<range><ge>7.4.0</ge><lt>7.4.5</lt></range>
       </package>
       <package>
 	<name>redis72</name>
 	<range><ge>7.2.0</ge><lt>7.2.10</lt></range>
       </package>
       <package>
 	<name>redis62</name>
 	<range><ge>6.2.0</ge><lt>6.2.19</lt></range>
       </package>
       <package>
 	<name>valkey</name>
 	<range><lt>8.1.3</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Seunghyun Lee reports:</p>
 	<blockquote cite="https://github.com/redis/redis/security/advisories/GHSA-rp2m-q4j6-gr43">
 	  <p>
 	    An authenticated user may use a specially crafted string
 	    to trigger a stack/heap out of bounds write on hyperloglog
 	    operations, potentially leading to remote code execution.
 	  </p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-32023</cvename>
       <url>https://github.com/redis/redis/security/advisories/GHSA-rp2m-q4j6-gr43</url>
     </references>
     <dates>
       <discovery>2025-07-06</discovery>
       <entry>2025-07-07</entry>
     </dates>
   </vuln>
 
   <vuln vid="4ea9cbc3-5b28-11f0-b507-000c295725e4">
     <topic>redis,valkey -- {redis,valkey}-check-aof may lead to stack overflow and potential RCE</topic>
     <affects>
       <package>
 	<name>redis</name>
 	<range><ge>8.0.0</ge><lt>8.0.2</lt></range>
       </package>
       <package>
 	<name>redis74</name>
 	<range><ge>7.4.0</ge><lt>7.4.4</lt></range>
       </package>
       <package>
 	<name>redis72</name>
 	<range><ge>7.2.0</ge><lt>7.2.9</lt></range>
       </package>
       <package>
 	<name>valkey</name>
 	<range><lt>8.1.2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Simcha Kosman &amp; CyberArk Labs reports:</p>
 	<blockquote cite="https://github.com/redis/redis/security/advisories/GHSA-5453-q98w-cmvm">
 	  <p>A user can run the {redis,valkeyu}-check-aof cli and pass
 	  a long file path to trigger a stack buffer overflow, which
 	  may potentially lead to remote code execution.</p>
 	  <p></p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-27151</cvename>
       <url>https://github.com/redis/redis/security/advisories/GHSA-5453-q98w-cmvm</url>
     </references>
     <dates>
       <discovery>2025-05-28</discovery>
       <entry>2025-07-07</entry>
     </dates>
   </vuln>
 
   <vuln vid="7642ba72-5abf-11f0-87ba-002590c1f29c">
     <topic>FreeBSD -- Use-after-free in multi-threaded xz decoder</topic>
     <affects>
       <package>
 	<name>FreeBSD</name>
 	<range><ge>14.2</ge><lt>14.2_4</lt></range>
 	<range><ge>13.5</ge><lt>13.5_2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<h1>Problem Description:</h1>
 	<p>A worker thread could free its input buffer after decoding,
 	while the main thread might still be writing to it.  This leads to
 	an use-after-free condition on heap memory.</p>
 	<h1>Impact:</h1>
 	<p>An attacker may use specifically crafted .xz file to cause
 	multi-threaded xz decoder to crash, or potentially run arbitrary
 	code under the credential the decoder was executed.</p>
       </body>
     </description>
     <references>
       <cvename>CVE-2025-31115</cvename>
       <freebsdsa>SA-25:06.xz</freebsdsa>
     </references>
     <dates>
       <discovery>2025-07-02</discovery>
       <entry>2025-07-06</entry>
     </dates>
   </vuln>
 
   <vuln vid="69bfe2a4-5a39-11f0-8792-4ccc6adda413">
     <topic>gstreamer1-plugins-bad -- stack buffer overflow in H.266 video parser</topic>
     <affects>
       <package>
 	<name>gstreamer1-plugins-bad</name>
 	<range><lt>1.26.2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>GStreamer Security Center reports:</p>
 	<blockquote cite="https://gstreamer.freedesktop.org/security/sa-2025-0007.html">
 	  <p>It is possible for a malicious third party to trigger a buffer overflow that can
 	   result in a crash of the application and possibly also allow code execution through
 	   stack manipulation.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-6663</cvename>
       <url>https://gstreamer.freedesktop.org/security/sa-2025-0007.html</url>
     </references>
     <dates>
       <discovery>2025-06-26</discovery>
       <entry>2025-07-06</entry>
     </dates>
   </vuln>
 
   <vuln vid="a55d2120-58cf-11f0-b4ad-b42e991fc52e">
     <topic>firefox -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>140.0,2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/buglist.cgi?bug_id=1941377%2C1960948%2C1966187%2C1966505%2C1970764">
 	<p>An attacker was able to bypass the `connect-src`
 	  directive of a Content Security Policy by manipulating
 	  subdocuments.  This would have also hidden the connections
 	  from the Network tab in Devtools.</p>
 	<p>When Multi-Account Containers was enabled, DNS requests
 	could have bypassed a SOCKS proxy when the domain name was
 	invalid or the SOCKS proxy was not responding.</p>
 	<p>If a user visited a webpage with an invalid TLS
 	certificate, and granted an exception, the webpage was able to
 	provide a WebAuthn challenge that the user would be prompted
 	to complete.  This is in violation of the WebAuthN spec which
 	requires &quot;a secure transport established without
 	errors&quot;.</p>
 	<p>The exception page for the HTTPS-Only feature, displayed
 	when a website is opened via HTTP, lacked an anti-clickjacking
 	delay, potentially allowing an attacker to trick a user into
 	granting an exception and loading a webpage over HTTP.</p>
 	<p>If a user saved a response from the Network tab in Devtools
 	using the Save As context menu option, that file may not have
 	been saved with the `.download` file extension.
 	This could have led to the user inadvertently running a
 	malicious executable.</p>
 	<p>Memory safety bugs present in Firefox 139 and Thunderbird
 	139. Some of these bugs showed evidence of memory corruption
 	and we presume that with enough effort some of these could
 	have been exploited to run arbitrary code.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-6427</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-6427</url>
       <cvename>CVE-2025-6432</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-6432</url>
       <cvename>CVE-2025-6433</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-6433</url>
       <cvename>CVE-2025-6434</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-6434</url>
       <cvename>CVE-2025-6435</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-6435</url>
       <cvename>CVE-2025-6436</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-6436</url>
     </references>
     <dates>
       <discovery>2025-06-24</discovery>
       <entry>2025-07-04</entry>
     </dates>
   </vuln>
 
   <vuln vid="9bad6f79-58cf-11f0-b4ad-b42e991fc52e">
     <topic>firefox -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>128.12.0,2</lt></range>
 	<range><lt>140.0,2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1971140">
 	<p>Firefox could have incorrectly parsed a URL and rewritten
 	it to the youtube.com domain when parsing the URL specified
 	in an `embed` tag. This could have bypassed website security
 	checks that restricted which domains users were allowed to
 	embed.</p>
 	<p>When a file download is specified via the
 	`Content-Disposition` header, that directive would be ignored
 	if the file was included via a `&amp;lt;embed&amp;gt;` or
 	`&amp;lt;object&amp;gt;` tag, potentially making a website
 	vulnerable to a cross-site scripting attack.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-6429</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-6429</url>
       <cvename>CVE-2025-6430</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-6430</url>
     </references>
     <dates>
       <discovery>2025-06-24</discovery>
       <entry>2025-07-04</entry>
     </dates>
   </vuln>
 
   <vuln vid="9320590b-58cf-11f0-b4ad-b42e991fc52e">
     <topic>Mozilla -- persistent UUID that identifies browser</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>140.0,2</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>115.25.0</lt></range>
 	<range><lt>128.12</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>140.0</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>128.12</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1717672">
 	  <p>An attacker who enumerated resources from the WebCompat extension
 	could have obtained a persistent UUID that identified the browser,
 	and persisted between containers and normal/private browsing mode,
 	but not profiles.  This vulnerability affects Firefox &lt; 140,
 	Firefox ESR &lt; 115.25, Firefox ESR &lt; 128.12, Thunderbird &lt;
 	140, and Thunderbird &lt; 128.12.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-6425</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-6425</url>
     </references>
     <dates>
       <discovery>2025-06-24</discovery>
       <entry>2025-07-04</entry>
     </dates>
   </vuln>
 
   <vuln vid="d607b12c-5821-11f0-ab92-f02f7497ecda">
     <topic>php -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>php81</name>
 	<range><lt>8.1.33</lt></range>
       </package>
       <package>
 	<name>php82</name>
 	<range><lt>8.2.29</lt></range>
       </package>
       <package>
 	<name>php83</name>
 	<range><lt>8.3.23</lt></range>
       </package>
       <package>
 	<name>php84</name>
 	<range><lt>8.4.10</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>php.net reports:</p>
     <blockquote cite="https://www.php.net/ChangeLog-8.php">
     <ul>
       <li>
       CVE-2025-1735: pgsql extension does not check for errors during escaping
       </li>
       <li>
       CVE-2025-6491: NULL Pointer Dereference in PHP SOAP Extension via Large XML Namespace Prefix
       </li>
       <li>
       CVE-2025-1220: Null byte termination in hostnames
       </li>
     </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-1735</cvename>
       <cvename>CVE-2025-6491</cvename>
       <cvename>CVE-2025-1220</cvename>
     </references>
     <dates>
       <discovery>2025-02-27</discovery>
       <entry>2025-07-03</entry>
     </dates>
   </vuln>
 
   <vuln vid="bab7386a-582f-11f0-97d0-b42e991fc52e">
     <topic>Mozilla -- exploitable crash</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>140.0,2</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>115.25.0</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>140.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1966423">
 	  <p>A use-after-free in FontFaceSet resulted in a potentially
 	  exploitable crash.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-6424</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-6424</url>
     </references>
     <dates>
       <discovery>2025-06-24</discovery>
       <entry>2025-07-03</entry>
     </dates>
   </vuln>
 
   <vuln vid="5c777f88-40ff-4e1e-884b-ad63dfb9bb15">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>138.0.7204.96</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>138.0.7204.96</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2025/06/stable-channel-update-for-desktop_30.html">
 	 <p>This update includes 1 security fix:</p>
 	 <ul>
 	    <li>[427663123] High CVE-2025-6554: Type Confusion in V8.</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2025-6554</cvename>
       <url>https://chromereleases.googleblog.com/2025/06/stable-channel-update-for-desktop_30.html</url>
     </references>
     <dates>
       <discovery>2025-06-30</discovery>
       <entry>2025-07-02</entry>
     </dates>
   </vuln>
 
   <vuln vid="9c91e1f8-f255-4b57-babe-2e385558f1dc">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>138.0.7204.49</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>138.0.7204.49</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2025/06/stable-channel-update-for-desktop_24.html">
 	 <p>This update includes 11 security fixes:</p>
 	 <ul>
 	    <li>[407328533] Medium CVE-2025-6555: Use after free in Animation. Reported by Lyra Rebane (rebane2001) on 2025-03-30</li>
 	    <li>[40062462] Low CVE-2025-6556: Insufficient policy enforcement in Loader. Reported by Shaheen Fazim on 2023-01-02</li>
 	    <li>[406631048] Low CVE-2025-6557: Insufficient data validation in DevTools. Reported by Ameen Basha M K on 2025-03-27</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2025-6555</cvename>
       <cvename>CVE-2025-6556</cvename>
       <cvename>CVE-2025-6557</cvename>
       <url>https://chromereleases.googleblog.com/2025/06/stable-channel-update-for-desktop_24.html</url>
     </references>
     <dates>
       <discovery>2025-06-24</discovery>
       <entry>2025-07-02</entry>
     </dates>
   </vuln>
 
   <vuln vid="24f4b495-56a1-11f0-9621-93abbef07693">
     <topic>sudo -- privilege escalation vulnerability through host and chroot options</topic>
     <affects>
       <package>
 	<name>sudo</name>
 	<range><lt>1.9.17p1</lt></range>
       </package>
       <package>
 	<name>sudo-sssd</name>
 	<range><lt>1.9.17p1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Todd C. Miller reports, crediting Rich Mirch from Stratascale Cyber Research Unit (CRU):</p>
 	<blockquote cite="https://www.sudo.ws/releases/stable/">
 	  <p>Sudo 1.9.17p1:</p>
 	  <ul>
 	    <li>
 	      Fixed CVE-2025-32462. Sudo's -h (--host) option could be specified
 	      when running a command or editing a file. This could enable a
 	      local privilege escalation attack if the sudoers file allows the
 	      user to run commands on a different host. For more information,
 	      see Local Privilege Escalation via host option.
 	    </li>
 	    <li>
 	      Fixed CVE-2025-32463. An attacker can leverage sudo's -R
 	      (--chroot) option to run arbitrary commands as root, even if they
 	      are not listed in the sudoers file. The chroot support has been
 	      deprecated an will be removed entirely in a future release. For
 	      more information, see Local Privilege Escalation via chroot
 	      option.
 	    </li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-32462</cvename>
       <cvename>CVE-2025-32463</cvename>
       <url>https://www.sudo.ws/releases/stable/</url>
       <url>https://www.stratascale.com/vulnerability-alert-CVE-2025-32462-sudo-host</url>
       <url>https://www.stratascale.com/vulnerability-alert-CVE-2025-32463-sudo-chroot</url>
     </references>
     <dates>
       <discovery>2025-04-01</discovery>
       <entry>2025-07-01</entry>
     </dates>
   </vuln>
 
   <vuln vid="8df49466-5664-11f0-943a-18c04d5ea3dc">
     <topic>xorg server -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>xorg-server</name>
 	<name>xephyr</name>
 	<name>xorg-vfbserver</name>
 	<range><lt>21.1.18,1</lt></range>
       </package>
       <package>
 	<name>xorg-nextserver</name>
 	<range><lt>21.1.18,2</lt></range>
       </package>
       <package>
 	<name>xwayland</name>
 	<range><lt>24.1.8,1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The X.Org project reports:</p>
 	<blockquote cite="https://lists.x.org/archives/xorg-announce/2025-February/003584.html">
 	  <ul>
 	    <li>
 	      CVE-2025-49176: Integer overflow in Big Requests Extension
 	      <p>The Big Requests extension allows requests larger than the 16-bit length
 	      limit.
 	      It uses integers for the request length and checks for the size not to
 	      exceed the maxBigRequestSize limit, but does so after translating the
 	      length to integer by multiplying the given size in bytes by 4.
 	      In doing so, it might overflow the integer size limit before actually
 	      checking for the overflow, defeating the purpose of the test.</p>
 	    </li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-49176</cvename>
       <url>https://lists.x.org/archives/xorg/2025-June/062055.html</url>
     </references>
     <dates>
       <discovery>2025-06-17</discovery>
       <entry>2025-07-01</entry>
     </dates>
   </vuln>
 
   <vuln vid="b14cabf7-5663-11f0-943a-18c04d5ea3dc">
     <topic>xorg server -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>xorg-server</name>
 	<name>xephyr</name>
 	<name>xorg-vfbserver</name>
 	<range><lt>21.1.17,1</lt></range>
       </package>
       <package>
 	<name>xorg-nextserver</name>
 	<range><lt>21.1.17,2</lt></range>
       </package>
       <package>
 	<name>xwayland</name>
 	<range><lt>24.1.7,1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The X.Org project reports:</p>
 	<blockquote cite="https://lists.x.org/archives/xorg-announce/2025-February/003584.html">
 	  <ul>
 	    <li>
 	      CVE-2025-49175: Out-of-bounds access in X Rendering extension (Animated cursors)
 	      <p>The X Rendering extension allows creating animated cursors providing a
 	      list of cursors.
 	      By default, the Xserver assumes at least one cursor is provided while a
 	      client may actually pass no cursor at all, which causes an out-of-bound
 	      read creating the animated cursor and a crash of the Xserver.</p>
 	    </li>
 	    <li>
 	      CVE-2025-49177: Data leak in XFIXES Extension 6 (XFixesSetClientDisconnectMode)
 
 	      <p>The handler of XFixesSetClientDisconnectMode does not check the client
 	      request length.
 	      A client could send a shorter request and read data from a former
 	      request.</p>
 	    </li>
 	    <li>
 	      CVE-2025-49178: Unprocessed client request via bytes to ignore
 
 	      <p>When reading requests from the clients, the input buffer might be shared
 	      and used between different clients.
 	      If a given client sends a full request with non-zero bytes to ignore,
 	      the bytes to ignore may still be non-zero even though the request is
 	      full, in which case the buffer could be shared with another client who's
 	      request will not be processed because of those bytes to ignore, leading
 	      to a possible hang of the other client request.</p>
 	    </li>
 	    <li>
 	      CVE-2025-49179: Integer overflow in X Record extension
 
 	      <p>The RecordSanityCheckRegisterClients() function in the X Record extension
 	      implementation of the Xserver checks for the request length, but does not
 	      check for integer overflow.
 	      A client might send a very large value for either the number of clients
 	      or the number of protocol ranges that will cause an integer overflow in
 	      the request length computation, defeating the check for request length.</p>
 	    </li>
 	    <li>
 	      CVE-2025-49180: Integer overflow in RandR extension (RRChangeProviderProperty)
 
 	      <p>A client might send a request causing an integer overflow when computing
 	      the total size to allocate in RRChangeProviderProperty().</p>
 	    </li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-49175</cvename>
       <cvename>CVE-2025-49177</cvename>
       <cvename>CVE-2025-49178</cvename>
       <cvename>CVE-2025-49179</cvename>
       <cvename>CVE-2025-49180</cvename>
       <url>https://lists.x.org/archives/xorg/2025-June/062055.html</url>
     </references>
     <dates>
       <discovery>2025-06-17</discovery>
       <entry>2025-07-01</entry>
     </dates>
   </vuln>
 
   <vuln vid="6b1b8989-55b0-11f0-ac64-589cfc10a551">
     <topic>podman -- TLS connection used to pull VM images was not validated</topic>
     <affects>
       <package>
 	<name>podman</name>
 	<range><lt>5.5.2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>RedHat, Inc. reports:</p>
 	<blockquote cite="https://nvd.nist.gov/vuln/detail/CVE-2025-6032">
 	  <p>A flaw was found in Podman.  The podman machine init command fails to verify the TLS
 	  certificate when downloading the VM images from an OCI registry.  This issue results
 	  in a Man In The Middle attack.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-6032</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-6032</url>
     </references>
     <dates>
       <discovery>2025-06-30</discovery>
       <entry>2025-06-30</entry>
     </dates>
   </vuln>
 
   <vuln vid="5e64770c-52aa-11f0-b522-b42e991fc52e">
     <topic>MongoDB -- Running certain aggregation operations with the SBE engine may lead to unexpected behavior</topic>
     <affects>
       <package>
 	<name>mongodb60</name>
 	<range><lt>6.0.21</lt></range>
       </package>
       <package>
 	<name>mongodb70</name>
 	<range><lt>7.0.17</lt></range>
       </package>
       <package>
 	<name>mongodb80</name>
 	<range><lt>8.0.4</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>cna@mongodb.com reports:</p>
 	<blockquote cite="https://jira.mongodb.org/browse/SERVER-106746">
 	  <p>An authenticated user may trigger a use after free that may result
 	in MongoDB Server crash and other unexpected behavior, even if the
 	user does not have authorization to shut down a server.  The crash
 	is triggered on affected versions by issuing an aggregation framework
 	operation using a specific combination of rarely-used aggregation
 	pipeline expressions.  This issue affects MongoDB Server v6.0 version
 	prior to 6.0.21, MongoDB Server v7.0 version prior to 7.0.17 and
 	MongoDB Server v8.0 version prior to 8.0.4 when the SBE engine is
 	enabled.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-6706</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-6706</url>
     </references>
     <dates>
       <discovery>2025-06-26</discovery>
       <entry>2025-06-26</entry>
     </dates>
   </vuln>
 
   <vuln vid="5cd2bd2b-52aa-11f0-b522-b42e991fc52e">
     <topic>MongoDB -- Race condition in privilege cache invalidation cycle</topic>
     <affects>
       <package>
 	<name>mongodb50</name>
 	<range><lt>5.0.31</lt></range>
       </package>
       <package>
 	<name>mongodb60</name>
 	<range><lt>6.0.24</lt></range>
       </package>
       <package>
 	<name>mongodb70</name>
 	<range><lt>7.0.21</lt></range>
       </package>
       <package>
 	<name>mongodb80</name>
 	<range><lt>8.0.5</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>NVD reports:</p>
 	<blockquote cite="https://nvd.nist.gov/vuln/detail/CVE-2025-6707">
 	  <p>Under certain conditions, an authenticated user request
 	    may execute with stale privileges following an intentional
 	    change by an authorized administrator.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-6707</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-6707</url>
     </references>
     <dates>
       <discovery>2025-06-26</discovery>
       <entry>2025-06-26</entry>
     </dates>
   </vuln>
 
   <vuln vid="5b87eef6-52aa-11f0-b522-b42e991fc52e">
     <topic>MongoDB -- Pre-Authentication Denial of Service Vulnerability in MongoDB Server&apos;s OIDC Authentication</topic>
     <affects>
       <package>
 	<name>mongodb60</name>
 	<range><lt>6.0.21</lt></range>
       </package>
       <package>
 	<name>mongodb70</name>
 	<range><lt>7.0.17</lt></range>
       </package>
       <package>
 	<name>mongodb80</name>
 	<range><lt>8.0.5</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>NVD reports:</p>
 	<blockquote cite="https://nvd.nist.gov/vuln/detail/CVE-2025-6709">
 	  <p>The MongoDB Server is susceptible to a denial of service
 	    vulnerability due to improper handling of specific date
 	    values in JSON input when using OIDC authentication.
 	    This can be reproduced using the mongo shell to send a
 	    malicious JSON payload leading to an invariant failure
 	    and server crash. </p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-6709</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-6709</url>
     </references>
     <dates>
       <discovery>2025-06-26</discovery>
       <entry>2025-06-26</entry>
     </dates>
   </vuln>
 
   <vuln vid="59ed4b19-52aa-11f0-b522-b42e991fc52e">
     <topic>MongoDB -- Pre-authentication Denial of Service Stack Overflow Vulnerability in JSON Parsing via Excessive Recursion in MongoDB</topic>
     <affects>
       <package>
 	<name>mongodb70</name>
 	<range><lt>7.0.17</lt></range>
       </package>
       <package>
 	<name>mongodb80</name>
 	<range><lt>8.0.5</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>cna@mongodb.com reports:</p>
 	<blockquote cite="https://jira.mongodb.org/browse/SERVER-106749">
 	  <p>MongoDB Server may be susceptible to stack overflow due to JSON
 	parsing mechanism, where specifically crafted JSON inputs may induce
 	unwarranted levels of recursion, resulting in excessive stack space
 	consumption.  Such inputs can lead to a stack overflow that causes
 	the server to crash which could occur pre-authorisation.  This issue
 	affects MongoDB Server v7.0 versions prior to 7.0.17 and MongoDB
 	Server v8.0 versions prior to 8.0.5.
 	The same issue affects MongoDB Server v6.0 versions prior to 6.0.21,
 	but an attacker can only induce denial of service after authenticating.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-6710</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-6710</url>
     </references>
     <dates>
       <discovery>2025-06-26</discovery>
       <entry>2025-06-26</entry>
     </dates>
   </vuln>
 
   <vuln vid="e26608ff-5266-11f0-b522-b42e991fc52e">
     <topic>kanboard -- Password Reset Poisoning via Host Header Injection</topic>
     <affects>
       <package>
 	<name>kanboard</name>
 	<range><lt>1.2.45</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>GitHub Security Advisories reports:</p>
 	<blockquote cite="null">
 	<p>
 	Kanboard allows password reset emails to be sent with URLs
 	derived from the unvalidated Host header when the
 	application_url configuration is unset (default behavior).
 	This allows an attacker to craft a malicious password
 	reset link that leaks the token to an attacker-controlled
 	domain. If a victim (including an administrator) clicks
 	the poisoned link, their account can be taken over. This
 	affects all users who initiate a password reset while
 	application_url is not set.
 	</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-52560</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-52560</url>
     </references>
     <dates>
       <discovery>2025-06-26</discovery>
       <entry>2025-06-26</entry>
     </dates>
   </vuln>
 
   <vuln vid="d45dabd9-5232-11f0-9ca4-2cf05da270f3">
     <topic>Gitlab -- Vulnerabilities</topic>
     <affects>
       <package>
 	<name>gitlab-ce</name>
 	<name>gitlab-ee</name>
 	<range><ge>18.1.0</ge><lt>18.1.1</lt></range>
 	<range><ge>18.0.0</ge><lt>18.0.3</lt></range>
 	<range><ge>16.10.0</ge><lt>17.11.5</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Gitlab reports:</p>
 	<blockquote cite="https://about.gitlab.com/releases/2025/06/25/patch-release-gitlab-18-1-1-released/">
 	  <p>Denial of Service impacts GitLab CE/EE</p>
 	  <p>Missing Authentication issue impacts GitLab CE/EE</p>
 	  <p>Improper access control issue impacts GitLab CE/EE</p>
 	  <p>Elevation of Privilege impacts GitLab CE/EE</p>
 	  <p>Improper access control issue impacts GitLab EE</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-3279</cvename>
       <cvename>CVE-2025-1754</cvename>
       <cvename>CVE-2025-5315</cvename>
       <cvename>CVE-2025-2938</cvename>
       <cvename>CVE-2025-5846</cvename>
       <url>https://about.gitlab.com/releases/2025/06/25/patch-release-gitlab-18-1-1-released/</url>
     </references>
     <dates>
       <discovery>2025-06-25</discovery>
       <entry>2025-06-26</entry>
     </dates>
   </vuln>
 
   <vuln vid="03ba1cdd-4faf-11f0-af06-00a098b42aeb">
     <topic>cisco -- OpenH264 Decoding Functions Heap Overflow Vulnerability</topic>
     <affects>
       <package>
 	<name>openh264</name>
 	<range><lt>2.5.1,2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Cisco reports:</p>
 	<blockquote cite="https://github.com/cisco/openh264/releases/tag/2.5.1">
 	  <p>A vulnerability in the decoding functions
 	of OpenH264 codec library could allow a remote, unauthenticated
 	attacker to trigger a heap overflow.  This vulnerability is due to
 	a race condition between a Sequence Parameter Set (SPS) memory
 	allocation and a subsequent non Instantaneous Decoder Refresh
 	(non-IDR) Network Abstraction Layer (NAL) unit memory usage.  An
 	attacker could exploit this vulnerability by crafting a malicious
 	bitstream and tricking a victim user into processing an arbitrary
 	video containing the malicious bistream.  An exploit could allow
 	the attacker to cause an unexpected crash in the victim's user
 	decoding client and, possibly, perform arbitrary commands on the
 	victim's host by abusing the heap overflow.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-27091</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-27091</url>
     </references>
     <dates>
       <discovery>2025-02-20</discovery>
       <entry>2025-06-22</entry>
     </dates>
   </vuln>
 
   <vuln vid="6c6c1507-4da5-11f0-afcc-f02f7432cf97">
     <topic>clamav -- ClamAV UDF File Parsing Out-Of-Bounds Read Information Disclosure Vulnerability</topic>
     <affects>
       <package>
 	<name>clamav</name>
 	<range><ge>1.2.0,1</ge><lt>1.4.3,1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Cisco reports:</p>
 	<blockquote cite="https://blog.clamav.net/2025/06/clamav-143-and-109-security-patch.html">
 	  <p>A vulnerability in Universal Disk Format (UDF) processing of ClamAV
 	could allow an unauthenticated, remote attacker to cause a denial
 	of service (DoS) condition on an affected device.
 
 	This vulnerability is due to a memory overread during UDF file
 	scanning.  An attacker could exploit this vulnerability by submitting
 	a crafted file containing UDF content to be scanned by ClamAV on
 	an affected device.  A successful exploit could allow the attacker
 	to terminate the ClamAV scanning process, resulting in a DoS condition
 	on the affected software.  For a description of this vulnerability,
 	see the .</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-20234</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-20234</url>
     </references>
     <dates>
       <discovery>2025-06-18</discovery>
       <entry>2025-06-20</entry>
     </dates>
   </vuln>
 
   <vuln vid="3dcc0812-4da5-11f0-afcc-f02f7432cf97">
     <topic>clamav -- ClamAV PDF Scanning Buffer Overflow Vulnerability</topic>
     <affects>
       <package>
 	<name>clamav</name>
 	<range><lt>1.4.3,1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Cisco reports:</p>
 	<blockquote cite="https://blog.clamav.net/2025/06/clamav-143-and-109-security-patch.html">
 	  <p>A vulnerability in the PDF scanning processes of ClamAV could allow
 	an unauthenticated, remote attacker to cause a buffer overflow
 	condition, cause a denial of service (DoS) condition, or execute
 	arbitrary code on an affected device.
 
 	This vulnerability exists because memory buffers are allocated
 	incorrectly when PDF files are processed.  An attacker could exploit
 	this vulnerability by submitting a crafted PDF file to be scanned
 	by ClamAV on an affected device.  A successful exploit could allow
 	the attacker to trigger a buffer overflow, likely resulting in the
 	termination of the ClamAV scanning process and a DoS condition on
 	the affected software.  Although unproven, there is also a possibility
 	that an attacker could leverage the buffer overflow to execute
 	arbitrary code with the privileges of the ClamAV process.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-20260</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-20260</url>
     </references>
     <dates>
       <discovery>2025-06-18</discovery>
       <entry>2025-06-20</entry>
     </dates>
   </vuln>
 
   <vuln vid="333b4663-4cde-11f0-8cb5-a8a1599412c6">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>137.0.7151.119</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>137.0.7151.119</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2025/06/stable-channel-update-for-desktop_17.html">
 	 <p>This update includes 3 security fixes:</p>
 	 <ul>
 	    <li>[420697404] High CVE-2025-6191: Integer overflow in V8. Reported by Shaheen Fazim on 2025-05-27</li>
 	    <li>[421471016] High CVE-2025-6192: Use after free in Profiler. Reported by Chaoyuan Peng (@ret2happy) on 2025-05-31</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2025-6191</cvename>
       <cvename>CVE-2025-6192</cvename>
       <url>https://chromereleases.googleblog.com/2025/06/stable-channel-update-for-desktop_17.html</url>
     </references>
     <dates>
       <discovery>2025-06-17</discovery>
       <entry>2025-06-19</entry>
     </dates>
   </vuln>
 
   <vuln vid="fc2d2fb8-4c83-11f0-8deb-f8f21e52f724">
     <topic>Navidrome -- SQL Injection via role parameter</topic>
     <affects>
       <package>
 	<name>navidrome</name>
 	<range><gt>0.55.0</gt><lt>0.56.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Deluan reports:</p>
 	<blockquote cite="https://github.com/navidrome/navidrome/security/advisories/GHSA-5wgp-vjxm-3x2r">
 	  <p>This vulnerability arises due to improper input validation on the role parameter within the API endpoint /api/artist. Attackers can exploit this flaw to inject arbitrary SQL queries, potentially gaining unauthorized access to the backend database and compromising sensitive user information.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-48949</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-48949</url>
     </references>
     <dates>
       <discovery>2025-05-29</discovery>
       <entry>2025-06-18</entry>
     </dates>
   </vuln>
 
   <vuln vid="6548cb01-4c33-11f0-8a97-6c3be5272acd">
     <topic>Grafana -- DingDing contact points exposed in Grafana Alerting</topic>
     <affects>
       <package>
 	<name>grafana</name>
 	<range><lt>10.4.19+security-01</lt></range>
 	<range><ge>11.0.0</ge><lt>11.2.10+security-01</lt></range>
 	<range><ge>11.3.0</ge><lt>11.3.7+security-01</lt></range>
 	<range><ge>11.4.0</ge><lt>11.4.5+security-01</lt></range>
 	<range><ge>11.5.0</ge><lt>11.5.5+security-01</lt></range>
 	<range><ge>11.6.0</ge><lt>11.6.2+security-01</lt></range>
 	<range><ge>12.0.0</ge><lt>12.0.1+security-01</lt></range>
       </package>
       <package>
 	<name>grafana8</name>
 	<range><ge>8.0.0</ge></range>
       </package>
       <package>
 	<name>grafana9</name>
 	<range><ge>9.0.0</ge></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Grafana Labs reports:</p>
 	<blockquote cite="https://grafana.com/blog/2025/06/13/grafana-security-update-medium-severity-security-release-for-cve-2025-3415/">
 	  <p>An incident occurred where the DingDing alerting integration URL
 	  was inadvertently exposed to viewers due to a setting oversight,
 	  which we learned about through a <a href="https://grafana.com/blog/2023/05/04/introducing-the-grafana-labs-bug-bounty-program/">bug bounty report</a>.</p>
 	  <p>The CVSS 3.0 score for this vulnerability is 4.3 (Medium).</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-3415</cvename>
       <url>https://grafana.com/blog/2025/06/13/grafana-security-update-medium-severity-security-release-for-cve-2025-3415/</url>
     </references>
     <dates>
       <discovery>2025-04-05</discovery>
       <entry>2025-06-18</entry>
     </dates>
   </vuln>
 
   <vuln vid="ee046f5d-37a8-11f0-baaa-6c3be5272acd">
     <topic>Grafana -- User deletion issue</topic>
     <affects>
       <package>
 	<name>grafana</name>
 	<range><ge>5.4.0</ge><lt>10.4.18+security-01</lt></range>
 	<range><ge>11.0.0</ge><lt>11.2.9+security-01</lt></range>
 	<range><ge>11.3.0</ge><lt>11.3.6+security-01</lt></range>
 	<range><ge>11.4.0</ge><lt>11.4.4+security-01</lt></range>
 	<range><ge>11.5.0</ge><lt>11.5.4+security-01</lt></range>
 	<range><ge>11.6.0</ge><lt>11.6.1+security-01</lt></range>
 	<range><ge>12.0.0</ge><lt>12.0.0+security-01</lt></range>
       </package>
       <package>
 	<name>grafana8</name>
 	<range><ge>8.0.0</ge></range>
       </package>
       <package>
 	<name>grafana9</name>
 	<range><ge>9.0.0</ge></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Grafana Labs reports:</p>
 	<blockquote cite="https://grafana.com/blog/2025/05/23/grafana-security-release-medium-and-high-severity-security-fixes-for-cve-2025-4123-and-cve-2025-3580/">
 	  <p>On April 15, we discovered a vulnerability that stems from the user
 	  deletion logic associated with organization administrators.
 	  An organization admin could remove any user from the specific
 	  organization they manage. Additionally, they have the power to delete
 	  users entirely from the system if they have no other org membership.
 	  This leads to two situations:</p>
 	  <ol>
 	    <li>They can delete a server admin if the organization
 	    the Organization Admin manages is the server admin’s final
 	    organizational membership.</li>
 	    <li>They can delete any user (regardless of whether they are a server
 	    admin or not) if that user currently belongs to no organizations.</li>
 	  </ol>
 	  <p>These two situations allow an organization manager to disrupt
 	  instance-wide activity by continually deleting server administrators
 	  if there is only one organization or if the server administrators are
 	  not part of any organization.</p>
 	  <p>The CVSS score for this vulnerability is 5.5 Medium.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-3580</cvename>
       <url>https://grafana.com/blog/2025/05/23/grafana-security-release-medium-and-high-severity-security-fixes-for-cve-2025-4123-and-cve-2025-3580/</url>
     </references>
     <dates>
       <discovery>2025-04-15</discovery>
       <entry>2025-05-23</entry>
     </dates>
   </vuln>
 
   <vuln vid="b704d4b8-4b87-11f0-9605-b42e991fc52e">
     <topic>Firefox -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>139.0.4,2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1970095">
 	  <p>CVE-2025-49709: Certain canvas operations could have lead
 	  to memory corruption.</p>
 	  <p>CVE-2025-49710: An integer overflow was present in
 	  `OrderedHashTable` used by the JavaScript engine.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-49709</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-49709</url>
       <cvename>CVE-2025-49710</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-49710</url>
     </references>
     <dates>
       <discovery>2025-06-11</discovery>
       <entry>2025-06-17</entry>
     </dates>
   </vuln>
 
   <vuln vid="e3d6d485-c93c-4ada-90b3-09f1c454fb8a">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>137.0.7151.103</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>137.0.7151.103</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2025/06/stable-channel-update-for-desktop_10.html">
 	 <p>This update includes 2 security fixes:</p>
 	 <ul>
 	    <li>[$8000][420150619] High CVE-2025-5958: Use after free in Media. Reported by Huang Xilin of Ant Group Light-Year Security Lab on 2025-05-25</li>
 	    <li>[NA][422313191] High CVE-2025-5959: Type Confusion in V8. Reported by Seunghyun Lee as part of TyphoonPWN 2025 on 2025-06-04</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2025-5958</cvename>
       <cvename>CVE-2025-5959</cvename>
       <url>https://chromereleases.googleblog.com/2025/06/stable-channel-update-for-desktop_10.html</url>
     </references>
     <dates>
       <discovery>2025-06-10</discovery>
       <entry>2025-06-17</entry>
     </dates>
   </vuln>
 
   <vuln vid="4323e86c-2422-4fd7-8c8f-ec71c81ea7dd">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>137.0.7151.68</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>137.0.7151.68</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2025/06/stable-channel-update-for-desktop.html">
 	 <p>This update includes 3 security fixes:</p>
 	 <ul>
 	    <li>[420636529] High CVE-2025-5419: Out of bounds read and write in V8. Reported by Clement Lecigne and Benoît Sevens of Google Threat Analysis Group on 2025-05-27. This issue was mitigated on 2025-05-28 by a configuration change pushed out to Stable across all Chrome platforms.</li>
 	    <li>[409059706] Medium CVE-2025-5068: Use after free in Blink. Reported by Walkman on 2025-04-07</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2025-5419</cvename>
       <cvename>CVE-2025-5068</cvename>
       <url>https://chromereleases.googleblog.com/2025/06/stable-channel-update-for-desktop.html</url>
     </references>
     <dates>
       <discovery>2025-06-02</discovery>
       <entry>2025-06-17</entry>
     </dates>
   </vuln>
 
   <vuln vid="201cccc1-4a01-11f0-b0f8-b42e991fc52e">
     <topic>Mozilla -- control access bypass</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>138.0,2</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>128.10</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>128.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1917536">
 	  <p>Thunderbird&apos;s update mechanism allowed a medium-integrity user
 	process to interfere with the SYSTEM-level updater by manipulating
 	the file-locking behavior.  By injecting code into the user-privileged
 	process, an attacker could bypass intended access controls, allowing
 	SYSTEM-level file operations on paths controlled by a non-privileged
 	user and enabling privilege escalation.  This vulnerability affects
 	Firefox &lt; 138, Firefox ESR &lt; 128.10, Firefox ESR &lt; 115.23,
 	Thunderbird &lt; 138, and Thunderbird &lt; 128.10.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-2817</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-2817</url>
     </references>
     <dates>
       <discovery>2025-04-29</discovery>
       <entry>2025-06-15</entry>
     </dates>
   </vuln>
 
   <vuln vid="805ad2e0-49da-11f0-87e8-bcaec55be5e5">
     <topic>webmin -- CGI Command Injection Remote Code Execution</topic>
     <affects>
       <package>
 	<name>webmin</name>
 	<range><le>2.105</le></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Webmin reports:</p>
 	<blockquote cite="https://webmin.com/security/">
 	  <p>A less-privileged Webmin user can execute commands as root via a vulnerability in the shell autocomplete feature.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-12828</cvename>
       <url>https://webmin.com/security/</url>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-12828</url>
     </references>
     <dates>
       <discovery>2024-12-30</discovery>
       <entry>2025-06-15</entry>
     </dates>
   </vuln>
 
   <vuln vid="9449f018-84a3-490d-959f-38c05fbc77a7">
     <topic>Yelp -- arbitrary file read</topic>
     <affects>
       <package>
 	<name>yelp-xsl</name>
 	<range><lt>42.3</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>secalert@redhat.com reports:</p>
 	<blockquote cite="https://access.redhat.com/errata/RHSA-2025:4450">
 	  <p>A flaw was found in Yelp.  The Gnome user help application allows
 	the help document to execute arbitrary scripts.  This vulnerability
 	allows malicious users to input help documents, which may exfiltrate
 	user files to an external environment.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-3155</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-3155</url>
     </references>
     <dates>
       <discovery>2025-04-03</discovery>
       <entry>2025-06-14</entry>
     </dates>
   </vuln>
 
   <vuln vid="0e200a73-289a-489e-b405-40b997911036">
     <topic>Yelp -- arbitrary file read</topic>
     <affects>
       <package>
 	<name>yelp</name>
 	<range><lt>42.3</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>secalert@redhat.com reports:</p>
 	<blockquote cite="https://access.redhat.com/errata/RHSA-2025:4450">
 	  <p>A flaw was found in Yelp.  The Gnome user help application allows
 	the help document to execute arbitrary scripts.  This vulnerability
 	allows malicious users to input help documents, which may exfiltrate
 	user files to an external environment.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-3155</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-3155</url>
     </references>
     <dates>
       <discovery>2025-04-03</discovery>
       <entry>2025-06-14</entry>
     </dates>
   </vuln>
 
   <vuln vid="ae028662-475e-11f0-9ca4-2cf05da270f3">
     <topic>Gitlab -- Vulnerabilities</topic>
     <affects>
       <package>
 	<name>gitlab-ce</name>
 	<name>gitlab-ee</name>
 	<range><ge>18.0.0</ge><lt>18.0.2</lt></range>
 	<range><ge>17.11.0</ge><lt>17.11.4</lt></range>
 	<range><ge>2.1.0</ge><lt>17.10.8</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Gitlab reports:</p>
 	<blockquote cite="https://about.gitlab.com/releases/2025/06/11/patch-release-gitlab-18-0-2-released/">
 	  <p>HTML injection impacts GitLab CE/EE</p>
 	  <p>Cross-site scripting issue impacts GitLab CE/EE</p>
 	  <p>Missing authorization issue impacts GitLab Ultimate EE</p>
 	  <p>Denial of Service impacts GitLab CE/EE</p>
 	  <p>Denial of Service via unbounded Webhook token names impacts GitLab CE/EE</p>
 	  <p>Denial of Service via unbounded Board Names impacts GitLab CE/EE</p>
 	  <p>Information disclosure issue impacts GitLab CE/EE</p>
 	  <p>Denial of Service (DoS) via uncontrolled HTTP Response Processing impacts GitLab CE/EE</p>
 	  <p>Information disclosure via authorization bypass impacts GitLab CE/EE</p>
 	  <p>Sensitive information disclosure via Group IP restriction bypass</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-4278</cvename>
       <cvename>CVE-2025-2254</cvename>
       <cvename>CVE-2025-5121</cvename>
       <cvename>CVE-2025-0673</cvename>
       <cvename>CVE-2025-1516</cvename>
       <cvename>CVE-2025-1478</cvename>
       <cvename>CVE-2024-9512</cvename>
       <cvename>CVE-2025-5996</cvename>
       <cvename>CVE-2025-5195</cvename>
       <cvename>CVE-2025-5982</cvename>
       <url>https://about.gitlab.com/releases/2025/06/11/patch-release-gitlab-18-0-2-released/</url>
     </references>
     <dates>
       <discovery>2025-06-11</discovery>
       <entry>2025-06-12</entry>
     </dates>
   </vuln>
 
   <vuln vid="2a220a73-4759-11f0-a44a-6cc21735f730">
     <topic>PostgreSQL JDBC library -- Improper Authentication</topic>
     <affects>
       <package>
 	<name>postgresql-jdbc</name>
 	<range><lt>42.7.7</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>PostgreSQL JDBC Driver project reports:</p>
 	<blockquote cite="https://jdbc.postgresql.org/changelogs/2025-06-11-42">
 	<p>
 	Client Allows Fallback to Insecure Authentication Despite
 	channelBinding=require configuration. Fix channel binding
 	required handling to reject non-SASL authentication Previously,
 	when channel binding was set to "require", the driver
 	would silently ignore this requirement for non-SASL
 	authentication methods. This could lead to a false sense of
 	security when channel binding was explicitly requested but not
 	actually enforced. The fix ensures that when channel binding is
 	set to "require", the driver will reject connections that use
 	non-SASL authentication methods or when SASL authentication has
 	not completed properly.
 	</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-49146</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-49146</url>
     </references>
     <dates>
       <discovery>2025-06-12</discovery>
       <entry>2025-06-12</entry>
     </dates>
   </vuln>
 
   <vuln vid="fa1d42c8-42fe-11f0-a9fa-b42e991fc52e">
     <topic>ModSecurity -- possible DoS vulnerability</topic>
     <affects>
       <package>
 	<name>ap24-mod_security</name>
 	<range><lt>2.9.10</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security-advisories@github.com reports:</p>
 	<blockquote cite="https://github.com/owasp-modsecurity/ModSecurity/commit/3a54ccea62d3f7151bb08cb78d60c5e90b53ca2e">
 	<p>
 		ModSecurity is an open source, cross platform web
 		application firewall (WAF) engine for Apache, IIS
 		and Nginx. Versions prior to 2.9.10 contain a denial of
 		service vulnerability similar to
 		GHSA-859r-vvv8-rm8r/CVE-2025-47947. The `sanitiseArg`
 		(and `sanitizeArg` - this is the same action but an
 		alias) is vulnerable to adding an excessive number
 		of arguments, thereby leading to denial of service.
 		Version 2.9.10 fixes the issue. As a workaround, avoid
 		using rules that contain the `sanitiseArg` (or
 		`sanitizeArg`) action.
 	</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-48866</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-48866</url>
     </references>
     <dates>
       <discovery>2025-06-02</discovery>
       <entry>2025-06-06</entry>
     </dates>
   </vuln>
 
   <vuln vid="ecea70d2-42fe-11f0-a9fa-b42e991fc52e">
     <topic>ModSecurity -- possible DoS vulnerability</topic>
     <affects>
       <package>
 	<name>ap24-mod_security</name>
 	<range><lt>2.9.8</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security-advisories@github.com reports:</p>
 	<blockquote cite="https://github.com/owasp-modsecurity/ModSecurity/pull/3389">
 	  <p>ModSecurity is an open source, cross platform web
 	  application firewall (WAF) engine for Apache, IIS and Nginx.
 	  Versions up to and including 2.9.8 are vulnerable to denial
 	  of service in one special case (in stable released versions):
 	  when the payload&apos;s content type is `application/json`,
 	  and there is at least one rule which does a
 	  `sanitiseMatchedBytes` action.  A patch is available at
 	  pull request 3389 and expected to be part of version 2.9.9.
 	  No known workarounds are available.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-47947</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-47947</url>
     </references>
     <dates>
       <discovery>2025-05-21</discovery>
       <entry>2025-06-06</entry>
     </dates>
   </vuln>
 
   <vuln vid="63268efe-4222-11f0-976e-b42e991fc52e">
     <topic>Mozilla -- clickjacking vulnerability</topic>
     <affects>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>128.11.0</lt></range>
       </package>
       <package>
 	<name>firefox</name>
 	<range><lt>139.0,2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1954137">
 	  <p>A clickjacking vulnerability could have been used to trick a user
 	into leaking saved payment card details to a malicious page.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-5267</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-5267</url>
     </references>
     <dates>
       <discovery>2025-05-27</discovery>
       <entry>2025-06-05</entry>
     </dates>
   </vuln>
 
   <vuln vid="61be5684-4222-11f0-976e-b42e991fc52e">
     <topic>Mozilla -- XS-leak attack</topic>
     <affects>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>128.11.0</lt></range>
       </package>
       <package>
 	<name>firefox</name>
 	<range><lt>139.0,2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1965628">
 	  <p>Script elements loading cross-origin resources generated load and
 	error events which leaked information enabling XS-Leaks attacks.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-5266</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-5266</url>
     </references>
     <dates>
       <discovery>2025-05-27</discovery>
       <entry>2025-06-05</entry>
     </dates>
   </vuln>
 
   <vuln vid="5ec0b4e5-4222-11f0-976e-b42e991fc52e">
     <topic>Mozilla -- local code execution</topic>
     <affects>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>115.24.0</lt></range>
       </package>
       <package>
 	<name>firefox</name>
 	<range><lt>139.0,2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1950001">
 	  <p>Due to insufficient escaping of the newline character in the Copy
 	as cURL feature, an attacker could trick a user into using this
 	command, potentially leading to local code execution on the user&apos;s
 	system.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-5264</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-5264</url>
     </references>
     <dates>
       <discovery>2025-05-27</discovery>
       <entry>2025-06-05</entry>
     </dates>
   </vuln>
 
   <vuln vid="5d1e56dc-4222-11f0-976e-b42e991fc52e">
     <topic>Mozilla -- cross-origin leak attack</topic>
     <affects>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>115.24.0</lt></range>
       </package>
       <package>
 	<name>firefox</name>
 	<range><lt>139.0,2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1960745">
 	  <p>Error handling for script execution was incorrectly isolated from
 	web content, which could have allowed cross-origin leak attacks.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-5263</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-5263</url>
     </references>
     <dates>
       <discovery>2025-05-27</discovery>
       <entry>2025-06-05</entry>
     </dates>
   </vuln>
 
   <vuln vid="5759c6e2-410a-11f0-a945-b42e991fc52e">
     <topic>Chrome -- Out of bounds read</topic>
     <affects>
       <package>
 	<name>chromium</name>
 	<range><lt>137.0.7151.68</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>chrome-cve-admin@google.com reports:</p>
 	<blockquote cite="https://chromereleases.googleblog.com/2025/06/stable-channel-update-for-desktop.html">
 	  <p>Out of bounds read and write in V8 in Google Chrome prior
 	  to 137.0.7151.68 allowed a remote attacker to potentially
 	  exploit heap corruption via a crafted HTML page.
 	  (Chromium security severity: High)</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-5419</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-5419</url>
     </references>
     <dates>
       <discovery>2025-06-03</discovery>
       <entry>2025-06-04</entry>
     </dates>
   </vuln>
 
   <vuln vid="8c94ae2a-06f5-4383-9a7f-1211cb0dd476">
     <topic>electron{34,35,36} -- Out of bounds read and write in V8</topic>
     <affects>
       <package>
 	<name>electron34</name>
 	<range><lt>34.5.8</lt></range>
       </package>
       <package>
 	<name>electron35</name>
 	<range><lt>35.5.1</lt></range>
       </package>
       <package>
 	<name>electron36</name>
 	<range><lt>36.4.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Electron developers report:</p>
 	<blockquote cite="https://github.com/electron/electron/releases/tag/v35.5.1">
 	  <p>This update fixes the following vulnerability:</p>
 	  <ul>
 	    <li>Security: backported fix for CVE-2025-5419.</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-5419</cvename>
       <url>https://github.com/advisories/GHSA-x828-wp24-7h9m</url>
     </references>
     <dates>
       <discovery>2025-06-04</discovery>
       <entry>2025-06-04</entry>
       <modified>2025-06-04</modified>
     </dates>
   </vuln>
 
   <vuln vid="0d6094a2-4095-11f0-8c92-00d861a0e66d">
     <topic>Post-Auth Remote Code Execution found in Roundcube Webmail</topic>
     <affects>
       <package>
 	<name>roundcube-php81</name>
 	<range><lt>1.6.11</lt></range>
       </package>
       <package>
 	<name>roundcube-php82</name>
 	<range><lt>1.6.11</lt></range>
       </package>
       <package>
 	<name>roundcube-php83</name>
 	<range><lt>1.6.11</lt></range>
       </package>
       <package>
 	<name>roundcube-php84</name>
 	<range><lt>1.6.11</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Roundcube Webmail reports:</p>
 	<blockquote cite="https://roundcube.net/news/2025/06/01/security-updates-1.6.11-and-1.5.10">
 	  <p>Fix Post-Auth RCE via PHP Object Deserialization reported by firs0v</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-49113</cvename>
       <url>https://roundcube.net/news/2025/06/01/security-updates-1.6.11-and-1.5.10</url>
     </references>
     <dates>
       <discovery>2025-06-01</discovery>
       <entry>2025-06-03</entry>
     </dates>
   </vuln>
 
   <vuln vid="dc99c67a-3fc9-11f0-a39d-b42e991fc52e">
     <topic>Gimp -- GIMP FLI File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability</topic>
     <affects>
       <package>
 	<name>gimp</name>
 	<range><lt>3.0.0,2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>zdi-disclosures@trendmicro.com reports:</p>
 	<blockquote cite="https://www.zerodayinitiative.com/advisories/ZDI-25-204/">
 	  <p>GIMP FLI File Parsing Out-Of-Bounds Write Remote Code Execution
 	Vulnerability.  This vulnerability allows remote attackers to execute
 	arbitrary code on affected installations of GIMP.  User interaction
 	is required to exploit this vulnerability in that the target must
 	visit a malicious page or open a malicious file.
 	The specific flaw exists within the parsing of FLI files.  The issue
 	results from the lack of proper validation of user-supplied data,
 	which can result in a write past the end of an allocated buffer.
 	An attacker can leverage this vulnerability to execute code in the
 	context of the current process.  Was ZDI-CAN-25100.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-2761</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-2761</url>
     </references>
     <dates>
       <discovery>2025-04-23</discovery>
       <entry>2025-06-02</entry>
     </dates>
   </vuln>
 
   <vuln vid="da0a4374-3fc9-11f0-a39d-b42e991fc52e">
     <topic>Gimp -- GIMP XWD File Parsing Integer Overflow Remote Code Execution Vulnerability</topic>
     <affects>
       <package>
 	<name>gimp</name>
 	<range><lt>3.0.0,2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>zdi-disclosures@trendmicro.com reports:</p>
 	<blockquote cite="https://www.zerodayinitiative.com/advisories/ZDI-25-203/">
 	  <p>GIMP XWD File Parsing Integer Overflow Remote Code Execution
 	Vulnerability.  This vulnerability allows remote attackers to execute
 	arbitrary code on affected installations of GIMP.  User interaction
 	is required to exploit this vulnerability in that the target must
 	visit a malicious page or open a malicious file.
 	The specific flaw exists within the parsing of XWD files.  The issue
 	results from the lack of proper validation of user-supplied data,
 	which can result in an integer overflow before allocating a buffer.
 	An attacker can leverage this vulnerability to execute code in the
 	context of the current process.  Was ZDI-CAN-25082.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-2760</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-2760</url>
     </references>
     <dates>
       <discovery>2025-04-23</discovery>
       <entry>2025-06-02</entry>
     </dates>
   </vuln>
 
   <vuln vid="533b4470-3f25-11f0-b440-f02f7432cf97">
     <topic>curl -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>curl</name>
 	<range><ge>8.5.0</ge><lt>8.14.0</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
 	<p>curl security team reports:</p>
 	<blockquote cite="https://curl.se/docs/security.html">
 	  <p>CVE-2025-5025: No QUIC certificate pinning with wolfSSL</p>
 	  <p>CVE-2025-4947: QUIC certificate check skip with wolfSSL</p>
 	</blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2025-5025</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-5025</url>
       <cvename>CVE-2025-4947</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-4947</url>
     </references>
     <dates>
       <discovery>2025-05-28</discovery>
       <entry>2025-06-01</entry>
     </dates>
   </vuln>
 
   <vuln vid="2926c487-3e53-11f0-95d4-00a098b42aeb">
     <topic>libxml2 -- Out-of-bounds memory access</topic>
     <affects>
       <package>
 	<name>py39-libxml2</name>
 	<name>py310-libxml2</name>
 	<name>py311-libxml2</name>
 	<name>py312-libxml2</name>
 	<range><lt>2.11.9_3</lt></range>
 	<range><ge>2.12.0</ge><lt>2.13.8</lt></range>
 	<range><ge>2.14.0</ge><lt>2.14.2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>cve@mitre.org reports:</p>
 	<blockquote cite="https://gitlab.gnome.org/GNOME/libxml2/-/issues/889">
 	  <p>In libxml2 before 2.13.8 and 2.14.x before 2.14.2, out-of-bounds
 	memory access can occur in the Python API (Python bindings) because
 	of an incorrect return value.  This occurs in xmlPythonFileRead and
 	xmlPythonFileReadRaw because of a difference between bytes and
 	characters.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-32414</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-32414</url>
     </references>
     <dates>
       <discovery>2025-04-08</discovery>
       <entry>2025-05-31</entry>
     </dates>
   </vuln>
 
   <vuln vid="fdd02be0-3e50-11f0-95d4-00a098b42aeb">
     <topic>libxml2 -- Stack-based Buffer Overflow</topic>
     <affects>
       <package>
 	<name>libxml2</name>
 	<range><lt>2.11.9_1</lt></range>
 	<range><ge>2.12.0</ge><lt>2.12.10</lt></range>
 	<range><ge>2.13.0</ge><lt>2.13.6</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>cve@mitre.org reports:</p>
 	<blockquote cite="https://gitlab.gnome.org/GNOME/libxml2/-/issues/847">
 	  <p>libxml2 before 2.12.10 and 2.13.x before 2.13.6 has a stack-based
 	buffer overflow in xmlSnprintfElements in valid.c.  To exploit this,
 	DTD validation must occur for an untrusted document or untrusted
 	DTD.  NOTE: this is similar to CVE-2017-9047.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-24928</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-24928</url>
     </references>
     <dates>
       <discovery>2025-02-18</discovery>
       <entry>2025-05-31</entry>
     </dates>
   </vuln>
 
   <vuln vid="bd2af307-3e50-11f0-95d4-00a098b42aeb">
     <topic>libxml2 -- Use After Free</topic>
     <affects>
       <package>
 	<name>libxml2</name>
 	<range><lt>2.11.9_1</lt></range>
 	<range><ge>2.12.0</ge><lt>2.12.10</lt></range>
 	<range><ge>2.13.0</ge><lt>2.13.6</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>cve@mitre.org reports:</p>
 	<blockquote cite="https://gitlab.gnome.org/GNOME/libxml2/-/issues/828">
 	  <p>libxml2 before 2.12.10 and 2.13.x before 2.13.6 has a use-after-free
 	in xmlSchemaIDCFillNodeTables and xmlSchemaBubbleIDCNodeTables in
 	xmlschemas.c.  To exploit this, a crafted XML document must be
 	validated against an XML schema with certain identity constraints,
 	or a crafted XML schema must be used.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-56171</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-56171</url>
     </references>
     <dates>
       <discovery>2025-02-18</discovery>
       <entry>2025-05-31</entry>
     </dates>
   </vuln>
 
   <vuln vid="25acd603-3dde-11f0-8cb5-a8a1599412c6">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>137.0.7151.55</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>137.0.7151.55</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2025/05/stable-channel-update-for-desktop_27.html">
 	 <p>This update includes 11 security fixes:</p>
 	 <ul>
 	    <li>[411573532] High CVE-2025-5063: Use after free in Compositing. Reported by Anonymous on 2025-04-18</li>
 	    <li>[417169470] High CVE-2025-5280: Out of bounds write in V8. Reported by [pwn2car] on 2025-05-12</li>
 	    <li>[40058068] Medium CVE-2025-5064: Inappropriate implementation in Background Fetch API. Reported by Maurice Dauer  on 2021-11-29</li>
 	    <li>[40059071] Medium CVE-2025-5065: Inappropriate implementation in FileSystemAccess API. Reported by NDevTK on 2022-03-11</li>
 	    <li>[356658477] Medium CVE-2025-5066: Inappropriate implementation in Messages. Reported by Mohit Raj (shadow2639)  on 2024-07-31</li>
 	    <li>[417215501] Medium CVE-2025-5281: Inappropriate implementation in BFCache. Reported by Jesper van den Ende (Pelican Party Studios) on 2025-05-12</li>
 	    <li>[419467315] Medium CVE-2025-5283: Use after free in libvpx. Reported by Mozilla on 2025-05-22</li>
 	    <li>[40075024] Low CVE-2025-5067: Inappropriate implementation in Tab Strip. Reported by Khalil Zhani on 2023-10-17</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2025-5063</cvename>
       <cvename>CVE-2025-5280</cvename>
       <cvename>CVE-2025-5064</cvename>
       <cvename>CVE-2025-5065</cvename>
       <cvename>CVE-2025-5066</cvename>
       <cvename>CVE-2025-5281</cvename>
       <cvename>CVE-2025-5283</cvename>
       <cvename>CVE-2025-5067</cvename>
       <url>https://chromereleases.googleblog.com/2025/05/stable-channel-update-for-desktop_27.html</url>
     </references>
     <dates>
       <discovery>2025-05-27</discovery>
       <entry>2025-05-31</entry>
     </dates>
   </vuln>
 
   <vuln vid="4864aec7-3d80-11f0-9a55-b42e991fc52e">
     <topic>Chrome -- Heap corruption exploitation</topic>
     <affects>
       <package>
 	<name>chromium</name>
 	<range><lt>137.0.7151.55</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>chrome-cve-admin@google.com reports:</p>
 	<blockquote cite="https://chromereleases.googleblog.com/2025/05/stable-channel-update-for-desktop_27.html">
 	  <p>Use after free in Compositing in Google Chrome prior to
 	  137.0.7151.55 allowed a remote attacker to potentially
 	  exploit heap corruption via a crafted HTML page.
 	  (Chromium security severity: High)</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-5063</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-5063</url>
     </references>
     <dates>
       <discovery>2025-05-27</discovery>
       <entry>2025-05-30</entry>
     </dates>
   </vuln>
 
   <vuln vid="a6e1b7ee-3d7c-11f0-9a55-b42e991fc52e">
     <topic>Mozilla -- memory corruption</topic>
     <affects>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>128.11.0</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>128.11.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1924108">
 	  <p>Memory safety bug present in Firefox ESR 128.10, and
 	  Thunderbird 128.10.
 	  This bug showed evidence of memory corruption and we presume
 	  that with enough effort this could have been exploited to run
 	  arbitrary code.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-5269</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-5269</url>
     </references>
     <dates>
       <discovery>2025-05-27</discovery>
       <entry>2025-05-30</entry>
     </dates>
   </vuln>
 
   <vuln vid="a5b553e5-3d7c-11f0-9a55-b42e991fc52e">
     <topic>Mozilla -- Memory safety bugs</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>139.0,2</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>128.11</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>128.11</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/buglist.cgi?bug_id=1950136%2C1958121%2C1960499%2C1962634">
 	  <p>Memory safety bugs present in Firefox 138, Thunderbird
 	  138, Firefox ESR 128.10, and Thunderbird 128.10.
 	  Some of these bugs showed evidence of memory corruption and
 	  we presume that with enough effort some of these could have
 	  been exploited to run arbitrary code.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-5268</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-5268</url>
     </references>
     <dates>
       <discovery>2025-05-27</discovery>
       <entry>2025-05-30</entry>
     </dates>
   </vuln>
 
   <vuln vid="a470ac63-3d7c-11f0-9a55-b42e991fc52e">
     <topic>Firefox -- unencrypted SNI</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>139.0,2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1910298">
 	  <p>In certain cases, SNI could have been sent unencrypted
 	  even when encrypted DNS was enabled.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-5270</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-5270</url>
     </references>
     <dates>
       <discovery>2025-05-27</discovery>
       <entry>2025-05-30</entry>
     </dates>
   </vuln>
 
   <vuln vid="a3291f81-3d7c-11f0-9a55-b42e991fc52e">
     <topic>Firefox -- content injection attack</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>139.0,2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1920348">
 	  <p>Previewing a response in Devtools ignored CSP headers,
 	  which could have allowed content injection attacks.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-5271</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-5271</url>
     </references>
     <dates>
       <discovery>2025-05-27</discovery>
       <entry>2025-05-30</entry>
     </dates>
   </vuln>
 
   <vuln vid="a14dbea7-3d7c-11f0-9a55-b42e991fc52e">
     <topic>Mozilla -- Memory safety bugs</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>139.0,2</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>129.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/buglist.cgi?bug_id=1726254%2C1742738%2C1960121">
 	  <p>Memory safety bugs present in Firefox 138 and Thunderbird
 	  138. Some of these bugs showed evidence of memory corruption
 	  and we presume that with enough effort some of these could
 	  have been exploited to run arbitrary code.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-5272</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-5272</url>
     </references>
     <dates>
       <discovery>2025-05-27</discovery>
       <entry>2025-05-30</entry>
     </dates>
   </vuln>
 
   <vuln vid="a372abb0-3d3c-11f0-86e7-b42e991fc52e">
     <topic>ModSecurity -- Possible DoS Vulnerability</topic>
     <affects>
       <package>
 	<name>ap24-mod_security</name>
 	<range><lt>2.9.8</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security-advisories@github.com reports:</p>
 	<blockquote cite="https://github.com/owasp-modsecurity/ModSecurity/pull/3389">
 	  <p>ModSecurity is an open source, cross platform web application
 	firewall (WAF) engine for Apache, IIS and Nginx.  Versions up to
 	and including 2.9.8 are vulnerable to denial of service in one
 	special case (in stable released versions): when the payload&apos;s
 	content type is `application/json`, and there is at least one rule
 	which does a `sanitiseMatchedBytes` action.  A patch is available
 	at pull request 3389 and expected to be part of version 2.9.9.  No
 	known workarounds are available.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-47947</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-47947</url>
     </references>
     <dates>
       <discovery>2025-05-21</discovery>
       <entry>2025-05-30</entry>
     </dates>
   </vuln>
 
   <vuln vid="67dd7a9e-3cd8-11f0-b601-5404a68ad561">
     <topic>traefik -- Path traversal vulnerability</topic>
     <affects>
       <package>
 	<name>traefik</name>
 	<range><lt>3.4.1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The traefik project reports:</p>
 	<blockquote cite="https://github.com/traefik/traefik/security/advisories/GHSA-vrch-868g-9jx5">
 	  <p>There is a potential vulnerability in Traefik managing the requests
 	  using a PathPrefix, Path or PathRegex matcher. When Traefik is configured
 	  to route the requests to a backend using a matcher based on the path, if
 	  the URL contains a URL encoded string in its path, it's possible to target
 	  a backend, exposed using another router, by-passing the middlewares chain.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-47952</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-47952</url>
     </references>
     <dates>
       <discovery>2025-05-27</discovery>
       <entry>2025-05-29</entry>
     </dates>
   </vuln>
 
   <vuln vid="c36decbe-3c84-11f0-8d29-b42e991fc52e">
     <topic>glpi-project -- GLPI multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>glpi</name>
 	<range><lt>10.0.18</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security-advisories@github.com reports:</p>
 	<blockquote cite="https://github.com/glpi-project/glpi/releases/tag/10.0.18">
 	<p>
 	  CVE-2024-11955: A vulnerability was found in GLPI up to
 	  10.0.17. It has been declared as problematic. Affected by
 	  this vulnerability is an unknown functionality of the file
 	  /index.php.
 	  The manipulation of the argument redirect leads to
 	  open redirect. The attack can be launched remotely.
 	  The exploit has been disclosed to the public and
 	  may be used. Upgrading to version 10.0.18 is able to
 	  address this issue.
 	  It is recommended to upgrade the affected component.
 	</p>
 	<p>
 	  CVE-2025-23024: Starting in version 0.72 and prior to
 	  version 10.0.18, an anonymous user can disable all the
 	  active plugins. Version 10.0.18 contains a patch.
 	  As a workaround, one may delete the `install/update.php`
 	  file.
 	</p>
 	<p>
 	  CVE-2025-23046: Prior to version 10.0.18, a low privileged
 	  user can enable debug mode and access sensitive information.
 	  Version 10.0.18 contains a patch.
 	  As a workaround, one may delete the `install/update.php`
 	  file.
 	</p>
 	<p>
 	  CVE-2025-25192: Starting in version 9.5.0 and prior to
 	  version 10.0.18, if a &quot;Mail servers&quot;
 	  authentication provider is configured to use an Oauth
 	  connection provided by the OauthIMAP plugin, anyone can
 	  connect to GLPI using a user name on which an Oauth
 	  authorization has already been established.
 	  Version 10.0.18 contains a patch. As a
 	  workaround, one may disable any &quot;Mail
 	  servers&quot; authentication provider configured to
 	  use an Oauth connection provided by the OauthIMAP
 	  plugin.
 	</p>
 	<p>
 	  CVE-2025-21626: Starting in version 0.71 and prior to
 	  version 10.0.18, an anonymous user can fetch sensitive
 	  information from the `status.php` endpoint.
 	  Version 10.0.18 contains a fix for the issue.
 	  Some workarounds are available. One may delete the
 	  `status.php` file, restrict its access, or
 	  remove any sensitive values from the `name` field of
 	  the active LDAP directories, mail servers authentication
 	  providers and mail receivers.
 	</p>
 	<p>
 	  CVE-2025-21627: In versions prior to 10.0.18, a malicious
 	  link can be crafted to perform a reflected XSS attack on the
 	  search page. If the anonymous ticket creation is enabled,
 	  this attack can be performed by an unauthenticated
 	  user. Version 10.0.18 contains a fix for the issue.
 	</p>
 	<p>
 	  CVE-2025-21619: An administrator user can perfom a SQL
 	  injection through the rules configuration forms.
 	  This vulnerability is fixed in 10.0.18.
 	</p>
 	<p>
 	  CVE-2025-24799: An unauthenticated user can perform a SQL
 	  injection through the inventory endpoint.
 	  This vulnerability is fixed in 10.0.18.
 	</p>
 	<p>
 	  CVE-2025-24801: An authenticated user can upload and force
 	  the execution of *.php files located on the GLPI server.
 	  This vulnerability is fixed in 10.0.18.
 	</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-11955</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-11955</url>
       <cvename>CVE-2025-23024</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-23024</url>
       <cvename>CVE-2025-23046</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-23046</url>
       <cvename>CVE-2025-25192</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-25192</url>
       <cvename>CVE-2025-21626</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-21626</url>
       <cvename>CVE-2025-21627</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-21627</url>
       <cvename>CVE-2025-21619</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-21619</url>
       <cvename>CVE-2025-24799</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-24799</url>
       <cvename>CVE-2025-24801</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-24801</url>
     </references>
     <dates>
       <discovery>2025-02-25</discovery>
       <entry>2025-05-29</entry>
     </dates>
   </vuln>
 
   <vuln vid="47ef0ac6-38fc-4b35-850b-c794f04619fe">
     <topic>electron{34,35} -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>electron34</name>
 	<range><lt>34.5.7</lt></range>
       </package>
       <package>
 	<name>electron35</name>
 	<range><lt>35.5.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Electron developers report:</p>
 	<blockquote cite="https://github.com/electron/electron/releases/tag/v34.5.7">
 	  <p>This update fixes the following vulnerability:</p>
 	  <ul>
 	    <li>Security: backported fix for CVE-2025-4609.</li>
 	    <li>Security: backported fix for CVE-2025-4664.</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-4609</cvename>
       <cvename>CVE-2025-4664</cvename>
       <url>https://github.com/advisories/GHSA-vxhm-55mv-5fhx</url>
     </references>
     <dates>
       <discovery>2025-05-29</discovery>
       <entry>2025-05-29</entry>
     </dates>
   </vuln>
 
   <vuln vid="34744aab-3bf7-11f0-b81c-001b217e4ee5">
     <topic>ISC KEA -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>kea</name>
 	<range><lt>2.6.3</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Internet Systems Consortium, Inc. reports:</p>
 	<blockquote cite="https://kb.isc.org/docs/">
 	<ul>
 	    <li>Loading a malicious hook library can lead to local privilege escalation https://kb.isc.org/docs/cve-2025-32801</li>
 	    <li>Insecure handling of file paths allows multiple local attacks https://kb.isc.org/docs/cve-2025-32802</li>
 	    <li>Insecure file permissions can result in confidential information leakage https://kb.isc.org/docs/cve-2025-32803</li>
 	</ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-32801</cvename>
       <cvename>CVE-2025-32802</cvename>
       <cvename>CVE-2025-32803</cvename>
     </references>
     <dates>
       <discovery>2025-05-28</discovery>
       <entry>2025-05-28</entry>
     </dates>
   </vuln>
 
   <vuln vid="45eb98d6-3b13-11f0-97f7-b42e991fc52e">
     <topic>grafana -- XSS vulnerability</topic>
     <affects>
       <package>
 	<name>grafana</name>
 	<range><ge>8.0.0</ge><lt>10.4.18+security-01</lt></range>
 	<range><ge>11.0.0</ge><lt>11.2.9+security-01</lt></range>
 	<range><ge>11.3.0</ge><lt>11.3.6+security-01</lt></range>
 	<range><ge>11.4.0</ge><lt>11.4.4+security-01</lt></range>
 	<range><ge>11.5.0</ge><lt>11.5.4+security-01</lt></range>
 	<range><ge>11.6.0</ge><lt>11.6.1+security-01</lt></range>
 	<range><ge>12.0.0</ge><lt>12.0.0+security-01</lt></range>
       </package>
       <package>
 	<name>grafana8</name>
 	<range><ge>8.0.0</ge></range>
       </package>
       <package>
 	<name>grafana9</name>
 	<range><ge>9.0.0</ge></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@grafana.com reports:</p>
 	<blockquote cite="https://grafana.com/security/security-advisories/cve-2025-4123/">
 	  <p>A cross-site scripting (XSS) vulnerability exists in Grafana caused
 	by combining a client path traversal and open redirect.  This allows
 	attackers to redirect users to a website that hosts a frontend
 	plugin that will execute arbitrary JavaScript.  This vulnerability
 	does not require editor permissions and if anonymous access is
 	enabled, the XSS will work.  If the Grafana Image Renderer plugin
 	is installed, it is possible to exploit the open redirect to achieve
 	a full read SSRF.
 
 	The default Content-Security-Policy (CSP) in Grafana will block the
 	XSS though the `connect-src` directive.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-4123</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-4123</url>
     </references>
     <dates>
       <discovery>2025-04-26</discovery>
       <entry>2025-05-27</entry>
     </dates>
   </vuln>
 
   <vuln vid="e587b52d-38ac-11f0-b7b6-dcfe074bd614">
     <topic>cpython -- Use-after-free in &quot;unicode_escape&quot; decoder with error handler</topic>
     <affects>
       <package>
 	<name>python39</name>
 	<range><lt>3.9.22_1</lt></range>
       </package>
       <package>
 	<name>python310</name>
 	<range><lt>3.10.17_1</lt></range>
       </package>
       <package>
 	<name>python311</name>
 	<range><lt>3.11.12_1</lt></range>
       </package>
       <package>
 	<name>python312</name>
 	<range><lt>3.12.10_1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>cna@python.org reports:</p>
 	<blockquote cite="https://github.com/python/cpython/commit/69b4387f78f413e8c47572a85b3478c47eba8142">
 	  <p>There is an issue in CPython when using
 	`bytes.decode(&quot;unicode_escape&quot;,
 	error=&quot;ignore|replace&quot;)`.  If you are not using the
 	&quot;unicode_escape&quot; encoding or an error handler your
 	usage is not affected.  To work-around this issue you may stop
 	using the error= handler and instead wrap the bytes.decode()
 	call in a try-except catching the DecodeError.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-4516</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-4516</url>
     </references>
     <dates>
       <discovery>2025-05-15</discovery>
       <entry>2025-05-24</entry>
     </dates>
   </vuln>
 
   <vuln vid="5baa64d6-37ee-11f0-a116-8447094a420f">
     <topic>OpenSSL -- Inverted security logic in x509 app</topic>
     <affects>
       <package>
 	<name>openssl35</name>
 	<range><lt>3.5.0_1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The OpenSSL project reports:</p>
 	<blockquote cite="https://openssl-library.org/news/secadv/20250522.txt">
 	  <p>The x509 application adds trusted use instead of rejected use (low)</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-4575</cvename>
       <url>https://openssl-library.org/news/secadv/20250522.txt</url>
     </references>
     <dates>
       <discovery>2025-05-23</discovery>
       <entry>2025-05-23</entry>
     </dates>
   </vuln>
 
   <vuln vid="6529e5e7-36d5-11f0-8f57-b42e991fc52e">
     <topic>Firefox -- memory corruption due to race condition</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>137.0.2,2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1951554">
 	  <p>A race condition existed in nsHttpTransaction that could
 	  have been exploited to cause memory corruption, potentially
 	  leading to an exploitable condition.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-3608</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-3608</url>
     </references>
     <dates>
       <discovery>2025-04-15</discovery>
       <entry>2025-05-22</entry>
     </dates>
   </vuln>
 
   <vuln vid="a1a1b0c2-3791-11f0-8600-2cf05da270f3">
     <topic>Gitlab -- vulnerabilities</topic>
     <affects>
       <package>
 	<name>gitlab-ce</name>
 	<name>gitlab-ee</name>
 	<range><ge>18.0.0</ge><lt>18.0.1</lt></range>
 	<range><ge>17.11.0</ge><lt>17.11.3</lt></range>
 	<range><ge>10.2.0</ge><lt>17.10.7</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Gitlab reports:</p>
 	<blockquote cite="https://about.gitlab.com/releases/2025/05/21/patch-release-gitlab-18-0-1-released/">
 	  <p>Unprotected large blob endpoint in GitLab allows Denial of Service</p>
 	  <p>Improper XPath validation allows modified SAML response to bypass 2FA requirement</p>
 	  <p>A Discord webhook integration may cause DoS</p>
 	  <p>Unbounded Kubernetes cluster tokens may lead to DoS</p>
 	  <p>Unvalidated notes position may lead to Denial of Service</p>
 	  <p>Hidden/masked variables may get exposed in the UI</p>
 	  <p>Two-factor authentication requirement bypass</p>
 	  <p>View full email addresses that should be partially obscured</p>
 	  <p>Branch name confusion in confidential MRs</p>
 	  <p>Unauthorized access to job data via a GraphQL query</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-0993</cvename>
       <cvename>CVE-2024-12093</cvename>
       <cvename>CVE-2024-7803</cvename>
       <cvename>CVE-2025-3111</cvename>
       <cvename>CVE-2025-2853</cvename>
       <cvename>CVE-2025-4979</cvename>
       <cvename>CVE-2025-0605</cvename>
       <cvename>CVE-2025-0679</cvename>
       <cvename>CVE-2024-9163</cvename>
       <cvename>CVE-2025-1110</cvename>
       <url>https://about.gitlab.com/releases/2025/05/21/patch-release-gitlab-18-0-1-released/</url>
     </references>
     <dates>
       <discovery>2025-05-21</discovery>
       <entry>2025-05-23</entry>
     </dates>
   </vuln>
 
   <vuln vid="4abd86c1-366d-11f0-9c0c-000c29ffbb6c">
     <topic>screen -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>screen</name>
 	<range><lt>5.0.1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The screen project reports:</p>
 	<blockquote cite="https://lists.gnu.org/archive/html/info-gnu/2025-05/msg00002.html">
 	  <p>Multiple security issues in screen.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-46805</cvename>
       <cvename>CVE-2025-46804</cvename>
       <cvename>CVE-2025-46803</cvename>
       <cvename>CVE-2025-46802</cvename>
       <cvename>CVE-2025-23395</cvename>
       <url>https://lists.gnu.org/archive/html/info-gnu/2025-05/msg00002.html</url>
     </references>
     <dates>
       <discovery>2025-05-12</discovery>
       <entry>2025-05-21</entry>
     </dates>
   </vuln>
 
   <vuln vid="07560111-34cc-11f0-af94-b42e991fc52e">
     <topic>firefox -- out-of-bounds read/write</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>138.0.4,2</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>128.10.1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1966614">
 	  <p>An attacker was able to perform an out-of-bounds read or
 	  write on a JavaScript object by confusing array index sizes.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-4918</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-4918</url>
       <cvename>CVE-2025-4919</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-4919</url>
     </references>
     <dates>
       <discovery>2025-05-17</discovery>
       <entry>2025-05-19</entry>
     </dates>
   </vuln>
 
   <vuln vid="46594aa3-32f7-11f0-a116-8447094a420f">
     <topic>WeeChat -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>weechat</name>
 	<range><lt>4.6.3</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The Weechat project reports:</p>
 	<blockquote cite="https://weechat.org/doc/weechat/security/">
 	  <p>Multiple integer and buffer overflows in WeeChat core.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <url>https://weechat.org/doc/weechat/security/</url>
     </references>
     <dates>
       <discovery>2025-05-11</discovery>
       <entry>2025-05-17</entry>
     </dates>
   </vuln>
 
   <vuln vid="79400d31-3166-11f0-8cb5-a8a1599412c6">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>136.0.7103.113</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>136.0.7103.113</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2025/05/stable-channel-update-for-desktop_14.html">
 	 <p>This update includes 4 security fixes:</p>
 	 <ul>
 	    <li>[415810136] High CVE-2025-4664: Insufficient policy enforcement in Loader. Source: X post from @slonser_ on 2025-05-05</li>
 	    <li>[412578726] High CVE-2025-4609: Incorrect handle provided in unspecified circumstances in Mojo. Reported by Micky on 2025-04-22</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2025-4664</cvename>
       <cvename>CVE-2025-4609</cvename>
       <url>https://chromereleases.googleblog.com/2025/05/stable-channel-update-for-desktop_14.html</url>
     </references>
     <dates>
       <discovery>2025-05-14</discovery>
       <entry>2025-05-15</entry>
     </dates>
   </vuln>
 
   <vuln vid="52efdd56-30bd-11f0-81be-b42e991fc52e">
     <topic>Mozilla -- memory safety bugs</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>138.0,2</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>128.10</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>138.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/buglist.cgi?bug_id=1951161%2C1952105">
 	  <p>Memory safety bugs present in Firefox 137, Thunderbird 137,
 	  Firefox ESR 128.9, and Thunderbird 128.9. Some of these bugs
 	  showed evidence of memory corruption and we presume that
 	  with enough effort some of these could have been exploited
 	  to run arbitrary code.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-4091</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-4091</url>
     </references>
     <dates>
       <discovery>2025-04-29</discovery>
       <entry>2025-05-14</entry>
     </dates>
   </vuln>
 
   <vuln vid="4f17db64-30bd-11f0-81be-b42e991fc52e">
     <topic>Mozilla -- memory corruption</topic>
     <affects>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>128.10</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>128.10</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1894100">
 	  <p>Memory safety bug present in Firefox ESR 128.9, and
 	  Thunderbird 128.9. This bug showed evidence of memory
 	  corruption and we presume that with enough effort this could
 	  have been exploited to run arbitrary code.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-4093</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-4093</url>
     </references>
     <dates>
       <discovery>2025-04-29</discovery>
       <entry>2025-05-14</entry>
     </dates>
   </vuln>
 
   <vuln vid="6f10b49d-07b1-4be4-8abf-edf880b16ad2">
     <topic>vscode -- security feature bypass vulnerability</topic>
     <affects>
       <package>
 	<name>vscode</name>
 	<range><lt>1.100.1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>VSCode developers report:</p>
 	<blockquote cite="https://github.com/microsoft/vscode/security/advisories/GHSA-742r-ggwg-vqxm">
 	  <p>A security feature bypass vulnerability exists in VS Code 1.100.0 and earlier versions where a maliciously crafted URL could be considered trusted when it should not have due to how VS Code handled glob patterns in the trusted domains feature. When paired with the #fetch tool in Chat, this scenario would require the attacker to convince an LLM (via prompt injection) to fetch the maliciously crafted URL but when fetched, the user would have no moment to confirm the flighting of the request.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-21264</cvename>
       <url>https://github.com/microsoft/vscode/security/advisories/GHSA-742r-ggwg-vqxm</url>
       <url>https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-21264</url>
     </references>
     <dates>
       <discovery>2025-05-13</discovery>
       <entry>2025-05-14</entry>
     </dates>
   </vuln>
 
   <vuln vid="a96cd659-303e-11f0-94b5-54ee755069b5">
     <topic>libxslt -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>libxslt</name>
 	<range><lt>1.1.43</lt></range>
       </package>
     </affects>
     <description>
     <body xmlns="http://www.w3.org/1999/xhtml">
     <h1>[CVE-2024-55549] Fix UAF related to excluded namespaces</h1>
     <blockquote cite="https://gitlab.gnome.org/GNOME/libxslt/-/issues/127">
     <p>xsltGetInheritedNsList in libxslt before 1.1.43 has a use-after-free issue related to exclusion of result prefixes.</p>
     </blockquote>
     <h1>[CVE-2025-24855] Fix use-after-free of XPath context node</h1>
     <blockquote cite="https://gitlab.gnome.org/GNOME/libxslt/-/issues/128">
       <p>numbers.c in libxslt before 1.1.43 has a use-after-free because
 	, in nested XPath evaluations, an XPath context node can be
 	modified but never restored. This is related to
 	xsltNumberFormatGetValue, xsltEvalXPathPredicate,
 	xsltEvalXPathStringNs, and xsltComputeSortResultInternal.</p>
     </blockquote>
     </body>
     </description>
     <references>
       <cvename>CVE-2024-55549</cvename>
       <cvename>CVE-2025-24855</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-55549</url>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-24855</url>
     </references>
     <dates>
       <discovery>2025-03-13</discovery>
       <entry>2025-05-13</entry>
     </dates>
   </vuln>
 
   <vuln vid="89c668d5-2f80-11f0-9632-641c67a117d8">
     <topic>www/varnish7 -- Request Smuggling Attack</topic>
     <affects>
       <package>
 	<name>varnish7</name>
 	<range><lt>7.7.1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The Varnish Development Team reports:</p>
 	<blockquote cite="https://varnish-cache.org/security/VSV00016.html">
 	<p>A client-side desync vulnerability can be triggered in Varnish Cache
 	   and Varnish Enterprise. This vulnerability can be triggered under
 	   specific circumstances involving malformed HTTP/1 requests.</p>
 	<p>An attacker can abuse a flaw in Varnish's handling of chunked
 	   transfer encoding which allows certain malformed HTTP/1 requests
 	   to exploit improper framing of the message body to smuggle additional
 	   requests. Specifically, Varnish incorrectly permits CRLF to be
 	   skipped to delimit chunk boundaries.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <url>https://varnish-cache.org/security/VSV00016.html</url>
     </references>
     <dates>
       <discovery>2025-05-12</discovery>
       <entry>2025-05-12</entry>
     </dates>
   </vuln>
 
   <vuln vid="a8a1a8e7-2e85-11f0-a989-b42e991fc52e">
     <topic>Mozilla -- memory corruption</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>138.0,2</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>138.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/buglist.cgi?bug_id=1924108%2C1950780%2C1959367">
 	  <p>Memory safety bugs present in Firefox 137 and Thunderbird 137.
 	  Some of these bugs showed evidence of memory corruption and
 	  we presume that with enough effort some of these could have
 	  been exploited to run arbitrary code.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-4092</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-4092</url>
     </references>
     <dates>
       <discovery>2025-04-29</discovery>
       <entry>2025-05-11</entry>
     </dates>
   </vuln>
 
   <vuln vid="a59bd59e-2e85-11f0-a989-b42e991fc52e">
     <topic>Mozilla -- insufficient character escaping</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>138.0,2</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>138.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/buglist.cgi?bug_id=1949994%2C1956698%2C1960198">
 	  <p>Due to insufficient escaping of special characters in the
 	    &quot;copy as cURL&quot; feature, an attacker could trick
 	  a user into using this command, potentially leading to local
 	  code execution on the user&apos;s system.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-4089</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-4089</url>
     </references>
     <dates>
       <discovery>2025-04-29</discovery>
       <entry>2025-05-11</entry>
     </dates>
   </vuln>
 
   <vuln vid="a4422500-2e85-11f0-a989-b42e991fc52e">
     <topic>Mozilla -- Cross-Site Request Forgery</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>138.0,2</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>138.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1953521">
 	  <p>A security vulnerability in Thunderbird allowed malicious
 	  sites to use redirects to send credentialed requests to
 	  arbitrary endpoints on any site that had invoked the Storage
 	  Access API.  This enabled potential Cross-Site Request
 	  Forgery attacks across origins.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-4088</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-4088</url>
     </references>
     <dates>
       <discovery>2025-04-29</discovery>
       <entry>2025-05-11</entry>
     </dates>
   </vuln>
 
   <vuln vid="a2d5bd7b-2e85-11f0-a989-b42e991fc52e">
     <topic>Mozilla -- XPath parsing undefined behavior</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>138.0,2</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>128.10,1</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>138</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1952465">
 	  <p>A vulnerability was identified in Thunderbird where XPath
 	  parsing could trigger undefined behavior due to missing null
 	  checks during attribute access. This could lead to
 	  out-of-bounds read access and potentially, memory
 	  corruption.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-4087</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-4087</url>
     </references>
     <dates>
       <discovery>2025-04-29</discovery>
       <entry>2025-05-11</entry>
     </dates>
   </vuln>
 
   <vuln vid="9fa8c4a2-2e85-11f0-a989-b42e991fc52e">
     <topic>Mozilla -- Information leak</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>138.0,2</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>138.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1915280">
 	  <p>An attacker with control over a content process could
 	  potentially leverage the privileged UITour actor to leak
 	  sensitive information or escalate privileges.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-4085</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-4085</url>
     </references>
     <dates>
       <discovery>2025-04-29</discovery>
       <entry>2025-05-11</entry>
     </dates>
   </vuln>
 
   <vuln vid="9c37a02e-2e85-11f0-a989-b42e991fc52e">
     <topic>Mozilla -- javascript content execution</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>138.0,2</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>128.10,1</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>138.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1958350">
 	  <p>A process isolation vulnerability in Thunderbird stemmed
 	  from improper handling of javascript: URIs, which could
 	  allow content to execute in the top-level document&apos;s
 	  process instead of the intended frame, potentially enabling
 	  a sandbox escape.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-4083</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-4083</url>
     </references>
     <dates>
       <discovery>2025-04-29</discovery>
       <entry>2025-05-11</entry>
     </dates>
   </vuln>
 
   <vuln vid="6943cbf2-2d55-11f0-9471-2cf05da270f3">
     <topic>Gitlab -- vulnerabilities</topic>
     <affects>
       <package>
 	<name>gitlab-ce</name>
 	<name>gitlab-ee</name>
 	<range><ge>17.11.0</ge><lt>17.11.2</lt></range>
 	<range><ge>17.10.0</ge><lt>17.10.6</lt></range>
 	<range><ge>12.0.0</ge><lt>17.9.8</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Gitlab reports:</p>
 	<blockquote cite="https://about.gitlab.com/releases/2025/05/07/patch-release-gitlab-17-11-2-released/">
 	  <p>Partial Bypass for Device OAuth flow using Cross Window Forgery</p>
 	  <p>Denial of service by abusing Github import API</p>
 	  <p>Group IP restriction bypass allows disclosing issue title of restricted project</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-0549</cvename>
       <cvename>CVE-2024-8973</cvename>
       <cvename>CVE-2025-1278</cvename>
       <url>https://about.gitlab.com/releases/2025/05/07/patch-release-gitlab-17-11-2-released/</url>
     </references>
     <dates>
       <discovery>2025-05-07</discovery>
       <entry>2025-05-10</entry>
     </dates>
   </vuln>
 
   <vuln vid="78b8e808-2c45-11f0-9a65-6cc21735f730">
     <topic>PostgreSQL -- PostgreSQL GB18030 encoding validation can read one byte past end of allocation for text that fails validation</topic>
     <affects>
       <package>
 	<name>postgresql17-client</name>
 	<range><lt>17.5</lt></range>
       </package>
       <package>
 	<name>postgresql16-client</name>
 	<range><lt>16.9</lt></range>
       </package>
       <package>
 	<name>postgresql15-client</name>
 	<range><lt>15.13</lt></range>
       </package>
       <package>
 	<name>postgresql14-client</name>
 	<range><lt>14.18</lt></range>
       </package>
       <package>
 	<name>postgresql13-client</name>
 	<range><lt>13.21</lt></range>
       </package>
       <package>
 	<name>postgresql17-server</name>
 	<range><lt>17.5</lt></range>
       </package>
       <package>
 	<name>postgresql16-server</name>
 	<range><lt>16.9</lt></range>
       </package>
       <package>
 	<name>postgresql15-server</name>
 	<range><lt>15.13</lt></range>
       </package>
       <package>
 	<name>postgresql14-server</name>
 	<range><lt>14.18</lt></range>
       </package>
       <package>
 	<name>postgresql13-server</name>
 	<range><lt>13.21</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>PostgreSQL project reports:</p>
 	<blockquote cite="https://www.postgresql.org/support/security/CVE-2025-4207/">
 	  <p>
 	    A buffer over-read in PostgreSQL GB18030 encoding
 	    validation allows a database input provider to achieve
 	    temporary denial of service on platforms where a 1-byte
 	    over-read can elicit process termination. This affects
 	    the database server and also libpq. Versions before
 	    PostgreSQL 17.5, 16.9, 15.13, 14.18, and 13.21 are
 	    affected.
 	  </p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-4207</cvename>
       <url>https://www.postgresql.org/support/security/CVE-2025-4207/</url>
     </references>
     <dates>
       <discovery>2025-05-08</discovery>
       <entry>2025-05-08</entry>
     </dates>
   </vuln>
 
   <vuln vid="db221414-2b0d-11f0-8cb5-a8a1599412c6">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>136.0.7103.92</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>136.0.7103.92</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2025/05/stable-channel-update-for-desktop.html">
 	 <p>This update includes 2 security fixes:</p>
 	 <ul>
 	    <li>[412057896] Medium CVE-2025-4372: Use after free in WebAudio. Reported by Huang Xilin of Ant Group Light-Year Security Lab on 2025-04-20</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2025-4372</cvename>
       <url>https://chromereleases.googleblog.com/2025/05/stable-channel-update-for-desktop.html</url>
     </references>
     <dates>
       <discovery>2025-05-06</discovery>
       <entry>2025-05-07</entry>
     </dates>
   </vuln>
 
   <vuln vid="e195e915-2a43-11f0-8cb5-a8a1599412c6">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>136.0.7103.59</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>136.0.7103.59</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2025/04/stable-channel-update-for-desktop_29.html">
 	 <p>This update includes 8 security fixes:</p>
 	 <ul>
 	    <li>[409911705] High CVE-2025-4096: Heap buffer overflow in HTML. Reported by Anonymous on 2025-04-11</li>
 	    <li>[409342999] Medium CVE-2025-4050: Out of bounds memory access in DevTools. Reported by Anonymous on 2025-04-09</li>
 	    <li>[404000989] Medium CVE-2025-4051: Insufficient data validation in DevTools. Reported by Daniel Fröjdendahl on 2025-03-16</li>
 	    <li>[401927528] Low CVE-2025-4052: Inappropriate implementation in DevTools. Reported by vanillawebdev on 2025-03-10</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2025-4096</cvename>
       <cvename>CVE-2025-4050</cvename>
       <cvename>CVE-2025-4051</cvename>
       <cvename>CVE-2025-4052</cvename>
       <url>https://chromereleases.googleblog.com/2025/04/stable-channel-update-for-desktop_29.html</url>
     </references>
     <dates>
       <discovery>2025-04-29</discovery>
       <entry>2025-05-06</entry>
     </dates>
   </vuln>
 
   <vuln vid="5f868a5f-2943-11f0-bb22-f02f7432cf97">
     <topic>fcgi -- Heap-based buffer overflow via crafted nameLen/valueLen in ReadParams</topic>
     <affects>
       <package>
 	<name>fcgi</name>
 	<range><lt>2.4.5</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>cve@mitre.org reports:</p>
 	<blockquote cite="https://github.com/FastCGI-Archives/fcgi2/issues/67">
 	<p>FastCGI fcgi2 (aka fcgi) 2.x through 2.4.4 has an integer
 	overflow (and resultant heap-based buffer overflow) via
 	crafted nameLen or valueLen values in data to the IPC socket.
 	This occurs in ReadParams in fcgiapp.c.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-23016</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-23016</url>
       <url>https://github.com/FastCGI-Archives/fcgi2/issues/67</url>
     </references>
     <dates>
       <discovery>2025-01-10</discovery>
       <entry>2025-05-04</entry>
     </dates>
   </vuln>
 
   <vuln vid="7e7a32e7-2901-11f0-ab20-b42e991fc52e">
     <topic>dnsdist -- Denial of service via crafted DoH exchange</topic>
     <affects>
       <package>
 	<name>null</name>
 	<range><lt>null</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@open-xchange.com reports:</p>
 	<blockquote cite="https://dnsdist.org/security-advisories/powerdns-advisory-for-dnsdist-2025-02.html">
 	<p>
 	When DNSdist is configured to provide DoH via the
 	nghttp2provider, an attacker can cause a denial of service by
 	crafting a DoH exchange that triggers an illegal memory
 	access (double-free) and crash of DNSdist, causing a denial
 	of service. The remedy is: upgrade to the patched 1.9.9
 	version. A workaround is to temporarily switch to the h2o
 	provider until DNSdist has been upgraded to a fixed version.
 	We would like to thank Charles Howes for bringing this issue
 	to our attention.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-30194</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-30194</url>
     </references>
     <dates>
       <discovery>2025-04-29</discovery>
       <entry>2025-05-04</entry>
     </dates>
   </vuln>
 
   <vuln vid="d70d5e0a-1f5e-11f0-9c67-6805ca2fa271">
     <topic>powerdns-recursor -- denial of service</topic>
     <affects>
       <package>
 	<name>powerdns-recursor</name>
 	<range><eq>5.2.0</eq></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>PowerDNS Team reports:</p>
 	<blockquote cite="https://blog.powerdns.com/2025/04/07/powerdns-recursor-5-2-1-released">
 	  <p>PowerDNS Security Advisory 2025-01: A crafted zone can
 	  lead to an illegal memory access in the Recursor</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-30195</cvename>
       <url>https://docs.powerdns.com/recursor/security-advisories/powerdns-advisory-2025-01.html</url>
     </references>
     <dates>
       <discovery>2025-04-07</discovery>
       <entry>2025-04-22</entry>
     </dates>
   </vuln>
 
   <vuln vid="409206f6-25e6-11f0-9360-b42e991fc52e">
     <topic>sqlite -- integer overflow</topic>
     <affects>
       <package>
 	<name>sqlite</name>
 	<range><lt>3.49.1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>cve@mitre.org reports:</p>
 	<blockquote cite="https://gist.github.com/ylwango613/a44a29f1ef074fa783e29f04a0afd62a">
 	<p>
 	In SQLite 3.44.0 through 3.49.0 before 3.49.1, the
 	concat_ws() SQL function can cause memory to be written
 	beyond the end of a malloc-allocated buffer. If the
 	separator argument is attacker-controlled and has a large
 	string (e.g., 2MB or more), an integer overflow occurs in
 	calculating the size of the result buffer, and thus malloc
 	may not allocate enough memory.
 	</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-29087</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-29087</url>
     </references>
     <dates>
       <discovery>2025-04-07</discovery>
       <entry>2025-04-30</entry>
     </dates>
   </vuln>
 
   <vuln vid="df126e23-24fa-11f0-ab92-f02f7497ecda">
     <topic>h11 accepts some malformed Chunked-Encoding bodies</topic>
     <affects>
       <package>
     <name>py39-h11</name>
     <name>py310-h11</name>
     <name>py311-h11</name>
     <name>py312-h11</name>
     <range><lt>0.16.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
     <p>h11 reports:</p>
     <blockquote cite="https://github.com/python-hyper/h11/security/advisories/GHSA-vqfr-h8mv-ghfj">
       <p>h11 is a Python implementation of HTTP/1.1. Prior to version 0.16.0, a leniency in h11's parsing of line terminators in chunked-coding message bodies can lead to request smuggling vulnerabilities under certain conditions. This issue has been patched in version 0.16.0. Since exploitation requires the combination of buggy h11 with a buggy (reverse) proxy, fixing either component is sufficient to mitigate this issue.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-43859</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-43859</url>
     </references>
     <dates>
       <discovery>2025-04-24</discovery>
       <entry>2025-04-29</entry>
     </dates>
   </vuln>
 
   <vuln vid="310f5923-211c-11f0-8ca6-6c3be5272acd">
     <topic>Grafana -- Authorization bypass in data source proxy API</topic>
     <affects>
       <package>
 	<name>grafana</name>
 	<range><ge>8.0.0</ge><lt>10.4.17+security-01</lt></range>
 	<range><ge>11.0.0</ge><lt>11.2.8+security-01</lt></range>
 	<range><ge>11.3.0</ge><lt>11.3.5+security-01</lt></range>
 	<range><ge>11.4.0</ge><lt>11.4.3+security-01</lt></range>
 	<range><ge>11.5.0</ge><lt>11.5.3+security-01</lt></range>
 	<range><ge>11.6.0</ge><lt>11.6.0+security-01</lt></range>
       </package>
       <package>
 	<name>grafana8</name>
 	<range><ge>8.0.0</ge></range>
       </package>
       <package>
 	<name>grafana9</name>
 	<range><ge>9.0.0</ge></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Grafana Labs reports:</p>
 	<blockquote cite="https://grafana.com/blog/2025/04/22/grafana-security-release-medium-and-high-severity-fixes-for-cve-2025-3260-cve-2025-2703-cve-2025-3454/">
 	  <p>This vulnerability, which was discovered while reviewing a pull
 	  request from an external contributor, effects Grafana’s data source
 	  proxy API and allows authorization checks to be bypassed by adding
 	  an extra slash character (/) in the URL path. Among Grafana-maintained
 	  data sources, the vulnerability only affects the read paths
 	  of Prometheus (all flavors) and Alertmanager when configured with
 	  basic authorization.</p>
 	  <p>The CVSS score for this vulnerability is
 	  <a href="https://www.first.org/cvss/calculator/3-1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N">5.0 MEDIUM</a>.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-3454</cvename>
       <url>https://grafana.com/blog/2025/04/22/grafana-security-release-medium-and-high-severity-fixes-for-cve-2025-3260-cve-2025-2703-cve-2025-3454/</url>
     </references>
     <dates>
       <discovery>2025-03-25</discovery>
       <entry>2025-04-24</entry>
     </dates>
   </vuln>
 
   <vuln vid="6adfda5a-2118-11f0-8ca6-6c3be5272acd">
     <topic>Grafana -- Bypass Viewer and Editor permissions</topic>
     <affects>
       <package>
 	<name>grafana</name>
 	<range><ge>11.6.0</ge><lt>11.6.0+security-01</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Grafana Labs reports:</p>
 	<blockquote cite="https://grafana.com/blog/2025/04/22/grafana-security-release-medium-and-high-severity-fixes-for-cve-2025-3260-cve-2025-2703-cve-2025-3454/">
 	  <p>During the development of a new feature in Grafana 11.6.x,
 	  a security vulnerability was introduced that allows for Viewers
 	  and Editors to bypass dashboard-specific permissions. As a result,
 	  users with the Viewer role could view all the dashboards within their
 	  org and users with the Editor role could view, edit, and delete all
 	  the dashboards in their org.</p>
 	  <p><em>Note: Organization isolation boundaries still apply, which
 	  means viewers and editors in one organization cannot view or edit
 	  dashboards in another org. Also this vulnerability does not allow
 	  users to query data via data sources they don’t have access to.</em>
 	  </p>
 	  <p>The CVSS score for this vulnerability is
 	  <a href="https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L&amp;version=3.1">8.3 HIGH</a>.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-3260</cvename>
       <url>https://grafana.com/blog/2025/04/22/grafana-security-release-medium-and-high-severity-fixes-for-cve-2025-3260-cve-2025-2703-cve-2025-3454/</url>
     </references>
     <dates>
       <discovery>2025-04-04</discovery>
       <entry>2025-04-24</entry>
     </dates>
   </vuln>
 
   <vuln vid="f8b7af82-2116-11f0-8ca6-6c3be5272acd">
     <topic>Grafana -- DOM XSS vulnerability</topic>
     <affects>
       <package>
 	<name>grafana</name>
 	<range><ge>11.1.0</ge><lt>11.2.8+security-01</lt></range>
 	<range><ge>11.3.0</ge><lt>11.3.5+security-01</lt></range>
 	<range><ge>11.4.0</ge><lt>11.4.3+security-01</lt></range>
 	<range><ge>11.5.0</ge><lt>11.5.3+security-01</lt></range>
 	<range><ge>11.6.0</ge><lt>11.6.0+security-01</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Grafana Labs reports:</p>
 	<blockquote cite="https://grafana.com/blog/2025/04/22/grafana-security-release-medium-and-high-severity-fixes-for-cve-2025-3260-cve-2025-2703-cve-2025-3454/">
 	  <p>An external security researcher responsibly reported a security
 	  vulnerability in Grafana’s built-in
 	  <a href="https://grafana.com/docs/grafana/latest/panels-visualizations/visualizations/xy-chart/">XY chart plugin</a>
 	  that is vulnerable to a
 	  <a href="https://grafana.com/blog/2023/07/11/trusted-types-how-we-mitigate-xss-threats-in-grafana-10/#what-is-dom-xss">DOM XSS vulnerability</a>.</p>
 	  <p>The CVSS score for this vulnerability is
 	  <a href="https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:L/A:L&amp;version=3.1">6.8 MEDIUM</a>.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-2703</cvename>
       <url>https://grafana.com/security/security-advisories/cve-2025-2703/</url>
     </references>
     <dates>
       <discovery>2025-03-14</discovery>
       <entry>2025-04-24</entry>
     </dates>
   </vuln>
 
   <vuln vid="af8d043f-20df-11f0-b9c5-000c295725e4">
     <topic>redis,valkey -- DoS Vulnerability due to unlimited growth of output buffers abused by unauthenticated client</topic>
     <affects>
       <package>
 	<name>redis</name>
 	<range><lt>7.4.3</lt></range>
       </package>
       <package>
 	<name>redis72</name>
 	<range><lt>7.2.8</lt></range>
       </package>
       <package>
 	<name>redis62</name>
 	<range><lt>6.2.18</lt></range>
       </package>
       <package>
 	<name>valkey</name>
 	<range><lt>8.1.1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Axel Mierczuk reports:</p>
 	<blockquote cite="https://github.com/redis/redis/security/advisories/GHSA-r67f-p999-2gff">
 	  <p>
 	    By default, the Redis configuration does not limit the
 	    output buffer of normal clients (see
 	    client-output-buffer-limit). Therefore, the output buffer
 	    can grow unlimitedly over time. As a result, the service
 	    is exhausted and the memory is unavailable.
 	  </p>
 	  <p>
 	    When password authentication is enabled on the Redis
 	    server, but no password is provided, the client can still
 	    cause the output buffer to grow from "NOAUTH" responses
 	    until the system will run out of memory.
 	  </p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-21605</cvename>
       <url>https://github.com/redis/redis/security/advisories/GHSA-r67f-p999-2gff</url>
     </references>
     <dates>
       <discovery>2025-04-23</discovery>
       <entry>2025-04-24</entry>
     </dates>
   </vuln>
 
   <vuln vid="11b71871-20ba-11f0-9471-2cf05da270f3">
     <topic>Gitlab -- Vulnerabilities</topic>
     <affects>
       <package>
 	<name>gitlab-ce</name>
 	<name>gitlab-ee</name>
 	<range><ge>17.11.0</ge><lt>17.11.1</lt></range>
 	<range><ge>17.10.0</ge><lt>17.10.5</lt></range>
 	<range><ge>16.6.0</ge><lt>17.9.7</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Gitlab reports:</p>
 	<blockquote cite="https://about.gitlab.com/releases/2025/04/23/patch-release-gitlab-17-11-1-released/">
 	  <p>Cross Site Scripting (XSS) in Maven Dependency Proxy through CSP directives</p>
 	  <p>Cross Site Scripting (XSS) in Maven dependency proxy through cache headers</p>
 	  <p>Network Error Logging (NEL) Header Injection in Maven Dependency Proxy Allows Browser Activity Monitoring</p>
 	  <p>Denial of service (DOS) via issue preview</p>
 	  <p>Unauthorized access to branch names when Repository assets are disabled in the project</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-1763</cvename>
       <cvename>CVE-2025-2443</cvename>
       <cvename>CVE-2025-1908</cvename>
       <cvename>CVE-2025-0639</cvename>
       <cvename>CVE-2024-12244</cvename>
       <url>https://about.gitlab.com/releases/2025/04/23/patch-release-gitlab-17-11-1-released/</url>
     </references>
     <dates>
       <discovery>2025-04-23</discovery>
       <entry>2025-04-24</entry>
     </dates>
   </vuln>
 
   <vuln vid="194f79c3-1ffe-11f0-8cb5-a8a1599412c6">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>135.0.7049.114</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>135.0.7049.114</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2025/04/stable-channel-update-for-desktop_22.html">
 	 <p>This update includes 1 security fix.</p>
        </blockquote>
       </body>
     </description>
     <references>
       <url>https://chromereleases.googleblog.com/2025/04/stable-channel-update-for-desktop_22.html</url>
     </references>
     <dates>
       <discovery>2025-04-22</discovery>
       <entry>2025-04-23</entry>
     </dates>
   </vuln>
 
   <vuln vid="5ca2cafa-1f24-11f0-ab07-f8f21e52f724">
     <topic>Navidrome -- Authentication bypass in Subsonic API</topic>
     <affects>
       <package>
 	<name>navidrome</name>
 	<range><gt>0.52.0</gt><lt>0.54.5</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Deluan reports:</p>
 	<blockquote cite="https://github.com/navidrome/navidrome/security/advisories/GHSA-c3p4-vm8f-386p">
 	  <p>In certain Subsonic API endpoints, authentication can be
 	bypassed by using a non-existent username combined with an
 	empty (salted) password hash. This allows read-only access to
 	the server’s resources, though attempts at write operations
 	fail with a “permission denied” error.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-27112</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-27112</url>
     </references>
     <dates>
       <discovery>2025-02-25</discovery>
       <entry>2025-04-22</entry>
     </dates>
   </vuln>
 
   <vuln vid="06269ae8-1e0d-11f0-ad0b-b42e991fc52e">
     <topic>Erlang -- Erlang/OTP SSH Vulnerable to Pre-Authentication RCE</topic>
     <affects>
       <package>
 	<name>erlang</name>
 	<range><lt>26.2.5.11</lt></range>
       </package>
       <package>
 	<name>erlang-runtime21</name>
 	<range><lt>25.3.2.20</lt></range>
       </package>
       <package>
 	<name>erlang-runtime22</name>
 	<range><lt>25.3.2.20</lt></range>
       </package>
       <package>
 	<name>erlang-runtime23</name>
 	<range><lt>25.3.2.20</lt></range>
       </package>
       <package>
 	<name>erlang-runtime24</name>
 	<range><lt>25.3.2.20</lt></range>
       </package>
       <package>
 	<name>erlang-runtime25</name>
 	<range><lt>25.3.2.20</lt></range>
       </package>
       <package>
 	<name>erlang-runtime26</name>
 	<range><lt>26.2.5.11</lt></range>
       </package>
       <package>
 	<name>erlang-runtime27</name>
 	<range><lt>27.3.3</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security-advisories@github.com reports:</p>
 	<blockquote cite="https://github.com/erlang/otp/commit/0fcd9c56524b28615e8ece65fc0c3f66ef6e4c12">
 	<p>
 	Erlang/OTP is a set of libraries for the Erlang
 	programming language. Prior to versions OTP-27.3.3,
 	OTP-26.2.5.11, and OTP-25.3.2.20, a SSH server may allow
 	an attacker to perform unauthenticated remote code
 	execution (RCE). By exploiting a flaw in SSH protocol
 	message handling, a malicious actor could gain
 	unauthorized access to affected systems and execute
 	arbitrary commands without valid credentials. This issue
 	is patched in versions OTP-27.3.3, OTP-26.2.5.11, and
 	OTP-25.3.2.20. A temporary workaround involves disabling
 	the SSH server or to prevent access via firewall rules.
 	</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-32433</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-32433</url>
     </references>
     <dates>
       <discovery>2025-04-16</discovery>
       <entry>2025-04-20</entry>
     </dates>
   </vuln>
 
   <vuln vid="1b8d502e-1cfd-11f0-944d-901b0e9408dc">
     <topic>ejabberd -- mod_muc_occupantid: Fix handling multiple occupant-id</topic>
     <affects>
       <package>
 	<name>ejabberd</name>
 	<range><lt>25.04</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>ejabberd team reports:</p>
 	<blockquote cite="https://www.process-one.net/blog/ejabberd-25-04/#occupantid">
 	  <p>Fixed issue with handling of user provided occupant-id in
 	  messages and presences sent to muc room. Server was
 	  replacing just first instance of occupant-id with its own
 	  version, leaving other ones untouched. That would mean that
 	  depending on order in which clients send occupant-id, they
 	  could see value provided by sender, and that could be used
 	  to spoof as different sender.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <url>https://www.process-one.net/blog/ejabberd-25-04/#occupantid</url>
     </references>
     <dates>
       <discovery>2025-04-16</discovery>
       <entry>2025-04-19</entry>
     </dates>
   </vuln>
 
   <vuln vid="bf5d29ea-1a93-11f0-8cb5-a8a1599412c6">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>135.0.7049.95</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>135.0.7049.95</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2025/04/stable-channel-update-for-desktop_15.html">
 	 <p>This update includes 2 security fixes:</p>
 	 <ul>
 	    <li>[409619251] Critical CVE-2025-3619: Heap buffer overflow in Codecs. Reported by Elias Hohl on 2025-04-09</li>
 	    <li>[405292639] High CVE-2025-3620: Use after free in USB. Reported by @retsew0x01 on 2025-03-21</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2025-3619</cvename>
       <cvename>CVE-2025-3620</cvename>
       <url>https://chromereleases.googleblog.com/2025/04/stable-channel-update-for-desktop_15.html</url>
     </references>
     <dates>
       <discovery>2025-04-15</discovery>
       <entry>2025-04-16</entry>
     </dates>
   </vuln>
 
   <vuln vid="030778d5-19cc-11f0-8cb5-a8a1599412c6">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>135.0.7049.84</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>135.0.7049.84</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2025/04/stable-channel-update-for-desktop_8.html">
 	 <p>This update includes 2 security fixes:</p>
 	 <ul>
 	    <li>[405140652] High CVE-2025-3066: Use after free in Site Isolation. Reported by Sven Dysthe (@svn-dys) on 2025-03-21</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2025-3066</cvename>
       <url>https://chromereleases.googleblog.com/2025/04/stable-channel-update-for-desktop_8.html</url>
     </references>
     <dates>
       <discovery>2025-04-08</discovery>
       <entry>2025-04-15</entry>
     </dates>
   </vuln>
 
   <vuln vid="e9b8e519-0d50-11f0-86d8-901b0e934d69">
     <topic>py-matrix-synapse -- federation denial of service via malformed events</topic>
     <affects>
       <package>
 	<name>py38-matrix-synapse</name>
 	<name>py39-matrix-synapse</name>
 	<name>py310-matrix-synapse</name>
 	<name>py311-matrix-synapse</name>
 	<range><lt>1.127.1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>element-hq/synapse developers report:</p>
 	<blockquote cite="https://github.com/element-hq/synapse/security/advisories/GHSA-v56r-hwv5-mxg6">
 	  <p>A malicious server can craft events which, when received, prevent Synapse version up to 1.127.0 from federating with other servers. The vulnerability has been exploited in the wild.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-30355</cvename>
       <url>https://github.com/element-hq/synapse/security/advisories/GHSA-v56r-hwv5-mxg6</url>
     </references>
     <dates>
       <discovery>2025-03-26</discovery>
       <entry>2025-03-26</entry>
     </dates>
   </vuln>
 
   <vuln vid="45276ea6-1653-4240-9986-ccfc6fec7ece">
     <topic>jenkins -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>jenkins</name>
 	<range><lt>2.504</lt></range>
       </package>
       <package>
 	<name>jenkins-lts</name>
 	<range><lt>2.492.3</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Jenkins Security Advisory:</p>
 	<blockquote cite="https://www.jenkins.io/security/advisory/2025-04-02/">
 	  <h1>Description</h1>
 	  <h5>(Medium) SECURITY-3512 / CVE-2025-31720</h5>
 	  <p>Missing permission check allows retrieving agent configurations</p>
 	  <h1>Description</h1>
 	  <h5>(Medium) SECURITY-3513 / CVE-2025-31721</h5>
 	  <p>Missing permission check allows retrieving secrets from agent configurations</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-31720</cvename>
       <cvename>CVE-2025-31721</cvename>
       <url>https://www.jenkins.io/security/advisory/2025-04-02/</url>
     </references>
     <dates>
       <discovery>2025-04-02</discovery>
       <entry>2025-04-11</entry>
     </dates>
   </vuln>
 
   <vuln vid="ed602f8b-15c2-11f0-b4e4-2cf05da270f3">
     <topic>Gitlab -- Vulnerabilities</topic>
     <affects>
       <package>
 	<name>gitlab-ce</name>
 	<name>gitlab-ee</name>
 	<range><ge>17.10.0</ge><lt>17.10.4</lt></range>
 	<range><ge>17.9.0</ge><lt>17.9.6</lt></range>
 	<range><ge>7.7.0</ge><lt>17.8.7</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Gitlab reports:</p>
 	<blockquote cite="https://about.gitlab.com/releases/2025/04/09/patch-release-gitlab-17-10-4-released/">
 	  <p>Denial of service via CI pipelines</p>
 	  <p>Unintentionally authorizing sensitive actions on users behalf</p>
 	  <p>IP Restriction Bypass through GraphQL Subscription</p>
 	  <p>Unauthorized users can list the number of confidential issues</p>
 	  <p>Debugging Information Disclosed</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-1677</cvename>
       <cvename>CVE-2025-0362</cvename>
       <cvename>CVE-2025-2408</cvename>
       <cvename>CVE-2024-11129</cvename>
       <cvename>CVE-2025-2469</cvename>
       <url>https://about.gitlab.com/releases/2025/04/09/patch-release-gitlab-17-10-4-released/</url>
     </references>
     <dates>
       <discovery>2025-04-09</discovery>
       <entry>2025-04-10</entry>
     </dates>
   </vuln>
 
   <vuln vid="8f71ad3b-14f5-11f0-87ba-002590c1f29c">
     <topic>expat: improper restriction of xml entity expansion depth</topic>
     <affects>
       <package>
 	<name>expat</name>
 	<range><lt>2.7.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>secalert@redhat.com reports:</p>
 	<blockquote cite="https://access.redhat.com/errata/RHSA-2025:3531">
 	  <p>A stack overflow vulnerability exists in the libexpat library due
 	  to the way it handles recursive entity expansion in XML documents.
 	  When parsing an XML document with deeply nested entity references,
 	  libexpat can be forced to recurse indefinitely, exhausting the stack
 	  space and causing a crash.  This issue could lead to denial of
 	  service (DoS) or, in some cases, exploitable memory corruption,
 	  depending on the environment and library usage.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-8176</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-8176</url>
     </references>
     <dates>
       <discovery>2025-03-14</discovery>
       <entry>2025-04-09</entry>
     </dates>
   </vuln>
 
   <vuln vid="34c51a2b-13c8-11f0-a5bd-b42e991fc52e">
     <topic>Mozilla -- memory corruption</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>137.0,2</lt></range>
       </package>
       <package>
 	<name>librewolf</name>
 	<range><lt>137.0</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>137.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/buglist.cgi?bug_id=1894100%2C1934086%2C1950360">
 	  <p>Memory safety bugs present in Firefox 136 and Thunderbird 136.
 	  Some of these bugs showed evidence of memory corruption and
 	  we presume that with enough effort some of these could have
 	  been exploited to run arbitrary code.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-3034</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-3034</url>
     </references>
     <dates>
       <discovery>2025-04-01</discovery>
       <entry>2025-04-07</entry>
     </dates>
   </vuln>
 
   <vuln vid="315f568e-13c8-11f0-a5bd-b42e991fc52e">
     <topic>Mozilla -- privilege escalation attack</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>137.0,2</lt></range>
       </package>
       <package>
 	<name>librewolf</name>
 	<range><lt>137.0</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>137.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1949987">
 	  <p>Leaking of file descriptors from the fork server to web
 	    content processes could allow for privilege escalation
 	    attacks.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-3032</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-3032</url>
     </references>
     <dates>
       <discovery>2025-04-01</discovery>
       <entry>2025-04-07</entry>
     </dates>
   </vuln>
 
   <vuln vid="2fc74cae-13c8-11f0-a5bd-b42e991fc52e">
     <topic>Mozilla -- stack memory read</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>137.0,2</lt></range>
       </package>
       <package>
 	<name>librewolf</name>
 	<range><lt>137.0</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>137.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1947141">
 	  <p>An attacker could read 32 bits of values spilled onto the stack in
 	a JIT compiled function.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-3031</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-3031</url>
     </references>
     <dates>
       <discovery>2025-04-01</discovery>
       <entry>2025-04-07</entry>
     </dates>
   </vuln>
 
   <vuln vid="2e0ff31b-13c8-11f0-a5bd-b42e991fc52e">
     <topic>Mozilla -- Memory corruption</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>137.0</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>128.9.0</lt></range>
       </package>
       <package>
 	<name>firefox</name>
 	<range><lt>137.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/buglist.cgi?bug_id=1850615%2C1932468%2C1942551%2C1951017%2C1951494">
 	  <p>Memory safety bugs present in Firefox 136, Thunderbird
 	  136, Firefox ESR 128.8, and Thunderbird 128.8. Some of these
 	  bugs showed evidence of memory corruption and we presume
 	  that with enough effort some of these could have been
 	  exploited to run arbitrary code.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-3030</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-3030</url>
     </references>
     <dates>
       <discovery>2025-04-01</discovery>
       <entry>2025-04-07</entry>
     </dates>
   </vuln>
 
   <vuln vid="2c0180a5-13c8-11f0-a5bd-b42e991fc52e">
     <topic>Mozilla -- URL spoofing attack</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>137.0,2</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>128.9</lt></range>
       </package>
       <package>
 	<name>librewolf</name>
 	<range><lt>137.0</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>137.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1952213">
 	  <p>A crafted URL containing specific Unicode characters
 	  could have hidden the true origin of the page, resulting in
 	  a potential spoofing attack.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-3029</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-3029</url>
     </references>
     <dates>
       <discovery>2025-04-01</discovery>
       <entry>2025-04-07</entry>
     </dates>
   </vuln>
 
   <vuln vid="28e5f7be-13c8-11f0-a5bd-b42e991fc52e">
     <topic>Mozilla -- use-after-free error</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>137.0,2</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>115.22</lt></range>
       </package>
       <package>
 	<name>librewolf</name>
 	<range><lt>137.0</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>137.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1941002">
 	  <p>JavaScript code running while transforming a document
 	  with the XSLTProcessor could lead to a use-after-free.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-3028</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-3028</url>
     </references>
     <dates>
       <discovery>2025-04-01</discovery>
       <entry>2025-04-07</entry>
     </dates>
   </vuln>
 
   <vuln vid="789bcfb6-1224-11f0-85f3-a8a1599412c6">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>135.0.7049.52</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>135.0.7049.52</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2025/04/stable-channel-update-for-desktop.html">
 	 <p>This update includes 13 security fixes:</p>
 	 <ul>
 	    <li>[376491759] Medium CVE-2025-3067: Inappropriate implementation in Custom Tabs. Reported by Philipp Beer (TU Wien) on 2024-10-31</li>
 	    <li>[401823929] Medium CVE-2025-3068: Inappropriate implementation in Intents. Reported by Simon Rawet on 2025-03-09</li>
 	    <li>[40060076] Medium CVE-2025-3069: Inappropriate implementation in Extensions. Reported by NDevTK on 2022-06-26</li>
 	    <li>[40086360] Medium CVE-2025-3070: Insufficient validation of untrusted input in Extensions. Reported by Anonymous on 2017-01-01</li>
 	    <li>[40051596] Low CVE-2025-3071: Inappropriate implementation in Navigations. Reported by David Erceg on 2020-02-23</li>
 	    <li>[362545037] Low CVE-2025-3072: Inappropriate implementation in Custom Tabs. Reported by Om Apip on 2024-08-27</li>
 	    <li>[388680893] Low CVE-2025-3073: Inappropriate implementation in Autofill. Reported by Hafiizh on 2025-01-09</li>
 	    <li>[392818696] Low CVE-2025-3074: Inappropriate implementation in Downloads. Reported by Farras Givari on 2025-01-28</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2025-3067</cvename>
       <cvename>CVE-2025-3068</cvename>
       <cvename>CVE-2025-3069</cvename>
       <cvename>CVE-2025-3070</cvename>
       <cvename>CVE-2025-3071</cvename>
       <cvename>CVE-2025-3072</cvename>
       <cvename>CVE-2025-3073</cvename>
       <cvename>CVE-2025-3074</cvename>
       <url>https://chromereleases.googleblog.com/2025/04/stable-channel-update-for-desktop.html</url>
     </references>
     <dates>
       <discovery>2025-04-01</discovery>
       <entry>2025-04-05</entry>
     </dates>
   </vuln>
 
   <vuln vid="1205eccf-116d-11f0-8b2c-b42e991fc52e">
     <topic>Mozilla -- Memory corruption bug</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>134.0,2</lt></range>
       </package>
       <package>
 	<name>librewolf</name>
 	<range><lt>134.0</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>128.6.0</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>134.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/buglist.cgi?bug_id=1827142%2C1932783">
 	  <p>Memory safety bugs present in Firefox 133, Thunderbird 133,
 	  Firefox ESR 128.5, and Thunderbird 128.5.  Some of these
 	  bugs showed evidence of memory corruption and we presume
 	  that with enough effort some of these could have been
 	  exploited to run arbitrary code.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-0243</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-0243</url>
     </references>
     <dates>
       <discovery>2025-01-07</discovery>
       <entry>2025-04-04</entry>
     </dates>
   </vuln>
 
   <vuln vid="f9d7b6ae-116c-11f0-8b2c-b42e991fc52e">
     <topic>Mozilla -- Memory safety bugs</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>134.0,2</lt></range>
       </package>
       <package>
 	<name>librewolf</name>
 	<range><lt>134.0</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>134.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/buglist.cgi?bug_id=1835193%2C1910021%2C1919803%2C1931576%2C1931948%2C1932173">
 	  <p>Memory safety bugs present in Firefox 133 and Thunderbird 133.
 	  Some of these bugs showed evidence of memory corruption and
 	  we presume that with enough effort some of these could have
 	  been exploited to run arbitrary code.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-0247</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-0247</url>
     </references>
     <dates>
       <discovery>2025-01-07</discovery>
       <entry>2025-04-04</entry>
     </dates>
   </vuln>
 
   <vuln vid="f7d80111-116c-11f0-8b2c-b42e991fc52e">
     <topic>firefox -- authentication bypass</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>134.0,2</lt></range>
       </package>
       <package>
 	<name>librewolf</name>
 	<range><lt>134.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1895342">
 	  <p>Under certain circumstances, a user opt-in setting that
 	  Focus should require authentication before use could have
 	  been be bypassed.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-0245</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-0245</url>
     </references>
     <dates>
       <discovery>2025-01-07</discovery>
       <entry>2025-04-04</entry>
     </dates>
   </vuln>
 
   <vuln vid="f508f81e-116c-11f0-8b2c-b42e991fc52e">
     <topic>Mozilla -- Memory safety bugs</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>134.0,2</lt></range>
       </package>
       <package>
 	<name>librewolf</name>
 	<range><lt>134.0</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>115.19</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>134.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/buglist.cgi?bug_id=1874523%2C1926454%2C1931873%2C1932169">
 	  <p>Memory safety bugs present in Firefox 133, Thunderbird 133,
 	  Firefox ESR 115.18, Firefox ESR 128.5, Thunderbird 115.18,
 	  and Thunderbird 128.5.  Some of these bugs showed evidence
 	  of memory corruption and we presume that with enough effort
 	  some of these could have been exploited to run arbitrary
 	  code.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-0242</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-0242</url>
     </references>
     <dates>
       <discovery>2025-01-07</discovery>
       <entry>2025-04-04</entry>
     </dates>
   </vuln>
 
   <vuln vid="f38dd0f1-116c-11f0-8b2c-b42e991fc52e">
     <topic>Mozilla -- DoS via segmentation fault</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>134.0,2</lt></range>
       </package>
       <package>
 	<name>librewolf</name>
 	<range><lt>134.0</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>128.6.0</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>134.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1933023">
 	  <p>When segmenting specially crafted text, segmentation
 	  would corrupt memory leading to a potentially exploitable
 	  crash.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-0241</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-0241</url>
     </references>
     <dates>
       <discovery>2025-01-07</discovery>
       <entry>2025-04-04</entry>
     </dates>
   </vuln>
 
   <vuln vid="f1f92cd3-116c-11f0-8b2c-b42e991fc52e">
     <topic>Mozilla -- use-after-free while parsing JSON</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>134.0,2</lt></range>
       </package>
       <package>
 	<name>librewolf</name>
 	<range><lt>134.0</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>128.6.0</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>134.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1929623">
 	  <p>Parsing a JavaScript module as JSON could, under some
 	  circumstances, cause cross-compartment access, which may
 	  result in a use-after-free.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-0240</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-0240</url>
     </references>
     <dates>
       <discovery>2025-01-07</discovery>
       <entry>2025-04-04</entry>
     </dates>
   </vuln>
 
   <vuln vid="f02e3c59-116c-11f0-8b2c-b42e991fc52e">
     <topic>Mozilla -- redirection to insecure site</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>134.0,2</lt></range>
       </package>
       <package>
 	<name>librewolf</name>
 	<range><lt>134.0</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>128.6.0</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>134.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1929156">
 	  <p>When using Alt-Svc, ALPN did not properly validate
 	    certificates when the original server is redirecting to an
 	    insecure site.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-0239</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-0239</url>
     </references>
     <dates>
       <discovery>2025-01-07</discovery>
       <entry>2025-04-04</entry>
     </dates>
   </vuln>
 
   <vuln vid="ee407762-116c-11f0-8b2c-b42e991fc52e">
     <topic>Mozilla -- use-after-free after failed memory allocation</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>134.0,2</lt></range>
       </package>
       <package>
 	<name>librewolf</name>
 	<range><lt>134.0</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>128.6.0</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>128.6</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1915535">
 	  <p>Assuming a controlled failed memory allocation, an
 	  attacker could have caused a use-after-free, leading to a
 	  potentially exploitable crash.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-0238</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-0238</url>
     </references>
     <dates>
       <discovery>2025-01-07</discovery>
       <entry>2025-04-04</entry>
     </dates>
   </vuln>
 
   <vuln vid="ea51e89a-116c-11f0-8b2c-b42e991fc52e">
     <topic>Mozilla -- privilege escalation attack</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>134.0,2</lt></range>
       </package>
       <package>
 	<name>librewolf</name>
 	<range><lt>134.0</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>128.6.0</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>128.6</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1915257">
 	  <p>The WebChannel API, which is used to transport various
 	  information across processes, did not check the sending
 	  principal but rather accepted the principal being sent.
 	  This could have led to privilege escalation attacks.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-0237</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-0237</url>
     </references>
     <dates>
       <discovery>2025-01-07</discovery>
       <entry>2025-04-04</entry>
     </dates>
   </vuln>
 
   <vuln vid="37c368f1-10a2-11f0-8195-b42e991fc52e">
     <topic>mozilla -- memory corruption</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>136.0,2</lt></range>
       </package>
       <package>
 	<name>librewolf</name>
 	<range><lt>136.0</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>136.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/buglist.cgi?bug_id=1869650%2C1938451%2C1940326%2C1944052%2C1944063%2C1947281">
 	  <p>Memory safety bugs present in Firefox 135 and Thunderbird
 	  135. Some of these bugs showed evidence of memory corruption
 	  and we presume that with enough effort some of these could
 	  have been exploited to run arbitrary code.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-1943</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-1943</url>
     </references>
     <dates>
       <discovery>2025-03-04</discovery>
       <entry>2025-04-03</entry>
     </dates>
   </vuln>
 
   <vuln vid="b31a4e74-109d-11f0-8195-b42e991fc52e">
     <topic>mozilla -- memory corruption</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>136.0,2</lt></range>
       </package>
       <package>
 	<name>librewolf</name>
 	<range><lt>136.0</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>128.8,1</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>136.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/buglist.cgi?bug_id=1922889%2C1935004%2C1943586%2C1943912%2C1948111">
 	<p>CVE-2025-1938: Memory safety bugs present in Firefox 135,
 	Thunderbird 135, Firefox ESR 128.7, and Thunderbird 128.7.
 	Some of these bugs showed evidence of memory corruption and
 	we presume that with enough effort some of these could have
 	been exploited to run arbitrary code.</p>
 	<p>CVE-2025-1935: A web page could trick a user into setting
 	that site as the default handler for a custom URL protocol.</p>
 	<p>CVE-2025-1934: It was possible to interrupt the processing
 	of a RegExp bailout and run additional JavaScript, potentially
 	triggering garbage collection when the engine was not
 	expecting it.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-1938</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-1938</url>
       <cvename>CVE-2025-1935</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-1935</url>
       <cvename>CVE-2025-1934</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-1934</url>
     </references>
     <dates>
       <discovery>2025-03-04</discovery>
       <entry>2025-04-03</entry>
     </dates>
   </vuln>
 
   <vuln vid="aeb2ca87-109d-11f0-8195-b42e991fc52e">
     <topic>mozilla -- Memory safety bugs</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>136.0,2</lt></range>
       </package>
       <package>
 	<name>librewolf</name>
 	<range><lt>136.0</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>115.21,1</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>136.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/buglist.cgi?bug_id=1938471%2C1940716">
 	<p>Memory safety bugs present in Firefox 135, Thunderbird 135,
 	Firefox ESR 115.20, Firefox ESR 128.7, and Thunderbird 128.7.
 	Some of these bugs showed evidence of memory corruption and
 	we presume that with enough effort some of these could have
 	been exploited to run arbitrary code.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-1937</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-1937</url>
     </references>
     <dates>
       <discovery>2025-03-04</discovery>
       <entry>2025-04-03</entry>
     </dates>
   </vuln>
 
   <vuln vid="acf902f6-109d-11f0-8195-b42e991fc52e">
     <topic>mozilla -- use-after-free in WebTransport connection</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>136.0,2</lt></range>
       </package>
       <package>
 	<name>librewolf</name>
 	<range><lt>136.0</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>115.21,1</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>136.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1944126">
 	  <p>It was possible to cause a use-after-free in the content
 	  process side of a WebTransport connection, leading to a
 	  potentially exploitable crash.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-1931</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-1931</url>
     </references>
     <dates>
       <discovery>2025-03-04</discovery>
       <entry>2025-04-03</entry>
     </dates>
   </vuln>
 
   <vuln vid="a93a1d2a-109d-11f0-8195-b42e991fc52e">
     <topic>mozilla -- 64 bit JIT WASM read on left over memory</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>136.0,2</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>115.21,1</lt></range>
       </package>
       <package>
 	<name>librewolf</name>
 	<range><lt>136.0</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>136.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1946004">
 	 <p>On 64-bit CPUs, when the JIT compiles WASM i32 return
 	 values they can pick up bits from left over memory.
 	 This can potentially cause them to be treated as a different
 	 type.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-1933</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-1933</url>
     </references>
     <dates>
       <discovery>2025-03-04</discovery>
       <entry>2025-04-03</entry>
     </dates>
   </vuln>
 
   <vuln vid="350b3389-107f-11f0-8195-b42e991fc52e">
     <topic>MongoDB -- crash due to improper validation of explain command</topic>
     <affects>
       <package>
 	<name>mongodb50</name>
 	<range><lt>5.0.31</lt></range>
       </package>
       <package>
 	<name>mongodb60</name>
 	<range><lt>6.0.20</lt></range>
       </package>
       <package>
 	<name>mongodb70</name>
 	<range><lt>7.0.16</lt></range>
       </package>
       <package>
 	<name>mongodb80</name>
 	<range><lt>8.0.4</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>cna@mongodb.com reports:</p>
 	<blockquote cite="https://jira.mongodb.org/browse/SERVER-103153">
 	  <p>When run on commands with certain arguments set, explain may fail
 	to validate these arguments before using them.  This can lead to
 	crashes in router servers.  This affects MongoDB Server v5.0 prior
 	to 5.0.31, MongoDB Server v6.0 prior to 6.0.20, MongoDB Server v7.0
 	prior to 7.0.16 and MongoDB Server v8.0 prior to 8.0.4</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-3084</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-3084</url>
     </references>
     <dates>
       <discovery>2025-04-01</discovery>
       <entry>2025-04-03</entry>
     </dates>
   </vuln>
 
   <vuln vid="32f5e57f-107f-11f0-8195-b42e991fc52e">
     <topic>MongoDB -- Malformed wire protocol messages may cause mongos to crash</topic>
     <affects>
       <package>
 	<name>mongodb50</name>
 	<range><lt>5.0.31</lt></range>
       </package>
       <package>
 	<name>mongodb60</name>
 	<range><lt>6.0.20</lt></range>
       </package>
       <package>
 	<name>mongodb70</name>
 	<range><lt>7.0.16</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>cna@mongodb.com reports:</p>
 	<blockquote cite="https://jira.mongodb.org/browse/SERVER-103152">
 	  <p>Specifically crafted MongoDB wire protocol messages can cause mongos
 	to crash during command validation.  This can occur without using
 	an authenticated connection.  This issue affects MongoDB v5.0
 	versions prior to 5.0.31, MongoDB v6.0 versions prior to6.0.20 and
 	MongoDB v7.0 versions prior to 7.0.16</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-3083</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-3083</url>
     </references>
     <dates>
       <discovery>2025-04-01</discovery>
       <entry>2025-04-03</entry>
     </dates>
   </vuln>
 
   <vuln vid="30418b26-107f-11f0-8195-b42e991fc52e">
     <topic>MongoDB -- Unauthorized access to underlying data</topic>
     <affects>
       <package>
 	<name>mongodb50</name>
 	<range><lt>5.0.31</lt></range>
       </package>
       <package>
 	<name>mongodb60</name>
 	<range><lt>6.0.20</lt></range>
       </package>
       <package>
 	<name>mongodb70</name>
 	<range><lt>7.0.16</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>cna@mongodb.com reports:</p>
 	<blockquote cite="https://jira.mongodb.org/browse/SERVER-103151">
 	  <p>A user authorized to access a view may be able to alter the intended
 	collation, allowing them to access to a different or unintended
 	view of underlying data.  This issue affects MongoDB Server v5.0
 	version prior to 5.0.31, MongoDB Server v6.0 version prior to 6.0.20,
 	MongoDB Server v7.0 version prior to 7.0.14 and MongoDB Server v7.3
 	versions prior to 7.3.4.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-3082</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-3082</url>
     </references>
     <dates>
       <discovery>2025-04-01</discovery>
       <entry>2025-04-03</entry>
     </dates>
   </vuln>
 
   <vuln vid="2cad4541-0f5b-11f0-89f8-411aefea0df9">
     <topic>openvpn -- server-side denial-of-service vulnerability with tls-crypt-v2</topic>
     <affects>
       <package>
 	<name>openvpn</name>
 	<range><ge>2.6.1</ge><lt>2.6.14</lt></range>
       </package>
       <package>
 	<name>openvpn-devel</name>
 	<range><lt>g20250402,1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Gert Doering reports:</p>
 	<blockquote cite="https://github.com/OpenVPN/openvpn/blob/v2.6.14/Changes.rst#overview-of-changes-in-2614">
 	  <p>OpenVPN servers between 2.6.1 and 2.6.13 using
 	    --tls-crypt-v2 can be made to abort with an ASSERT() message by
 	    sending a particular combination of authenticated and malformed packets.</p>
 	  <p>To trigger the bug, a valid tls-crypt-v2 client key is needed, or
 	    network observation of a handshake with a valid tls-crypt-v2 client key</p>
 	  <p>No crypto integrity is violated, no data is leaked, and no remote
 	    code execution is possible.</p>
 	  <p>This bug does not affect OpenVPN clients.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-2704</cvename>
       <url>https://github.com/OpenVPN/openvpn/blob/v2.6.14/Changes.rst#overview-of-changes-in-2614</url>
     </references>
     <dates>
       <discovery>2025-03-26</discovery>
       <entry>2025-04-02</entry>
     </dates>
   </vuln>
 
   <vuln vid="300f86de-0e4d-11f0-ae40-b42e991fc52e">
     <topic>gitea -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>gitea</name>
 	<range><lt>1.23.6</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@golang.org reports:</p>
 	<blockquote cite="https://go.dev/cl/654697">
 	<p>Matching of hosts against proxy patterns can improperly treat an
 	IPv6 zone ID as a hostname component.  For example, when the NO_PROXY
 	environment variable is set to &quot;*.example.com&quot;, a request
 	to &quot;[::1%25.example.com]:80` will incorrectly match and not
 	be proxied.</p>
 	<p>go-redis is the official Redis client library for the Go programming
 	language.  Prior to 9.5.5, 9.6.3, and 9.7.3, go-redis potentially
 	responds out of order when `CLIENT SETINFO` times out during
 	connection establishment.  This can happen when the client is
 	configured to transmit its identity, there are network connectivity
 	issues, or the client was configured with aggressive timeouts.  The
 	problem occurs for multiple use cases.  For sticky connections, you
 	receive persistent out-of-order responses for the lifetime of the
 	connection.  All commands in the pipeline receive incorrect responses.
 	When used with the default ConnPool once a connection is returned
 	after use with ConnPool#Put the read buffer will be checked and the
 	connection will be marked as bad due to the unread data.  This means
 	that at most one out-of-order response before the connection is
 	discarded.  This issue is fixed in 9.5.5, 9.6.3, and 9.7.3.  You
 	can prevent the vulnerability by setting the flag DisableIndentity
 	to true when constructing the client instance.</p>
 	<p>golang-jwt is a Go implementation of JSON Web Tokens.  Prior to
 	5.2.2 and 4.5.2, the function parse.ParseUnverified splits (via a
 	call to strings.Split) its argument (which is untrusted data) on
 	periods.  As a result, in the face of a malicious request whose
 	Authorization header consists of Bearer followed by many period
 	characters, a call to that function incurs allocations to the tune
 	of O(n) bytes (where n stands for the length of the function&apos;s
 	argument), with a constant factor of about 16.  This issue is fixed
 	in 5.2.2 and 4.5.2.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-22870</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-22870</url>
       <cvename>CVE-2025-29923</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-29923</url>
       <cvename>CVE-2025-30204</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-30204</url>
     </references>
     <dates>
       <discovery>2025-03-12</discovery>
       <entry>2025-03-31</entry>
     </dates>
   </vuln>
 
   <vuln vid="1a67144d-0d86-11f0-8542-b42e991fc52e">
     <topic>mozilla -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>136.0,2</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>128.8,1</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>136.0</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>128.8</lt></range>
       </package>
       <package>
 	<name>librewolf</name>
 	<range><lt>136.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1945392">
 	  <p>An inconsistent comparator in xslt/txNodeSorter could have resulted
 	in potentially exploitable out-of-bounds access.  Only affected
 	version 122 and later.  This vulnerability affects Firefox &lt;
 	136, Firefox ESR &lt; 128.8, Thunderbird &lt; 136, and Thunderbird
 	&lt; 128.8.</p>
 	  <p>Under certain circumstances, a user opt-in setting that Focus should
 	require authentication before use could have been be bypassed
 	(distinct from CVE-2025-0245).  This vulnerability affects Firefox
 	&lt; 136.</p>
 	  <p>When String.toUpperCase() caused a string to get longer it was
 	possible for uninitialized memory to be incorporated into the result
 	string This vulnerability affects Firefox &lt; 136 and Thunderbird
 	&lt; 136.</p>
 	  <p>Websites redirecting to a non-HTTP scheme URL could allow a website
 	address to be spoofed for a malicious page This vulnerability affects
 	Firefox for iOS &lt; 136.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-1932</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-1932</url>
       <cvename>CVE-2025-1941</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-1941</url>
       <cvename>CVE-2025-1942</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-1942</url>
       <cvename>CVE-2025-27424</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-27424</url>
     </references>
     <dates>
       <discovery>2025-03-04</discovery>
       <entry>2025-03-30</entry>
     </dates>
   </vuln>
 
   <vuln vid="1d53db32-0d60-11f0-8542-b42e991fc52e">
     <topic>suricata -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>suricata</name>
 	<range><lt>7.0.9</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Suricate team reports:</p>
 	<blockquote cite="https://forum.suricata.io/t/suricata-7-0-9-released/5495">
 	  <p>Multiple vulnerabilities</p>
 	</blockquote>
 	<ul>
 	<li>
 	CVE-2025-29915: Severity HIGH. The AF_PACKET defrag option
 	is enabled by default and allows AF_PACKET to re-assemble
 	fragmented packets before reaching Suricata. However the
 	default packet size in Suricata is based on the network
 	interface MTU which leads to Suricata seeing truncated
 	packets.
 	</li>
 	<li>
 	CVE-2025-29916: Severity Moderate. Datasets declared in
 	rules have an option to specify the `hashsize` to use.
 	This size setting isn't properly limited, so the hash
 	table allocation can be large. Untrusted rules can lead to
 	large memory allocations, potentially leading to denial of
 	service due to resource starvation
 	</li>
 	<li>
 	CVE-2025-29917: Severity HIGH. The bytes setting in the
 	decode_base64 keyword is not properly limited. Due to
 	this, signatures using the keyword and setting can cause
 	large memory allocations of up to 4 GiB per thread.
 	</li>
 	<li>
 	CVE-2025-29918: Severity HIGH. A PCRE rule can be written
 	that leads to an infinite loop when negated PCRE is used.
 	Packet processing thread becomes stuck in infinite loop
 	limiting visibility and availability in inline mode.
 	</li>
 	</ul>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-29915</cvename>
       <url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-29915</url>
       <cvename>CVE-2025-29916</cvename>
       <url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-29916</url>
       <cvename>CVE-2025-29917</cvename>
       <url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-29917</url>
       <cvename>CVE-2025-29918</cvename>
       <url>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-29918</url>
     </references>
     <dates>
       <discovery>2025-03-12</discovery>
       <entry>2025-03-30</entry>
     </dates>
   </vuln>
 
   <vuln vid="7cb6642c-0c5a-11f0-8688-4ccc6adda413">
     <topic>qt6-webengine -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>qt6-pdf</name>
 	<name>qt6-webengine</name>
 	<range><lt>6.8.3</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Qt qtwebengine-chromium repo reports:</p>
 	<blockquote cite="https://code.qt.io/cgit/qt/qtwebengine-chromium.git/log/?h=122-based">
 	  <p>Backports for 11 security bugs in Chromium:</p>
 	  <ul>
 	    <li>CVE-2024-11477: 7-Zip Zstd decompression integer underflow</li>
 	    <li>CVE-2025-0762: Use after free in DevTools</li>
 	    <li>CVE-2025-0996: Inappropriate implementation in Browser UI</li>
 	    <li>CVE-2025-0998: Out of bounds memory access in V8</li>
 	    <li>CVE-2025-0999: Heap buffer overflow in V8</li>
 	    <li>CVE-2025-1006: Use after free in Network</li>
 	    <li>CVE-2025-1426: Heap buffer overflow in GPU</li>
 	    <li>CVE-2025-1918: Out of bounds read in Pdfium</li>
 	    <li>CVE-2025-1919: Out of bounds read in Media</li>
 	    <li>CVE-2025-1921: Inappropriate implementation in Media</li>
 	    <li>CVE-2025-2036: Use after free in Inspector</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-11477</cvename>
       <cvename>CVE-2025-0762</cvename>
       <cvename>CVE-2025-0996</cvename>
       <cvename>CVE-2025-0998</cvename>
       <cvename>CVE-2025-0999</cvename>
       <cvename>CVE-2025-1006</cvename>
       <cvename>CVE-2025-1426</cvename>
       <cvename>CVE-2025-1918</cvename>
       <cvename>CVE-2025-1919</cvename>
       <cvename>CVE-2025-1921</cvename>
       <cvename>CVE-2025-2036</cvename>
       <url>https://code.qt.io/cgit/qt/qtwebengine-chromium.git/log/?h=122-based</url>
     </references>
     <dates>
       <discovery>2025-02-20</discovery>
       <entry>2025-03-29</entry>
     </dates>
   </vuln>
 
   <vuln vid="01a7e1e1-d249-4dd8-9a4a-ef95b5747afb">
     <topic>electron{33,34} -- Incorrect handle provided in unspecified circumstances in Mojo</topic>
     <affects>
       <package>
 	<name>electron33</name>
 	<range><lt>33.4.8</lt></range>
       </package>
       <package>
 	<name>electron34</name>
 	<range><lt>34.4.1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Electron developers report:</p>
 	<blockquote cite="https://github.com/electron/electron/releases/tag/v33.4.8">
 	  <p>This update fixes the following vulnerability:</p>
 	  <ul>
 	    <li>Security: backported fix for CVE-2025-2783.</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-2783</cvename>
       <url>https://github.com/advisories/GHSA-hfqm-jfc6-rh2f</url>
     </references>
     <dates>
       <discovery>2025-03-27</discovery>
       <entry>2025-03-28</entry>
     </dates>
   </vuln>
 
   <vuln vid="1daa2814-0a6c-11f0-b4e4-2cf05da270f3">
     <topic>Gitlab -- Vulnerabilities</topic>
     <affects>
       <package>
 	<name>gitlab-ce</name>
 	<name>gitlab-ee</name>
 	<range><ge>17.10.0</ge><lt>17.10.1</lt></range>
 	<range><ge>17.9.0</ge><lt>17.9.3</lt></range>
 	<range><ge>12.10.0</ge><lt>17.8.6</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Gitlab reports:</p>
 	<blockquote cite="https://about.gitlab.com/releases/2025/03/26/patch-release-gitlab-17-10-1-released/">
 	  <p>Cross-site Scripting (XSS) through merge-request error messages</p>
 	  <p>Cross-site Scripting (XSS) through improper rendering of certain file types</p>
 	  <p>Admin Privileges Persists After Role is Revoked</p>
 	  <p>External user can access internal projects</p>
 	  <p>Prompt injection in Amazon Q integration may allow unauthorized actions</p>
 	  <p>Uncontrolled Resource Consumption via a maliciously crafted terraform file in merge request</p>
 	  <p>Maintainer can inject shell code in Harbor project name configuration when using helper scripts</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-2255</cvename>
       <cvename>CVE-2025-0811</cvename>
       <cvename>CVE-2025-2242</cvename>
       <cvename>CVE-2024-12619</cvename>
       <cvename>CVE-2024-10307</cvename>
       <cvename>CVE-2024-9773</cvename>
       <url>https://about.gitlab.com/releases/2025/03/26/patch-release-gitlab-17-10-1-released/</url>
     </references>
     <dates>
       <discovery>2025-03-26</discovery>
       <entry>2025-03-26</entry>
     </dates>
   </vuln>
 
   <vuln vid="964aa5da-f094-47fe-9ebd-2142f9157440">
     <topic>electron{33,34} -- Type Confusion in V8</topic>
     <affects>
       <package>
 	<name>electron33</name>
 	<range><lt>33.4.6</lt></range>
       </package>
       <package>
 	<name>electron34</name>
 	<range><lt>34.3.4</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Electron developers report:</p>
 	<blockquote cite="https://github.com/electron/electron/releases/tag/v33.4.6">
 	  <p>This update fixes the following vulnerability:</p>
 	  <ul>
 	    <li>Security: backported fix for CVE-2025-1920.</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-1920</cvename>
       <url>https://github.com/advisories/GHSA-fhwv-7gx3-h767</url>
     </references>
     <dates>
       <discovery>2025-03-20</discovery>
       <entry>2025-03-25</entry>
     </dates>
   </vuln>
 
   <vuln vid="a58fdfef-07c6-11f0-8688-4ccc6adda413">
     <topic>qt5-webengine -- Use after free in Compositing</topic>
     <affects>
       <package>
 	<name>qt5-webengine</name>
 	<range><lt>5.15.18p7</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Qt qtwebengine-chromium repo reports:</p>
 	<blockquote cite="https://code.qt.io/cgit/qt/qtwebengine-chromium.git/log/?h=87-based">
 	  <p>Backports for 1 security bug in Chromium:</p>
 	  <ul>
 	    <li>CVE-2024-12694: Use after free in Compositing</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-12694</cvename>
       <url>https://code.qt.io/cgit/qt/qtwebengine-chromium.git/log/?h=87-based</url>
     </references>
     <dates>
       <discovery>2025-02-14</discovery>
       <entry>2025-03-23</entry>
     </dates>
   </vuln>
 
   <vuln vid="26f6733d-06a9-11f0-ba0b-641c67a117d8">
     <topic>www/varnish7 -- client-side desync vulnerability</topic>
     <affects>
       <package>
 	<name>varnish7</name>
 	<range><lt>7.6.2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The Varnish Development Team reports:</p>
 	<blockquote cite="https://varnish-cache.org/security/VSV00015.html#vsv00015">
 	<p>A client-side desync vulnerability can be triggered in Varnish Cache
 	   and Varnish Enterprise. This vulnerability can be triggered under
 	   specific circumstances involving malformed HTTP/1 requests.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-30346</cvename>
       <url>https://varnish-cache.org/security/VSV00015.html#vsv00015</url>
     </references>
     <dates>
       <discovery>2024-12-17</discovery>
       <entry>2025-03-22</entry>
     </dates>
   </vuln>
 
   <vuln vid="9456d4e9-055f-11f0-85f3-a8a1599412c6">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>134.0.6998.117</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>134.0.6998.117</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2025/03/stable-channel-update-for-desktop_19.html">
 	 <p>This update includes 2 security fixes:</p>
 	 <ul>
 	    <li>[401029609] Critical CVE-2025-2476: Use after free in Lens. Reported by SungKwon Lee of Enki Whitehat on 2025-03-05</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2025-2476</cvename>
       <url>https://chromereleases.googleblog.com/2025/03/stable-channel-update-for-desktop_19.html</url>
     </references>
     <dates>
       <discovery>2025-03-19</discovery>
       <entry>2025-03-20</entry>
     </dates>
   </vuln>
 
   <vuln vid="2ac2ddc2-0051-11f0-8673-f02f7432cf97">
   <topic>php -- Multiple vulnerabilities</topic>
   <affects>
     <package>
       <name>php81</name>
       <range>
 	<lt>8.1.32</lt>
       </range>
     </package>
     <package>
       <name>php82</name>
       <range>
 	<lt>8.2.28</lt>
       </range>
     </package>
     <package>
       <name>php83</name>
       <range>
 	<lt>8.3.19</lt>
       </range>
     </package>
     <package>
       <name>php84</name>
       <range>
 	<lt>8.4.5</lt>
       </range>
     </package>
   </affects>
   <description>
     <body xmlns="http://www.w3.org/1999/xhtml">
       <p>php.net reports:</p>
       <blockquote cite="https://www.php.net/ChangeLog-8.php">
 	<ul>
 	  <li>
 	    CVE-2024-11235: Core: Fixed GHSA-rwp7-7vc6-8477 (Reference counting in php_request_shutdown causes Use-After-Free).
 	  </li>
 	  <li>
 	    CVE-2025-1219: LibXML: Fixed GHSA-p3x9-6h7p-cgfc (libxml streams use wrong `content-type` header when requesting a redirected resource).
 	  </li>
 	  <li>
 	    CVE-2025-1736: Streams: Fixed GHSA-hgf5-96fm-v528 (Stream HTTP wrapper header check might omit basic auth header).
 	  </li>
 	  <li>
 	    CVE-2025-1861: Streams: Fixed GHSA-52jp-hrpf-2jff (Stream HTTP wrapper truncate redirect location to 1024 bytes).
 	  </li>
 	  <li>
 	    CVE-2025-1734: Streams: Fixed GHSA-pcmh-g36c-qc44 (Streams HTTP wrapper does not fail for headers without colon).
 	  </li>
 	  <li>
 	    CVE-2025-1217: Streams: Fixed GHSA-v8xr-gpvj-cx9g (Header parser of `http` stream wrapper does not handle folded headers).
 	  </li>
 	</ul>
       </blockquote>
     </body>
   </description>
   <references>
     <cvename>CVE-2024-11235</cvename>
     <cvename>CVE-2025-1219</cvename>
     <cvename>CVE-2025-1736</cvename>
     <cvename>CVE-2025-1861</cvename>
     <cvename>CVE-2025-1734</cvename>
     <cvename>CVE-2025-1217</cvename>
     <url>https://www.php.net/ChangeLog-8.php</url>
   </references>
   <dates>
     <discovery>2025-03-13</discovery>
     <entry>2025-03-13</entry>
   </dates>
   </vuln>
 
   <vuln vid="0b43fac4-005d-11f0-a540-6cc21735f730">
     <topic>shibboleth-sp -- Parameter manipulation allows the forging of signed SAML messages</topic>
     <affects>
       <package>
 	<name>opensaml</name>
 	<range><lt>3.3.1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The Shibboleth Project reports:</p>
 	<blockquote cite="https://shibboleth.net/community/advisories/secadv_20250313.txt">
 	  <p>
 	    An updated version of the OpenSAML C++ library is available
 	    which corrects a parameter manipulation vulnerability when using
 	    SAML bindings that rely on non-XML signatures. The Shibboleth
 	    Service Provider is impacted by this issue, and it manifests as
 	    a critical security issue in that context.
 	  </p>
 	  <p>
 	    Parameter manipulation allows the forging of signed SAML messages
 	  </p>
 	  <p>
 	    A number of vulnerabilities in the OpenSAML library used by the
 	    Shibboleth Service Provider allowed for creative manipulation of
 	    parameters combined with reuse of the contents of older requests
 	    to fool the library's signature verification of non-XML based
 	    signed messages.
 	  </p>
 	  <p>
 	    Most uses of that feature involve very low or
 	    low impact use cases without critical security implications;
 	    however, there are two scenarios that are much more critical,
 	    one affecting the SP and one affecting some implementers who
 	    have implemented their own code on top of our OpenSAML library
 	    and done so improperly.
 	  </p>
 	  <p>
 	    The SP's support for the HTTP-POST-SimpleSign SAML binding for
 	    Single Sign-On responses is its critical vulnerability, and it
 	    is enabled by default (regardless of what one's published SAML
 	    metadata may advertise).
 	  </p>
 	  <p>
 	    The other critical case involves a mistake that
 	    does *not* impact the Shibboleth SP, allowing SSO to occur over
 	    the HTTP-Redirect binding contrary to the plain language of the
 	    SAML Browser SSO profile. The SP does not support this, but
 	    other implementers may have done so.
 	  </p>
 	  <p>
 	    Prior to updating, it is possible to mitigate the POST-SimpleSign
 	    vulnerability by editing the protocols.xml configuration file and
 	    removing this line:
 	    <code>&lt;Binding id="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST-SimpleSign"
 		path="/SAML2/POST-SimpleSign" /&gt;</code>
 	  </p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <url>https://shibboleth.net/community/advisories/secadv_20250313.txt</url>
     </references>
     <dates>
       <discovery>2025-03-13</discovery>
       <entry>2025-03-13</entry>
     </dates>
   </vuln>
 
   <vuln vid="a435609c-ffd5-11ef-b4e4-2cf05da270f3">
     <topic>Gitlab -- Vulnerabilities</topic>
     <affects>
       <package>
 	<name>gitlab-ce</name>
 	<name>gitlab-ee</name>
 	<range><ge>17.9.0</ge><lt>17.9.2</lt></range>
 	<range><ge>17.8.0</ge><lt>17.8.5</lt></range>
 	<range><ge>11.5</ge><lt>17.7.7</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Gitlab reports:</p>
 	<blockquote cite="https://about.gitlab.com/releases/2025/03/12/patch-release-gitlab-17-9-2-released/">
 	  <p>CVE-2025-25291 and CVE-2025-25292 (third party gem ruby-saml)</p>
 	  <p>CVE-2025-27407 (third party gem graphql)</p>
 	  <p>Denial of Service Due to Inefficient Processing of Untrusted Input</p>
 	  <p>Credentials disclosed when repository mirroring fails</p>
 	  <p>Denial of Service Vulnerability in GitLab Approval Rules due to Unbounded Field</p>
 	  <p>Internal Notes in Merge Requests Are Emailed to Non-Members Upon Review Submission</p>
 	  <p>Maintainer can inject shell code in Google integrations</p>
 	  <p>Guest with custom Admin group member permissions can approve the users invitation despite user caps</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-25291</cvename>
       <cvename>CVE-2025-25292</cvename>
       <cvename>CVE-2025-27407</cvename>
       <cvename>CVE-2024-13054</cvename>
       <cvename>CVE-2024-12380</cvename>
       <cvename>CVE-2025-1257</cvename>
       <cvename>CVE-2025-0652</cvename>
       <cvename>CVE-2024-8402</cvename>
       <cvename>CVE-2024-7296</cvename>
       <url>https://about.gitlab.com/releases/2025/03/12/patch-release-gitlab-17-9-2-released/</url>
     </references>
     <dates>
       <discovery>2025-03-12</discovery>
       <entry>2025-03-13</entry>
     </dates>
   </vuln>
 
   <vuln vid="9cf03c96-ffa5-11ef-bb15-002590af0794">
     <topic>vim -- potential data loss with zip.vim and specially crafted zip files</topic>
     <affects>
       <package>
 	<name>vim</name>
 	<range><lt>9.1.1198</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Vim reports:</p>
 	<blockquote cite="https://github.com/vim/vim/security/advisories/GHSA-693p-m996-3rmf">
 	  <p>See https://github.com/vim/vim/security/advisories/GHSA-693p-m996-3rmf</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-29768</cvename>
       <url>https://github.com/vim/vim/security/advisories/GHSA-693p-m996-3rmf</url>
     </references>
     <dates>
       <discovery>2025-03-12</discovery>
       <entry>2025-03-12</entry>
     </dates>
   </vuln>
 
   <vuln vid="a02a6d94-fe53-11ef-85f3-a8a1599412c6">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>134.0.6998.88</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>134.0.6998.88</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2025/03/stable-channel-update-for-desktop_10.html">
 	 <p>This update includes 5 security fixes:</p>
 	 <ul>
 	    <li>[398065918] High CVE-2025-1920: Type Confusion in V8. Reported by Excello s.r.o. on 2025-02-21</li>
 	    <li>[400052777] High CVE-2025-2135: Type Confusion in V8. Reported by Zhenghang Xiao (@Kipreyyy) on 2025-03-02</li>
 	    <li>[401059730] High CVE-TBD: Out of bounds write in GPU. Reported on 2025-03-05</li>
 	    <li>[395032416] Medium CVE-2025-2136: Use after free in Inspector. Reported by Sakana.S on 2025-02-10</li>
 	    <li>[398999390] Medium CVE-2025-2137: Out of bounds read in V8. Reported by zeroxiaobai@ on 2025-02-25</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2025-1920</cvename>
       <cvename>CVE-2025-2135</cvename>
       <cvename>CVE-2025-2136</cvename>
       <cvename>CVE-2025-2137</cvename>
       <url>https://chromereleases.googleblog.com/2025/03/stable-channel-update-for-desktop_10.html</url>
     </references>
     <dates>
       <discovery>2025-03-10</discovery>
       <entry>2025-03-11</entry>
     </dates>
   </vuln>
 
   <vuln vid="a86f9189-fdd9-11ef-91ff-b42e991fc52e">
     <topic>libreoffice -- Macro URL arbitrary script execution</topic>
     <affects>
       <package>
 	<name>libreoffice</name>
 	<range><ge>24.8</ge><lt>24.8.5</lt></range>
 	<range><ge>25.2</ge><lt>25.2.1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@documentfoundation.org reports:</p>
 	<blockquote cite="https://www.libreoffice.org/about-us/security/advisories/cve-2025-1080">
 	  <p>LibreOffice supports Office URI Schemes to enable browser integration
 	of LibreOffice with MS SharePoint server.  An additional scheme
 	&apos;vnd.libreoffice.command&apos; specific to LibreOffice was
 	added.  In the affected versions of LibreOffice a link in a browser
 	using that scheme could be constructed with an embedded inner URL
 	that when passed to LibreOffice could call internal macros with
 	arbitrary arguments.  This issue affects LibreOffice: from 24.8
 	before &lt; 24.8.5, from 25.2 before &lt; 25.2.1.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-1080</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-1080</url>
     </references>
     <dates>
       <discovery>2025-03-04</discovery>
       <entry>2025-03-10</entry>
     </dates>
   </vuln>
 
   <vuln vid="2ec7816d-fdb7-11ef-91ff-b42e991fc52e">
     <topic>vim -- Improper Input Validation in Vim</topic>
     <affects>
       <package>
 	<name>vim</name>
 	<range><lt>9.1.1164</lt></range>
       </package>
       <package>
 	<name>vim-gtk2</name>
 	<range><lt>9.1.1164</lt></range>
       </package>
       <package>
 	<name>vim-gtk3</name>
 	<range><lt>9.1.1164</lt></range>
       </package>
       <package>
 	<name>vim-motif</name>
 	<range><lt>9.1.1164</lt></range>
       </package>
       <package>
 	<name>vim-tiny</name>
 	<range><lt>9.1.1164</lt></range>
       </package>
       <package>
 	<name>vim-x11</name>
 	<range><lt>9.1.1164</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security-advisories@github.com reports:</p>
 	<blockquote cite="https://github.com/vim/vim/commit/129a8446d23cd9cb4445fcfea259cba5e0487d29">
 	  <p>Vim is distributed with the tar.vim plugin, that allows
 	  easy editing and viewing of (compressed or uncompressed) tar
 	  files.  Starting with 9.1.0858, the tar.vim plugin uses the
 	  &quot;:read&quot; ex command line to append below the
 	  cursor position, however the is not sanitized and is taken
 	  literally from the tar archive.  This allows to execute
 	  shellcommands via special crafted tar archives. Whether
 	  this really happens, depends on the shell being used
 	  (&apos;shell&apos; option, which is set using $SHELL).
 	  </p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-27423</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-27423</url>
     </references>
     <dates>
       <discovery>2025-03-03</discovery>
       <entry>2025-03-10</entry>
     </dates>
   </vuln>
 
   <vuln vid="6ba9e26e-c9c6-49f7-ae43-47e5864f0b66">
     <topic>electron33 -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>electron33</name>
 	<range><lt>33.4.3</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Electron develpers report:</p>
 	<blockquote cite="https://github.com/electron/electron/releases/tag/v33.4.3">
 	  <p>This update fixes the following vulnerabilities:</p>
 	  <ul>
 	    <li>Security: backported fix for CVE-2025-0445.</li>
 	    <li>Security: backported fix for CVE-2025-0995.</li>
 	    <li>Security: backported fix for CVE-2025-0998.</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-0445</cvename>
       <url>https://github.com/advisories/GHSA-q4fq-38gr-ccp3</url>
       <cvename>CVE-2025-0995</cvename>
       <url>https://github.com/advisories/GHSA-377p-4737-hx6m</url>
       <cvename>CVE-2025-0998</cvename>
       <url>https://github.com/advisories/GHSA-4v9x-qxmv-4h58</url>
     </references>
     <dates>
       <discovery>2025-03-06</discovery>
       <entry>2025-03-08</entry>
     </dates>
   </vuln>
 
   <vuln vid="6e27040b-61b7-4989-9471-dfb10c3cd76e">
     <topic>electron32 -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>electron32</name>
 	<range><lt>32.3.3</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Electron developers report:</p>
 	<blockquote cite="https://github.com/electron/electron/releases/tag/v32.3.3">
 	  <p>This update fixes the following vulnerabilities:</p>
 	  <ul>
 	    <li>Security: backported fix for CVE-2025-0445.</li>
 	    <li>Security: backported fix for CVE-2025-0998.</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-0445</cvename>
       <url>https://github.com/advisories/GHSA-q4fq-38gr-ccp3</url>
       <cvename>CVE-2025-0998</cvename>
       <url>https://github.com/advisories/GHSA-4v9x-qxmv-4h58</url>
     </references>
     <dates>
       <discovery>2025-03-03</discovery>
       <entry>2025-03-07</entry>
     </dates>
   </vuln>
 
   <vuln vid="3299cbfd-fa6e-11ef-929d-b0416f0c4c67">
     <topic>Jinja2 -- Sandbox breakout through attr filter selecting format method</topic>
     <affects>
       <package>
 	<name>py38-Jinja2</name>
 	<name>py39-Jinja2</name>
 	<name>py310-Jinja2</name>
 	<name>py311-Jinja2</name>
 	<range><lt>3.1.6</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security-advisories@github.com reports:</p>
 	<blockquote cite="https://github.com/pallets/jinja/commit/90457bbf33b8662926ae65cdde4c4c32e756e403">
 	  <p>Jinja is an extensible templating engine.  Prior to 3.1.6, an
 	oversight in how the Jinja sandboxed environment interacts with the
 	|attr filter allows an attacker that controls the content of a
 	template to execute arbitrary Python code.  To exploit the
 	vulnerability, an attacker needs to control the content of a template.
 	Whether that is the case depends on the type of application using
 	Jinja.  This vulnerability impacts users of applications which
 	execute untrusted templates.  Jinja&apos;s sandbox does catch calls
 	to str.format and ensures they don&apos;t escape the sandbox.
 	However, it&apos;s possible to use the |attr filter to get a reference
 	to a string&apos;s plain format method, bypassing the sandbox.
 	After the fix, the |attr filter no longer bypasses the environment&apos;s
 	attribute lookup.  This vulnerability is fixed in 3.1.6.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-27516</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-27516</url>
     </references>
     <dates>
       <discovery>2025-03-05</discovery>
       <entry>2025-03-06</entry>
     </dates>
   </vuln>
 
   <vuln vid="f4297478-fa62-11ef-b597-001fc69cd6dc">
     <topic>xorg server -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>xorg-server</name>
 	<name>xephyr</name>
 	<name>xorg-vfbserver</name>
 	<range><lt>21.1.16,1</lt></range>
       </package>
       <package>
 	<name>xorg-nextserver</name>
 	<range><lt>21.1.16,2</lt></range>
       </package>
       <package>
 	<name>xwayland</name>
 	<range><lt>24.1.6</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The X.Org project reports:</p>
 	<blockquote cite="https://lists.x.org/archives/xorg-announce/2025-February/003584.html">
 	  <ul>
 	    <li>
 	      CVE-2025-26594: Use-after-free of the root cursor
 
 	      <p>The root cursor is referenced in the xserver as a global variable. If
 	      a client manages to free the root cursor, the internal reference points
 	      to freed memory and causes a use-after-free.</p>
 	    </li>
 	    <li>
 	      CVE-2025-26595: Buffer overflow in XkbVModMaskText()
 
 	      <p>The code in XkbVModMaskText() allocates a fixed sized buffer on the
 	      stack and copies the names of the virtual modifiers to that buffer.
 	      The code however fails to check the bounds of the buffer correctly and
 	      would copy the data regardless of the size, which may lead to a buffer
 	      overflow.</p>
 	    </li>
 	    <li>
 	      CVE-2025-26596: Heap overflow in XkbWriteKeySyms()
 
 	      <p>The computation of the length in XkbSizeKeySyms() differs from what is
 	      actually written in XkbWriteKeySyms(), which may lead to a heap based
 	      buffer overflow.</p>
 	    </li>
 	    <li>
 	      CVE-2025-26597: Buffer overflow in XkbChangeTypesOfKey()
 
 	      <p>If XkbChangeTypesOfKey() is called with 0 group, it will resize the key
 	      symbols table to 0 but leave the key actions unchanged.
 	      If later, the same function is called with a non-zero value of groups,
 	      this will cause a buffer overflow because the key actions are of the wrong
 	      size.</p>
 	    </li>
 	    <li>
 	      CVE-2025-26598: Out-of-bounds write in CreatePointerBarrierClient()
 
 	      <p>The function GetBarrierDevice() searches for the pointer device based on
 	      its device id and returns the matching value, or supposedly NULL if no
 	      match was found.
 	      However the code will return the last element of the list if no matching
 	      device id was found which can lead to out of bounds memory access.</p>
 	    </li>
 	    <li>
 	      CVE-2025-26599: Use of uninitialized pointer in compRedirectWindow()
 
 	      <p>The function compCheckRedirect() may fail if it cannot allocate the backing
 	      pixmap. In that case, compRedirectWindow() will return a BadAlloc error
 	      without the validation of the window tree marked just before, which leaves
 	      the validate data partly initialized, and the use of an uninitialized pointer
 	      later.</p>
 	    </li>
 	    <li>
 	      CVE-2025-26600: Use-after-free in PlayReleasedEvents()
 
 	      <p>When a device is removed while still frozen, the events queued for that
 	      device remain while the device itself is freed and replaying the events
 	      will cause a use after free.</p>
 	    </li>
 	    <li>
 	      CVE-2025-26601: Use-after-free in SyncInitTrigger()
 
 	      <p>When changing an alarm, the values of the change mask are evaluated one
 	      after the other, changing the trigger values as requested and eventually,
 	      SyncInitTrigger() is called.
 	      If one of the changes triggers an error, the function will return early,
 	      not adding the new sync object.
 	      This can be used to cause a use after free when the alarm eventually
 	      triggers.</p>
 	    </li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-26594</cvename>
       <cvename>CVE-2025-26595</cvename>
       <cvename>CVE-2025-26596</cvename>
       <cvename>CVE-2025-26597</cvename>
       <cvename>CVE-2025-26598</cvename>
       <cvename>CVE-2025-26599</cvename>
       <cvename>CVE-2025-26600</cvename>
       <cvename>CVE-2025-26601</cvename>
       <url>https://lists.x.org/archives/xorg-announce/2025-February/003584.html</url>
     </references>
     <dates>
       <discovery>2025-02-25</discovery>
       <entry>2025-03-06</entry>
     </dates>
   </vuln>
 
   <vuln vid="d8bd20ae-fa48-11ef-ab7a-ace2d30de67a">
     <topic>caldera -- Remote Code Execution</topic>
     <affects>
       <package>
 	<name>caldera</name>
 	<range><lt>5.2.0</lt></range>
       </package>
       <package>
 	<name>caldera4</name>
 	<range><le>4.2.0</le></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>MITRE Caldera contributor report:</p>
 	<blockquote cite="https://github.com/mitre/caldera/pull/3129">
 	  <p>In MITRE Caldera through 4.2.0 and 5.0.0 before 35bc06e,
  a Remote Code Execution (RCE) vulnerability was found in the dynamic
  agent (implant) compilation functionality of the server. This allows
  remote attackers to execute arbitrary code on the server that Caldera
  is running on via a crafted web request to the Caldera server API used
  for compiling and downloading of Caldera's Sandcat or Manx agent
  (implants). This web request can use the gcc -extldflags linker flag
  with sub-commands.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-27364</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-27364</url>
     </references>
     <dates>
       <discovery>2025-02-16</discovery>
       <entry>2025-03-06</entry>
     </dates>
   </vuln>
 
   <vuln vid="cb98d018-f9f5-11ef-a398-00e081b7aa2d">
     <topic>jenkins -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>jenkins</name>
 	<range><lt>2.500</lt></range>
       </package>
       <package>
 	<name>jenkins-lts</name>
 	<range><lt>2.492.2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Jenkins Security Advisory:</p>
 	<blockquote cite="https://www.jenkins.io/security/advisory/2025-03-05/">
 	  <h1>Description</h1>
 	  <h5>(Medium) SECURITY-3495 / CVE-2025-27622</h5>
 	  <p>Encrypted values of secrets stored in agent configuration revealed to users with Agent/Extended Read permission</p>
 	  <h1>Description</h1>
 	  <h5>(Medium) SECURITY-3496 / CVE-2025-27623</h5>
 	  <p>Encrypted values of secrets stored in view configuration revealed to users with View/Read permission</p>
 	  <h1>Description</h1>
 	  <h5>(Medium) SECURITY-3498 / CVE-2025-27624</h5>
 	  <p>CSRF vulnerability</p>
 	  <h1>Description</h1>
 	  <h5>(Medium) SECURITY-3501 / CVE-2025-27625</h5>
 	  <p>Open redirect vulnerability</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-27622</cvename>
       <cvename>CVE-2025-27623</cvename>
       <cvename>CVE-2025-27624</cvename>
       <cvename>CVE-2025-27625</cvename>
       <url>https://www.jenkins.io/security/advisory/2025-03-05/</url>
     </references>
     <dates>
       <discovery>2025-03-05</discovery>
       <entry>2025-03-05</entry>
     </dates>
   </vuln>
 
   <vuln vid="475d1968-f99d-11ef-b382-b0416f0c4c67">
     <topic>Spotipy -- Spotipy&apos;s cache file, containing spotify auth token, is created with overly broad permissions</topic>
     <affects>
       <package>
 	<name>py38-spotipy</name>
 	<name>py39-spotipy</name>
 	<name>py310-spotipy</name>
 	<name>py311-spotipy</name>
 	<range><lt>2.25.1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security-advisories@github.com reports:</p>
 	<blockquote cite="https://github.com/spotipy-dev/spotipy/blob/master/spotipy/cache_handler.py#L93-L98">
 	  <p>Spotipy is a lightweight Python library for the Spotify Web API.
 	The `CacheHandler` class creates a cache file to store the auth
 	token.  Prior to version 2.25.1, the file created has `rw-r--r--`
 	(644) permissions by default, when it could be locked down to
 	`rw-------` (600) permissions.  This leads to overly broad exposure
 	of the spotify auth token.  If this token can be read by an attacker
 	(another user on the machine, or a process running as another user),
 	it can be used to perform administrative actions on the Spotify
 	account, depending on the scope granted to the token.  Version
 	2.25.1 tightens the cache file permissions.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-27154</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-27154</url>
     </references>
     <dates>
       <discovery>2025-02-27</discovery>
       <entry>2025-03-05</entry>
     </dates>
   </vuln>
 
   <vuln vid="9c62d3f0-f997-11ef-85f3-a8a1599412c6">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>134.0.6998.35</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>134.0.6998.35</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2025/03/stable-channel-update-for-desktop.html">
 	 <p>This update includes 14 security fixes:</p>
 	 <ul>
 	    <li>[397731718] High CVE-2025-1914: Out of bounds read in V8. Reported by Zhenghang Xiao (@Kipreyyy) and Nan Wang (@eternalsakura13) on 2025-02-20</li>
 	    <li>[391114799] Medium CVE-2025-1915: Improper Limitation of a Pathname to a Restricted Directory in DevTools. Reported by Topi Lassila on 2025-01-20</li>
 	    <li>[376493203] Medium CVE-2025-1916: Use after free in Profiles. Reported by parkminchan, SSD Labs Korea on 2024-10-31</li>
 	    <li>[329476341] Medium CVE-2025-1917: Inappropriate Implementation in Browser UI. Reported by Khalil Zhani on 2024-03-14</li>
 	    <li>[388557904] Medium CVE-2025-1918: Out of bounds read in PDFium. Reported by asnine on 2025-01-09</li>
 	    <li>[392375312] Medium CVE-2025-1919: Out of bounds read in Media. Reported by @Bl1nnnk and @Pisanbao on 2025-01-26</li>
 	    <li>[387583503] Medium CVE-2025-1921: Inappropriate Implementation in Media Stream. Reported by Kaiido on 2025-01-04</li>
 	    <li>[384033062] Low CVE-2025-1922: Inappropriate Implementation in Selection. Reported by Alesandro Ortiz on 2024-12-14</li>
 	    <li>[382540635] Low CVE-2025-1923: Inappropriate Implementation in Permission Prompts. Reported by Khalil Zhani on 2024-12-06</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2025-1914</cvename>
       <cvename>CVE-2025-1915</cvename>
       <cvename>CVE-2025-1916</cvename>
       <cvename>CVE-2025-1917</cvename>
       <cvename>CVE-2025-1918</cvename>
       <cvename>CVE-2025-1919</cvename>
       <cvename>CVE-2025-1921</cvename>
       <cvename>CVE-2025-1922</cvename>
       <cvename>CVE-2025-1923</cvename>
       <url>https://chromereleases.googleblog.com/2025/03/stable-channel-update-for-desktop.html</url>
     </references>
     <dates>
       <discovery>2025-03-04</discovery>
       <entry>2025-03-05</entry>
     </dates>
   </vuln>
 
   <vuln vid="f4f3e001-402b-4d6d-8efa-ab11fcf8de2b">
     <topic>electron{32,33} -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>electron32</name>
 	<range><lt>32.3.2</lt></range>
       </package>
       <package>
 	<name>electron33</name>
 	<range><lt>33.4.2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Electron developers report:</p>
 	<blockquote cite="https://github.com/electron/electron/releases/tag/v32.3.2">
 	  <p>This update fixes the following vulnerabilities:</p>
 	  <ul>
 	    <li>Security: backported fix for CVE-2025-0611.</li>
 	    <li>Security: backported fix for CVE-2025-0612.</li>
 	    <li>Security: backported fix for CVE-2025-0999.</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-0611</cvename>
       <url>https://github.com/advisories/GHSA-83vc-v46q-mv3w</url>
       <cvename>CVE-2025-0612</cvename>
       <url>https://github.com/advisories/GHSA-c6xg-jh94-mf2w</url>
       <cvename>CVE-2025-0999</cvename>
       <url>https://github.com/advisories/GHSA-f2jv-hxph-r5wm</url>
     </references>
     <dates>
       <discovery>2025-02-27</discovery>
       <entry>2025-03-04</entry>
     </dates>
   </vuln>
 
   <vuln vid="6af5e3a3-f85a-11ef-95b9-589cfc10a551">
     <topic>unit -- potential security issue</topic>
     <affects>
       <package>
 	<name>unit</name>
 	<name>unit-java</name>
 	<range><ge>1.11.0</ge><lt>1.34.2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>SO-AND-SO reports:</p>
 	<blockquote cite="https://mailman.nginx.org/pipermail/unit/2025-March/QVYLJKLBIDWOJ7OLYGT27VUWH7RGBRQM.html">
 	  <p>Unit 1.34.2 fixes two issues in the Java language module websocket code.</p>
 	    <ol>
 	    <li>It addresses a potential security issue where we could get a negative
 	    payload length that could cause the Java language module process(es) to
 	    enter an infinite loop and consume excess CPU. This was a bug carried
 	    over from the initial Java websocket code import. It has been re-issued
 	    a CVE number (CVE-2025-1695).</li>
 	    <li>It addresses an issue whereby decoded payload lengths would be limited
 	    to 32 bits.</li>
 	    </ol>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-1695</cvename>
       <url>https://mailman.nginx.org/pipermail/unit/2025-March/QVYLJKLBIDWOJ7OLYGT27VUWH7RGBRQM.html</url>
     </references>
     <dates>
       <discovery>2025-03-03</discovery>
       <entry>2025-03-03</entry>
     </dates>
   </vuln>
 
   <vuln vid="398d1ec1-f7e6-11ef-bb15-002590af0794">
     <topic>vim -- Potential code execution</topic>
     <affects>
       <package>
 	<name>vim</name>
 	<name>vim-gtk2</name>
 	<name>vim-gtk3</name>
 	<name>vim-motif</name>
 	<name>vim-x11</name>
 	<name>vim-tiny</name>
 	<range><lt>9.1.1164</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>vim reports:</p>
 	<blockquote cite="https://github.com/vim/vim/security/advisories/GHSA-wfmf-8626-q3r3">
 	  <h1>Summary</h1>
 	  <p>Potential code execution with tar.vim and special crafted tar files</p>
 	  <h1>Description</h1>
 	  <p>Vim is distributed with the tar.vim plugin, that allows easy
 	  editing and viewing of (compressed or uncompressed) tar files.</p>
 	  <p>Since commit 129a844 (Nov 11, 2024 runtime(tar): Update tar.vim to
 	  support permissions), the tar.vim plugin uses the ":read " ex command
 	  line to append below the cursor position, however the is not sanitized
 	  and is taken literaly from the tar archive. This allows to execute
 	  shell commands via special crafted tar archives. Whether this really
 	  happens, depends on the shell being used ('shell' option, which is set
 	  using $SHELL).</p>
 	  <h1>Impact</h1>
 	  <p>Impact is high but a user must be convinced to edit such a file
 	  using Vim which will reveal the filename, so a careful user may suspect
 	  some strange things going on.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <url>https://github.com/vim/vim/security/advisories/GHSA-wfmf-8626-q3r3</url>
     </references>
     <dates>
       <discovery>2025-03-02</discovery>
       <entry>2025-03-02</entry>
     </dates>
   </vuln>
 
   <vuln vid="8fb9101e-f58a-11ef-b4e4-2cf05da270f3">
     <topic>Gitlab -- Vulnerabilities</topic>
     <affects>
       <package>
 	<name>gitlab-ce</name>
 	<name>gitlab-ee</name>
 	<range><ge>17.9.0</ge><lt>17.9.1</lt></range>
 	<range><ge>17.8.0</ge><lt>17.8.4</lt></range>
 	<range><ge>15.10.0</ge><lt>17.7.6</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Gitlab reports:</p>
 	<blockquote cite="https://about.gitlab.com/releases/2025/02/26/patch-release-gitlab-17-9-1-released/">
 	  <p>XSS in k8s proxy endpoint</p>
 	  <p>XSS Maven Dependency Proxy</p>
 	  <p>HTML injection leads to XSS on self hosted instances</p>
 	  <p>Improper Authorisation Check Allows Guest User to Read Security Policy</p>
 	  <p>Planner role can read code review analytics in private projects</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-0475</cvename>
       <cvename>CVE-2025-0555</cvename>
       <cvename>CVE-2024-8186</cvename>
       <cvename>CVE-2024-10925</cvename>
       <cvename>CVE-2025-0307</cvename>
       <url>https://about.gitlab.com/releases/2025/02/26/patch-release-gitlab-17-9-1-released/</url>
     </references>
     <dates>
       <discovery>2025-02-26</discovery>
       <entry>2025-02-28</entry>
     </dates>
   </vuln>
 
   <vuln vid="a4cb7f9b-f506-11ef-85f3-a8a1599412c6">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>133.0.6943.141</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>133.0.6943.141</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2025/02/stable-channel-update-for-desktop_25.html">
 	 <p>This update includes 1 security fix.</p>
        </blockquote>
       </body>
     </description>
     <references>
       <url>https://chromereleases.googleblog.com/2025/02/stable-channel-update-for-desktop_25.html</url>
     </references>
     <dates>
       <discovery>2025-02-25</discovery>
       <entry>2025-02-27</entry>
     </dates>
   </vuln>
 
   <vuln vid="6ae77556-f31d-11ef-a695-4ccc6adda413">
     <topic>exiv2 -- Use after free in TiffSubIfd</topic>
     <affects>
       <package>
 	<name>exiv2</name>
 	<range><ge>0.28.0</ge><lt>0.28.5</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Kevin Backhouse reports:</p>
 	<blockquote cite="https://github.com/Exiv2/exiv2/security/advisories/GHSA-38h4-fx85-qcx7">
 	  <p>A heap buffer overflow was found in Exiv2 versions v0.28.0 to v0.28.4.
 	  Versions prior to v0.28.0, such as v0.27.7, are not affected. Exiv2 is a
 	  command-line utility and C++ library for reading, writing, deleting, and
 	  modifying the metadata of image files. The heap overflow is triggered when
 	  Exiv2 is used to write metadata into a crafted image file. An attacker
 	  could potentially exploit the vulnerability to gain code execution, if
 	  they can trick the victim into running Exiv2 on a crafted image file.</p>
 	  <p>Note that this bug is only triggered when writing the metadata, which
 	  is a less frequently used Exiv2 operation than reading the metadata. For
 	  example, to trigger the bug in the Exiv2 command-line application, you
 	  need to add an extra command-line argument such as fixiso.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-26623</cvename>
       <url>https://github.com/Exiv2/exiv2/security/advisories/GHSA-38h4-fx85-qcx7</url>
     </references>
     <dates>
       <discovery>2025-02-18</discovery>
       <entry>2025-02-25</entry>
     </dates>
   </vuln>
 
   <vuln vid="e60e538f-e795-4a00-b475-cc85a7546e00">
     <topic>Emacs -- Arbitrary code execution vulnerability</topic>
     <affects>
       <package>
 	<name>emacs</name>
 	<name>emacs-canna</name>
 	<name>emacs-nox</name>
 	<name>emacs-wayland</name>
 	<range><lt>30.1,3</lt></range>
       </package>
       <package>
 	<name>emacs-devel</name>
 	<name>emacs-devel-nox</name>
 	<range><lt>30.0.50.20240115,3</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	  <h1>Problem Description</h1>
 	  <p>A shell injection vulnerability exists in GNU Emacs due to improper
 	  handling of custom man URI schemes.</p>
 	  <h1>Impact</h1>
 	  <p>Initially considered low severity, as it required user interaction with
 	  local files, it was later discovered that an attacker could exploit this
 	  vulnerability by tricking a user into visiting a specially crafted
 	  website or an HTTP URL with a redirect, leading to arbitrary shell
 	  command execution without further user action.</p>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-1244</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-1244</url>
     </references>
     <dates>
       <discovery>2025-02-11</discovery>
       <entry>2025-02-24</entry>
       <modified>2025-02-25</modified>
     </dates>
   </vuln>
 
   <vuln vid="7ba6c085-1590-491a-98ce-5452646b196f">
     <topic>Emacs -- Shell injection vulnerability</topic>
     <affects>
       <package>
 	<name>emacs</name>
 	<name>emacs-canna</name>
 	<name>emacs-nox</name>
 	<name>emacs-wayland</name>
 	<range><lt>30.1,3</lt></range>
       </package>
       <package>
 	<name>emacs-devel</name>
 	<name>emacs-devel-nox</name>
 	<range><lt>31.0.50.20250101,3</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	  <h1>Problem Description:</h1>
 	  <p>An Emacs user who chooses to invoke elisp-completion-at-point (for
 	  code completion) on untrusted Emacs Lisp source code can trigger unsafe
 	  Lisp macro expansion that allows attackers to execute arbitrary code.
 	  This unsafe expansion also occurs if a user chooses to enable on-the-fly
 	  diagnosis that byte compiles untrusted Emacs Lisp source code.</p>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-53920</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-53920</url>
     </references>
     <dates>
       <discovery>2024-11-27</discovery>
       <entry>2025-02-24</entry>
     </dates>
   </vuln>
 
   <vuln vid="07c34df5-f299-11ef-a441-b42e991fc52e">
     <topic>exim -- SQL injection</topic>
     <affects>
       <package>
 	<name>exim</name>
 	<range><lt>4.98.1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>cve@mitre.org reports:</p>
 	<blockquote cite="https://bugzilla.suse.com/show_bug.cgi?id=1237424">
 	  <p>Exim 4.98 before 4.98.1, when SQLite hints and ETRN serialization
 	are used, allows remote SQL injection.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-26794</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-26794</url>
     </references>
     <dates>
       <discovery>2025-02-21</discovery>
       <entry>2025-02-24</entry>
     </dates>
   </vuln>
 
   <vuln vid="a8f1ee74-f267-11ef-87ba-002590c1f29c">
     <topic>FreeBSD -- Multiple vulnerabilities in OpenSSH</topic>
     <affects>
       <package>
 	<name>FreeBSD</name>
 	<range><ge>14.2</ge><lt>14.2_2</lt></range>
 	<range><ge>14.1</ge><lt>14.1_8</lt></range>
 	<range><ge>13.4</ge><lt>13.4_4</lt></range>
       </package>
       <package>
 	<name>openssh-portable</name>
 	<range><lt>9.9.p2_1,1</lt></range>
       </package>
       <package>
 	<name>openssh-portable-hpn</name>
 	<range><lt>9.9.p2_1,1</lt></range>
       </package>
       <package>
 	<name>openssh-portable-gssapi</name>
 	<range><lt>9.9.p2_1,1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<h1>Problem Description:</h1>
 	<p>OpenSSH client host verification error (CVE-2025-26465)</p>
 	<p>ssh(1) contains a logic error that allows an on-path attacker to
 	impersonate any server during certain conditions when the
 	VerifyHostKeyDNS option is enabled.</p>
 	<p>OpenSSH server denial of service (CVE-2025-26466)</p>
 	<p>The OpenSSH client and server are both vulnerable to a memory/CPU
 	denial of service while handling SSH2_MSG_PING packets.</p>
 	<h1>Impact:</h1>
 	<p>OpenSSH client host verification error (CVE-2025-26465)</p>
 	<p>Under specific circumstances, a machine-in-the-middle may impersonate
 	any server when the client has the VerifyHostKeyDNS option enabled.</p>
 	<p>OpenSSH server denial of service (CVE-2025-26466)</p>
 	<p>During the processing of SSH2_MSG_PING packets, a server may be
 	subject to a memory/CPU denial of service.</p>
       </body>
     </description>
     <references>
       <cvename>CVE-2025-26465</cvename>
       <cvename>CVE-2025-26466</cvename>
       <freebsdsa>SA-25:05.openssh</freebsdsa>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-26465</url>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-26466</url>
     </references>
     <dates>
       <discovery>2025-02-21</discovery>
       <entry>2025-02-24</entry>
       <modified>2025-03-08</modified>
     </dates>
   </vuln>
 
   <vuln vid="2a3be628-ef6e-11ef-85f3-a8a1599412c6">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>133.0.6943.126</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>133.0.6943.126</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2025/02/stable-channel-update-for-desktop_18.html">
 	 <p>This update includes 3 security fixes:</p>
 	 <ul>
 	    <li>[394350433] High CVE-2025-0999: Heap buffer overflow in V8. Reported by Seunghyun Lee (@0x10n) on 2025-02-04</li>
 	    <li>[383465163] High CVE-2025-1426: Heap buffer overflow in GPU. Reported by un3xploitable and GF on 2024-12-11</li>
 	    <li>[390590778] Medium CVE-2025-1006: Use after free in Network. Reported by Tal Keren, Sam Agranat, Eran Rom, Edouard Bochin, Adam Hatsir of Palo Alto Networks on 2025-01-18</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2025-0999</cvename>
       <cvename>CVE-2025-1426</cvename>
       <cvename>CVE-2025-1006</cvename>
       <url>https://chromereleases.googleblog.com/2025/02/stable-channel-update-for-desktop_18.html</url>
     </references>
     <dates>
       <discovery>2025-02-18</discovery>
       <entry>2025-02-20</entry>
     </dates>
   </vuln>
 
   <vuln vid="f572b9d1-ef6d-11ef-85f3-a8a1599412c6">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>133.0.6943.98</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>133.0.6943.98</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2025/02/stable-channel-update-for-desktop_12.html">
 	 <p>This update includes 4 security fixes:</p>
 	 <ul>
 	    <li>[391907159] High CVE-2025-0995: Use after free in V8. Reported by Popax21 on 2025-01-24</li>
 	    <li>[391788835] High CVE-2025-0996: Inappropriate implementation in Browser UI. Reported by yuki yamaoto on 2025-01-23</li>
 	    <li>[391666328] High CVE-2025-0997: Use after free in Navigation. Reported by asnine on 2025-01-23</li>
 	    <li>[386857213] High CVE-2025-0998: Out of bounds memory access in V8. Reported by Alan Goodman on 2024-12-31</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2025-0995</cvename>
       <cvename>CVE-2025-0996</cvename>
       <cvename>CVE-2025-0997</cvename>
       <cvename>CVE-2025-0998</cvename>
       <url>https://chromereleases.googleblog.com/2025/02/stable-channel-update-for-desktop_12.html</url>
     </references>
     <dates>
       <discovery>2025-02-12</discovery>
       <entry>2025-02-20</entry>
     </dates>
   </vuln>
 
   <vuln vid="b09d0b3b-ef6d-11ef-85f3-a8a1599412c6">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>133.0.6943.53</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>133.0.6943.53</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2025/02/stable-channel-update-for-desktop.html">
 	 <p>This update includes 12 security fixes:</p>
 	 <ul>
 	    <li>[390889644] High CVE-2025-0444: Use after free in Skia. Reported by Francisco Alonso (@revskills) on 2025-01-19</li>
 	    <li>[392521083] High CVE-2025-0445: Use after free in V8. Reported by 303f06e3 on 2025-01-27</li>
 	    <li>[40061026] Medium CVE-2025-0451: Inappropriate implementation in Extensions API. Reported by Vitor Torres and Alesandro Ortiz on 2022-09-18</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2025-0444</cvename>
       <cvename>CVE-2025-0445</cvename>
       <cvename>CVE-2025-0451</cvename>
       <url>https://chromereleases.googleblog.com/2025/02/stable-channel-update-for-desktop.html</url>
     </references>
     <dates>
       <discovery>2025-02-04</discovery>
       <entry>2025-02-20</entry>
     </dates>
   </vuln>
 
   <vuln vid="cbf5d976-656b-4bb6-805f-3af038e2de3e">
     <topic>vscode -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>vscode</name>
 	<range><lt>1.97.1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>VSCode developers report:</p>
 	<blockquote cite="https://github.com/microsoft/vscode/releases/tag/1.97.1">
 	  <p>The update addresses these issues, including a fix for a security vulnerability.</p>
 	  <ul>
 	    <li>Scope node_module binary resolution in js-debug</li>
 	    <li>Elevation of Privilege Vulnerability with VS Code server for web UI</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-24042</cvename>
       <url>https://github.com/microsoft/vscode/security/advisories/GHSA-f85p-3684-2g3j</url>
       <cvename>CVE-2025-24039</cvename>
       <url>https://github.com/microsoft/vscode/security/advisories/GHSA-532g-4pv9-25f2</url>
     </references>
     <dates>
       <discovery>2025-02-11</discovery>
       <entry>2025-02-13</entry>
     </dates>
   </vuln>
 
   <vuln vid="e915b60e-ea25-11ef-a1c0-0050569f0b83">
     <topic>security/openvpn-auth-ldap -- Fix buffer overflow in challenge/response</topic>
     <affects>
       <package>
 	<name>openvpn-auth-ldap</name>
 	<range><lt>2.0.4_3</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Graham Northup reports:</p>
 	<blockquote cite="https://nvd.nist.gov/vuln/detail/CVE-2024-28820">
 	  <p>A buffer overflow in extract_openvpn_cr allows attackers with a valid
 	     LDAP username and who can control the challenge/response password field
 	     to pass a string with more than 14 colons into this field and cause a
 	     buffer overflow.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-28820</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-28820</url>
     </references>
     <dates>
       <discovery>2024-06-27</discovery>
       <entry>2025-02-13</entry>
     </dates>
   </vuln>
 
   <vuln vid="fadf3b41-ea19-11ef-a540-6cc21735f730">
     <topic>PostgreSQL -- PostgreSQL quoting APIs miss neutralizing quoting syntax in text that fails encoding validation</topic>
     <affects>
       <package>
 	<name>postgresql17-client</name>
 	<range><lt>17.3</lt></range>
       </package>
       <package>
 	<name>postgresql16-client</name>
 	<range><lt>16.7</lt></range>
       </package>
       <package>
 	<name>postgresql15-client</name>
 	<range><lt>15.11</lt></range>
       </package>
       <package>
 	<name>postgresql14-client</name>
 	<range><lt>14.16</lt></range>
       </package>
       <package>
 	<name>postgresql13-client</name>
 	<range><lt>13.19</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The PostgreSQL Project reports:</p>
 	<blockquote cite="https://www.postgresql.org/support/security/CVE-2025-1094/">
 	<p>
 	  Improper neutralization of quoting syntax in PostgreSQL
 	  libpq functions PQescapeLiteral(), PQescapeIdentifier(),
 	  PQescapeString(), and PQescapeStringConn() allows a
 	  database input provider to achieve SQL injection in
 	  certain usage patterns. Specifically, SQL injection
 	  requires the application to use the function result to
 	  construct input to psql, the PostgreSQL interactive
 	  terminal. Similarly, improper neutralization of quoting
 	  syntax in PostgreSQL command line utility programs
 	  allows a source of command line arguments to achieve SQL
 	  injection when client_encoding is BIG5 and
 	  server_encoding is one of EUC_TW or MULE_INTERNAL.
 	  Versions before PostgreSQL 17.3, 16.7, 15.11, 14.16, and
 	  13.19 are affected.
 	</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-1094</cvename>
       <url>https://www.postgresql.org/support/security/CVE-2025-1094/</url>
     </references>
     <dates>
       <discovery>2025-02-13</discovery>
       <entry>2025-02-13</entry>
     </dates>
   </vuln>
 
   <vuln vid="1a8c5720-e9cf-11ef-9e96-2cf05da270f3">
     <topic>Gitlab -- Vulnerabilities</topic>
     <affects>
       <package>
 	<name>gitlab-ce</name>
 	<name>gitlab-ee</name>
 	<range><ge>17.8.0</ge><lt>17.8.2</lt></range>
 	<range><ge>17.7.0</ge><lt>17.7.4</lt></range>
 	<range><ge>8.3.0</ge><lt>17.6.5</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Gitlab reports:</p>
 	<blockquote cite="https://about.gitlab.com/releases/2025/02/12/patch-release-gitlab-17-8-2-released/">
 	  <p>A CSP-bypass XSS in merge-request page</p>
 	  <p>Denial of Service due to Unbounded Symbol Creation</p>
 	  <p>Exfiltrate content from private issues using Prompt Injection</p>
 	  <p>A custom permission may allow overriding Repository settings</p>
 	  <p>Internal HTTP header leak via route confusion in workhorse</p>
 	  <p>SSRF via workspaces</p>
 	  <p>Unauthorized Incident Closure and Deletion by Planner Role in GitLab</p>
 	  <p>ActionCable does not invalidate tokens after revocation</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-0376</cvename>
       <cvename>CVE-2024-12379</cvename>
       <cvename>CVE-2024-3303</cvename>
       <cvename>CVE-2025-1042</cvename>
       <cvename>CVE-2025-1212</cvename>
       <cvename>CVE-2024-9870</cvename>
       <cvename>CVE-2025-0516</cvename>
       <cvename>CVE-2025-1198</cvename>
       <url>https://about.gitlab.com/releases/2025/02/12/patch-release-gitlab-17-8-2-released/</url>
     </references>
     <dates>
       <discovery>2025-02-12</discovery>
       <entry>2025-02-13</entry>
     </dates>
   </vuln>
 
   <vuln vid="d598266d-7772-4a31-9594-83b76b1fb837">
     <topic>Intel CPUs -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>cpu-microcode-intel</name>
 	<range><lt>20250211</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Intel reports:</p>
 	<blockquote cite="https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01166.html">
 	 <p>
 	  A potential security vulnerability in some Intel Processors may allow
 	  denial of service.  Intel released microcode updates to mitigate this
 	  potential vulnerability.
 	 </p>
 	</blockquote>
 	<blockquote cite="https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01213.html">
 	 <p>
 	  A potential security vulnerability in some Intel Software Guard
 	  Extensions (Intel SGX) Platforms may allow denial of service.  Intel
 	  is released microcode updates to mitigate this potential
 	  vulnerability.
 	 </p>
 	</blockquote>
 	<blockquote cite="https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01139.html">
 	 <p>
 	  Potential security vulnerabilities in the UEFI firmware for some Intel
 	  Processors may allow escalation of privilege, denial of service, or
 	  information disclosure. Intel released UEFI firmware and CPU microcode
 	  updates to mitigate these potential vulnerabilities.
 	 </p>
 	</blockquote>
 	<blockquote cite="https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01228.html">
 	 <p>
 	  A potential security vulnerability in some 13th and 14th Generation
 	  Intel Core™ Processors may allow denial of service.  Intel released
 	  microcode and UEFI reference code updates to mitigate this potential
 	  vulnerability.
 	 </p>
 	</blockquote>
 	<blockquote cite="https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01194.html">
 	 <p>
 	  A potential security vulnerability in the Intel Data Streaming
 	  Accelerator (Intel DSA) for some Intel Xeon Processors may allow
 	  denial of service.  Intel released software updates to mitigate this
 	  potential vulnerability.
 	 </p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-31068</cvename>
       <cvename>CVE-2024-36293</cvename>
       <cvename>CVE-2023-43758</cvename>
       <cvename>CVE-2024-39355</cvename>
       <cvename>CVE-2024-37020</cvename>
       <url>https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases/tag/microcode-20250211</url>
     </references>
     <dates>
       <discovery>2025-02-11</discovery>
       <entry>2025-02-12</entry>
     </dates>
   </vuln>
 
   <vuln vid="a64761a1-e895-11ef-873e-8447094a420f">
     <topic>OpenSSL -- Man-in-the-Middle vulnerability</topic>
     <affects>
       <package>
 	<name>openssl32</name>
 	<range><lt>3.2.4</lt></range>
       </package>
       <package>
 	<name>openssl33</name>
 	<range><lt>3.3.2</lt></range>
       </package>
       <package>
 	<name>openssl34</name>
 	<range><lt>3.4.1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The OpenSSL project reports:</p>
 	<blockquote cite="https://openssl-library.org/news/secadv/20250211.txt">
 	  <p>RFC7250 handshakes with unauthenticated servers don't abort as expected (High).
 	    Clients using RFC7250 Raw Public Keys (RPKs) to authenticate a server may fail to notice that the server was not authenticated, because handshakes don't abort as expected when the SSL_VERIFY_PEER verification mode is set.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-12797</cvename>
       <url>https://openssl-library.org/news/secadv/20250211.txt</url>
     </references>
     <dates>
       <discovery>2025-02-11</discovery>
       <entry>2025-02-11</entry>
     </dates>
   </vuln>
 
   <vuln vid="20485d27-e540-11ef-a845-b42e991fc52e">
     <topic>mozilla -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>135.0.0,2</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>128.7,1</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>128.7</lt></range>
 	<range><gt>129</gt><lt>135</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/buglist.cgi?bug_id=1926256%2C1935984%2C1935471">
 	<p>A bug in WebAssembly code generation could have lead to a crash.
 	It may have been possible for an attacker to leverage this to achieve
 	code execution.</p>
 	<p>A race condition could have led to private browsing tabs being
 	opened in normal browsing windows.  This could have resulted in a
 	potential privacy leak.</p>
 	<p>Certificate length was not properly checked when added to a certificate
 	store.  In practice only trusted data was processed.</p>
 	<p>Memory safety bugs present in Firefox 134, Thunderbird 134, Firefox
 	ESR 128.6, and Thunderbird 128.6.  Some of these bugs showed evidence
 	of memory corruption and we presume that with enough effort some
 	of these could have been exploited to run arbitrary code.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-1011</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-1011</url>
       <cvename>CVE-2025-1013</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-1013</url>
       <cvename>CVE-2025-1014</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-1014</url>
       <cvename>CVE-2025-1017</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-1017</url>
     </references>
     <dates>
       <discovery>2025-02-04</discovery>
       <entry>2025-02-07</entry>
     </dates>
   </vuln>
 
   <vuln vid="f7ca4ff7-e53f-11ef-a845-b42e991fc52e">
     <topic>mozilla -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>mozilla</name>
 	<range><lt>135.0.0,2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/buglist.cgi?bug_id=1939063%2C1942169">
 	  <p>Memory safety bugs present in Firefox 134 and Thunderbird 134.  Some
 	of these bugs showed evidence of memory corruption and we presume
 	that with enough effort some of these could have been exploited to
 	run arbitrary code.</p>
 	  <p>The fullscreen notification is prematurely hidden when fullscreen
 	is re-requested quickly by the user.  This could have been leveraged
 	to perform a potential spoofing attack.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-1018</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-1018</url>
       <cvename>CVE-2025-1019</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-1019</url>
       <cvename>CVE-2025-1020</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-1020</url>
     </references>
     <dates>
       <discovery>2025-02-04</discovery>
       <entry>2025-02-07</entry>
     </dates>
   </vuln>
 
   <vuln vid="e54a1413-e539-11ef-a845-b42e991fc52e">
     <topic>mozilla -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>firefox</name>
 	<range><lt>135.0.0,2</lt></range>
       </package>
       <package>
 	<name>firefox-esr</name>
 	<range><lt>115.20,1</lt></range>
 	<range><gt>116.0,1</gt><lt>128.6,1</lt></range>
       </package>
       <package>
 	<name>thunderbird</name>
 	<range><lt>128.7</lt></range>
 	<range><gt>129</gt><lt>135</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/buglist.cgi?bug_id=1936601%2C1936844%2C1937694%2C1938469%2C1939583%2C1940994">
 	<p>An attacker could have caused a use-after-free via crafted XSLT
 	data, leading to a potentially exploitable crash.</p>
 	<p>An attacker could have caused a use-after-free via the Custom
 	Highlight API, leading to a potentially exploitable crash.</p>
 	<p>A race during concurrent delazification could have led to a
 	use-after-free.</p>
 	<p>Memory safety bugs present in Firefox 134, Thunderbird 134, Firefox
 	ESR 115.19, Firefox ESR 128.6, Thunderbird 115.19, and Thunderbird
 	128.6.  Some of these bugs showed evidence of memory corruption and
 	we presume that with enough effort some of these could have been
 	exploited to run arbitrary code.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-1009</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-1009</url>
       <cvename>CVE-2025-1010</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-1010</url>
       <cvename>CVE-2025-1012</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-1012</url>
       <cvename>CVE-2025-1016</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-1016</url>
     </references>
     <dates>
       <discovery>2025-02-04</discovery>
       <entry>2025-02-07</entry>
     </dates>
   </vuln>
 
   <vuln vid="830381c7-e539-11ef-a845-b42e991fc52e">
     <topic>Thundirbird -- unprivileged JavaScript code execution</topic>
     <affects>
       <package>
 	<name>mozilla</name>
 	<range><lt>128.7,1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>security@mozilla.org reports:</p>
 	<blockquote cite="https://bugzilla.mozilla.org/show_bug.cgi?id=1939458">
 	  <p>The Thunderbird Address Book URI fields contained unsanitized links.
 	This could be used by an attacker to create and export an address
 	book containing a malicious payload in a field.  For example, in
 	the Other field of the Instant Messaging section.  If another user
 	imported the address book, clicking on the link could result in
 	opening a web page inside Thunderbird, and that page could execute
 	(unprivileged) JavaScript.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-1015</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2025-1015</url>
     </references>
     <dates>
       <discovery>2025-02-04</discovery>
       <entry>2025-02-07</entry>
     </dates>
   </vuln>
 
   <vuln vid="7bcfca95-e563-11ef-873e-8447094a420f">
     <topic>MariaDB -- DoS vulnerability in InnoDB</topic>
     <affects>
       <package>
 	<name>mariadb105-server</name>
 	<range><lt>10.5.28</lt></range>
       </package>
       <package>
 	<name>mariadb106-server</name>
 	<range><lt>10.6.21</lt></range>
       </package>
       <package>
 	<name>mariadb1011-server</name>
 	<range><lt>10.11.11</lt></range>
       </package>
       <package>
 	<name>mariadb114-server</name>
 	<range><lt>11.4.5</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>MariaDB reports:</p>
 	<blockquote cite="https://mariadb.com/kb/en/security/">
 	  <p>Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-21490</cvename>
       <url>http://mariadb.com/kb/en/security/</url>
     </references>
     <dates>
       <discovery>2025-02-04</discovery>
       <entry>2025-02-07</entry>
     </dates>
   </vuln>
 
   <vuln vid="c10b639c-e51c-11ef-9e76-4ccc6adda413">
     <topic>libcaca -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>libcaca</name>
 	<range><lt>0.99.b20</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Sam Hocevar reports:</p>
 	<blockquote cite="https://github.com/cacalabs/libcaca/releases/tag/v0.99.beta20">
 	  <p>Multiple memory leaks and invalid memory accesses:</p>
 	  <ul>
 	    <li>CVE-2018-20545: Illegal WRITE memory access at common-image.c</li>
 	    <li>CVE-2018-20546: Illegal READ memory access at caca/dither.c</li>
 	    <li>CVE-2018-20547: Illegal READ memory access at caca/dither.c</li>
 	    <li>CVE-2018-20548: Illegal WRITE memory access at common-image.c</li>
 	    <li>CVE-2018-20549: Illegal WRITE memory access at caca/file.c</li>
 	    <li>CVE-2021-3410:  Buffer overflow in libcaca/caca/canvas.c in function caca_resize</li>
 	    <li>CVE-2021-30498: Heap buffer overflow in export.c in function export_tga</li>
 	    <li>CVE-2021-30499: Buffer overflow in export.c in function export_troff</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2018-20545</cvename>
       <cvename>CVE-2018-20546</cvename>
       <cvename>CVE-2018-20547</cvename>
       <cvename>CVE-2018-20548</cvename>
       <cvename>CVE-2018-20549</cvename>
       <cvename>CVE-2021-3410</cvename>
       <cvename>CVE-2021-30498</cvename>
       <cvename>CVE-2021-30499</cvename>
       <url>https://github.com/cacalabs/libcaca/releases/tag/v0.99.beta20</url>
     </references>
     <dates>
       <discovery>2021-10-19</discovery>
       <entry>2025-02-07</entry>
     </dates>
   </vuln>
 
   <vuln vid="e7974ca5-e4c8-11ef-aab3-40b034429ecf">
     <topic>cacti -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>cacti</name>
 	<range><lt>1.2.29</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Cacti repo reports:</p>
 	<blockquote cite="https://github.com/Cacti/cacti/releases/tag/release%2F1.2.29">
 	  <ul>
 	    <li>security #GHSA-c5j8-jxj3-hh36: Authenticated RCE via multi-line SNMP responses</li>
 	    <li>security #GHSA-f9c7-7rc3-574c: SQL Injection vulnerability when using tree rules through Automation API</li>
 	    <li>security #GHSA-fh3x-69rr-qqpp: SQL Injection vulnerability when request automation devices</li>
 	    <li>security #GHSA-fxrq-fr7h-9rqq: Arbitrary File Creation leading to RCE</li>
 	    <li>security #GHSA-pv2c-97pp-vxwg: Local File Inclusion (LFI) Vulnerability via Poller Standard Error Log Path</li>
 	    <li>security #GHSA-vj9g-p7f2-4wqj: SQL Injection vulnerability when view host template</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-22604</cvename>
       <cvename>CVE-2025-24368</cvename>
       <cvename>CVE-2024-54145</cvename>
       <cvename>CVE-2025-24367</cvename>
       <cvename>CVE-2024-45598</cvename>
       <cvename>CVE-2024-54146</cvename>
     </references>
     <dates>
       <discovery>2025-02-02</discovery>
       <entry>2025-02-05</entry>
     </dates>
   </vuln>
 
   <vuln vid="9761af78-e3e4-11ef-9f4a-589cfc10a551">
     <topic>nginx-devel -- SSL session reuse vulnerability</topic>
     <affects>
       <package>
 	<name>nginx-devel</name>
 	<range><lt>1.27.4</lt></range>
       </package>
       <package>
 	<name>nginx</name>
 	<range><lt>1.26.3</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The nginx development team reports:</p>
 	<blockquote cite="http://nginx.org/en/security_advisories.html">
 	  <p>This update fixes the SSL session reuse vulnerability.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-23419</cvename>
     </references>
     <dates>
       <discovery>2025-02-05</discovery>
       <entry>2025-02-05</entry>
     </dates>
   </vuln>
 
   <vuln vid="72b8729e-e134-11ef-9e76-4ccc6adda413">
     <topic>qt6-webengine -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>qt6-webengine</name>
 	<range><lt>6.8.2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Qt qtwebengine-chromium repo reports:</p>
 	<blockquote cite="https://code.qt.io/cgit/qt/qtwebengine-chromium.git/log/?h=122-based">
 	  <p>Backports for 9 security bugs in Chromium:</p>
 	  <ul>
 	    <li>CVE-2024-12693: Out of bounds memory access in V8</li>
 	    <li>CVE-2024-12694: Use after free in Compositing</li>
 	    <li>CVE-2025-0436: Integer overflow in Skia</li>
 	    <li>CVE-2025-0437: Out of bounds read in Metrics</li>
 	    <li>CVE-2025-0438: Stack buffer overflow in Tracing</li>
 	    <li>CVE-2025-0441: Inappropriate implementation in Fenced Frames</li>
 	    <li>CVE-2025-0443: Insufficient data validation in Extensions</li>
 	    <li>CVE-2025-0447: Inappropriate implementation in Navigation</li>
 	    <li>CVE-2025-0611: Object corruption in V8</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-12693</cvename>
       <cvename>CVE-2024-12694</cvename>
       <cvename>CVE-2025-0436</cvename>
       <cvename>CVE-2025-0437</cvename>
       <cvename>CVE-2025-0438</cvename>
       <cvename>CVE-2025-0441</cvename>
       <cvename>CVE-2025-0443</cvename>
       <cvename>CVE-2025-0447</cvename>
       <cvename>CVE-2025-0611</cvename>
       <url>https://code.qt.io/cgit/qt/qtwebengine-chromium.git/log/?h=122-based</url>
     </references>
     <dates>
       <discovery>2025-01-09</discovery>
       <entry>2025-02-02</entry>
     </dates>
   </vuln>
 
   <vuln vid="186101b4-dfa6-11ef-8c1c-a8a1599412c6">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>132.0.6834.159</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>132.0.6834.159</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2025/01/stable-channel-update-for-desktop_28.html">
 	 <p>This update includes 2 security fixes:</p>
 	 <ul>
 	    <li>[384844003] Medium CVE-2025-0762: Use after free in DevTools. Reported by Sakana.S on 2024-12-18</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2025-0762</cvename>
       <url>https://chromereleases.googleblog.com/2025/01/stable-channel-update-for-desktop_28.html</url>
     </references>
     <dates>
       <discovery>2025-01-18</discovery>
       <entry>2025-01-31</entry>
     </dates>
   </vuln>
 
   <vuln vid="cd2ace09-df23-11ef-a205-901b0e9408dc">
     <topic>dendrite -- Server-side request forgery vulnerability</topic>
     <affects>
       <package>
 	<name>dendrite</name>
 	<range><lt>0.14.1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Dendrite team reports:</p>
 	<blockquote cite="https://github.com/matrix-org/gomatrixserverlib/security/advisories/GHSA-4ff6-858j-r822">
 	  <p>This is a security release, gomatrixserverlib was vulnerable to server-side request forgery, serving content from a private network it can access, under certain conditions.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-52594</cvename>
       <url>https://github.com/matrix-org/gomatrixserverlib/security/advisories/GHSA-4ff6-858j-r822</url>
     </references>
     <dates>
       <discovery>2025-01-16</discovery>
       <entry>2025-01-30</entry>
     </dates>
   </vuln>
 
   <vuln vid="2830b374-debd-11ef-87ba-002590c1f29c">
     <topic>FreeBSD -- Uninitialized kernel memory disclosure via ktrace(2)</topic>
     <affects>
       <package>
 	<name>FreeBSD-kernel</name>
 	<range><ge>14.2</ge><lt>14.2_1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<h1>Problem Description:</h1>
 	<p>In some cases, the ktrace facility will log the contents of
 	kernel structures to userspace.  In one such case, ktrace dumps a
 	variable-sized sockaddr to userspace.  There, the full sockaddr is
 	copied, even when it is shorter than the full size.  This can result
 	in up to 14 uninitialized bytes of kernel memory being copied out
 	to userspace.</p>
 	<h1>Impact:</h1>
 	<p>It is possible for an unprivileged userspace program to leak
 	14 bytes of a kernel heap allocation to userspace.</p>
       </body>
     </description>
     <references>
       <cvename>CVE-2025-0662</cvename>
       <freebsdsa>SA-25:04.ktrace</freebsdsa>
     </references>
     <dates>
       <discovery>2025-01-29</discovery>
       <entry>2025-01-30</entry>
     </dates>
   </vuln>
 
   <vuln vid="fa9ae646-debc-11ef-87ba-002590c1f29c">
     <topic>FreeBSD -- Unprivileged access to system files</topic>
     <affects>
       <package>
 	<name>FreeBSD</name>
 	<range><ge>14.2</ge><lt>14.2_1</lt></range>
 	<range><ge>14.1</ge><lt>14.1_7</lt></range>
 	<range><ge>13.4</ge><lt>13.4_3</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<h1>Problem Description:</h1>
 	<p>When etcupdate encounters conflicts while merging files, it
 	saves a version containing conflict markers in /var/db/etcupdate/conflicts.
 	This version does not preserve the mode of the input file, and is
 	world-readable.  This applies to files that would normally have
 	restricted visibility, such as /etc/master.passwd.</p>
 	<h1>Impact:</h1>
 	<p>An unprivileged local user may be able to read encrypted root
 	and user passwords from the temporary master.passwd file created
 	in /var/db/etcupdate/conflicts.  This is possible only when conflicts
 	within the password file arise during an update, and the unprotected
 	file is deleted when conflicts are resolved.</p>
       </body>
     </description>
     <references>
       <cvename>CVE-2025-0374</cvename>
       <freebsdsa>SA-25:03.etcupdate</freebsdsa>
     </references>
     <dates>
       <discovery>2025-01-29</discovery>
       <entry>2025-01-30</entry>
     </dates>
   </vuln>
 
   <vuln vid="ab0cbe3f-debc-11ef-87ba-002590c1f29c">
     <topic>FreeBSD -- Buffer overflow in some filesystems via NFS</topic>
     <affects>
       <package>
 	<name>FreeBSD-kernel</name>
 	<range><ge>14.2</ge><lt>14.2_1</lt></range>
 	<range><ge>14.1</ge><lt>14.1_7</lt></range>
 	<range><ge>13.4</ge><lt>13.4_3</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<h1>Problem Description:</h1>
 	<p>In order to export a file system via NFS, the file system must
 	define a file system identifier (FID) for all exported files.  Each
 	FreeBSD file system implements operations to translate between FIDs
 	and vnodes, the kernel's in-memory representation of files.  These
 	operations are VOP_VPTOFH(9) and VFS_FHTOVP(9).</p>
 	<p>On 64-bit systems, the implementation of VOP_VPTOFH() in the
 	cd9660, tarfs and ext2fs filesystems overflows the destination FID
 	buffer by 4 bytes, a stack buffer overflow.</p>
 	<h1>Impact:</h1>
 	<p>A NFS server that exports a cd9660, tarfs, or ext2fs file system
 	can be made to panic by mounting and accessing the export with an
 	NFS client.  Further exploitation (e.g., bypassing file permission
 	checking or remote kernel code execution) is potentially possible,
 	though this has not been demonstrated.  In particular, release
 	kernels are compiled with stack protection enabled, and some instances
 	of the overflow are caught by this mechanism, causing a panic.</p>
       </body>
     </description>
     <references>
       <cvename>CVE-2025-0373</cvename>
       <freebsdsa>SA-25:02.fs</freebsdsa>
     </references>
     <dates>
       <discovery>2025-01-29</discovery>
       <entry>2025-01-30</entry>
     </dates>
   </vuln>
 
   <vuln vid="69e19c0b-debc-11ef-87ba-002590c1f29c">
     <topic>FreeBSD -- OpenSSH Keystroke Obfuscation Bypass</topic>
     <affects>
       <package>
 	<name>FreeBSD</name>
 	<range><ge>14.1</ge><lt>14.1_7</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<h1>Problem Description:</h1>
 	<p>A logic error in the ssh(1) ObscureKeystrokeTiming feature (on
 	by default) rendered this feature ineffective.</p>
 	<h1>Impact:</h1>
 	<p>A passive observer could detect which network packets contain
 	real keystrokes, and infer the specific characters being transmitted
 	from packet timing.</p>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-39894</cvename>
       <freebsdsa>SA-25:01.openssh</freebsdsa>
     </references>
     <dates>
       <discovery>2025-01-29</discovery>
       <entry>2025-01-30</entry>
     </dates>
   </vuln>
 
   <vuln vid="258a58a9-6583-4808-986b-e785c27b0a18">
     <topic>oauth2-proxy -- Non-linear parsing of case-insensitive content</topic>
     <affects>
       <package>
 	<name>oauth2-proxy</name>
 	<range><lt>7.8.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Golang reports:</p>
 	<blockquote cite="https://github.com/advisories/GHSA-w32m-9786-jp63">
 	  <p>This update include security fixes:</p>
 	  <ul>
 	    <li>CVE-2024-45338: Non-linear parsing of case-insensitive content</li>
 	  </ul>
 	</blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2024-45338</cvename>
     </references>
     <dates>
       <discovery>2025-01-14</discovery>
       <entry>2025-01-30</entry>
      </dates>
   </vuln>
 
   <vuln vid="41711c0d-db27-11ef-873e-8447094a420f">
     <topic>Vaultwarden -- Multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>vaultwarden</name>
 	<range><lt>1.33.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The Vaultwarden project reports:</p>
 	<blockquote cite="https://github.com/dani-garcia/vaultwarden/releases/tag/1.33.0">
 	  <p>RCE in the admin panel.</p>
 	  <p>Getting access to the Admin Panel via CSRF.</p>
 	  <p>Escalation of privilege via variable confusion in OrgHeaders trait.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-24364</cvename>
       <url>https://github.com/dani-garcia/vaultwarden/security/advisories/GHSA-j4h8-vch3-f797</url>
       <cvename>CVE-2025-24365</cvename>
       <url>https://github.com/dani-garcia/vaultwarden/security/advisories/GHSA-h6cc-rc6q-23j4</url>
     </references>
     <dates>
       <discovery>2025-01-25</discovery>
       <entry>2025-01-25</entry>
     </dates>
   </vuln>
 
   <vuln vid="c53cd328-8131-4fc2-a083-a9e9d45e3028">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>132.0.6834.110</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>132.0.6834.110</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2025/01/stable-channel-update-for-desktop_22.html">
 	 <p>This update includes 3 security fixes:</p>
 	 <ul>
 	    <li>[386143468] High CVE-2025-0611: Object corruption in V8. Reported by 303f06e3 on 2024-12-26</li>
 	    <li>[385155406] High CVE-2025-0612: Out of bounds memory access in V8. Reported by Alan Goodman on 2024-12-20</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2025-0611</cvename>
       <cvename>CVE-2025-0612</cvename>
       <url>https://chromereleases.googleblog.com/2025/01/stable-channel-update-for-desktop_22.html</url>
     </references>
     <dates>
       <discovery>2025-01-22</discovery>
       <entry>2025-01-25</entry>
     </dates>
   </vuln>
 
   <vuln vid="756839e1-cd78-4082-9f9e-d0da616ca8dd">
     <topic>chromium -- multiple security fixes</topic>
     <affects>
       <package>
        <name>chromium</name>
        <range><lt>132.0.6834.83</lt></range>
       </package>
       <package>
        <name>ungoogled-chromium</name>
        <range><lt>132.0.6834.83</lt></range>
       </package>
     </affects>
     <description>
       <body xmlns="http://www.w3.org/1999/xhtml">
        <p>Chrome Releases reports:</p>
        <blockquote cite="https://chromereleases.googleblog.com/2025/01/stable-channel-update-for-desktop_14.html">
 	 <p>This update includes 16 security fixes:</p>
 	 <ul>
 	    <li>[374627491] High CVE-2025-0434: Out of bounds memory access in V8. Reported by ddme on 2024-10-21</li>
 	    <li>[379652406] High CVE-2025-0435: Inappropriate implementation in Navigation. Reported by Alesandro Ortiz on 2024-11-18</li>
 	    <li>[382786791] High CVE-2025-0436: Integer overflow in Skia. Reported by Han Zheng (HexHive) on 2024-12-08</li>
 	    <li>[378623799] High CVE-2025-0437: Out of bounds read in Metrics. Reported by Xiantong Hou of Wuheng Lab and Pisanbao on 2024-11-12</li>
 	    <li>[384186539] High CVE-2025-0438: Stack buffer overflow in Tracing. Reported by Han Zheng (HexHive) on 2024-12-15</li>
 	    <li>[371247941] Medium CVE-2025-0439: Race in Frames. Reported by Hafiizh on 2024-10-03</li>
 	    <li>[40067914] Medium CVE-2025-0440: Inappropriate implementation in Fullscreen. Reported by Umar Farooq on 2023-07-22</li>
 	    <li>[368628042] Medium CVE-2025-0441: Inappropriate implementation in Fenced Frames. Reported by someoneverycurious on 2024-09-21</li>
 	    <li>[40940854] Medium CVE-2025-0442: Inappropriate implementation in Payments. Reported by Ahmed ElMasry on 2023-11-08</li>
 	    <li>[376625003] Medium CVE-2025-0443: Insufficient data validation in Extensions. Reported by Anonymous on 2024-10-31</li>
 	    <li>[359949844] Low CVE-2025-0446: Inappropriate implementation in Extensions. Reported by Hafiizh on 2024-08-15</li>
 	    <li>[375550814] Low CVE-2025-0447: Inappropriate implementation in Navigation. Reported by Khiem Tran (@duckhiem) on 2024-10-25</li>
 	    <li>[377948403] Low CVE-2025-0448: Inappropriate implementation in Compositing. Reported by Dahyeon Park on 2024-11-08</li>
 	 </ul>
        </blockquote>
       </body>
     </description>
     <references>
       <cvename>CVE-2025-0434</cvename>
       <cvename>CVE-2025-0435</cvename>
       <cvename>CVE-2025-0436</cvename>
       <cvename>CVE-2025-0437</cvename>
       <cvename>CVE-2025-0438</cvename>
       <cvename>CVE-2025-0439</cvename>
       <cvename>CVE-2025-0440</cvename>
       <cvename>CVE-2025-0441</cvename>
       <cvename>CVE-2025-0442</cvename>
       <cvename>CVE-2025-0443</cvename>
       <cvename>CVE-2025-0446</cvename>
       <cvename>CVE-2025-0447</cvename>
       <cvename>CVE-2025-0448</cvename>
       <url>https://chromereleases.googleblog.com/2025/01/stable-channel-update-for-desktop_14.html</url>
     </references>
     <dates>
       <discovery>2025-01-14</discovery>
       <entry>2025-01-25</entry>
     </dates>
   </vuln>
 
   <vuln vid="ef303b6a-7d9e-4e28-b92e-21f39d519d9e">
     <topic>electron32 -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>electron32</name>
 	<range><lt>32.3.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Electron developers report:</p>
 	<blockquote cite="https://github.com/electron/electron/releases/tag/v32.3.0">
 	  <p>This update fixes the following vulnerabilities:</p>
 	  <ul>
 	    <li>Security: backported fix for CVE-2024-12693.</li>
 	    <li>Security: backported fix for CVE-2024-12694.</li>
 	    <li>Security: backported fix for CVE-2024-12695.</li>
 	    <li>Security: backported fix for CVE-2025-0434.</li>
 	    <li>Security: backported fix for CVE-2025-0436.</li>
 	    <li>Security: backported fix for CVE-2025-0437.</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-12693</cvename>
       <url>https://github.com/advisories/GHSA-m84q-p89f-6cc5</url>
       <cvename>CVE-2024-12694</cvename>
       <url>https://github.com/advisories/GHSA-cgc6-4xgf-5q5x</url>
       <cvename>CVE-2024-12695</cvename>
       <url>https://github.com/advisories/GHSA-6895-2frg-pq5j</url>
       <cvename>CVE-2025-0434</cvename>
       <url>https://github.com/advisories/GHSA-fpmx-pfpg-92xg</url>
       <cvename>CVE-2025-0436</cvename>
       <url>https://github.com/advisories/GHSA-ww3g-8h77-wr7v</url>
       <cvename>CVE-2025-0437</cvename>
       <url>https://github.com/advisories/GHSA-4353-vp82-4qq4</url>
     </references>
     <dates>
       <discovery>2025-01-23</discovery>
       <entry>2025-01-25</entry>
     </dates>
   </vuln>
 
   <vuln vid="2def27c7-7dd0-42cb-adf6-8e5a7afe4db3">
     <topic>electron33 -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>electron33</name>
 	<range><lt>33.3.2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Electron developers report:</p>
 	<blockquote cite="https://github.com/electron/electron/releases/tag/v33.3.2">
 	  <p>This update fixes the following vulnerabilities:</p>
 	  <ul>
 	    <li>Security: backported fix for CVE-2025-0434.</li>
 	    <li>Security: backported fix for CVE-2025-0436.</li>
 	    <li>Security: backported fix for CVE-2025-0437.</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-0434</cvename>
       <url>https://github.com/advisories/GHSA-fpmx-pfpg-92xg</url>
       <cvename>CVE-2025-0436</cvename>
       <url>https://github.com/advisories/GHSA-ww3g-8h77-wr7v</url>
       <cvename>CVE-2025-0437</cvename>
       <url>https://github.com/advisories/GHSA-4353-vp82-4qq4</url>
     </references>
     <dates>
       <discovery>2025-01-22</discovery>
       <entry>2025-01-23</entry>
     </dates>
   </vuln>
 
   <vuln vid="24c93a28-d95b-11ef-b6b2-2cf05da270f3">
     <topic>Gitlab -- Vulnerabilities</topic>
     <affects>
       <package>
 	<name>gitlab-ce</name>
 	<name>gitlab-ee</name>
 	<range><ge>17.8.0</ge><lt>17.8.1</lt></range>
 	<range><ge>17.7.0</ge><lt>17.7.3</lt></range>
 	<range><ge>15.7.0</ge><lt>17.6.4</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Gitlab reports:</p>
 	<blockquote cite="https://about.gitlab.com/releases/2025/01/22/patch-release-gitlab-17-8-1-released/">
 	  <p>Stored XSS via Asciidoctor render</p>
 	  <p>Developer could exfiltrate protected CI/CD variables via CI lint</p>
 	  <p>Cyclic reference of epics leads resource exhaustion</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-0314</cvename>
       <cvename>CVE-2024-11931</cvename>
       <cvename>CVE-2024-6324</cvename>
       <url>https://about.gitlab.com/releases/2025/01/22/patch-release-gitlab-17-8-1-released/</url>
     </references>
     <dates>
       <discovery>2025-01-22</discovery>
       <entry>2025-01-23</entry>
     </dates>
   </vuln>
 
   <vuln vid="1e109b60-d92e-11ef-a661-08002784c58d">
     <topic>clamav -- Possbile denial-of-service vulnerability</topic>
     <affects>
       <package>
 	<name>clamav</name>
 	<range><ge>1.0.0,1</ge><lt>1.4.2,1</lt></range>
       </package>
       <package>
 	<name>clamav-lts</name>
 	<range><ge>1.0.0,1</ge><lt>1.0.8,1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The ClamAV project reports:</p>
 	<blockquote cite="https://blog.clamav.net/2025/01/clamav-142-and-108-security-patch.html">
 	  <p>
 	    A possible buffer overflow read bug is found in the OLE2
 	    file parser that could cause a denial-of-service (DoS)
 	    condition.
 	  </p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-20128</cvename>
       <url>https://blog.clamav.net/2025/01/clamav-142-and-108-security-patch.html</url>
     </references>
     <dates>
       <discovery>2025-01-22</discovery>
       <entry>2025-01-23</entry>
     </dates>
   </vuln>
 
   <vuln vid="7d17676d-4828-4a43-85d6-1ee14362de6e">
     <topic>electron32 -- Type Confusion in V8</topic>
     <affects>
       <package>
 	<name>electron32</name>
 	<range><lt>32.2.8</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Electron developers report:</p>
 	<blockquote cite="https://github.com/electron/electron/releases/tag/v32.2.8">
 	  <p>This update fixes the following vulnerability:</p>
 	  <ul>
 	    <li>Security: backported fix for CVE-2024-12053.</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-12053</cvename>
       <url>https://github.com/advisories/GHSA-wvx7-72hc-rp32</url>
     </references>
     <dates>
       <discovery>2025-01-06</discovery>
       <entry>2025-01-22</entry>
     </dates>
   </vuln>
 
   <vuln vid="704aa72a-d840-11ef-a205-901b0e9408dc">
     <topic>go -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>go122</name>
 	<range><lt>1.22.11</lt></range>
       </package>
       <package>
 	<name>go123</name>
 	<range><lt>1.23.5</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>The Go project reports:</p>
 	<blockquote cite="https://go.dev/issue/71156">
 	  <p>crypto/x509: usage of IPv6 zone IDs can bypass URI name constraints</p>
 	  <p>A certificate with a URI which has a IPv6 address with a
 	  zone ID may incorrectly satisfy a URI name constraint that
 	  applies to the certificate chain.</p>
 	</blockquote>
 	<blockquote cite="https://go.dev/issue/70530">
 	  <p>net/http: sensitive headers incorrectly sent after cross-domain redirect</p>
 	  <p>The HTTP client drops sensitive headers after following a
 	  cross-domain redirect.  For example, a request to a.com/
 	  containing an Authorization header which is redirected to
 	  b.com/ will not send that header to b.com.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-45341</cvename>
       <cvename>CVE-2024-45336</cvename>
       <url>https://go.dev/issue/71156</url>
       <url>https://go.dev/issue/70530</url>
     </references>
     <dates>
       <discovery>2025-01-07</discovery>
       <entry>2025-01-21</entry>
     </dates>
   </vuln>
 
   <vuln vid="3161429b-3897-4593-84a0-b41ffbbfa36b">
     <topic>electron31 -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>electron31</name>
 	<range><lt>31.7.7</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Electron developers report:</p>
 	<blockquote cite="https://github.com/electron/electron/releases/tag/v31.7.7">
 	  <p>This update fixes the following vulnerabilities:</p>
 	  <ul>
 	    <li>Security: backported fix for CVE-2024-12053.</li>
 	    <li>Security: backported fix for CVE-2024-12693.</li>
 	    <li>Security: backported fix for CVE-2024-12694.</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-12053</cvename>
       <url>https://github.com/advisories/GHSA-wvx7-72hc-rp32</url>
       <cvename>CVE-2024-12693</cvename>
       <url>https://github.com/advisories/GHSA-m84q-p89f-6cc5</url>
       <cvename>CVE-2024-12694</cvename>
       <url>https://github.com/advisories/GHSA-cgc6-4xgf-5q5x</url>
     </references>
     <dates>
       <discovery>2025-01-14</discovery>
       <entry>2025-01-20</entry>
     </dates>
   </vuln>
 
   <vuln vid="d9b0fea0-d564-11ef-b9bc-d05099c0ae8c">
     <topic>age -- age vulnerable to malicious plugin names, recipients, or identities causing arbitrary binary execution</topic>
     <affects>
       <package>
 	<name>age</name>
 	<range><lt>1.2.1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Filippo Valsorda reports:</p>
 	<blockquote cite="https://github.com/advisories/GHSA-32gq-x56h-299c">
 	  <p>A plugin name containing a path separator may allow an
 	    attacker to execute an arbitrary binary.</p>
 	  <p>Such a plugin name can be provided to the age CLI through
 	    an attacker-controlled recipient or identity string, or to
 	    the plugin.NewIdentity, plugin.NewIdentityWithoutData, or
 	    plugin.NewRecipient APIs.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <url>https://github.com/advisories/GHSA-32gq-x56h-299c</url>
     </references>
     <dates>
       <discovery>2024-12-18</discovery>
       <entry>2025-01-18</entry>
     </dates>
   </vuln>
 
   <vuln vid="47bc292a-d472-11ef-aaab-7d43732cb6f5">
     <topic>openvpn -- too long a username or password from a client can confuse openvpn servers</topic>
     <affects>
       <package>
 	<name>openvpn</name>
 	<range><lt>2.6.13</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Frank Lichtenheld reports:</p>
 	<blockquote cite="https://github.com/OpenVPN/openvpn/releases/tag/v2.6.13">
 	  <p>[OpenVPN v2.6.13 ...] improve server-side handling of clients sending
 	    usernames or passwords longer than USER_PASS_LEN - this would not
 	    result in a crash, buffer overflow or other security issues, but the
 	    server would then misparse incoming IV variables and produce misleading
 	    error messages.</p>
 	</blockquote>
        </body>
     </description>
     <references>
       <url>https://github.com/OpenVPN/openvpn/releases/tag/v2.6.13</url>
     </references>
     <dates>
       <discovery>2024-10-28</discovery>
       <entry>2025-01-17</entry>
     </dates>
   </vuln>
 
   <vuln vid="163edccf-d2ba-11ef-b10e-589cfc10a551">
     <topic>rsync -- Multiple security fixes</topic>
     <affects>
       <package>
 	<name>rsync</name>
 	<range><lt>3.4.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>rsync reports:</p>
 	<blockquote cite="https://kb.cert.org/vuls/id/952657">
 	  <p>This update includes multiple security fixes:</p>
 	  <ul>
 	    <li>CVE-2024-12084: Heap Buffer Overflow in Checksum Parsing</li>
 	    <li>CVE-2024-12085: Info Leak via uninitialized Stack contents defeats ASLR</li>
 	    <li>CVE-2024-12086: Server leaks arbitrary client files</li>
 	    <li>CVE-2024-12087: Server can make client write files outside of destination directory using symbolic links</li>
 	    <li>CVE-2024-12088: --safe-links Bypass</li>
 	    <li>CVE-2024-12747: symlink race condition</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-12084</cvename>
       <cvename>CVE-2024-12085</cvename>
       <cvename>CVE-2024-12086</cvename>
       <cvename>CVE-2024-12087</cvename>
       <cvename>CVE-2024-12088</cvename>
       <cvename>CVE-2024-12747</cvename>
     </references>
     <dates>
       <discovery>2025-01-14</discovery>
       <entry>2025-01-14</entry>
     </dates>
   </vuln>
 
   <vuln vid="3445e4b6-d2b8-11ef-9ff3-43c2b5d6c4c8">
     <topic>git -- multiple vulnerabilities</topic>
     <affects>
       <package>
 	<name>git</name>
 	<name>git-cvs</name>
 	<name>git-gui</name>
 	<name>git-p4</name>
 	<name>git-svn</name>
 	<range><lt>2.48.1</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Git development team reports:</p>
 	<blockquote cite="https://lore.kernel.org/git/xmqq5xmh46oc.fsf@gitster.g/">
 	  <p>CVE-2024-50349: Printing unsanitized URLs when asking for credentials made the
 	  user susceptible to crafted URLs (e.g. in recursive clones) that
 	  mislead the user into typing in passwords for trusted sites that
 	  would then be sent to untrusted sites instead.</p>
 	  <p>CVE-2024-52006: Git may pass on Carriage Returns via the credential protocol to
 	  credential helpers which use line-reading functions that
 	  interpret said Carriage Returns as line endings, even though Git
 	  did not intend that.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-50349</cvename>
       <url>https://github.com/git/git/security/advisories/GHSA-hmg8-h7qf-7cxr</url>
       <cvename>CVE-2024-52006</cvename>
       <url>https://github.com/git/git/security/advisories/GHSA-r5ph-xg7q-xfrp</url>
     </references>
     <dates>
       <discovery>2024-10-29</discovery>
       <entry>2025-01-14</entry>
     </dates>
   </vuln>
 
   <vuln vid="5e2bd238-d2bb-11ef-bc0e-1c697a616631">
     <topic>keycloak -- Multiple security fixes</topic>
     <affects>
       <package>
 	<name>keycloak</name>
 	<range><lt>26.0.8</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Keycloak reports:</p>
 	<blockquote cite="https://www.keycloak.org/2024/11/keycloak-2606-released.html">
 	  <p>This update includes 2 security fixes:</p>
 	  <ul>
 	    <li>CVE-2024-11734: Unrestricted admin use of system and environment variables</li>
 	    <li>CVE-2024-11736: Denial of Service in Keycloak Server via Security Headers</li>
 	  </ul>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-11734</cvename>
       <cvename>CVE-2024-11736</cvename>
     </references>
     <dates>
       <discovery>2025-01-13</discovery>
       <entry>2025-01-13</entry>
      </dates>
   </vuln>
 
   <vuln vid="7624c151-d116-11ef-b232-b42e991fc52e">
     <topic>asterisk - path traversal</topic>
     <affects>
       <package>
 	<name>asterisk18</name>
 	<range><lt>18.26.2</lt></range>
       </package>
       <package>
 	<name>asterisk20</name>
 	<range><lt>20.11.0</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>cve@mitre.org reports:</p>
 	<blockquote cite="https://gist.github.com/hyp164D1/e7c0f44ffb38c00320aa1a6d98bee616">
 	  <p>An issue in the action_listcategories() function of Sangoma Asterisk
 	v22/22.0.0/22.0.0-rc1/22.0.0-rc2/22.0.0-pre1 allows attackers to
 	execute a path traversal.</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-53566</cvename>
       <url>https://nvd.nist.gov/vuln/detail/CVE-2024-53566</url>
     </references>
     <dates>
       <discovery>2024-12-02</discovery>
       <entry>2025-01-12</entry>
     </dates>
   </vuln>
 
   <vuln vid="4d79fd1a-cc93-11ef-abed-08002784c58d">
     <topic>redis,valkey -- Denial-of-service valnerability due to malformed ACL selectors</topic>
     <affects>
       <package>
 	<name>redis</name>
 	<range><ge>7.0.0</ge><lt>7.4.2</lt></range>
       </package>
       <package>
 	<name>redis72</name>
 	<range><lt>7.2.7</lt></range>
       </package>
       <package>
 	<name>redis-devel</name>
 	<range><lt>7.4.2.20250201</lt></range>
       </package>
       <package>
 	<name>valkey</name>
 	<range><lt>8.0.2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Redis core team reports:</p>
 	<blockquote cite="https://github.com/redis/redis/security/advisories/GHSA-prpq-rh5h-46g9">
 	  <p>
 	    An authenticated with sufficient privileges may create a
 	    malformed ACL selector which, when accessed, triggers a
 	    server panic and subsequent denial of service.The problem
 	    exists in Redis 7.0.0 or newer.
 	  </p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-51741</cvename>
       <url>https://github.com/redis/redis/security/advisories/GHSA-prpq-rh5h-46g9</url>
     </references>
     <dates>
       <discovery>2025-01-06</discovery>
       <entry>2025-01-10</entry>
     </dates>
   </vuln>
 
   <vuln vid="5f19ac58-cc90-11ef-abed-08002784c58d">
     <topic>redis,valkey -- Remote code execution valnerability</topic>
     <affects>
       <package>
 	<name>redis</name>
 	<range><lt>7.4.2</lt></range>
       </package>
       <package>
 	<name>redis72</name>
 	<range><lt>7.2.7</lt></range>
       </package>
       <package>
 	<name>redis62</name>
 	<range><lt>6.2.17</lt></range>
       </package>
       <package>
 	<name>redis-devel</name>
 	<range><lt>7.4.2.20250201</lt></range>
       </package>
       <package>
 	<name>valkey</name>
 	<range><lt>8.0.2</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Redis core team reports:</p>
 	<blockquote cite="https://github.com/redis/redis/security/advisories/GHSA-39h2-x6c4-6w4c">
 	  <p>
 	    An authenticated user may use a specially crafted Lua
 	    script to manipulate the garbage collector and potentially
 	    lead to remote code execution. The problem exists in all
 	    versions of Redis with Lua scripting.
 	  </p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2024-46981</cvename>
       <url>https://github.com/redis/redis/security/advisories/GHSA-39h2-x6c4-6w4c</url>
     </references>
     <dates>
       <discovery>2025-01-06</discovery>
       <entry>2025-01-10</entry>
     </dates>
   </vuln>
 
   <vuln vid="2bfde261-cdf2-11ef-b6b2-2cf05da270f3">
     <topic>Gitlab -- Vulnerabilities</topic>
     <affects>
       <package>
 	<name>gitlab-ce</name>
 	<name>gitlab-ee</name>
 	<range><ge>17.7.0</ge><lt>17.7.1</lt></range>
 	<range><ge>17.6.0</ge><lt>17.6.3</lt></range>
 	<range><ge>11.0.0</ge><lt>17.5.5</lt></range>
       </package>
     </affects>
     <description>
 	<body xmlns="http://www.w3.org/1999/xhtml">
 	<p>Gitlab reports:</p>
 	<blockquote cite="https://about.gitlab.com/releases/2025/01/08/patch-release-gitlab-17-7-1-released/">
 	  <p>Possible access token exposure in GitLab logs</p>
 	  <p>Cyclic reference of epics leads resource exhaustion</p>
 	  <p>Unauthorized user can manipulate status of issues in public projects</p>
 	  <p>Instance SAML does not respect external_provider configuration</p>
 	</blockquote>
 	</body>
     </description>
     <references>
       <cvename>CVE-2025-0194</cvename>
       <cvename>CVE-2024-6324</cvename>
       <cvename>CVE-2024-12431</cvename>
       <cvename>CVE-2024-13041</cvename>
       <url>https://about.gitlab.com/releases/2025/01/08/patch-release-gitlab-17-7-1-released/</url>
     </references>
     <dates>
       <discovery>2025-01-08</discovery>
       <entry>2025-01-08</entry>
     </dates>
   </vuln>