Advertisement
Guest User

Untitled

a guest
Mar 30th, 2017
224
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 2.05 KB | None | 0 0
  1.  
  2. Issue:  
  3. Cleartext submission of password
  4. Severity:  
  5. High
  6. Confidence:  
  7. Certain
  8. Host:  
  9. http://blog.andersenenviro.com
  10. Path:  
  11. /wp-login.php
  12.  
  13. Issue detail
  14. The page contains a form with the following action URL, which is submitted over clear-text HTTP:
  15. http://blog.andersenenviro.com/wp-login.php
  16. The form contains the following password field:
  17. pwd
  18.  
  19. Issue background
  20. Some applications transmit passwords over unencrypted connections, making them vulnerable to interception. To exploit this vulnerability, an attacker must be suitably positioned to eavesdrop on the victim's network traffic. This scenario typically occurs when a client communicates with the server over an insecure connection such as public Wi-Fi, or a corporate or home network that is shared with a compromised computer. Common defenses such as switched networks are not sufficient to prevent this. An attacker situated in the user's ISP or the application's hosting infrastructure could also perform this attack. Note that an advanced adversary could potentially target any connection made over the Internet's core infrastructure.
  21. Vulnerabilities that result in the disclosure of users' passwords can result in compromises that are extremely difficult to investigate due to obscured audit trails. Even if the application itself only handles non-sensitive information, exposing passwords puts users who have re-used their password elsewhere at risk.
  22. Issue remediation
  23. Applications should use transport-level encryption (SSL or TLS) to protect all sensitive communications passing between the client and the server. Communications that should be protected include the login mechanism and related functionality, and any functions where sensitive data can be accessed or privileged actions can be performed. These areas should employ their own session handling mechanism, and the session tokens used should never be transmitted over unencrypted communications. If HTTP cookies are used for transmitting session tokens, then the secure flag should be set to prevent transmission over clear-text HTTP.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement