https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 06 Oct 2026 05:14:13 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-136371 EUVD-2026-136371 https://cve.radiocsirt.org/vuln/euvd-2026-136371 https://cve.radiocsirt.org/vuln/fkie_cve-2024-41948 <p>biscuit-java is the java implementation of Biscuit, an authentication and authorization token for microservices architectures. Third-party blocks can be generated without transferring the whole token to the third-party authority. Instead, a ThirdPartyBlock request can be sent, providing only the necessary info to generate a third-party block and to sign it, which includes the public key of the previous block (used in the signature) and the public keys part of the token symbol table (for public key interning in datalog expressions). A third-part block request forged by a malicious user can trick the third-party authority into generating datalog trusting the wrong keypair. This vulnerability is fixed in 4.0.0.</p> <p>biscuit-java is the java implementation of Biscuit, an authentication and authorization token for microservices architectures. Third-party blocks can be generated without transferring the whole token to the third-party authority. Instead, a ThirdPartyBlock request can be sent, providing only the necessary info to generate a third-party block and to sign it, which includes the public key of the previous block (used in the signature) and the public keys part of the token symbol table (for public key interning in datalog expressions). A third-part block request forged by a malicious user can trick the third-party authority into generating datalog trusting the wrong keypair. This vulnerability is fixed in 4.0.0.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2024-41948 https://cve.radiocsirt.org/vuln/ghsa-5hcj-rwm6-xmw4 <p><strong>Affected:</strong> Maven: org.biscuitsec:biscuit</p> <p>### Impact Tokens with third-party blocks containing trusted annotations generated through a third party block request. Due to implementation issues in biscuit-java, third party block support in published versions is inoperating. Nevertheless, to synchronize with other implementations, we publish this advisory and the related fix.</p> <p>### Description Third-party blocks can be generated without transferring the whole token to the third-party authority. Instead, a `ThirdPartyBlock` request can be sent, providing only the necessary info to generate a third-party block and to sign it:</p> <p>the public key of the previous block (used in the signature) the public keys part of the token symbol table (for public key interning in datalog expressions) A third-part block request forged by a malicious user can trick the third-party authority into generating datalog trusting the wrong keypair.</p> <p>Consider the following example (nominal case) * Authority A emits the following token: `check if thirdparty(&#34;b&#34;) trusting ${pubkeyB}` * The well-behaving holder then generates a third-party block request based on the token and sends it to third-party authority B * Third-party B generates the following third-party block `thirdparty(&#34;b&#34;); check if thirdparty(&#34;c&#34;) trusting ${pubkeyC}` * The token holder now must obtain a third-party block from third party C to be able to use the token</p> <p>Now, with a malicious user: * Authority A emits the following token: `check if thirdparty(&#34;b&#34;) trusting ${pubkeyB}` * The h…</p> <p><strong>Affected:</strong> Maven: org.biscuitsec:biscuit</p> <p>### Impact Tokens with third-party blocks containing trusted annotations generated through a third party block request. Due to implementation issues in biscuit-java, third party block support in published versions is inoperating. Nevertheless, to synchronize with other implementations, we publish this advisory and the related fix.</p> <p>### Description Third-party blocks can be generated without transferring the whole token to the third-party authority. Instead, a `ThirdPartyBlock` request can be sent, providing only the necessary info to generate a third-party block and to sign it:</p> <p>the public key of the previous block (used in the signature) the public keys part of the token symbol table (for public key interning in datalog expressions) A third-part block request forged by a malicious user can trick the third-party authority into generating datalog trusting the wrong keypair.</p> <p>Consider the following example (nominal case) * Authority A emits the following token: `check if thirdparty(&#34;b&#34;) trusting ${pubkeyB}` * The well-behaving holder then generates a third-party block request based on the token and sends it to third-party authority B * Third-party B generates the following third-party block `thirdparty(&#34;b&#34;); check if thirdparty(&#34;c&#34;) trusting ${pubkeyC}` * The token holder now must obtain a third-party block from third party C to be able to use the token</p> <p>Now, with a malicious user: * Authority A emits the following token: `check if thirdparty(&#34;b&#34;) trusting ${pubkeyB}` * The h…</p> https://cve.radiocsirt.org/vuln/ghsa-5hcj-rwm6-xmw4