ON http://iflamme.com/ :

VULNERABLE JAVASCRIPT LIBRARY
	- Your javascript library is 1.8.2, and it is definitly not UPDATE

- IMPACT vulnerability : LOW (can conduct to xss & stored & csrf & malicious uses of javascript function which are deprecated)
- ATTACKER LEVEL : HIGH
- FIX : Update ur JS library



ON http://new.iflamme.com/ :

REDIRECTION WITHOUT SESSION CHECKING :

Thoses paths are accessible with session checking, which is dangerious if someone can get acces to an account, and change his SSID:

/account
/account/corder
/account/password
/account/info

- IMPACT vulnerability : MEDIUM/HIGH (can conduct to session hijacking, which is really commun in security)
- ATTACKER LEVEL : MEDIUM/EXPERT
-FIX : evry time you let someone acces a page, you need to :

 if (!isset($_SESSION[auth])) {   <---------------- not "connected" or something else between quotes
        header("Location: auth.php");
        exit(); <-------------
    }


2ND VULNERABILITY:

MULTIPLE XSS ON THE WEBSITE :

/foot
/foot/index
/news
/news/index

thoses paths contains xss, you already know what can conduct an xss, even if not stored (CSRF vulnerability, XXE, LFI, server-side template injection )
It always depends on what is running behind, but its never, never good to let XSS on a website, and its really easy to get ride of it

- IMPACT : MEDIUM
- ATTACKER LEVEL : beginner
- FIX : Escape ALL the un-wanted caracteres on the formulars you are using, the GET/POST parameters & evrything else that the user can write in/on

3RD VULNERABILITY :


http://2.haxro.fr/dperk/Bountys/pocpass.html

 ;) ;) ;) ;) <3



4RD VULNERABILITY :::

http://2.haxro.fr/dperk/Bountys/PoCSqliIgMaxe.php


 ___________


ON http://igmaxe.com/ :

VULNERABLE JAVASCRIPT LIBRARY
	- Your javascript library is 1.8.2, and it is definitly not UPDATE

- IMPACT vulnerability : LOW (can conduct to xss & stored & csrf & malicious uses of javascript function which are deprecated)
- ATTACKER LEVEL : HIGH
- FIX : Update ur JS library





------------ OVERALL TIPS--------------

----- You need https, for many reasons, but the most importants one is that the users will trust your website, with https enable. I know implementing https can be a bit tricking, but it was also protect you in the server side, an attacker can, for exemple, listen the ports on the server, if he gets an acces on it, and catch all the trafic of yours users & you (credit card & password) so it will protect you even more.

----- Change your password if you fear something, use something strong, really. MAKE THAT NO ONE APPLICATION (API, test server) HAS DEFAULT PASSWORD ON IT. Also, all the users that you are using on your server MUST HAVE RIGHTS PROTECTED, you can't give all the sudo rights so an user which only host the MYSQL server for exemple. DELET THE OLD AND NOT NEEDED USER, DO NOT LOGGIN ON THE SERVER WITH PASSWORD, USE ONLY SSH-KEY, NO ONE USERS ON YOUR SERVER HAS TO HAVE PASSWORD LOGIN ENABLE.

----- DO YOUR TESTS (migration, new website) ON AN OTHER DOMAIN NAME. new.iflamme.com is BAD, since its in construction there is vulnerability. Get an other DNS and do your test on it, and not on the same server that host the BDD & the iflamme website

----- If you have anyquestion, protection prevention, DDOS or other, feel free to ask me on skype.





27 Champions & 0 Skins
27€

Show Content