CVE-2020-26244: Oic Multiple Cryptographic Issues Vulnerability

HIGH
Advisory Identifier: GHSA-4fjv-pmhg-3rfg
Share
CVSS 6.8
CWE-325 CWE-347
Published
Advisory Summary

CVE-2020-26244 is a HIGH (CVSS 6.8) multiple cryptographic issues vulnerability (CWE-325: Missing Cryptographic Step) affecting Oic libraries in the PyPI ecosystem. The issue involves multiple cryptographic issues in python oic. Remediation is available by upgrading affected packages to version 1.2.1.

CVE-2020-26244 at a Glance

CVE Identifier CVE-2020-26244
GHSA Identifier GHSA-4fjv-pmhg-3rfg
Severity HIGH
CVSS v3.1 Base Score 6.8
CWE Classification CWE-325: Missing Cryptographic Step
Affected Product Oic
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 6.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2020-26244

To remediate this vulnerability, upgrade all affected Oic dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

oic fixed: 1.2.1 
pip install oic>=1.2.1
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

pip show oic

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2020-26244, inspect your installed packages using pip:

pip show oic

Analyze the terminal output to locate any version of Oic in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.2.1), your application is affected.

Note: The pip show oic command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-325: Missing Cryptographic Step, where the product does not implement a required step in a cryptographic algorithm, resulting in weaker encryption than advertised by the algorithm. In Oic, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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.

CVE-2020-26244 Affected Oic Versions

1 component(s)
Fixed Versions:
1.2.1
Product / Package Ecosystem Affected Versions Fixed Version
oic
pypi/oic
PyPI
< 1.2.1
1.2.1

References

pypi.org/project/oic WEB
https://pypi.org/project/oic
GitHub Advisory / Wiki ADVISORY
https://github.com/OpenIDC/pyoidc/security/advisories/GHSA-4fjv-pmhg-3rfg
NVD — CVE-2020-26244 NVD
https://nvd.nist.gov/vuln/detail/CVE-2020-26244
Security Fix Commit FIX COMMIT
https://github.com/OpenIDC/pyoidc/commit/62f8d753fa17c8b1f29f8be639cf0b33afb02498
Oic Source Repository REPOSITORY
https://github.com/OpenIDC/pyoidc
Oic Release RELEASE
https://github.com/OpenIDC/pyoidc/releases/tag/1.2.1
Oic Source Repository REPOSITORY
https://github.com/pypa/advisory-database/tree/main/vulns/oic/PYSEC-2020-69.yaml

Frequently Asked Questions

What is CVE-2020-26244?
CVE-2020-26244 is a security vulnerability in Oic involving Multiple cryptographic issues in Python oic under CWE-325: Missing Cryptographic Step.
Which Oic versions are affected?
Affected versions include releases prior to 1.2.1 across affected packages: oic.
What version fixes CVE-2020-26244?
Upgrading to 1.2.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is oic affected?
Yes, oic is affected in releases prior to 1.2.1. Upgrade your dependency to 1.2.1 or later.
What is the CVSS score of CVE-2020-26244?
CVE-2020-26244 has a CVSS v3.1 base score of 6.8 (HIGH) with vector string CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N.
What CWE is associated with CVE-2020-26244?
CVE-2020-26244 is classified under CWE-325: Missing Cryptographic Step (The product does not implement a required step in a cryptographic algorithm, resulting in weaker encryption than advertised by the algorithm.).
How can I check PyPI dependencies for CVE-2020-26244?
Run the dependency tree command: 'pip show oic'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-4fjv-pmhg-3rfg",
  "modified" : "2024-10-07T21:07:21Z",
  "published" : "2020-12-04T16:47:12Z",
  "aliases" : [ "CVE-2020-26244" ],
  "summary" : "Multiple cryptographic issues in Python oic",
  "details" : "### Impact\n* Client implementations using this library\n\n### Issues\n1) The IdToken signature algorithm was not checked automatically, but only if the expected algorithm was passed in as a kwarg.\n2) JWA `none` algorithm was allowed in all flows.\n3) `oic.consumer.Consumer.parse_authz` returns an unverified IdToken. The verification of the token was left to the discretion of the implementator.\n4) `iat` claim was not checked for sanity (i.e. it could be in the future)\n\n### Patches\n1) IdToken signature is now always checked.\n2) JWA `none` algorithm is now allowed only if using the `response_type` `code`\n3) IdToken verification is now done automatically.\n4) `iat` claim is now checked for sanity.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N"
  }, {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "oic"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.2.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/OpenIDC/pyoidc/security/advisories/GHSA-4fjv-pmhg-3rfg"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2020-26244"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/OpenIDC/pyoidc/commit/62f8d753fa17c8b1f29f8be639cf0b33afb02498"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/OpenIDC/pyoidc"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/OpenIDC/pyoidc/releases/tag/1.2.1"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/pypa/advisory-database/tree/main/vulns/oic/PYSEC-2020-69.yaml"
  }, {
    "type" : "WEB",
    "url" : "https://pypi.org/project/oic"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-325", "CWE-347" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2020-12-02T20:06:06Z",
    "nvd_published_at" : null
  }
}