CVE-2024-38361

Spicedb is an Open Source, Google Zanzibar-inspired permissions database to enable fine-grained authorization for customer applications. Use of an exclusion under an arrow that has multiple resources may resolve to `NO_PERMISSION` when permission is expected. If the resource exists under *multiple* folders and the user has access to view more than a single folder, SpiceDB may report the user does not have access due to a failure in the exclusion dispatcher to request that *all* the folders in which the user is a member be returned. Permission is returned as `NO_PERMISSION` when `PERMISSION` is expected on the `CheckPermission` API. This issue has been addressed in version 1.33.1. All users are advised to upgrade. There are no known workarounds for this issue.

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/ecef31d2b266fde17eb2c3415e2ec4ceff96fbeb
https://github.com/authzed/spicedb/security/advisories/GHSA-grjv-gjgr-66g2

Configurations

No configuration.

History

No history.

Information

Published : 2024-06-20 23:15

Updated : 2024-06-21 11:22

NVD link : CVE-2024-38361

Mitre link : CVE-2024-38361

CVE.ORG link : CVE-2024-38361

JSON object : View

Products Affected

No product.

CWE

CWE-281

Improper Preservation of Permissions

{"id": "CVE-2024-38361", "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-06-20T23:15:52.930", "references": [{"url": "https://github.com/authzed/spicedb/commit/ecef31d2b266fde17eb2c3415e2ec4ceff96fbeb", "source": "security-advisories@github.com"}, {"url": "https://github.com/authzed/spicedb/security/advisories/GHSA-grjv-gjgr-66g2", "source": "security-advisories@github.com"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-281"}]}], "descriptions": [{"lang": "en", "value": "Spicedb is an Open Source, Google Zanzibar-inspired permissions database to enable fine-grained authorization for customer applications. Use of an exclusion under an arrow that has multiple resources may resolve to `NO_PERMISSION` when permission is expected. If the resource exists under *multiple* folders and the user has access to view more than a single folder, SpiceDB may report the user does not have access due to a failure in the exclusion dispatcher to request that *all* the folders in which the user is a member be returned. Permission is returned as `NO_PERMISSION` when `PERMISSION` is expected on the `CheckPermission` API. This issue has been addressed in version 1.33.1. All users are advised to upgrade. There are no known workarounds for this issue."}, {"lang": "es", "value": "Spicedb es una base de datos de permisos de c\u00f3digo abierto inspirada en Google Zanz\u00edbar para permitir una autorizaci\u00f3n detallada para las aplicaciones de los clientes. El uso de una exclusi\u00f3n debajo de una flecha que tiene m\u00faltiples recursos puede resolverse como \"NO_PERMISSION\" cuando se espera permiso. Si el recurso existe en *m\u00faltiples* carpetas y el usuario tiene acceso para ver m\u00e1s de una carpeta, SpiceDB puede informar que el usuario no tiene acceso debido a una falla en el despachador de exclusi\u00f3n al solicitar que *todas* las carpetas en las que se encuentra el recurso. El usuario es miembro y se devolver\u00e1. El permiso se devuelve como \"NO_PERMISSION\" cuando se espera \"PERMISSION\" en la API \"CheckPermission\". Este problema se solucion\u00f3 en la versi\u00f3n 1.33.1. Se recomienda a todos los usuarios que actualicen. No se conocen workarounds para este problema."}], "lastModified": "2024-06-21T11:22:01.687", "sourceIdentifier": "security-advisories@github.com"}