A client of ours needs total PCI compliance (medical-related website). We initially passed the first scan last month with help from our host and all seemed fine. But this week a new scan failed at the login screen for EE. The details:
Path: /admin/admin.php?S=0=cp=login
Poor authentication practices may leave the web application vulnerable to authentication attacks.Solution:
To use HTML form-based authentication more securely in web applications, do the following:
- Remove the value attribute from the INPUT tag corresponding to the password field.
- Submit all forms to an SSL-enabled (https) service using the form’s action attribute.
- Place all protected web directories on an SSL-enabled (https) service.
- Use the autocomplete=“off” attribute in the INPUT tag corresponding to the password field.
A few things. We access the CP through /adm and not /admin. I also did a search on HTTPS for the CP and didn’t find much definitive information in return (just a handful of broken / hacky options). Wasn’t sure, too, if I could manually adjust the login form HTML itself to mitigate the scan error.
What do you think?