Описание
Multiple cryptographic issues in Python oic
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.
Ссылки
- https://github.com/OpenIDC/pyoidc/security/advisories/GHSA-4fjv-pmhg-3rfg
- https://nvd.nist.gov/vuln/detail/CVE-2020-26244
- https://github.com/OpenIDC/pyoidc/commit/62f8d753fa17c8b1f29f8be639cf0b33afb02498
- https://github.com/OpenIDC/pyoidc/releases/tag/1.2.1
- https://github.com/pypa/advisory-database/tree/main/vulns/oic/PYSEC-2020-69.yaml
- https://pypi.org/project/oic
Пакеты
oic
< 1.2.1
1.2.1
EPSS
7.6 High
CVSS4
6.8 Medium
CVSS3
CVE ID
Дефекты
Связанные уязвимости
Python oic is a Python OpenID Connect implementation. In Python oic before version 1.2.1, there are several related cryptographic issues affecting client implementations that use the library. The issues are: 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). These issues are patched in version 1.2.1.
EPSS
7.6 High
CVSS4
6.8 Medium
CVSS3