Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
GHSA-4fjv-pmhg-3rfg
No affected components available
Impact
- Client implementations using this library
Issues
- The IdToken signature algorithm was not checked automatically, but only if the expected algorithm was passed in as a kwarg.
- JWA
nonealgorithm was allowed in all flows. oic.consumer.Consumer.parse_authzreturns an unverified IdToken. The verification of the token was left to the discretion of the implementator.iatclaim was not checked for sanity (i.e. it could be in the future)
Patches
- IdToken signature is now always checked.
- JWA
nonealgorithm is now allowed only if using theresponse_typecode - IdToken verification is now done automatically.
iatclaim is now checked for sanity.
The vulnerability can be exploited over the network without needing physical access. It is difficult for an attacker to exploit this vulnerability and may require special conditions. An attacker needs basic access or low-level privileges. No user interaction is needed for the attacker to exploit this vulnerability. The impact is confined to the system where the vulnerability exists. There is a high impact on the confidentiality of the information. There is a high impact on the integrity of the data.
Exploitation attempts have been detected. Elevated vigilance and prompt remediation are advised.
The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Browse More
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard