Posts

Showing posts with the label Privacy Violation

Privacy Violation : Autocomplete

Summary Most recent browsers have features that will save password field content entered by users and then automatically complete password entry the next time the field are encountered. This feature is enabled by default and could leak password since it is stored on the hard drive of the user. The risk of this issue is greatly increased if users are accessing the application from a shared environment. Recommendations include setting autocomplete to "off" on all your password fields. Please Note: Recent versions of most browsers, as noted below, now ignore the autocomplete="off" attribute for password fields in html forms. Users are allowed to decide the password policy at their own discretion using the password manager. Although setting is ineffective on these versions of browsers, it would continue to protect website users of earlier versions of these and other browsers that support this attribute. Browsers NOT Supporting autocomplete="off": 1. Internet E...

Inconsistent Feedback

Image
Privacy Violation : Inconsistent Feedback OWASP Top 10: PCI 3.2: Summary When entering an invalid user name or password during a login, forgotten password, profile updates or new user signup function, the application provides meaningful feedback through a response  discrepancy. For the potential attacker, this discrepancy increases the chances of a successful brute force attack against the site's authentication. Explanation A successful brute force attack against the site's authentication would place the application user's personal information at risk as well as increase the likelihood of fraud within the application. Execution Due to the application providing meaningful feedback, an attacker can utilize a large list of potential usernames and/or email addresses to determine valid accounts. Recommendation The application should not indicate specifically whether a user account or password was incorrect, rather a very generic message stating that the login failed should be us...