Categories
CVE-2021-21430

Privilege Escalation in org.openapitools:openapi-generator (CVE-2021-21430)

Summary

Vulnerability in org.openapitools:openapi-generator (CVE-2021-21430). Confidential information can be exposed externally. Exploitable via File.createTempFile. Mitigation: upgrade to 5.1.0 or later.

Original description

The description as published by the source.

OpenAPI Generator allows generation of API client libraries (SDK generation), server stubs, documentation and configuration automatically given an OpenAPI Spec. Using File.createTempFile in JDK will result in creating and using insecure temporary files that can leave application and system data vulnerable to attacks. Auto-generated code (Java, Scala) that deals with uploading or downloading binary data through API endpoints will create insecure temporary files during the process. Affected generators: java (jersey2, okhttp-gson (default library)), scala-finch. The issue has been patched with Files.createTempFile and released in the v5.1.0 stable version.

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-2021-21430 has been found in org.openapitools:openapi-generator.
Attackers can target a specific entry point like File.createTempFile over the network to misuse the product.
Confidential information can be exposed externally.
What to do: upgrade org.openapitools:openapi-generator to 5.1.0 or later.
If unsure, ask your IT team or search "org.openapitools:openapi-generator CVE-2021-21430" on the vendor's site.

CVE-2021-21430 (org.openapitools:openapi-generator) — CWE-269
Attack vector: local / no user interaction
Attack surface: File.createTempFile / java / Files.createTempFile
Patched: 5.1.0 — 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-269) exists in org.openapitools:openapi-generator. Attackers reach the vulnerable code path via File.createTempFile.

📍 Affected scope

Check the vendor advisory for the affected versions of org.openapitools:openapi-generator. Attack surface: File.createTempFile / java / Files.createTempFile.

🔥 Severity

Severity: ?. Confidential information can be exposed externally.

🔧 How to fix

Update to 5.1.0.

🛡️ 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. Audit SBOM/dependencies to find affected services.

Response actions

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

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで org.openapitools:openapi-generator を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch
    Upgrade org.openapitools:openapi-generator to 5.1.0

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

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

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

Affected packages

Maven org.openapitools:openapi-generator
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.1.0"}]}]

References

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