Page MenuHomePhabricator

MediaWiki 1.27.1 security release
Closed, ResolvedPublic

Assigned To
Authored By
csteipp
Apr 19 2016, 5:17 PM
Referenced Files
F4345953: T130384.patch
Aug 8 2016, 9:59 PM
F4326047: T128624-part2-REL1_27
Aug 1 2016, 12:17 PM
F4326029: T132926-REL1_23.patch
Aug 1 2016, 12:14 PM
F4326026: T128624-REL1_27.patch
Aug 1 2016, 12:14 PM
F4326031: T132926-REL1_26.patch
Aug 1 2016, 12:14 PM
F4326039: T132926-master.patch
Aug 1 2016, 12:14 PM
F3657112: SECURITY: Check for valid but unusable user names.patch
Jul 18 2016, 11:02 PM

Description

This will probably happen several weeks after 1.27 is released.

MW Versions: 1.27.1/1.26.4/1.23.15. Note, 1.25 is already EOL.

Core

Maniphest IDCVE IDREL1_23REL1_26REL1_27REL1_28/master
T115333CVE-2016-6331
T129738CVE-2016-6332,,,,
T133147CVE-2016-6333,,,,
T137264CVE-2016-6334
T139570CVE-2016-6335Already present
T132926CVE-2016-6336
T139670CVE-2016-6337n/a (no SessionManager)n/a (no SessionManager)

Extensions

REL1_23REL1_26REL1_27REL1_28/master
T136402 [pdfHandler] [master patch applies cleanly to everything except 1.23]

Related Objects

Event Timeline

There are a very large number of changes, so older changes are hidden. Show Older Changes

Removed REL1_25 column as it hit EOL already.

MaxSem renamed this task from MediaWiki 1.26.4 security release to MediaWiki 1.27.1 security release.Jun 29 2016, 5:03 PM

The two Flow patches do not block this release, they are not bundled. They should be pushed to all supported branches and announced (mediawiki-announce, I can help with this)

Flow, as an un-bundled extension, can be removed from this tracker. They should be fixed in all supported branches and announced widely. That's all we need for that.

T130384 is not a core change and not a bundled extension (it's CentralAuth). Let's remove it from the list, push to branches, and announce.

doesn't apply cleanly to REL1_23. Otherwise that branch checks out ok.

doesn't apply cleanly to REL1_23. Otherwise that branch checks out ok.

I think that patch was based on top of the patch for T57548-REL1_23.patch (The two patches conflicted with each other)

I haven't checked the patches linked here, but can we make sure the commit message starts with "SECURITY"? We've been a bit inconsistent with that lately, and it makes them much easier to spot (noticed when rebasing before deploying on tin)

I haven't checked the patches linked here, but can we make sure the commit message starts with "SECURITY"? We've been a bit inconsistent with that lately, and it makes them much easier to spot (noticed when rebasing before deploying on tin)

Thanks for noticing that, @Legoktm. We'll be vigilant about that in the future.

Patch for T137264 does not apply to master.

@Bawolff Any opposition to applying the $wgWellFormedXml patch (T57548) directly to REL1_23 and REL1_26 directly and like now? It's already public and on the other branches and it makes the release a tad easier :)

@Bawolff Any opposition to applying the $wgWellFormedXml patch (T57548) directly to REL1_23 and REL1_26 directly and like now? It's already public and on the other branches and it makes the release a tad easier :)

Im fine with that, however im away for the rest of the week, so i cannot be the one to do it.

@Bawolff Any opposition to applying the $wgWellFormedXml patch (T57548) directly to REL1_23 and REL1_26 directly and like now? It's already public and on the other branches and it makes the release a tad easier :)

Im fine with that, however im away for the rest of the week, so i cannot be the one to do it.

Oh I can do it myself I just wanted a second opinion :)

T132926-REL1_26.patch, listed in the 1.27.1 column, doesn't apply to REL1_27 (as suggested by the name). T132926-master.patch does work on REL1_27 though.

T132926-REL1_26.patch, listed in the 1.27.1 column, doesn't apply to REL1_27 (as suggested by the name). T132926-master.patch does work on REL1_27 though.

Yeah, I had to do a manual rebase locally to sort out the conflicts. It's trivial though.

Removed T57548 since it's already backported to 1.23/1.26 as well.

demon claimed this task.
demon changed the visibility from "Custom Policy" to "Public (No Login Required)".
demon changed Security from Software security bug to None.
demon updated the task description. (Show Details)