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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date: Fri, 3 Aug 2018 15:16:00 +0200
From: "Stefan Kanthak" <>
To: <>
Subject: [FD] Executable installers are vulnerable^WEVIL (case 56):
	arbitrary code execution WITH escalation of privilege via rufus*.exe

Hi @ll,

like their predecessors, the recently (2018-05-29, 2018-06-19)
published versions 3.0 and 3.1 of "Rufus" are riddled with bloody
beginners errors, which ALL allow arbitrary code execution WITH
escalation of privilege, in MULTIPLE ways.

JFTR: to support and ease further attacks, this crap is built
      without ASLR and without stack cookies/canaries!

Vulnerability #1

rufus-3.0.exe, rufus-3.0p.exe, rufus-3.1.exe and rufus-3.1p.exe are
susceptible to DLL spoofing alias DLL search order hijacking: on a
fully patched Windows 7, they load at least the following Windows
system DLLs from their "application directory", typically the user's
"Downloads" directory %USERPROFILE%\Downloads\, instead from Windows
"system directory" %SystemRoot%\System32\, resulting in arbitrary
code execution:

    DWMAPI.dll, UXTheme.dll, Version.dll, CryptSP.dll, NCrypt.dll,
    BCrypt.dll, RichEd20.dll, DSRole.dll, LogonCli.dll, DFSCli.dll,
    SAMCli.dll, DSRole.dll

For this well-known and well-documented vulnerability see
<> and
<> plus

Additionally see Microsoft's developer guidance
<> und
to avoid this bloody beginner's error.

Also see
for "prior art".

And last but not least the 20+ year old

Since the clueless developer specified "requireAdministrator" in
the embedded application manifest, his crap can only be run with
administrative privileges, resulting in arbitary code execution
WITH escalation of privilege.

Demonstration/proof of concept #1:

1. Follow the instructions from
   and build a testbed/minefield of 32-bit DLLs in your
   "Downloads" directory.

2. Download <> and
   <> and save them
   in your "Downloads" directory.

3. Run rufus-3.0.exe and rufus-3.0p.exe: notice the message boxes
   displayed from multiple DLLs created in step 1!

4. Download <> and
   <> and save them
   in your "Downloads" directory.

5. Run rufus-3.1.exe and rufus-3.1p.exe: notice the message boxes
   displayed from at least DSROLE.DLL created in step 1!

JFTR: if you don't see a message box: open the event log and view
      the entries from source "Vulnerability and Exploit Detector".


DUMP the executable installer, DUMP the portable crap, provide an
.MSI, or a .CAB plus an .INF script.


See <!execute.html>

Vulnerability #2

Although running with administrative privileges, this crap extracts
files UNPROTECTED [1] into the "current working directory" for later
execution (and into the user's %TEMP% directory for later use).

For this well-known and well-documented vulnerability see
<> and
<> plus

An unprivileged user/process running in the same user account [2]
can modify the extracted files between their creation and use, and
can even create bogus files instead, which this crap then executes.
Remember that it runs with administrative rights!

Demonstration/proof of concept #2a:

1. Open a command prompt, then run the following command lines:

      MKDIR "%SystemDrive%\CRAPWARE"
      ATTRIB.exe +R

2. Run the following command line:


   Notice the string "\n" pasted into the command prompt
   window (really: into the window which happens to have focus) and
   the copy of the command processor started.

3. Run the following command line:


   Again notice the string "\n" pasted into the command
   prompt window, and the subsequent dialog box stating that
   another instance of this crap is already running.

Demonstration/proof of concept #2b:

1. Run the following command lines in the still open command

   ATTRIB.exe -R
   SET NoDefaultCurrentDirectoryInExePath=*

2. Run the command lines


3. Notice the error messages

   | "" is not recognized as an internal or external command,
   | operable program or batch file.

   from the command prompt, and the complete failure of this crap.

Demonstration/proof of concept #2c:

1. Add the NTFS ACE "(D;OIIO;WP;;;WD)" meaning "deny execution of
   files in this directory for everyone, inheritable to files in
   subdirectories" to the current working directory

2. Run the vulnerable applications: notice their complete failure,
   they neither display their window nor any error message!

3. View the access rights of the file "" created in the

stay tuned, and FAR AWAY from such vulnerable and defective crap
Stefan Kanthak

[1] on Windows, every developer past absolute beginner uses the
    fourth argument of CreateFile()
    or the second argument of CreateDirectory()
    to specify a "security descriptor" with the desired and needed
    access rights, at least and especially when running privileged.

[2] the ONE and ONLY user account created during Windows setup is an
    administrator account, and it is used by the vast majority of
    Windows users for their everyday work: according to Microsoft's
    own telemetry data, as published in their "Security Intelligence
    Reports" <>
    about 1/2 to 3/4 of all (some 600 million) Windows installations
    report only one active user account.

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

Powered by blists - more mailing lists