CVE-2017-3191

Allows detection of capture-replay attacks by showing the replayed logon's timestamp as the last logon.

Security testing and developer training directly verify and enforce proper input validation, reducing exploitability of injection and malformed-data weaknesses.

Security testing and evaluation at multiple SDLC stages directly detects missing or flawed input validation, with the required remediation process ensuring fixes are applied.

Protects against replay of captured session tokens or credentials by requiring authenticated, fresh session channels.

Wireless link protections commonly incorporate replay protection, reducing the exploitability of capture-replay weaknesses.

Accurate synchronized time enables tight timestamp windows that directly limit capture-replay windows in authentication protocols.

Directly implements checks on information inputs to reject invalid data before processing.

Spam protection mechanisms perform filtering and detection on inbound/outbound messages, directly compensating for missing or weak input validation of unsolicited content.

Network monitoring may detect anomalous replays after the fact but does not prevent the design flaw.

Strong authentication methods can reduce replay risk but do not inherently address captured messages.

Network security controls such as encryption and integrity protection reduce the feasibility of capturing and replaying authentication traffic.

Secure-coding guidelines and mandatory security testing (including code scans) compel developers to validate and sanitize inputs at design and implementation time, lowering the incidence of malformed or malicious data reaching downstream components.

Application security requirements can mandate replay-resistant authentication designs, but the control itself does not prescribe the technical measures.