PYSEC-2020-69
Vulnerability from pysec - Published: 2020-12-02 20:15 - Updated: 2020-12-08 02:37Python 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.
| Name | purl | oic | pkg:pypi/oic |
|---|
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "oic",
"purl": "pkg:pypi/oic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "62f8d753fa17c8b1f29f8be639cf0b33afb02498"
}
],
"repo": "https://github.com/OpenIDC/pyoidc",
"type": "GIT"
},
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.2.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.4.0",
"0.5.0",
"0.6.0",
"0.7.0",
"0.7.2",
"0.7.3",
"0.7.4",
"0.7.5",
"0.7.6",
"0.7.7",
"0.7.8",
"0.8.1",
"0.8.2",
"0.8.3",
"0.8.4.0",
"0.8.5.0",
"0.9.0.0",
"0.9.1.0",
"0.9.4.0",
"0.9.5.0",
"0.10.0.0",
"0.11.0.0",
"0.11.0.1",
"0.12.0",
"0.13.0",
"0.13.1",
"0.14.0",
"0.15.0",
"0.15.1",
"1.0.0",
"1.0.1",
"1.1.0",
"1.1.1",
"1.1.2",
"1.2.0"
]
}
],
"aliases": [
"CVE-2020-26244",
"GHSA-4fjv-pmhg-3rfg"
],
"details": "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.",
"id": "PYSEC-2020-69",
"modified": "2020-12-08T02:37:00Z",
"published": "2020-12-02T20:15:00Z",
"references": [
{
"type": "ADVISORY",
"url": "https://github.com/OpenIDC/pyoidc/security/advisories/GHSA-4fjv-pmhg-3rfg"
},
{
"type": "FIX",
"url": "https://github.com/OpenIDC/pyoidc/commit/62f8d753fa17c8b1f29f8be639cf0b33afb02498"
},
{
"type": "PACKAGE",
"url": "https://pypi.org/project/oic/"
},
{
"type": "WEB",
"url": "https://github.com/OpenIDC/pyoidc/releases/tag/1.2.1"
}
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.