First published: Thu Jun 03 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 abook_database.php.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
SGI ProPack | =3.0 | |
SquirrelMail | =1.0.4 | |
SquirrelMail | =1.0.5 | |
SquirrelMail | =1.2.0 | |
SquirrelMail | =1.2.1 | |
SquirrelMail | =1.2.2 | |
SquirrelMail | =1.2.3 | |
SquirrelMail | =1.2.4 | |
SquirrelMail | =1.2.5 | |
SquirrelMail | =1.2.6 | |
SquirrelMail | =1.2.7 | |
SquirrelMail | =1.2.8 | |
SquirrelMail | =1.2.9 | |
SquirrelMail | =1.2.10 | |
SquirrelMail | =1.2.11 | |
SquirrelMail | =1.4 | |
SquirrelMail | =1.4.1 | |
SquirrelMail | =1.4.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2004-0521 has a moderate severity level due to the potential for unauthorized access through SQL injection.
To fix CVE-2004-0521, upgrade SquirrelMail to version 1.4.3 RC1 or later, which addresses the SQL injection vulnerability.
CVE-2004-0521 affects SquirrelMail versions 1.0.4 through 1.4.2.
CVE-2004-0521 can potentially allow attackers to execute unauthorized SQL commands, which could lead to data exposure or loss.
Exploiting CVE-2004-0521 may allow attackers to manipulate the database backend, affecting the integrity and confidentiality of stored data.