CVE-2020-11979 high CVSS 7.5

Vulnerability in org.apache.ant:ant (CVE-2020-11979)

Summary

Vulnerability in org.apache.ant:ant (CVE-2020-11979). Data can be tampered with by attackers. Mitigation: upgrade to 1.10.9 or later.

Original description

The description as published by the source.

As mitigation for CVE-2020-1945 Apache Ant 1.10.8 changed the permissions of temporary files it created so that only the current user was allowed to access them. Unfortunately the fixcrlf task deleted the temporary file and created a new one without said protection, effectively nullifying the effort. This would still allow an attacker to inject modified source files into the build process.

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-11979 has been found in org.apache.ant:ant.
Data can be tampered with by attackers. CVSS score: 7.5/10.
What to do: upgrade org.apache.ant:ant to 1.10.9 or later.
If unsure, ask your IT team or search "org.apache.ant:ant CVE-2020-11979" on the vendor's site.

CVE-2020-11979 (org.apache.ant:ant) — CWE-379 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.10.9 — 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-379) exists in org.apache.ant:ant.

📍 Affected scope

Check the vendor advisory for the affected versions of org.apache.ant:ant.

🔥 Severity

Severity: High (CVSS 7.5/10). Data can be tampered with by attackers.

🔧 How to fix

Update to 1.10.9.

🛡️ 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
Identify exposure identify
```
Audit SBOM/dependencies for affected components.
```
資産台帳・SBOM・依存マニフェストで org.apache.ant:ant を使っているサービスとバージョンを洗い出す。
2
Apply patch patch
```
Upgrade org.apache.ant:ant to 1.10.9
```
ステージング環境で 1.10.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Maven org.apache.ant:ant

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.10.9"}]}]

Summary

Original description

Auto-generated summary

Response actions

Affected packages

References