Tuesday, February 19, 2008

Cross Site Scripting @ XSS

XSS
  • curi cookies
  • 1 teknik yg digunakan oleh attacker utk hantar sebrg script pd web user.
  • berlaku pd aplikasi web
  • script yg biasa digunakan oleh XSS Javascript@VBscript utk mdptkn cookies

  • cth :
  • masukkan script (vbscript) utk buatkan (dokumen.cookies) & dptkn cookies tsbt copy & paste pd website / pc.
  • website rujukan http://www.milw0rm.com

Definisi umum:

Mana2 attacker akan hantar script pd website user yg ada vulnerability, x kira mana2 script php,html script atau lain2 yg digunakan dihantar pd website user / aplikasi web utk bypass @ masuk website tsbt.
* cara utk hack komputer : (ada byk cara )
  1. SQL Injection
  2. Remote Injection
* masukkan
  • guestbook
  • upload file



"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.


Reference : http://www.cgisecurity.com/articles/xss-faq.shtml#whatis

No comments: