Wordpress May 2017 security updates
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
wordpress (Ubuntu) |
Expired
|
High
|
Unassigned | ||
Xenial |
Expired
|
High
|
Unassigned | ||
Yakkety |
Expired
|
High
|
Unassigned | ||
Zesty |
Expired
|
High
|
Unassigned |
Bug Description
Sponsorship
-----------
git-buildpackage from the ubuntu/* branches at
https:/
Impact
------
Update 17.04 from 4.7.3 to 4.7.5
Update 16.10 from 4.6.1 to 4.6.6
Update 16.04 LTS from 4.4.2 to 4.4.10
to fix numerous critical security bugs.
wordpress 4.7.5-1 was auto-synced from Debian to Ubuntu 17.10 Alpha "artful"
Changes for Ubuntu 17.04
-------
https:/
https:/
https:/
https:/
You can change the codex URL to a different version number if you really want to see all the individual security fixes.
The changelog entries were produced by tweaking the changelog from
https:/
For Xenial, I also used
https:/
and filled in the descriptions for these 2 that didn't apply to the Debian security update but apply to Xenial
https:/
https:/
Testing Done
------------
I have successfully test-built each package.
Regression Potential
-------
WordPress maintains separate branches to backport security fixes. I suspect that the older the branch gets, the more likely it is that something will break.
WordPress still uses trac/svn, but there's this handy read-only copy that is easier to examine:
https:/
WordPress only officially recommends the latest stable series (currently 4.7)
https:/
Other Info
----------
On one hand, I hope right now no one actually uses the Ubuntu package on a live web server. I mean, if they are using the development version of Ubuntu, it might actually work but otherwise, it's not really received any security support at all.
Similarly, I guess there's a concern that if we start providing security updates, then people will start thinking that Ubuntu's 'wordpress' package is safe to use, which is fine as long as someone from the community will indeed package these updates from now on. Otherwise, maybe doing these security updates is not really helping anyone?
WordPress also maintains a 3.8 branch (with a 3.8.21 release this week corresponding with 4.7.5) that we could use for Ubuntu 14.04 LTS. I could prepare that one too, but I don't think it's worth spending much time testing that version.
CVE References
description: | updated |
Changed in wordpress (Ubuntu): | |
status: | New → Confirmed |
Changed in wordpress (Ubuntu Xenial): | |
status: | New → Confirmed |
importance: | Undecided → High |
Changed in wordpress (Ubuntu Yakkety): | |
status: | New → Confirmed |
importance: | Undecided → High |
Changed in wordpress (Ubuntu Zesty): | |
status: | New → Confirmed |
importance: | Undecided → High |
description: | updated |
information type: | Public → Public Security |
Debian put out a fix today for https:/ /security- tracker. debian. org/tracker/ CVE-2017- 8295 but that seems a low enough priority to me (and not yet fixed in WordPress core) to wait until the next WordPress security release.