Vulnerability in com.okta.sdk:okta-sdk-root (CVE-2025-67505)
Summary
Vulnerability in com.okta.sdk:okta-sdk-root (CVE-2025-67505). Confidential information can be exposed externally. Mitigation: upgrade to 20.0.1 or later.
Original description
The description as published by the source.
Description
In the Okta Java SDK, race conditions may arise from concurrent requests using the ApiClient class. This could cause a status code or response header from one request’s response to influence another request’s response.
Affected product and versions
You may be affected if you meet the following preconditions:
- Using the Okta Java SDK between versions 11.0.0 and 20.0.0, and
- Implementing a multithreaded application with the ApiClient class where the response status code is used in access control flows
Resolution
Upgrade Okta/okta-sdk-java to versions 21.0.0 or greater.
Source: NIST National Vulnerability Database NVD GitHub Advisory
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-2025-67505 has been found in com.okta.sdk:okta-sdk-root.
Confidential information can be exposed externally. CVSS score: 8.4/10.
What to do: upgrade com.okta.sdk:okta-sdk-root to 20.0.1 or later.
If unsure, ask your IT team or search "com.okta.sdk:okta-sdk-root CVE-2025-67505" on the vendor's site.
CVE-2025-67505 (com.okta.sdk:okta-sdk-root) — CWE-362 / CVSS v3 8.4
Attack vector: remote (network-reachable) / no user interaction
Patched: 20.0.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.
A vulnerability (CWE-362) exists in com.okta.sdk:okta-sdk-root.
Check the vendor advisory for the affected versions of com.okta.sdk:okta-sdk-root.
Severity: High (CVSS 8.4/10). Confidential information can be exposed externally.
Update to 20.0.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで com.okta.sdk:okta-sdk-root を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade com.okta.sdk:okta-sdk-root to 20.0.1ステージング環境で 20.0.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web github.com
- web github.com