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!
GLPI 0.90.4 - SQL Injection Vulnerability
Author
Risk
[
Security Risk High
]0day-ID
Category
Date add
CVE
Platform
# Exploit Title: Multiple SQL injection vulnerabilities in GLPI 0.90.4 # Exploit Author: Eric CARTER (in/ericcarterengineer - CS c-s.fr) # Vendor Homepage: http://glpi-project.org # Software Link: http://glpi-project.org/spip.php?article3 # Version: 0.90.4 # Tested on: GLPI 0.90.4 running on a Debian 7, Apache 2.2.2, MySQL 5.5.49 # CVE : CVE-2016-7508 Multiple SQL injection vulnerabilities in GLPI 0.90.4 allow an authenticated remote attacker to execute arbitrary SQL commands by using the [ELIDED] character when the database is configured to use asian encoding (BIG 5). > [Affected Component] The file ./inc/dbmysql.class.php defines the encoding the database should use. This files uses the "SET NAMES" function which offers the possibility to use a specific encoding. > [Attack Type] Remote > [Impact Code execution] True > [Impact Escalation of Privileges] True > [Impact Information Disclosure] True > [Prerequisite] The administrator of GLPI must have defined the variable $dbenc='big5' in ./config/config_db.php to support asian encoding. It will then be possible to do SQL injection in almost all the forms of the application. > [Attack Vectors] For the proof-of-concept, the attacker targeted the "Surname" form input in the User profile by adding the characters ø (\xBF\x27) before the SQL code (the request must be sent using Western encoding) : ø', password=61529519452809720693702583126814 -- x Once received by the server, the request will be sanitized, giving : ø\', password=61529519452809720693702583126814 -- x The value will then be sent to the database with a BIG5 encoding. Here is the critical point, as BIG5 will see the string ø\ as a single asian character encoded on two bytes. As the single quote isn't escaped anymore, the SQL code will be executed and will set the password of every accounts to the value 61529519452809720693702583126814 (=MD5 hash of "ximaz" string) # 0day.today [2024-09-29] #