CVE-2020-8177 — Injection in Debian Debian Linux
curl 7.20.0 through 7.70.0 is vulnerable to improper restriction of names for files and other resources that can lead too overwriting a local file when the -J flag is used.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 1.3% (30-day exploitation probability)+10
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — cert-portal.siemens.com (NIST National Vulnerability Database)
- Documented patch — www.oracle.com (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Debian Debian Linux, Fujitsu M10-1 Firmware, Fujitsu M10-4 Firmware…).
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Debian | Debian Linux | version 10.0 | Vulnerable | NIST National Vulnerability Database |
| Fujitsu | M10-1 Firmware | < xcp2410< xcp3110 | Vulnerable | NIST National Vulnerability Database |
| Fujitsu | M10-4 Firmware | < xcp2410< xcp3110 | Vulnerable | NIST National Vulnerability Database |
| Fujitsu | M10-4s Firmware | < xcp2410< xcp3110 | Vulnerable | NIST National Vulnerability Database |
| Fujitsu | M12-1 Firmware | < xcp3110< xcp2410 | Vulnerable | NIST National Vulnerability Database |
| Fujitsu | M12-2 Firmware | < xcp3110< xcp2410 | Vulnerable | NIST National Vulnerability Database |
| Fujitsu | M12-2s Firmware | < xcp3110< xcp2410 | Vulnerable | NIST National Vulnerability Database |
| Haxx | Curl | ≥ 7.20.0 and ≤ 7.70.0 | Vulnerable | NIST National Vulnerability Database |
| Siemens | Sinec Infrastructure Network Services | < 1.0.1.1 | Vulnerable | NIST National Vulnerability Database |
| Splunk | Universal Forwarder | version 9.1.0≥ 9.0.0 and < 9.0.6≥ 8.2.0 and < 8.2.12 | Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.8 | CVSS 3.1 | High | 1.8 | 5.9 | nvd@nist.gov via NIST National Vulnerability Database |
| 7.8 | CVSS 3.1 | High | 1.8 | 5.9 | 134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database |
| 7.8 | CVSS 3.1 | High | — | — | CISA-ADP via CVE Program (cve.org) e CISA ADP |
| 4.6 | CVSS 2.0 | Medium | 3.9 | 6.4 | nvd@nist.gov via NIST National Vulnerability Database |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 14, 2026 → Oct 15, 2026 · 2 reading(s) · max 1.29%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
- Look for parameters with command/query metacharacters and unexpected child processes of the service.
Timeline
What happened to this CVE, newest first.
- 2026
- SSVC assessment updated
- Record published
- Fix documented
- CVSS changed · 7.8
- Source status changed · → Modified
- Record created in this database
- 2020
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 14, 2026 – Oct 14, 2026
References
7 on the record
- curl.se/docs/CVE-2020-8177.html
- www.oracle.com/security-alerts/cpujan2022.html
- cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf
- hackerone.com/reports/887462
- cert-portal.siemens.com/productcert/html/ssa-389290.html
- cert-portal.siemens.com/productcert/html/ssa-398330.html
- www.debian.org/security/2021/dsa-4881
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-80229 OpenSSL provider use-after-free Sep 6, 2026
- High CVE-2026-82208 wolfSSL CA-cache hit overrides callback Sep 6, 2026
- High CVE-2026-80255 secure cookie attribute bypass with tab Sep 6, 2026
- High CVE-2026-80231 native CA store conn reuse Sep 6, 2026
- High CVE-2026-80230 OpenSSL pinning bypass Sep 6, 2026
- High CVE-2026-82209 domain-scoped PSL domain cookie Sep 6, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2020-8177 is "Injection in Debian Debian Linux", rated High. It affects Debian Linux (Debian); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.8 describes technical severity. EPSS 1.29% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.