Facebook many vulnerabilities found by @AnonymousOwn3r

SUBMITTED BY: Guest

DATE: Nov. 9, 2013, 9:01 a.m.

FORMAT: Text only

SIZE: 4.6 kB

Raw Download

HITS: 1134

Report
  1. Facebook many vulnerabilities found by @AnonymousOwn3r
  3. https://twitter.com/AnonymousOwn3r
  7. http://www.facebook.com
  9. 2720/2724 100%
  10. Cross-site Request Forgery
  12. Cross-site Request Forgery (CSRF) is a type of attack whereby unauthorized commands are transmitted from a user that the application trusts. Unlike Cross-site Scripting (XSS), which exploits the trust a user has for a particular site, CSRF exploits the trust that a site has in a user's browser.
  14. solution: Url and Forms that perform important operations must be protected by random tokens (hidden nonce values). These tokens must be checked for validity at the server before the request is processed.
  16. url: http://www.facebook.com/
  18. form: <form method="POST" action="http://www.facebook.com/" enctype="application/x-www-form-urlencoded" autocomplete="on"> ... </form>
  20. url: http://www.facebook.com/find-friends?ref=pf
  22. form: <form method="POST" action="https://www.facebook.com/find-friends/index.php" enctype="application/x-www-form-urlencoded" autocomplete="on"> ... </form>
  24. url: http://www.facebook.com/facebook
  26. form: <form method="POST" action="http://www.facebook.com/ajax/ufi/modify.php" enctype="application/x-www-form-urlencoded" autocomplete="on"> ... </form>
  28. url: http://www.facebook.com/pages/create.php?ref_type=sitefooter
  30. form: <form method="POST" action="http://www.facebook.com/ajax/pages/create/CreatePageCheck.php" enctype="application/x-www-form-urlencoded" autocomplete="on"> ... </form>
  32. url: http://www.facebook.com/help/adpolicy
  34. form: <form method="POST" action="http://www.facebook.com/support/ajax/feedback.php" enctype="application/x-www-form-urlencoded" autocomplete="on"> ... </form>
  36. url: http://www.facebook.com/r.php?possible_fb_user=1&is_enabled=1&next=https%253A%252F%252Fwww.facebook.com%252Fphoto.php%253Fv%253D3802752155040&locale=en_US
  38. form: <form method="POST" action="http://www.facebook.com/r.php?possible_fb_user=1&is_enabled=1&next=https%253A%252F%252Fwww.facebook.com%252Fphoto.php%253Fv%253D3802752155040&locale=en_US" enctype="application/x-www-form-urlencoded" autoc...
  39. Autocomplete Enabled
  41. Autocomplete should be disabled (autocomplete="off"), especially in forms which process sensitive data, such as forms with password fields, since an attacker, if able to access the browser cache, could easily obtain the cached information in cleartext.
  43. solution: Disable the autocomplete feature (autocomplete="off") on forms which may hold sensitive data.
  45. url: http://www.facebook.com/
  47. form: <form method="POST" action="http://www.facebook.com/" enctype="application/x-www-form-urlencoded" autocomplete="on"> ... </form>
  49. url: http://www.facebook.com/r.php?possible_fb_user=1&is_enabled=1&next=https%253A%252F%252Fwww.facebook.com%252Fphoto.php%253Fv%253D3802752155040&locale=en_US
  51. form: <form method="POST" action="http://www.facebook.com/r.php?possible_fb_user=1&is_enabled=1&next=https%253A%252F%252Fwww.facebook.com%252Fphoto.php%253Fv%253D3802752155040&locale=en_US" enctype="application/x-www-form-urlencoded" autoc...
  52. Path Disclosure
  54. Various system paths were disclosed within the application client source code or other files. This information could be used by attackers to make an educated guess about the application environment and any inherited weaknesses that may come with it.
  56. solution: It is recommended to re-examine the system path disclosures and remove their reference from the application's source code.
  58. path: e:\u003C ...
  60. request:
  62. GET http://www.facebook.com/jackie HTTP/1.1
  65. path: d:\u003C ...
  67. request:
  69. GET http://www.facebook.com/jackie HTTP/1.1
  72. IP Disclosure
  74. The server or application disclosed internal network information. This information could be used by attackers to make an educated guess about the internal or external network topology. Leaked IP addresses could be used as a stepping-stone to more complex attacks.
  76. solution: Ensure that sensitive information such as internal or external IP addresses is safely guarded. Unless there is a good, prevent the disclosure of network information.
  78. ip: 10.3.181.34
  80. request:
  82. GET http://www.facebook.com/careers/?ref=pf HTTP/1.1
  85. Facebook many vulnerabilities found by @AnonymousOwn3r
  87. https://twitter.com/AnonymousOwn3r
comments powered by Disqus