git: 6cab62ade8ce - main - security/vuxml: fix parse errors
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Wed, 18 Dec 2024 05:49:27 UTC
The branch main has been updated by philip: URL: https://cgit.FreeBSD.org/ports/commit/?id=6cab62ade8ce62057e36d3ad0e1a875424e4dbfe commit 6cab62ade8ce62057e36d3ad0e1a875424e4dbfe Author: Philip Paeps <philip@FreeBSD.org> AuthorDate: 2024-12-18 05:47:43 +0000 Commit: Philip Paeps <philip@FreeBSD.org> CommitDate: 2024-12-18 05:47:43 +0000 security/vuxml: fix parse errors Fix parse errors introduced in 96ddbb42b98fcb6022729ea28cd6725fcfdc4597. --- security/vuxml/vuln/2024.xml | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/security/vuxml/vuln/2024.xml b/security/vuxml/vuln/2024.xml index df792ef7fec6..68055fc4e456 100644 --- a/security/vuxml/vuln/2024.xml +++ b/security/vuxml/vuln/2024.xml @@ -85,11 +85,11 @@ <package> <name>forgejo</name> <range><lt>9.0.2</lt></range> + </package> <package> - <name>forgejo</name> + <name>forgejo7</name> <range><lt>7.0.11</lt></range> </package> - </package> </affects> <description> <body xmlns="http://www.w3.org/1999/xhtml"> @@ -119,6 +119,7 @@ <dates> <discovery>2024-12-12</discovery> <entry>2024-12-17</entry> + <modified>2024-12-18</modified> </dates> </vuln> @@ -139,7 +140,7 @@ 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. + 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 @@ -173,7 +174,7 @@ 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. + 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