Posts

Http Strict Transport Security

Image
  Summary Http Strict Transport Security (HSTS) policy enables web applications to enforce web browsers to restrict communication with the server over an encrypted SSL/TLS connection for a set period. Policy is declared via special Strict Transport Security response header. Encrypted connection protects sensitive user and session data from attackers eavesdropping on network connection. Consider following attack scenarios: Users often omit the URI scheme i.e. https:// when typing a URL in location bar to access a website. Also third party websites can link to the site using the “http” scheme instead of "https”. This could result in an initial connection to a HTTPS-enabled site over an unencrypted channel. An eavesdropping attacker can hijack this unencrypted connection and replace the intended use of HTTPS protocol with HTTP in an attack known as SSLStrip, granting unauthorized access to all subsequent traffic. Websites often transfer non-sensitive resources such as help documents ...

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...

List of HTTP status codes

Image
This is a list of Hypertext Transfer Protocol (HTTP) response status codes. Status codes are issued by a server in response to a client's request made to the server. 100 Continue 101 Switching Protocols 102 Processing 103 Early Hints (RFC 8297) 200 OK 201 Created 202 Accepted 203 Non-Authoritative Information (since HTTP/1.1) 204 No Content 205 Reset Content 206 Partial Content 207 Multi-Status (WebDAV; RFC 4918) 208 Already Reported (WebDAV; RFC 5842) 226 IM Used (RFC 3229) 300 Multiple Choices 301 Moved Permanently 302 Found (Previously "Moved temporarily") 303 See Other (since HTTP/1.1) 304 Not Modified (RFC 7232) 305 Use Proxy (since HTTP/1.1) 306 Switch Proxy 307 Temporary Redirect (since HTTP/1.1) 308 Permanent Redirect (RFC 7538) 400 Bad Request 401 Unauthorized (RFC 7235) 402 Payment Required 403 Forbidden 404 Not Found 405 Method Not Allowed 406 Not Acceptable 407 Proxy Authentication Required (RFC 7235) 408 Request Timeout 409 Conflict 410 Gone 411 Length Requir...