Office Professional 2010 Key A (Microsoft) Codenam

As I introduced last week, I;m keeping a short but sweet Microsoft codename contest this week,Office Professional 2010 Key, with all the prize being a no cost signed duplicate of my Microsoft two.0 guide (which I will ship anyplace inside the globe to the winner).
Since I announced the rules and laws, I;ve gotten far more than several fascinating submissions. I was looking for from visitors new (but real and existing) Microsoft codenames which I;ve had but to detail as component of my expanding Microsoft Codename list. I'm operating a number of the greatest ones (as judged by yours genuinely) on my blog this week.
Without additional ado,Office Professional 2010, let;s get to it.
Codename with the day: Wringer
Best guess on what it really is: MOICE - the Microsoft Office Isolated Conversion Environment
Meaning/context with the codename: The MOICE undertaking isn;t new, however the codename and its origins had been new to me. MOICE is developed to “wring out” malicious content from Office documents.
Hold onto your hats for the full explanation from Software Security Engineer Robert Hensing;s blog:
“(B)asically what MOICE does is it hijacks the file associations in the registry and redirects them to a process called ‘MOICE.EXE;. This process basically spawns the Office 2007 file format converter to up-convert the double-clicked Workplace 2003 document to the new Open XML file format. Oh and the converter runs in its own desktop with a super-locked down token (Dave is the freaking man,Microsoft Office Professional Plus 2010!). Why run the converter in its own desktop with a super restricted token? Simple - what if the act of converting the file leads to an exploitable bug and / or code execution. This is effectively dropping the rights of the logged on user to *below* standard user levels in order to do the file conversion. Anyhoo - after the file is up-converted to the new Office 2007 file format - the theory is that the vulnerability will have been ‘wrung; out (indeed the code name for this challenge was ‘Wringer;).”
Back story: Workplace remains a big hacker target — something of which Microsoft is quite aware. As Hensing blogged:
“(I)t;s no secret that Office was utilised in some targetted attacks final year . . . some attacks involving 0-day vulnerabilities for which our customers had no way of protecting themselves (short of not opening documents). Had MOICE been available these customers could have deployed it to mitigate these attacks.”
Additional info: The National Security Agency published a fact sheet on Wringer, as well as a Wringer deployment tutorial.
Got a Microsoft code name you’ve been wondering about? Send it my way. All submitters will be kept confidential.Meanwhile,Microsoft Office 2007 Ultimate, if you want to keep track with the full month’s worth of Microsoft code names I end up posting, bookmark this “Microsoft Codenames” page.
“(B)asically what MOICE does is it hijacks the file associations inside the registry and redirects them to a process called ‘MOICE.EXE;. This process basically spawns the Workplace 2007 file format converter to up-convert the double-clicked Office 2003 document towards the new Open XML file format. Oh and the converter runs in its own desktop with a super-locked down token (Dave is the freaking man,Microsoft Office Professional Plus!). Why run the converter in its own desktop with a super restricted token? Simple - what if the act of converting the file leads to an exploitable bug and / or code execution. This is effectively dropping the rights of the logged on user to *below* standard user levels in order to do the file conversion. Anyhoo - after the file is up-converted to the new Workplace 2007 file format - the theory is that the vulnerability will have been ‘wrung; out (indeed the code name for this undertaking was ‘Wringer;).”
Back story: Office remains a big hacker target — something of which Microsoft is quite aware. As Hensing blogged:
“(I)t;s no secret that Workplace was used in some targetted attacks final year . . . some attacks involving 0-day vulnerabilities for which our customers had no way of protecting themselves (brief of not opening documents). Had MOICE been available these customers could have deployed it to mitigate these attacks.”
Additional info: The National Security Agency published a fact sheet on Wringer, as well as a Wringer deployment manual.
Got a Microsoft code name you’ve been wondering about? Send it my way. All submitters will be kept confidential.