CVE-2020-15570
MEDIUMCVSS 5.5/10EPSS 1.08%
Last modified
CVE-2020-15570 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. The parse_report() function in whoopsie.c in Whoopsie through 0.2.69 mishandles memory allocation failures, which allows an attacker to cause a denial of service via a malformed crash file.. EPSS estimates a 1.08% chance of exploitation in the next 30 days.
Description
The parse_report() function in whoopsie.c in Whoopsie through 0.2.69 mishandles memory allocation failures, which allows an attacker to cause a denial of service via a malformed crash file.
Metrics
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Whoopsie Project | Whoopsie | <= 0.2.69 |
References
- https://github.com/sungjungk/whoopsie_killer2/blob/master/README.mdExploit, Third Party Advisory
- https://github.com/sungjungk/whoopsie_killer2/blob/master/whoopsie_killer2.pyExploit, Third Party Advisory
- https://launchpad.net/ubuntu/+source/whoopsieThird Party Advisory
- https://www.youtube.com/watch?v=oZXGwC7PWYEExploit, Third Party Advisory
- https://github.com/sungjungk/whoopsie_killer2/blob/master/README.mdExploit, Third Party Advisory
- https://github.com/sungjungk/whoopsie_killer2/blob/master/whoopsie_killer2.pyExploit, Third Party Advisory
- https://launchpad.net/ubuntu/+source/whoopsieThird Party Advisory
- https://www.youtube.com/watch?v=oZXGwC7PWYEExploit, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2020-15570?
The parse_report() function in whoopsie.c in Whoopsie through 0.2.69 mishandles memory allocation failures, which allows an attacker to cause a denial of service via a malformed crash file.
How severe is CVE-2020-15570?
CVE-2020-15570 has a CVSS score of 5.5/10 (MEDIUM severity). The EPSS model estimates a 1.08% probability of exploitation in the next 30 days.
How do I fix CVE-2020-15570?
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 2020
- CVE-2020-15565An issue was discovered in Xen through 4.13.x, allowing x86 …8.8
- CVE-2020-15566An issue was discovered in Xen through 4.13.x, allowing gues…6.5
- CVE-2020-15567An issue was discovered in Xen through 4.13.x, allowing Inte…7.8
- CVE-2020-15568TerraMaster TOS before 4.1.29 has Invalid Parameter Checking…9.8
- CVE-2020-15569PlayerGeneric.cpp in MilkyTracker through 1.02.00 has a use-…5.5
- CVE-2020-1557A remote code execution vulnerability exists when the Window…7.3
- CVE-2020-15572Tor before 0.4.3.6 has an out-of-bounds memory access that a…7.5
- CVE-2020-15573SolarWinds Serv-U File Server before 15.2.1 has a "Cross-scr…6.1
- CVE-2020-15574SolarWinds Serv-U File Server before 15.2.1 mishandles the S…7.5
- CVE-2020-15575SolarWinds Serv-U File Server before 15.2.1 allows XSS as de…6.1
- CVE-2020-15576SolarWinds Serv-U File Server before 15.2.1 allows informati…7.5
- CVE-2020-15577An issue was discovered on Samsung mobile devices with P(9.0…5.5
Are you affected by CVE-2020-15570?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST