# whoopsie 0.2.62ubuntu0.5: whoopsie 0.2.62ubuntu0.5 for Ubuntu 18.04.6 LTS (bionic)

whoopsie 0.2.62ubuntu0.5, released July 6, 2020, fixes 3 CVEs in whoopsie. None of them is reported as exploited. Patch Radar priority: Routine. The product is no longer supported.

- Web page: https://patchblox.com/security/fix/linux/ubuntu-bionic-whoopsie-0.2.62ubuntu0.5
- Platform: Linux
- Released: Jul 6, 2020
- Priority: Routine (Closes 3 CVEs, none high severity)
- CVEs: 3, exploited: 0, on CISA KEV: 0

## Applies to

| Product | Release | Fixed in |
|---|---|---|
| [whoopsie](https://patchblox.com/security/data/product/linux/whoopsie.md) | Ubuntu 18.04.6 LTS (bionic) | 0.2.62ubuntu0.5 |

## CVEs this fix closes

| CVE | Priority | Title | CVSS | EPSS | Exploitation |
|---|---|---|---:|---:|---|
| [CVE-2020-12135](https://patchblox.com/security/data/cve/CVE-2020-12135.md) | Routine | libwhoopsie0: bson before 0.8 incorrectly uses int rather than size_t for many variables,parameters, and return values | n/a | 0.0117 |  |
| [CVE-2020-15570](https://patchblox.com/security/data/cve/CVE-2020-15570.md) | Routine | libwhoopsie0: The parse_report() function in whoopsie.c in Whoopsie through 0.2.69 mishandles memory allocation failures, which all... | n/a | 0.0108 |  |
| [CVE-2020-11937](https://patchblox.com/security/data/cve/CVE-2020-11937.md) | Routine | libwhoopsie0: In whoopsie, parse_report() from whoopsie.c allows a local attacker to cause a denial of service via a crafted file | n/a | 0.0047 |  |

---

Data as of 2026-11-11T19:49:26Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.