Bug#959391: wordpress: CVE-2020-11025 CVE-2020-11026 CVE-2020-11027 CVE-2020-11028 CVE-2020-11029 CVE-2020-11030

2020-05-02 Thread Salvatore Bonaccorso
Hi Craig, On Sat, May 02, 2020 at 10:31:24AM +1000, Craig Small wrote: > This is the analysis of the latest WordPress security bugs. > Is it awesome upstream already has CVE IDs and (almost) clear patches of > the fixes? Yes, it is! > > Sid: 5.4 > All vulnerabilities, use upstream 5.4.1 > >

Bug#959391: wordpress: CVE-2020-11025 CVE-2020-11026 CVE-2020-11027 CVE-2020-11028 CVE-2020-11029 CVE-2020-11030

2020-05-01 Thread Craig Small
This is the analysis of the latest WordPress security bugs. Is it awesome upstream already has CVE IDs and (almost) clear patches of the fixes? Yes, it is! Sid: 5.4 All vulnerabilities, use upstream 5.4.1 Bullseye: 5.3.2

Bug#959391: wordpress: CVE-2020-11025 CVE-2020-11026 CVE-2020-11027 CVE-2020-11028 CVE-2020-11029 CVE-2020-11030

2020-05-01 Thread Craig Small
Hi Salvatore, Thanks for the bug report. I'll look into it today and yes its good we finally have CVE IDs to work with. On Sat, 2 May 2020 at 06:21, Salvatore Bonaccorso wrote: > example CVE-2020-11030 lists via the GHSA as affected versions 5.2 to > 5.4, and patched in 5.4.1, 5.3.3 and

Bug#959391: wordpress: CVE-2020-11025 CVE-2020-11026 CVE-2020-11027 CVE-2020-11028 CVE-2020-11029 CVE-2020-11030

2020-05-01 Thread Salvatore Bonaccorso
Source: wordpress Version: 5.4+dfsg1-1 Severity: grave Tags: security upstream Justification: user security hole Hi, The following vulnerabilities were published for wordpress. Fortunately this time additionally to [6], there are GHSA advisories associated with each of this CVEs (advantage of