Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2020-26244

Vulnerability in oic (CVE-2020-26244)

Summary

Vulnerability in oic (CVE-2020-26244). Confidential information can be exposed externally. Exploitable via none. Mitigation: upgrade to 1.2.1 or later.

Original description

The description as published by the source.

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.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2020-26244 has been found in oic.
Attackers can target a specific entry point like none over the network to misuse the product.
Confidential information can be exposed externally.
What to do: upgrade oic to 1.2.1 or later.
If unsure, ask your IT team or search "oic CVE-2020-26244" on the vendor's site.

CVE-2020-26244 (oic) — CWE-325
Attack vector: remote (network-reachable) / no user interaction
Attack surface: none / oic.consumer.Consumer.parse_authz / iat / response_type
Patched: 1.2.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-325) exists in oic. Attackers reach the vulnerable code path via none.

📍 Affected scope

Check the vendor advisory for the affected versions of oic. Attack surface: none / oic.consumer.Consumer.parse_authz / iat / response_type.

🔥 Severity

Severity: ?. Confidential information can be exposed externally.

🔧 How to fix

Update to 1.2.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'oic' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'oic' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で oic を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade oic to 1.2.1

    ステージング環境で 1.2.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

PyPI oic
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.2.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details