https://db.gcve.eu/sightings/feed 2026-05-04T07:10:41.824116+00:00 Vulnerability-Lookup info@gcve.eu python-feedgen Contains only the most 10 recent sightings. https://db.gcve.eu/sighting/c3fc0282-4877-46fe-9478-29fe72e4c9ef/export 2026-05-04T07:10:42.286665+00:00 cedric http://db.gcve.eu/user/cedric {"uuid": "c3fc0282-4877-46fe-9478-29fe72e4c9ef", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-42350", "type": "seen", "source": "https://t.me/cvedetector/2487", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-42350 - Biscuit Third-Party Block Request Forgery Unauthorized Key Trusting\", \n \"Content\": \"CVE ID : CVE-2024-42350 \nPublished : Aug. 5, 2024, 8:15 p.m. | 38\u00a0minutes ago \nDescription : Biscuit is an authorization token with decentralized verification, offline attenuation and strong security policy enforcement based on a logic language. 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: 1. the public key of the previous block (used in the signature), 2. 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. Tokens with third-party blocks containing `trusted` annotations generated through a third party block request. This has been addressed in version 4 of the specification. Users are advised to update their implementations to conform. There are no known workarounds for this vulnerability. \nSeverity: 3.0 | LOW \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"05 Aug 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-05T23:06:41.000000Z"} 2024-08-05T23:06:41+00:00