CVE-2004-0521: SQL Injection
Published Jun 3, 2004
·Updated
SQL injection vulnerability in SquirrelMail before 1.4.3 RC1 allows remote attackers to execute unauthorized SQL statements, with unknown impact, probably via abookdatabase.php.
Affected Software
18 affected components
Squirrelmail Squirrelmail=1.4.2
Squirrelmail Squirrelmail=1.0.5
Squirrelmail Squirrelmail=1.2.7
Squirrelmail Squirrelmail=1.2.0
SGI ProPack=3.0
Squirrelmail Squirrelmail=1.2.9
Squirrelmail Squirrelmail=1.2.2
Squirrelmail Squirrelmail=1.2.1
Squirrelmail Squirrelmail=1.4.1
Squirrelmail Squirrelmail=1.4
Squirrelmail Squirrelmail=1.2.4
Squirrelmail Squirrelmail=1.2.3
Squirrelmail Squirrelmail=1.0.4
Squirrelmail Squirrelmail=1.2.6
Squirrelmail Squirrelmail=1.2.10
Squirrelmail Squirrelmail=1.2.5
Squirrelmail Squirrelmail=1.2.8
Squirrelmail Squirrelmail=1.2.11
Remediation
Patch Available
Event History
Jun 3, 2004
CVE Published
via MITRE·08:00 AM
Data Sourced
via MITRE·08:00 AM
Description
Frequently Asked Questions
1
What is the severity of CVE-2004-0521?
CVE-2004-0521 has a moderate severity level due to the potential for unauthorized access through SQL injection.
2
How do I fix CVE-2004-0521?
To fix CVE-2004-0521, upgrade SquirrelMail to version 1.4.3 RC1 or later, which addresses the SQL injection vulnerability.
3
Which versions of SquirrelMail are affected by CVE-2004-0521?
CVE-2004-0521 affects SquirrelMail versions 1.0.4 through 1.4.2.
4
Can CVE-2004-0521 lead to data loss?
CVE-2004-0521 can potentially allow attackers to execute unauthorized SQL commands, which could lead to data exposure or loss.
5
What is the impact of exploiting CVE-2004-0521?
Exploiting CVE-2004-0521 may allow attackers to manipulate the database backend, affecting the integrity and confidentiality of stored data.