{"vulnerability": "CVE-2024-48909", "sightings": [{"uuid": "a91279a8-d4ef-4201-b9a2-591eadae4e84", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-48909", "type": "seen", "source": "https://t.me/cvedetector/7860", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-48909 - SpiceDB Conditional Permission Context Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-48909 \nPublished : Oct. 14, 2024, 9:15 p.m. | 42\u00a0minutes ago \nDescription : SpiceDB is an open source database for scalably storing and querying fine-grained authorization data. Starting in version 1.35.0 and prior to version 1.37.1, clients that have enabled `LookupResources2` and have caveats in the evaluation path for their requests can return a permissionship of `CONDITIONAL` with context marked as missing, even then the context was supplied. LookupResources2 is the new default in SpiceDB 1.37.0 and has been opt-in since SpiceDB 1.35.0. The bug is patched as part of SpiceDB 1.37.1. As a workaround, disable LookupResources2 via the `--enable-experimental-lookup-resources` flag by setting it to `false`. \nSeverity: 2.0 | LOW \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"14 Oct 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-15T00:12:35.000000Z"}]}