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).
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.
- Abstraction
- BaseA weakness specific enough to point to detection and prevention methods.
- Likelihood of exploit
- High
- Status
- Incomplete
Common consequences
- Access Control
Gain Privileges or Assume Identity
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.
- 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.
Related weaknesses
Parent weaknesses
CAPEC attack patterns that exploit it
- CAPEC-60Reusing Session IDs (aka Session Replay)
- CAPEC-94Adversary in the Middle (AiTM)
- CAPEC-102Session Sidejacking
- CAPEC-509Kerberoasting
- CAPEC-555Remote Services with Stolen Credentials
- CAPEC-561Windows Admin Shares with Stolen Credentials
- CAPEC-644Use of Captured Hashes (Pass The Hash)
- CAPEC-645Use of Captured Tickets (Pass The Ticket)
- CAPEC-652Use of Known Kerberos Credentials
- CAPEC-701Browser in the Middle (BiTM)