CVE-2016-20013
HIGHCVSS 7.5/10EPSS 2.20%
Last modified
CVE-2016-20013 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. sha256crypt and sha512crypt through 0.6 allow attackers to cause a denial of service (CPU consumption) because the algorithm's runtime is proportional to the square of the length of the password.. EPSS estimates a 2.20% chance of exploitation in the next 30 days.
Description
sha256crypt and sha512crypt through 0.6 allow attackers to cause a denial of service (CPU consumption) because the algorithm's runtime is proportional to the square of the length of the password.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Sha256crypt Project | Sha256crypt | <= 0.6 |
| Sha512crypt Project | Sha512crypt | <= 0.6 |
References
- https://akkadia.org/drepper/SHA-crypt.txtExploit, Third Party Advisory
- https://pthree.org/2018/05/23/do-not-use-sha256crypt-sha512crypt-theyre-dangerous/Exploit, Third Party Advisory
- https://twitter.com/solardiz/status/795601240151457793Third Party Advisory
- https://akkadia.org/drepper/SHA-crypt.txtExploit, Third Party Advisory
- https://pthree.org/2018/05/23/do-not-use-sha256crypt-sha512crypt-theyre-dangerous/Exploit, Third Party Advisory
- https://twitter.com/solardiz/status/795601240151457793Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2016-20013?
sha256crypt and sha512crypt through 0.6 allow attackers to cause a denial of service (CPU consumption) because the algorithm's runtime is proportional to the square of the length of the password.
How severe is CVE-2016-20013?
CVE-2016-20013 has a CVSS score of 7.5/10 (HIGH severity). The EPSS model estimates a 2.20% probability of exploitation in the next 30 days.
How do I fix CVE-2016-20013?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2016
- CVE-2016-20008The REST/JSON project 7.x-1.x for Drupal allows session enum…7.5
- CVE-2016-20009A DNS client stack-based buffer overflow in ipdnsc_decode_na…9.8
- CVE-2016-2001HPE Universal CMDB Foundation 10.0, 10.01, 10.10, 10.11, and…
- CVE-2016-20010EWWW Image Optimizer before 2.8.5 allows remote command exec…10
- CVE-2016-20011libgrss through 0.7.0 fails to perform TLS certificate verif…7.5
- CVE-2016-20012OpenSSH through 8.7 allows remote attackers, who have a susp…5.3
- CVE-2016-20014In pam_tacplus.c in pam_tacplus before 1.4.1, pam_sm_acct_mg…9.8
- CVE-2016-20015In the ebuild package through smokeping-2.7.3-r1 for SmokePi…7.5
- CVE-2016-20016MVPower CCTV DVR models, including TV-7104HE 1.8.4 115215B9 …9.8
- CVE-2016-20017D-Link DSL-2750B devices before 1.05 allow remote unauthenti…9.8
- CVE-2016-20018Knex Knex.js through 2.3.0 has a limited SQL injection vulne…7.5
- CVE-2016-2002The validateAdminConfig handler in the Analytics Management …
Are you affected by CVE-2016-20013?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST