A weakness and a vulnerability have been reported in phpMyAdmin, which can be exploited by malicious users to conduct script insertion attacks and by malicious people to conduct spoofing attacks, according to Secunia.
![](https://lh3.googleusercontent.com/blogger_img_proxy/AEn0k_snC5ghcZ0Y-u1so9FbeiRLcoJKvUWw9JxvxVbHlYBfXkBpCKbqvDIruwDTgGWe9HSw4_is1IIKg9p3j6DGzOoQ_tE83AU5UBRogmLO6fBL1OC1cjSqnki5Pg=s0-d)
1. Input passed via the "url" parameter to url.php is not properly verified before being used to redirect users. This can be exploited to redirect a user to an arbitrary website e.g. when a user clicks a specially crafted link to the affected script hosted on a trusted domain.
This vulnerability is reported in version 3.4.0.
2. Input passed to the application when creating a database table name is not properly sanitized before being used on the "Tracking" page. This can be exploited to insert arbitrary HTML and script code, which will be executed in a user's browser session in context of an affected site when the malicious data is being viewed.
This vulnerability is reported in version 3.4.0 and versions prior to 3.3.10.1.
Solution: Update to version 3.4.1.
1. Input passed via the "url" parameter to url.php is not properly verified before being used to redirect users. This can be exploited to redirect a user to an arbitrary website e.g. when a user clicks a specially crafted link to the affected script hosted on a trusted domain.
This vulnerability is reported in version 3.4.0.
2. Input passed to the application when creating a database table name is not properly sanitized before being used on the "Tracking" page. This can be exploited to insert arbitrary HTML and script code, which will be executed in a user's browser session in context of an affected site when the malicious data is being viewed.
This vulnerability is reported in version 3.4.0 and versions prior to 3.3.10.1.
Solution: Update to version 3.4.1.
No comments:
Post a Comment