{"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-2022-21646 in the wild and no public exploit code.","fix":"Upgrade github.com/authzed/spicedb to 1.4.0 or later.","what":"CVE-2022-21646 is a high-severity vulnerability in authzed spicedb, published on 11 Jan 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-21646 and fix it if it is affected.\n\nWhat it is: CVE-2022-21646 is a high-severity vulnerability in authzed spicedb, published on 11 Jan 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-21646 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/authzed/spicedb (Go): affected from 1.3.0; fixed in 1.4.0\n- github.com/authzed/spicedb (Go): affected from 1.3.0; fixed in 1.4.0\n- github.com/authzed/spicedb (Go): affected from 1.3.0; fixed in 1.4.0\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-2022-21646/ (Markdown: https://insights.sbomify.com/CVE-2022-21646/index.md)","id":"CVE-2022-21646","markdown":"https://insights.sbomify.com/CVE-2022-21646/index.md","name":"CVE-2022-21646","record":{"aliases":["GHSA-7p8f-8hjm-wm92","GO-2022-0295"],"analysis":{"component_type":"database","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"SpiceDB permission database","requires_auth":"low_privilege","summary":"Attackers can bypass permission checks in SpiceDB when wildcards are used in exclusions or intersections, gaining unauthorized access to resources.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"spicedb","vendor":"authzed"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"},{"id":"CWE-155","name":"Improper Neutralization of Wildcards or Matching Symbols"}],"description":"SpiceDB is a database system for managing security-critical application permissions. Any user making use of a wildcard relationship under the right hand branch of an `exclusion` or within an `intersection` operation will see `Lookup`/`LookupResources` return a resource as \"accessible\" if it is *not* accessible by virtue of the inclusion of the wildcard in the intersection or the right side of the exclusion. In `v1.3.0`, the wildcard is ignored entirely in lookup's dispatch, resulting in the `banned` wildcard being ignored in the exclusion. Version 1.4.0 contains a patch for this issue. As a workaround, don't make use of wildcards on the right side of intersections or within exclusions.","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":"Lookup operations do not take into account wildcards in SpiceDB","id":"CVE-2022-21646","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"business_logic","year":"2022"},"n_packages":3,"n_references":4,"next":{"headline":"Deserialization of Untrusted Data in Codeigniter4","id":"CVE-2022-21647"},"packages":[{"ecosystem":"Go","fixed":["1.4.0"],"introduced":["1.3.0"],"last_affected":[],"package":"github.com/authzed/spicedb","purl":null,"source":"GHSA-7p8f-8hjm-wm92"},{"ecosystem":"Go","fixed":["1.4.0"],"introduced":["1.3.0"],"last_affected":[],"package":"github.com/authzed/spicedb","purl":"pkg:golang/github.com/authzed/spicedb","source":"GHSA-7p8f-8hjm-wm92"},{"ecosystem":"Go","fixed":["1.4.0"],"introduced":["1.3.0"],"last_affected":[],"package":"github.com/authzed/spicedb","purl":"pkg:golang/github.com/authzed/spicedb","source":"GO-2022-0295"}],"prev":{"headline":"SQL Injection via search in USOC","id":"CVE-2022-21644"},"products":["spicedb"],"published":"2022-01-11","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":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":"total"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["authzed"]},"summary":"Attackers can bypass permission checks in SpiceDB when wildcards are used in exclusions or intersections, gaining unauthorized access to resources.","url":"https://insights.sbomify.com/CVE-2022-21646/"}