CVE-2024-32001

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.

CVSS v3 2.2 LOW

2.2^/10

CVSS v3 : LOW

Vector :

Exploitability : 0.7 / Impact : 1.4

Attack Vector NETWORK

Attack Complexity HIGH

Privileges Required HIGH

User Interaction NONE

Confidentiality Impact NONE

Integrity Impact LOW

Availability Impact NONE

Scope UNCHANGED

References

Link	Resource
https://github.com/authzed/spicedb/commit/a244ed1edfaf2382711dccdb699971ec97190c7b
https://github.com/authzed/spicedb/releases/tag/v1.30.1
https://github.com/authzed/spicedb/security/advisories/GHSA-j85q-46hg-36p2

Configurations

No configuration.

History

No history.

Information

Published : 2024-04-10 23:15

Updated : 2024-04-11 12:47

NVD link : CVE-2024-32001

Mitre link : CVE-2024-32001

CVE.ORG link : CVE-2024-32001

JSON object : View

Products Affected

No product.

CWE

CWE-755

Improper Handling of Exceptional Conditions

{"id": "CVE-2024-32001", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 2.2, "attackVector": "NETWORK", "baseSeverity": "LOW", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:N", "integrityImpact": "LOW", "userInteraction": "NONE", "attackComplexity": "HIGH", "availabilityImpact": "NONE", "privilegesRequired": "HIGH", "confidentialityImpact": "NONE"}, "impactScore": 1.4, "exploitabilityScore": 0.7}]}, "published": "2024-04-10T23:15:07.363", "references": [{"url": "https://github.com/authzed/spicedb/commit/a244ed1edfaf2382711dccdb699971ec97190c7b", "source": "security-advisories@github.com"}, {"url": "https://github.com/authzed/spicedb/releases/tag/v1.30.1", "source": "security-advisories@github.com"}, {"url": "https://github.com/authzed/spicedb/security/advisories/GHSA-j85q-46hg-36p2", "source": "security-advisories@github.com"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-755"}]}], "descriptions": [{"lang": "en", "value": "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.\n"}, {"lang": "es", "value": "SpiceDB es una base de datos gr\u00e1fica manipulada espec\u00edficamente para almacenar y evaluar datos de control de acceso. Uso de una relaci\u00f3n de la forma: `relation folder: folder | folder#parent` con una flecha como `folder->view` puede hacer que LookupSubjects solo devuelva los asuntos encontrados en los asuntos de `folder` o `folder#parent`. Este error solo se manifiesta si el mismo tipo de asunto se usa en varios tipos en una relaci\u00f3n, existen relaciones para ambos tipos de asunto y se usa una flecha sobre la relaci\u00f3n. Cualquier usuario que tome una decisi\u00f3n de autorizaci\u00f3n negativa basada en los resultados de una solicitud de LookupSubjects con una versi\u00f3n anterior a la v1.30.1 se ver\u00e1 afectado. La versi\u00f3n 1.30.1 contiene un parche para el problema. Como workaround, evite el uso de LookupSubjects para decisiones de autorizaci\u00f3n negativas y/o evite el uso del esquema roto."}], "lastModified": "2024-04-11T12:47:44.137", "sourceIdentifier": "security-advisories@github.com"}