CVE-2020-26244
Multiple cryptographic issues in Python oic
Auswirkung
### 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.
Ein Angreifer kann die Lücke über das Netzwerk ausnutzen, mit einem normalen Benutzerkonto, ohne Zutun eines Nutzers. Dafür müssen bestimmte Bedingungen erfüllt sein, was einen Angriff erschwert. Bei Erfolg: hohes Risiko, dass Daten ausgelesen werden, hohes Risiko, dass Daten oder Systeme verändert werden.
Betroffene Pakete
| Ökosystem | Paket | Betroffen | Behoben in |
|---|---|---|---|
| pip | oic | < 1.2.1 | 1.2.1 |
Betroffene Produkte · Python Openid Connect Project
| Produkt | Betroffene Versionen |
|---|---|
| Python Openid Connect | vor 1.2.1 |
Schwachstellenklasse
Referenzen
- NVD-Eintrag
- CVE.org-Eintrag
- GitHub-Advisory
- https://github.com/OpenIDC/pyoidc/commit/62f8d753fa17c8b1f29f8be639cf0b33afb02498
- https://github.com/OpenIDC/pyoidc/releases/tag/1.2.1
- https://github.com/OpenIDC/pyoidc/security/advisories/GHSA-4fjv-pmhg-3rfg
- https://pypi.org/project/oic/
- https://github.com/advisories/GHSA-4fjv-pmhg-3rfg
- https://nvd.nist.gov/vuln/detail/CVE-2020-26244
- https://github.com/pypa/advisory-database/tree/main/vulns/oic/PYSEC-2020-69.yaml
- https://pypi.org/project/oic