Ticket #2410 (closed security issue: fixed)
[Security Fail] A customer must not be able to connect to a database of another customer
|Reported by:||nuxwin||Owned by:||nuxwin|
|Priority:||critical||Milestone:||ispCP ω 1.0.6|
|Component:||Frontend (GUI)||Version:||ispCP ω 1.0.5|
Description (last modified by nuxwin) (diff)
Currently, it's possible for a customer to pass an arbitrary database identifier to perform pma authentication from ispCP panel (script client/pma_auth.php or client/sql_auth.php for current stable release).
Note: This security hole was discovered after the complete rewrite of the PMA authentication script but also exists in the old script (client/sql_auth.php). This security hole affect the current release and all prior versions of ispCP that implement the PMA authentication from the panel.
Note: See http://isp-control.net/ispcp/ticket/2410#comment:9 for a quick fix.
- Summary changed from [SECURITY FAIL] A customer must not be able to connect to a database of another customer to [Security Fail] A customer must not be able to connect to a database of another customer
- Status changed from assigned to closed
- Resolution set to fixed