Skip to content

Multiple cryptographic issues in Python oic

Moderate severity GitHub Reviewed Published Dec 1, 2020 in CZ-NIC/pyoidc • Updated Jan 9, 2023

Package

pip oic (pip)

Affected versions

< 1.2.1

Patched versions

1.2.1

Description

Impact

  • Client implementations using this library

Issues

  1. The IdToken signature algorithm was not checked automatically, but only if the expected algorithm was passed in as a kwarg.
  2. JWA none algorithm was allowed in all flows.
  3. oic.consumer.Consumer.parse_authz returns an unverified IdToken. The verification of the token was left to the discretion of the implementator.
  4. iat claim was not checked for sanity (i.e. it could be in the future)

Patches

  1. IdToken signature is now always checked.
  2. JWA none algorithm is now allowed only if using the response_type code
  3. IdToken verification is now done automatically.
  4. iat claim is now checked for sanity.

References

@tpazderka tpazderka published to CZ-NIC/pyoidc Dec 1, 2020
Reviewed Dec 2, 2020
Published to the GitHub Advisory Database Dec 4, 2020
Last updated Jan 9, 2023

Severity

Moderate
6.8
/ 10

CVSS base metrics

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N

CVE ID

CVE-2020-26244

GHSA ID

GHSA-4fjv-pmhg-3rfg

Source code

No known source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.