lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Fri, 9 Feb 2018 19:01:40 +0100
From: "Stefan Kanthak" <>
To: <>
Subject: [FD] Defense in depth -- the Microsoft way (part 51): Skype's
	home-grown updater allows escalation of privilege to SYSTEM

Hi @ll,

since about two or three years now, Microsoft offers Skype as
optional update on Windows/Microsoft Update.

JFTR: for Microsoft's euphemistic use of "update" see

Once installed, Skype uses its own proprietary update mechanism
instead of Windows/Microsoft Update: Skype periodically runs
under the SYSTEM account.
When an update is available, Updater.exe copies/extracts another
executable as "%SystemRoot%\Temp\SKY<abcd>.tmp" and executes it
using the command line
    "%SystemRoot%\Temp\SKY<abcd>.tmp" /QUIET

This executable is vulnerable to DLL hijacking: it loads at least
UXTheme.dll from its application directory %SystemRoot%\Temp\
instead from Windows' system directory.

An unprivileged (local) user who is able to place UXTheme.dll or
any of the other DLLs loaded by the vulnerable executable in
%SystemRoot%\Temp\ gains escalation of privilege to the SYSTEM

The attack vector is well-known and well-documented as CAPEC-471:

Microsoft published plenty advice/guidance to avoid this beginner's
error: <>,
... which their own developers and their QA but seem to ignore!

See <>
for the same vulnerability in another Microsoft product!

stay tuned
Stefan Kanthak


2017-09-02    vulnerability report sent to vendor

2017-09-03    reply from vendor: "MSRC case 40550 opened"

2017-09-06    notification from vendor's case manager: "report passed
              to product group for investigation"

2017-10-27    reply from vendor's case manager:

              "The engineers provided me with an update on this case.
               They've reviewed the code and were able to reproduce
               the issue, but have determined that the fix will be
               implemented in a newer version of the product rather
               than a security update. The team is planning on shipping
               a newer version of the client, and this current version
               will slowly be deprecated. The installer would need a
               large code revision to prevent DLL injection, but all
               resources have been put toward development of the new

2018-02-09    report published

Sent through the Full Disclosure mailing list
Web Archives & RSS:

Powered by blists - more mailing lists