CVE-2024-46989

spicedb is an Open Source, Google Zanzibar-inspired permissions database to enable fine-grained authorization for customer applications. Multiple caveats over the same indirect subject type on the same relation can result in no permission being returned when permission is expected. If the resource has multiple groups, and each group is caveated, it is possible for the returned permission to be "no permission" when permission is expected. Permission is returned as NO_PERMISSION when PERMISSION is expected on the CheckPermission API. This issue has been addressed in release version 1.35.3. Users are advised to upgrade. Users unable to upgrade should not use caveats or avoid the use of caveats on an indirect subject type with multiple entries.

CVSS v3 3.7 LOW

3.7^/10

CVSS v3 : LOW

Vector :

Exploitability : 2.2 / Impact : 1.4

Attack Vector NETWORK

Attack Complexity HIGH

Privileges Required NONE

User Interaction NONE

Confidentiality Impact NONE

Integrity Impact LOW

Availability Impact NONE

Scope UNCHANGED

References

Link	Resource
https://github.com/authzed/spicedb/commit/d4ef8e1dbce1eafaf25847f4c0f09738820f5bf2
https://github.com/authzed/spicedb/security/advisories/GHSA-jhg6-6qrx-38mr

Configurations

No configuration.

History

No history.

Information

Published : 2024-09-18 18:15

Updated : 2024-09-20 12:30

NVD link : CVE-2024-46989

Mitre link : CVE-2024-46989

CVE.ORG link : CVE-2024-46989

JSON object : View

Products Affected

No product.

CWE

CWE-269

Improper Privilege Management

{"id": "CVE-2024-46989", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 3.7, "attackVector": "NETWORK", "baseSeverity": "LOW", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N", "integrityImpact": "LOW", "userInteraction": "NONE", "attackComplexity": "HIGH", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}, "impactScore": 1.4, "exploitabilityScore": 2.2}]}, "published": "2024-09-18T18:15:07.650", "references": [{"url": "https://github.com/authzed/spicedb/commit/d4ef8e1dbce1eafaf25847f4c0f09738820f5bf2", "source": "security-advisories@github.com"}, {"url": "https://github.com/authzed/spicedb/security/advisories/GHSA-jhg6-6qrx-38mr", "source": "security-advisories@github.com"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Primary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-269"}]}], "descriptions": [{"lang": "en", "value": "spicedb is an Open Source, Google Zanzibar-inspired permissions database to enable fine-grained authorization for customer applications. Multiple caveats over the same indirect subject type on the same relation can result in no permission being returned when permission is expected. If the resource has multiple groups, and each group is caveated, it is possible for the returned permission to be \"no permission\" when permission is expected. Permission is returned as NO_PERMISSION when PERMISSION is expected on the CheckPermission API. This issue has been addressed in release version 1.35.3. Users are advised to upgrade. Users unable to upgrade should not use caveats or avoid the use of caveats on an indirect subject type with multiple entries."}, {"lang": "es", "value": "spicedb es una base de datos de permisos de c\u00f3digo abierto inspirada en Google Zanzibar que permite una autorizaci\u00f3n detallada para las aplicaciones de los clientes. Varias advertencias sobre el mismo tipo de sujeto indirecto en la misma relaci\u00f3n pueden provocar que no se devuelva ning\u00fan permiso cuando se espera que s\u00ed. Si el recurso tiene varios grupos y cada grupo tiene advertencias, es posible que el permiso devuelto sea \"sin permiso\" cuando se espera que s\u00ed. El permiso se devuelve como NO_PERMISSION cuando se espera PERMISSION en la API CheckPermission. Este problema se ha solucionado en la versi\u00f3n de lanzamiento 1.35.3. Se recomienda a los usuarios que actualicen la versi\u00f3n. Los usuarios que no puedan actualizar no deben utilizar advertencias o evitar el uso de advertencias en un tipo de sujeto indirecto con varias entradas."}], "lastModified": "2024-09-20T12:30:17.483", "sourceIdentifier": "security-advisories@github.com"}