Dark Mode

Settings

Capec-31 Detail

Accessing/Intercepting/Modifying HTTP Cookies

Detailed Software Likelihood: High Typical Severity: High

Parents: 39 157

Threats: T60 T65 T98 T291 T293

Tools: 18

Description

This attack relies on the use of HTTP Cookies to store credentials, state information and other critical data on client systems. There are several different forms of this attack. The first form of this attack involves accessing HTTP Cookies to mine for potentially sensitive data contained therein. The second form involves intercepting this data as it is transmitted from client to server. This intercepted information is then used by the adversary to impersonate the remote user/session. The third form is when the cookie's content is modified by the adversary before it is sent back to the server. Here the adversary seeks to convince the target server to operate on this falsified information.

Not present

Explore
  1. Obtain copy of cookie: The adversary first needs to obtain a copy of the cookie. The adversary may be a legitimate end user wanting to escalate privilege, or could be somebody sniffing on a network to get a copy of HTTP cookies.

  2. Techniques
    Sniff cookie using a network sniffer such as Wireshark
    Obtain cookie using a utility such as the Firefox Cookie Manager, Chrome DevTools or AnEC Cookie Editor.
    Steal cookie via a cross-site scripting attack.
    Guess cookie contents if it contains predictable information.
Experiment
  1. Obtain sensitive information from cookie: The adversary may be able to get sensitive information from the cookie. The web application developers may have assumed that cookies are not accessible by end users, and thus, may have put potentially sensitive information in them.

  2. Techniques
    If cookie shows any signs of being encoded using a standard scheme such as base64, decode it.
    Analyze the cookie's contents to determine whether it contains any sensitive information.
  3. Modify cookie to subvert security controls.: The adversary may be able to modify or replace cookies to bypass security controls in the application.

  4. Techniques
    Modify logical parts of cookie and send it back to server to observe the effects.
    Modify numeric parts of cookie arithmetically and send it back to server to observe the effects.
    Modify cookie bitwise and send it back to server to observe the effects.
    Replace cookie with an older legitimate cookie and send it back to server to observe the effects. This technique would be helpful in cases where the cookie contains a "points balance" for a given user where the points have some value. The user may spend their points and then replace their cookie with an older one to restore their balance.
  1. Target server software must be a HTTP daemon that relies on cookies.
  2. The cookies must contain sensitive information.
  3. The adversary must be able to make HTTP requests to the server, and the cookie must be contained in the reply.
  1. A utility that allows for the viewing and modification of cookies. Many modern web browsers support this behavior.
Low High
To overwrite session cookie data, and submit targeted attacks via HTTP
Exploiting a remote buffer overflow generated by attack
Integrity Authorization Access Control Confidentiality
Modify Data Gain Privileges Gain Privileges Read Data
Gain Privileges
  1. There are two main attack vectors for exploiting poorly protected session variables like cookies. One is the local machine itself which can be exploited directly at the physical level or indirectly through XSS and phishing. In addition, the adversary in the middle attack (CAPEC-94) relies on a network sniffer, proxy, or other intermediary to intercept the subject's credentials and use them to impersonate the digital subject on the host. The issue is that once the credentials are intercepted, impersonation is trivial for the adversary to accomplish if no other protection mechanisms are in place. See also: CVE-2010-5148 , CVE-2016-0353