CVE-2020-6174
No exploitation reported by the sources we read.
- Published2020-02-05
- Fixed in0.12.2
- WeaknessCWE-347
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
TUF (aka The Update Framework) through 0.12.1 has Improper Verification of a Cryptographic Signature.
Timeline
dates in UTC- 2020-02-0516:15CVE publishedNVD
Versions per branch
OSV · NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 0.12 | < 0.12.2 | 0.12.2 | OSV |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 0.12 | ≤ 0.12.1 | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update tuf to 0.12.2
Advisories and patches
- github.comPatch
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof of concept
- PoC-in-GitHubno public repository identifiedread 2026-11-08
- Metasploit modules
- none listed Metasploit Framework
Sources
- NVDCVSS 3.19.8read 2026-10-23
- NVDCVSS 2.07.5read 2026-10-23
- NVDweakness (CWE)CWE-347read 2026-10-23
- FIRST EPSSEPSS score1.0 %2026-11-08
- OSVaffected packages—
- GitHub AdvisoriesadvisoryCRITICAL2020-08-21
Identifiers
- EUVD-2020-0226same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-pwqf-9h7j-7mv8same flawGitHub Advisory Database · CC-BY-4.0
- PYSEC-2020-147same flawPyPA Advisory Database · CC-BY-4.0
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Published
- 2020-02-05
- Last Modified
- 2026-06-17
- NVD status
- Modified
- GitHub Advisory
- GHSA-pwqf-9h7j-7mv8
Frequently asked questions
What is CVE-2020-6174?
Is CVE-2020-6174 actively exploited?
What is the CVSS score for CVE-2020-6174?
Running tuf? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- FIRST EPSS · EPSS terms of use (free use, attribution requested)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-pwqf-9h7j-7mv8
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- OSV.dev · Per record, as its publisher states it: each row carries the label in sourceLicense when one is served