Описание
Cedar-Java has policy injection, type confusion, and incorrect equality comparison vulnerabilities
Summary
CedarJava is an open source Java implementation of the Cedar policy language, used for fine-grained authorization decisions. Under certain circumstances, it could lead to incorrect equality comparisons.
Impact
EntityIdentifier.equals() has inverted null/self branches
The EntityIdentifier.equals() method has inverted logic for null and self-reference checks, returning true for null comparisons and false for self-comparisons. This does not affect Cedar authorization decisions (computed in Rust from JSON), but could affect integrators who perform their own equality checks on entity identifiers.
Impacted versions:
< 4.9
Patches
It has been addressed in CedarJava version 4.9 and above. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes.
Workarounds
Avoid relying on EntityIdentifier.equals() for security-sensitive comparisons until upgraded to version 4.9.
References
If you have any questions or comments about this advisory, Cedar asks that you contact us directly via email to cedar-policy-security@lists.cncf.io. Please do not create a public GitHub issue.
Пакеты
com.cedarpolicy:cedar-java
< 2.3.6
2.3.6
com.cedarpolicy:cedar-java
>= 3.1.2, < 3.4.1
3.4.1
com.cedarpolicy:cedar-java
>= 4.0.0, < 4.9.0
4.9.0
Связанные уязвимости
CedarJava is an open source Java implementation of the Cedar policy language, used for fine-grained authorization decisions. In versions prior to 4.9.0, the EntityIdentifier.equals() has inverted null/self branches which could lead to incorrect equality comparisons. The EntityIdentifier.equals() method has inverted logic for null and self-reference checks, returning true for null comparisons and false for self-comparisons. This does not affect Cedar authorization decisions (computed in Rust from JSON), but could affect integrators who perform their own equality checks on entity identifiers. This issue has been fixed in version 4.9.0.