Conversation
| <!-- Following must be updated along with any updates to pac4j version. One can find the compatible version of nimbus libraries in org.pac4j:pac4j-oidc dependencies--> | ||
| <nimbus.lang.tag.version>1.7</nimbus.lang.tag.version> | ||
| <nimbus.jose.jwt.version>8.22.1</nimbus.jose.jwt.version> | ||
| <nimbus.jose.jwt.version>9.37.2</nimbus.jose.jwt.version> |
There was a problem hiding this comment.
is it compatible with pac4j-oidc dependency currently in use?
There was a problem hiding this comment.
Cannot infer compatibility as the maven page just lists the dependency for a specified version -- which was the earlier version. I've updated pac4j-oidc also to 5.7.3 which lists 9.37.2 as its dependency, and the version of oauth2.oidc.sdk.version corresponding to it as well.
There was a problem hiding this comment.
Tried multiple versions of pac4j (6.0.1, 5.7.3, 5.3.1) but all are failing compilation, so reverting it to the original version.
| <!-- Covers DOS on identity server by triggering high resource consumption. Used in Azure as a client. | ||
| Current latest version of Azure BOM (1.2.21) still uses 9.30.2, whereas bug resolved in 9.37.3 --> |
There was a problem hiding this comment.
The reasoning is a bit cryptic. Do you mean to say that CVE only impacts the server but not the client?
There was a problem hiding this comment.
Not clear about that. Simplified the comment to just say that the latest version of BOM still uses vulnerable dependency.
Suppress the following CVE errors: