CVE-2024-46989 Multiple caveats on resources of the same type can result in no permission when permission is expected

Low 3.7 Published Updated

Attackers can bypass authorization checks in SpiceDB when multiple caveats are applied to the same resource type, resulting in unexpected permission denials.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2024-46989?

CVE-2024-46989 is a low-severity missing authorization vulnerability in authzed spicedb, published on 18 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

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.

Weakness: CWE-269

Which versions are affected by CVE-2024-46989?

3 open source packages ship an affected version, including github.com/authzed/spicedb. It affects 1 product.

PackageAffectedFixed in
github.com/authzed/spicedb GoAll versions1.35.3
github.com/authzed/spicedb GoAll versions1.35.3
github.com/authzed/spicedb GoAll versions1.35.3

Products include Authzed Spicedb.

How do I fix CVE-2024-46989?

Upgrade github.com/authzed/spicedb to 1.35.3 or later.

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

Is CVE-2024-46989 being exploited?

There is no known exploitation of CVE-2024-46989 in the wild and no public exploit code.

Sources

Also known as GHSA-jhg6-6qrx-38mr, GO-2024-3131.

Is CVE-2024-46989 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free