what you don't know can hurt you

Microsoft POSReady 2009 Eval CD Remnants

Microsoft POSReady 2009 Eval CD Remnants
Posted Mar 4, 2012
Authored by Stefan Kanthak

The POSReady 2009 eval CD from Microsoft Download Center appears to show remnants of having been built on a system that may have been infested with malware.

tags | advisory
MD5 | e286fac6a7f52d5436a5656ef7a4ca36

Microsoft POSReady 2009 Eval CD Remnants

Change Mirror Download
Hi @ll,

the system image "\Setup\WIM\setup.wim" on the "POSReady 2009 eval CD",
available from the Microsoft Download Center under
<http://www.microsoft.com/downloads/en/details.aspx?FamilyID=1e077ece-3f19-4c41-b219-6fcc821fb5fc>,
contains the following registry entries:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Notify\SSOExec]
"Asynchronous"=dword:00000001
"Impersonate"=dword:00000001
"Logoff"="SSOReset"
"Unlock"="SSOExec"
"Lock"="SSOReset"
"DLLName"="%windir%\\temp\\sso\\ssoexec.dll"


The directory "%windir%\temp" in the system image is but empty.


The presence of these registry entries is evidence that (one of) the
system(s) used to build and capture the POSReady 2009 evaluation system
image were infested with malware, and that either the infestation was not
detected at all (bad) or the infestation was detected, but incompletely
(or accidentially, when "%windir%\temp" was cleared) "removed" and a
compromised system used to build the system image (worse).

JFTR: MSFT initiated their "trustworthy computing" about 10 years ago!


To complete the picture: the ACLs on the directory "%windir%\temp" in
systems installed from this image/CD allow unprivileged users to create
a subdirectory "sso" in "%windir%\temp" and then the "ssoexec.dll",
allowing them to have their code run under every (other) user account
used to log on afterwards, resulting in a privilege escalation.


Timeline
~~~~~~~~

2012-02-03 informed vendor

2012-02-03 vendor replies:
"The registry key and DLL are part of the Windows embedded
software package and their existence is expected."

.oO(OUCH! they must be joking...)

2012-02-04 informed vendor that SSOEXEC.DLL is NOT part of any Windows
software package

2012-02-06 vendor replies:
"we are still looking and hope to provide clarification soon."

2012-02-06 vendor replies:
"this reference in no way indicates there is or ever was a
virus on our build systems."

2012-02-08 asked vendor to consider that both
<http://www.bing.com/search?q=ssoexec> and
<https://encrypted.google.com/search?num=100&safe=off&q=%22ssoexec%22+OR+%22ssoreset%22>
only find hits that show problems with malware

2012-03-04 no more answer from vendor, report published


Stefan Kanthak

Comments

RSS Feed Subscribe to this comment feed

No comments yet, be the first!

Login or Register to post a comment

File Archive:

October 2019

  • Su
  • Mo
  • Tu
  • We
  • Th
  • Fr
  • Sa
  • 1
    Oct 1st
    24 Files
  • 2
    Oct 2nd
    15 Files
  • 3
    Oct 3rd
    7 Files
  • 4
    Oct 4th
    4 Files
  • 5
    Oct 5th
    10 Files
  • 6
    Oct 6th
    1 Files
  • 7
    Oct 7th
    21 Files
  • 8
    Oct 8th
    19 Files
  • 9
    Oct 9th
    5 Files
  • 10
    Oct 10th
    20 Files
  • 11
    Oct 11th
    17 Files
  • 12
    Oct 12th
    4 Files
  • 13
    Oct 13th
    4 Files
  • 14
    Oct 14th
    15 Files
  • 15
    Oct 15th
    19 Files
  • 16
    Oct 16th
    0 Files
  • 17
    Oct 17th
    0 Files
  • 18
    Oct 18th
    0 Files
  • 19
    Oct 19th
    0 Files
  • 20
    Oct 20th
    0 Files
  • 21
    Oct 21st
    0 Files
  • 22
    Oct 22nd
    0 Files
  • 23
    Oct 23rd
    0 Files
  • 24
    Oct 24th
    0 Files
  • 25
    Oct 25th
    0 Files
  • 26
    Oct 26th
    0 Files
  • 27
    Oct 27th
    0 Files
  • 28
    Oct 28th
    0 Files
  • 29
    Oct 29th
    0 Files
  • 30
    Oct 30th
    0 Files
  • 31
    Oct 31st
    0 Files

Top Authors In Last 30 Days

File Tags

Systems

packet storm

© 2019 Packet Storm. All rights reserved.

Services
Security Services
Hosting By
Rokasec
close