The Whoopsie Project maintains a focused error-reporting utility that, despite its narrow scope, sits in the diagnostic path of system components and thus reaches a wider deployment footprint. Its observed vulnerability surface centers on resource-handling weaknesses, particularly integer overflow conditions and unbounded resource allocation, which are characteristic of memory-constrained logging and crash-reporting contexts. Current severity, exploitation, and CVE counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Whoopsie Project over time
Signals from CVEs in this vendor scope (3 CVEs).
3 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2019-11484HIGH Kevin Backhouse discovered an integer overflow in bson_ensure_space, as used in whoopsie. | Feb 8, 2020 | 7.8 | 25 | NO | NO |
CVE-2020-15570MEDIUM 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 cr | Jul 6, 2020 | 5.5 | 21 | NO | NO |
CVE-2020-12135MEDIUM bson before 0.8 incorrectly uses int rather than size_t for many variables, parameters, and return values. In particular, the bson_ensure_space() parameter bytesNeeded could have a | Apr 24, 2020 | 5.5 | 16 | NO | NO |
Signals from CVEs in this vendor scope (3 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Whoopsie Project.
Media articles that mention a CVE ID that affects a product developed by Whoopsie Project — matched by CVE ID, not by vendor name.