Umbra Wiki attack-pattern attack-pattern/CAPEC-55
Back to wiki

CAPEC-55 — Rainbow Table Password Cracking

provenance: imported · ATT&CK: T1110.002 · CWE: CWE-261 CWE-262 CWE-263 CWE-308 CWE-309 CWE-521 CWE-654 CWE-916

CAPEC-55: Rainbow Table Password Cracking

MITRE CAPEC attack pattern

Status Draft
Typical severity Medium
Likelihood of attack Medium
Catalogue CAPEC 3.9 (2023-01-24)

Description

An attacker gets access to the database table where hashes of passwords are stored. They then use a rainbow table of pre-computed hash chains to attempt to look up the original password. Once the original password corresponding to the hash is obtained, the attacker uses the original password to gain access to the system.

Where this sits in the chain

A finding maps to a weakness (CWE), a weakness is exploited by an attack pattern (CAPEC), and an attack pattern shows up in ATT&CK as observed adversary behaviour. This page is the middle hop.

Weaknesses exploited: CWE-261, CWE-262, CWE-263, CWE-308, CWE-309, CWE-521, CWE-654, CWE-916

ATT&CK techniques: T1110.002

Prerequisites

  • Hash of the original password is available to the attacker. For a better chance of success, an attacker should have more than one hash of the original password, and ideally the whole table.
  • Salt was not used to create the hash of the original password. Otherwise the rainbow tables have to be re-computed, which is very expensive and will make the attack effectively infeasible (especially if salt was added in iterations).
  • The system uses one factor password based authentication.

Skills required

  • Low: A variety of password cracking tools are available that can leverage a rainbow table. The more difficult part is to obtain the password hash(es) in the first place.

Consequences

  • Confidentiality, Access Control, Authorization: Gain Privileges

Mitigations

  • Use salt when computing password hashes. That is, concatenate the salt (random bits) with the original password prior to hashing it.

Source