CWE-294: Authentication Bypass by Capture-replay

Description

A capture-replay flaw exists when the design of the product makes it possible for a malicious user to sniff network traffic and bypass authentication by replaying it to the server in question to the same effect as the original message (or with minor changes).

Extended Description

Capture-replay attacks are common and can be difficult to defeat without cryptography. They are a subset of network injection attacks that rely on observing previously-sent valid commands, then changing them slightly if necessary and resending the same commands to the server.

ThreatScore

Threat Mapped score: 0.0

Industry: Finiancial

Threat priority: Unclassified

Observed Examples (CVEs)

CVE: CVE-2005-3435

product authentication succeeds if user-provided MD5 hash matches the hash in its database; this can be subjected to replay attacks.
CVE: CVE-2007-4961

Chain: cleartext transmission of the MD5 hash of password (CWE-319) enables attacks against a server that is susceptible to replay (CWE-294).

Related Attack Patterns (CAPEC)

Attack TTPs

T1557 — Adversary-in-the-Middle (credential-access, collection)
T1133 — External Remote Services (persistence, initial-access)
T1558 — Steal or Forge Kerberos Tickets (credential-access)
T1021.002 — SMB/Windows Admin Shares (lateral-movement)
T1021 — Remote Services (lateral-movement)
T1550.003 — Pass the Ticket (defense-evasion, lateral-movement)
T1134.001 — Token Impersonation/Theft (defense-evasion, privilege-escalation)
T1114.002 — Remote Email Collection (collection)
T1550.004 — Web Session Cookie (defense-evasion, lateral-movement)
T1550.002 — Pass the Hash (defense-evasion, lateral-movement)
T1558.003 — Kerberoasting (credential-access)

Malware

APTs (Intrusion Sets)

Modes of Introduction

Phase	Note
Architecture and Design	COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic.

Common Consequences

Impact: Gain Privileges or Assume Identity — Notes: Messages sent with a capture-relay attack allow access to resources which are not otherwise accessible without proper authentication.

Potential Mitigations

Architecture and Design: Utilize some sequence or time stamping functionality along with a checksum which takes this into account in order to ensure that messages can be parsed only once. (N/A)
Architecture and Design: Since any attacker who can listen to traffic can see sequence numbers, it is necessary to sign messages with some kind of cryptography to ensure that sequence numbers are not simply doctored along with content. (N/A)

Applicable Platforms

None (Not Language-Specific, Undetermined)

Demonstrative Examples

N/A

Notes

No notes available.

← Back to CWE list