Linux ·
Ubuntu · Package update · May 26, 2020
Ubuntu · Package update · May 26, 2020qmail 1.06-6.2~deb10u1build0.18.04.1: qmail 1.06-6.2~deb10u1build0.18.04.1 for Ubuntu 18.04.6 LTS (bionic)
qmail 1.06-6.2~deb10u1build0.18.04.1, released May 26, 2020, fixes 5 CVEs in qmail. None of them is reported as exploited. Patch Radar priority: Routine. The product is no longer supported.
RoutineUnsupported product
CVEs closed
5
None rated Critical
Exploited
0
None reported
Highest CVSS
n/a
No CVSS score published
Highest EPSS
0.1079
95th percentile
Priority of the 5 CVEs
Patch now 0
Urgent 0
High 0
Routine 5
Fixed package versions
| Product | Release | Fixed in |
|---|---|---|
| qmail | Ubuntu 18.04.6 LTS (bionic) | 1.06-6.2~deb10u1build0.18.04.1 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| Routine | CVE-2005-1513 | qmail: Integer overflow in the stralloc_readyplus function in qmail, when running on 64 bit platforms with a large amount of... | n/a | 0.1079 | None reported |
| Routine | CVE-2005-1514 | qmail: commands.c in qmail, when running on 64 bit platforms with a large amount of virtual memory, allows remote attackers... | n/a | 0.0657 | None reported |
| Routine | CVE-2005-1515 | qmail: Integer signedness error in the qmail_put and substdio_put functions in qmail, when running on 64 bit platforms with... | n/a | 0.0652 | None reported |
| Routine | CVE-2020-3811 | qmail: qmail-verify as used in netqmail 1.06 is prone to a mail-address verification bypass vulnerability. | n/a | 0.0181 | None reported |
| Routine | CVE-2020-3812 | qmail: qmail-verify as used in netqmail 1.06 is prone to an information disclosure vulnerability | n/a | 0.0043 | None reported |
Showing 1 to 5 of 5
1
Patch Radar data is free to use with attribution. Terms and how to credit it.
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.