Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

x/vulndb: potential Go vuln in github.com/authzed/spicedb: CVE-2024-32001 #2720

Closed
GoVulnBot opened this issue Apr 11, 2024 · 1 comment
Closed

Comments

@GoVulnBot
Copy link

CVE-2024-32001 references github.com/authzed/spicedb, which may be a Go module.

Description:
SpiceDB is a graph database purpose-built for storing and evaluating access control data. Use of a relation of the form: relation folder: folder | folder#parent with an arrow such as folder->view can cause LookupSubjects to only return the subjects found under subjects for either folder or folder#parent. This bug only manifests if the same subject type is used multiple types in a relation, relationships exist for both subject types and an arrow is used over the relation. Any user making a negative authorization decision based on the results of a LookupSubjects request with version before v1.30.1 is affected. Version 1.30.1 contains a patch for the issue. As a workaround, avoid using LookupSubjects for negative authorization decisions and/or avoid using the broken schema.

References:

Cross references:

See doc/triage.md for instructions on how to triage this report.

id: GO-ID-PENDING
modules:
    - module: github.com/authzed/spicedb
      vulnerable_at: 1.30.1
      packages:
        - package: spicedb
cves:
    - CVE-2024-32001
references:
    - advisory: https://github.com/authzed/spicedb/security/advisories/GHSA-j85q-46hg-36p2
    - fix: https://github.com/authzed/spicedb/commit/a244ed1edfaf2382711dccdb699971ec97190c7b
    - web: https://github.com/authzed/spicedb/releases/tag/v1.30.1

@tatianab
Copy link
Contributor

Duplicate of #2716

@tatianab tatianab marked this as a duplicate of #2716 Apr 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants