Where is the January security update release of current channel?

%3CLINGO-SUB%20id%3D%22lingo-sub-39642%22%20slang%3D%22en-US%22%3EWhere%20is%20the%20January%20security%20update%20release%20of%20current%20channel%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-39642%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20page%20(%3CA%20href%3D%22https%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fmt592918.aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fmt592918.aspx%3C%2FA%3E)%20shows%20the%20last%20Current%20Channel%20release%20to%20be%20the%204th%20Jan.%26nbsp%3B%20This%20is%20before%20the%20patch%20Tuesday%20security%20bulletin%20publication.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThere%20was%20a%20bulletin%20released%20for%20Office%202016%2C%20and%20typically%20this%20is%20reflected%20in%20the%20same%20security%20fixes%20being%20applied%20to%20O365PP%20-%20but%20this%20hasn't%20happened.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMS17-002%20was%20published%20on%20the%2010th%2C%20but%20both%20the%20link%20above%20and%20%3CA%20href%3D%22https%3A%2F%2Ftechnet.microsoft.com%2Fen-gb%2Foffice%2Fmt465751%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Ftechnet.microsoft.com%2Fen-gb%2Foffice%2Fmt465751%3C%2FA%3E%20show%20no%20update%20made%20for%20Current%20Channel.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHas%20it%20been%20held%20back%2C%20or%20for%20some%20reason%20does%20the%20vulnerability%20in%20MS17-002%20somehow%20not%20apply%20to%20the%20Office%20apps%20within%20ProPlus%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-40714%22%20slang%3D%22en-US%22%3ERe%3A%20Where%20is%20the%20January%20security%20update%20release%20of%20current%20channel%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-40714%22%20slang%3D%22en-US%22%3E%3CP%3EDeferred%20Channel%20(DC)%201605%20and%20Current%20Channel%201611%20are%20about%206%20months%20apart%20from%20a%20code%20perspective.%20So%20it%20could%20very%20well%20happen%2C%20that%20discovered%20security%20issues%20is%20only%20affect%20a%20subset%20of%20available%20channels.%20The%26nbsp%3Bcode%20in%20other%20channels%20may%20already%20have%20changed%20and%20the%20issue%20was%20(maybe%20unintended)%20mitigated%20even%20before%20it%20was%20discovered.%20Protecting%20customer's%20security%20is%20a%20priority%20for%20Microsoft%2C%20rest%20assured%20that%20no%20security%20fix%20is%20held%20back%20when%20it%20is%20ready.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-39850%22%20slang%3D%22en-US%22%3ERe%3A%20Where%20is%20the%20January%20security%20update%20release%20of%20current%20channel%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-39850%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20does%20look%20strange%2C%20the%26nbsp%3BDeferred%20Channel%20having%20received%20the%26nbsp%3BMS17-002%20update%20on%2010th%20Jan%20but%20there%20is%20no%20sign%20of%20it%20on%20the%20Current%20Channel%20on%201611.%20%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20either%20it's%20not%20applicable%20or%20it%20will%20turn%20up%20in%20the%20next%20build%2C%20it%20would%20be%20good%20to%20know%20which.%20%26nbsp%3B1612%20is%20making%20its%20way%20through%20Office%20Insiders%20currently%20incidentally%20and%20was%20updated%20on%20the%2010th%20also%2C%20so%20maybe%20that%20will%20be%20the%20next%20Current%20Channel%20soon.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Visitor

This page (https://technet.microsoft.com/en-us/library/mt592918.aspx) shows the last Current Channel release to be the 4th Jan.  This is before the patch Tuesday security bulletin publication.

 

There was a bulletin released for Office 2016, and typically this is reflected in the same security fixes being applied to O365PP - but this hasn't happened.

 

MS17-002 was published on the 10th, but both the link above and https://technet.microsoft.com/en-gb/office/mt465751 show no update made for Current Channel.

 

Has it been held back, or for some reason does the vulnerability in MS17-002 somehow not apply to the Office apps within ProPlus?

2 Replies

This does look strange, the Deferred Channel having received the MS17-002 update on 10th Jan but there is no sign of it on the Current Channel on 1611.  

 

So either it's not applicable or it will turn up in the next build, it would be good to know which.  1612 is making its way through Office Insiders currently incidentally and was updated on the 10th also, so maybe that will be the next Current Channel soon.

 

Deferred Channel (DC) 1605 and Current Channel 1611 are about 6 months apart from a code perspective. So it could very well happen, that discovered security issues is only affect a subset of available channels. The code in other channels may already have changed and the issue was (maybe unintended) mitigated even before it was discovered. Protecting customer's security is a priority for Microsoft, rest assured that no security fix is held back when it is ready.