Resource exhaustion vulnerability in whoopsie

published 2020-08-06 6 y ago modified 2026-06-17 4 mo ago also EUVD-2020-4274

cvss: 5.5; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.5%; EPSS 0.5% chance of exploitation in 30 days, percentile 40%
public exploits: 0; none known

In whoopsie, parse_report() from whoopsie.c allows a local attacker to cause a denial of service via a crafted file. The DoS is caused by resource exhaustion due to a memory leak. Fixed in 0.2.52.5ubuntu0.5, 0.2.62ubuntu0.5 and 0.2.69ubuntu0.1.

Patch / fix

fixed in 1 distros 1

Canonical whoopsie 0.2.52.5ubuntu0.5, 0.2.62ubuntu0.5, 0.2.69ubuntu0.1

whoopsie Ubuntu 16.04 LTS 0.2.52.5ubuntu0.5
whoopsie Ubuntu 18.04 LTS 0.2.62ubuntu0.5
whoopsie Ubuntu 20.04 LTS 0.2.69ubuntu0.1

ubuntu advisories UBUNTU-CVE-2020-11937

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Exploit prediction

0.47% chance of exploitation in the next 30 days, higher than 40% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

launchpad.net https://launchpad.net/bugs/1881982 referenced PoC, tagged "exploit" by a source, unverified
github.com https://github.com/sungjungk/whoopsie_killer referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
CNA	3.1	5.5	CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD	3.1	5.5	CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD	2.0	2.1	AV:L/AC:L/Au:N/C:N/I:N/A:P

Affected products

Canonical whoopsie

Classification

Weakness

CWE-400 Uncontrolled Resource Consumption
CWE-401 Missing Release of Memory after Effective Lifetime

References

launchpad.net /bugs/1881982
exploit, issue-tracking, third-party-advisory
github.com /sungjungk/whoopsie_killer
exploit, third-party-advisory
usn.ubuntu.com /4450-1/
vendor-advisory, third-party-advisory
usn.ubuntu.com /4450-1
vendor-advisory

Sources

CVE List CVE-2020-11937
NVD CVE-2020-11937

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary