{"answers":{"affected":"3 open source packages ship an affected version, including github.com/authzed/spicedb. It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-48909 in the wild and no public exploit code.","fix":"Upgrade github.com/authzed/spicedb to 1.37.1 or later.","what":"CVE-2024-48909 is a low-severity vulnerability in authzed spicedb, published on 14 Oct 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-48909 and fix it if it is affected.\n\nWhat it is: CVE-2024-48909 is a low-severity vulnerability in authzed spicedb, published on 14 Oct 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2024-48909 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/authzed/spicedb (Go): affected from 1.35.0; fixed in 1.37.1\n- github.com/authzed/spicedb (Go): affected from 1.35.0; fixed in 1.37.1\n- github.com/authzed/spicedb (Go): affected from 1.35.0; fixed in 1.37.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-48909/ (Markdown: https://insights.sbomify.com/CVE-2024-48909/index.md)","id":"CVE-2024-48909","markdown":"https://insights.sbomify.com/CVE-2024-48909/index.md","name":"CVE-2024-48909","record":{"aliases":["GHSA-3c32-4hq9-6wgj","GO-2024-3200"],"analysis":{"component_type":"database","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"SpiceDB authorization database","requires_auth":"high_privilege","summary":"SpiceDB may incorrectly report missing context for conditional permissions, potentially leading to incorrect authorization decisions.","user_interaction":"required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"spicedb","vendor":"authzed"}],"cvss":{"score":2,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-172","name":"Improper Encoding or Decoding of Data"}],"description":"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`.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"SpiceDB calls to LookupResources using LookupResources2 with caveats may return context is missing when it is not","id":"CVE-2024-48909","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"business_logic","year":"2024"},"n_packages":3,"n_references":2,"next":{"headline":"DOMPurify vulnerable to tampering by prototype polution","id":"CVE-2024-48910"},"packages":[{"ecosystem":"Go","fixed":["1.37.1"],"introduced":["1.35.0"],"last_affected":[],"package":"github.com/authzed/spicedb","purl":null,"source":"GHSA-3c32-4hq9-6wgj"},{"ecosystem":"Go","fixed":["1.37.1"],"introduced":["1.35.0"],"last_affected":[],"package":"github.com/authzed/spicedb","purl":"pkg:golang/github.com/authzed/spicedb","source":"GHSA-3c32-4hq9-6wgj"},{"ecosystem":"Go","fixed":["1.37.1"],"introduced":["1.35.0"],"last_affected":[],"package":"github.com/authzed/spicedb","purl":"pkg:golang/github.com/authzed/spicedb","source":"GO-2024-3200"}],"prev":{"headline":"lychee-action vulnerable to arbitrary code injection in composite action","id":"CVE-2024-48908"},"products":["spicedb"],"published":"2024-10-14","related":[{"cvss_score":8.7,"headline":"SpiceDB binding metrics port to untrusted networks and can leak command-line flags","id":"CVE-2023-29193","kev_date_added":null,"published":"2023-04-14"},{"cvss_score":8.1,"headline":"Lookup operations do not take into account wildcards in SpiceDB","id":"CVE-2022-21646","kev_date_added":null,"published":"2022-01-11"},{"cvss_score":7.3,"headline":"Integer overflow in chunking helper causes dispatching to miss elements or panic","id":"CVE-2024-27101","kev_date_added":null,"published":"2024-03-01"},{"cvss_score":6,"headline":"SpiceDB: SPICEDB_DATASTORE_CONN_URI is leaked on startup logs","id":"CVE-2026-40091","kev_date_added":null,"published":"2026-04-14"},{"cvss_score":4.2,"headline":"`SPICEDB_DATASTORE_CONN_URI` is leaked when URI cannot be parsed","id":"CVE-2023-46255","kev_date_added":null,"published":"2023-10-31"},{"cvss_score":3.7,"headline":"SpiceDB checks involving relations with caveats can result in no permission when permission is expected","id":"CVE-2025-49011","kev_date_added":null,"published":"2025-06-06"},{"cvss_score":3.7,"headline":"Multiple caveats on resources of the same type can result in no permission when permission is expected","id":"CVE-2024-46989","kev_date_added":null,"published":"2024-09-18"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-10-15","vendors":["authzed"]},"summary":"SpiceDB may incorrectly report missing context for conditional permissions, potentially leading to incorrect authorization decisions.","url":"https://insights.sbomify.com/CVE-2024-48909/"}