Approved changes feed: RSS · Atom
cpe:2.3:a:openidc:pyoidc:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Openidc (ee2aeb60-bc45-5177-8b2e-2be2efdd818e) |
|---|---|
| Product | Pyoidc (20dee298-ff10-5916-923c-c599207cf6a2) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2020-26244 |
vulnerable | 2026-06-08 05:23:50.952791 |
Cryptographic issues in Python oic
MEDIUM (6.8)
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.
Published: 2020-12-02T20:05:15.000Z
Updated: 2024-08-04T15:56:04.228Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.