Impact
Any user making a negative authorization decision based on the results of a LookupResources request with 1.22.0 is affected.
For example, using LookupResources to find a list of resources to allow access to be okay: some subjects that should have access to a resource may not. But if using LookupResources to find a list of banned resources instead, then some users that shouldn't have access may.
Generally, LookupResources is not and should not be used to gate access in this way - that's what the Check API is for. Additionally, version 1.22.0 has included a warning about this bug since its initial release.
Workarounds
Avoid using LookupResources for negative authorization decisions if using 1.22.0.
Patches
The only affected release is v1.22.0, and it is patched in v1.22.2 (there is no v1.22.1 release, though there is a git tag).
References
For more information
If you have any questions or comments about this advisory:
References
Impact
Any user making a negative authorization decision based on the results of a LookupResources request with 1.22.0 is affected.
For example, using
LookupResourcesto find a list of resources to allow access to be okay: some subjects that should have access to a resource may not. But if usingLookupResourcesto find a list of banned resources instead, then some users that shouldn't have access may.Generally,
LookupResourcesis not and should not be used to gate access in this way - that's what theCheckAPI is for. Additionally, version 1.22.0 has included a warning about this bug since its initial release.Workarounds
Avoid using
LookupResourcesfor negative authorization decisions if using1.22.0.Patches
The only affected release is v1.22.0, and it is patched in v1.22.2 (there is no v1.22.1 release, though there is a git tag).
References
For more information
If you have any questions or comments about this advisory:
References