SQL injection vulnerability in MySQL 4.1.x before 4.1.20 and 5.0.x before 5.0.22 allows context-dependent attackers to execute arbitrary SQL commands via crafted multibyte encodings in character sets such as SJIS, BIG5, and GBK, which are not properly handled when the mysql_real_escape function is used to escape the input.
Publish Date : 2006-06-01 Last Update Date : 2010-08-21
| Cvss Score |
7.5 |
| Confidentiality Impact |
Partial
(There is considerable informational disclosure.) |
| Integrity Impact |
Partial
(Modification of some system files or information is possible, but the attacker does not have control over what can be modified, or the scope of what the attacker can affect is limited.) |
| Availability Impact |
Partial
(There is reduced performance or interruptions in resource availability.) |
| Access Complexity |
Low
(Specialized access conditions or extenuating circumstances do not exist. Very little knowledge or skill is required to exploit. ) |
| Authentication |
Not required
(Authentication is not required to exploit the vulnerability.) |
| Gained Access |
User |
| Vulnerability Type(s) |
Execute CodeSql Injection |
| CWE ID |
CWE id is not defined for this vulnerability |
OVAL (Open Vulnerability and Assessment Language) definitions define exactly what should be done to verify
a vulnerability or a missing patch. Check out the OVAL definitions
if you want to learn what you should do to verify a vulnerability.
