Skip to content
Exploiting Buffer Overflow Vulnerability In Borland AccuRev Reprise License Server
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.


mail : twitter :

I try to Exploit recently published vulnerability in Borland AccuRev

this vulnerability allows remote attackers to execute arbitrary code on 
vulnerable installations of Borland AccuRev. Authentication is not required
to exploit this vulnerability.

The specific flaw exists within the service_startup_doit functionality
of the Reprise License Manager service. The issue lies in the handling 
of the licfile parameter which can result in overflowing a stack-based buffer.
An attacker could leverage this vulnerability to execute code under the context of SYSTEM.

there was two fake information in ZDI report

  1. mapping between string and function is "service_Setup_doit" not "service_startup_doit".
  2. vulnerable parameter is "debuglog" not "licfile".

RLM come with AccuRev but it can be directly download by following link:

searching "service_startup_doit" string inside rlm.exe dont have any results so i changed it to "service_" to get following strings.

alt tag

after some reversing and analyzing functions that use above string i decide to use another way to finding bug.

ZDI said vulnerable function is accessible remotely so I start read RLM manual to find out how it work , RLM have Web interface it start http server on port 5054 , with the help of burpsuite we can view all http parameters in post or get requests, after fuzzing Web interface i found target "licfile" parameter in one Post request. alt tag

for checking licfile parameter vulnerability with help of BurpSuite i send big string parameter to web server. alt tag but rlm.exe send error response without any crash. alt tag i set breakpoint in Immunity debugger to track how rlm.exe validate size of string . alt tag

based on above asm code rlm check string size be less than or equal to 0x400 to prevent buffer overflow so i thought my rlm.exe version is not vulnerable but i start fuzzing other attack vectors,so I find out if we send big string with "debuglog" parameter to rlm.exe,and if string is less than 0x400 to bypass above check we can overwrite return value in stack with notorious 0x41414141,so i as said vulnerable function is "debuglog" not "licfile".

alt tag

i checked rlm.exe and it does not support ASLR but there was a big problem,rlm.exe contains null in its address,so we can't use any address on it to build our ROP,because it use string copy functions and it copy string in stack until null byte. so exploiting this vulnerability is so simple in XP,just return to shellcode inside stack without ROP.

import requests
data= {
print, data=data).text
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.