Riverbed Optimization System (RiOS) must implement replay-resistant authentication mechanisms for network access to privileged accounts.

From Riverbed SteelHead CX v8 NDM Security Technical Implementation Guide

Associated with: CCI-001941

SV-77443r1_rule Riverbed Optimization System (RiOS) must implement replay-resistant authentication mechanisms for network access to privileged accounts.

Vulnerability discussion

A replay attack may enable an unauthorized user to gain access to the application. Authentication sessions between the authenticator and the application validating the user credentials must not be vulnerable to a replay attack.An authentication process resists replay attacks if it is impractical to achieve a successful authentication by recording and replaying a previous authentication message. Techniques used to address this include protocols using nonces (e.g., numbers generated for a specific one-time use) or challenges (e.g., TLS, WS_Security). Additional techniques include time-synchronous or challenge-response one-time authenticators.

Check content

Verify that RiOS is configured to implement replay resistant authentication mechanisms for network access to privileged accounts. Navigate to the device CLI Type: enable Type: show config full Type: Spacebar to tab through the configuration Verify that the following commands are contained in the configuration "no web http enable" "web https enable" "no web ssl protocol sslv3" "no web ssl protocol tlsv1" "web ssl protocol tlsv1.1" "web ssl protocol tlsv1.2" If all of the above configurations are not defined as listed, this is a finding.

Fix text

Configure RiOS to implement replay resistant authentication mechanisms for network access to privileged accounts. Navigate to the device CLI Type: enable Type: conf t Type: no web http enable Type: web https enable Type: no web ssl protocol sslv3 Type: no web ssl protocol tlsv1 Type: web ssl protocol tlsv1.1 Type: web ssl protocol tlsv1.2 Type: write memory Type: exit Type: exit

Pro Tips

Lavender hyperlinks in small type off to the right (of CSS class id, if you view the page source) point to globally unique URIs for each document and item. Copy the link location and paste anywhere you need to talk unambiguously about these things.

You can obtain data about documents and items in other formats. Simply provide an HTTP header Accept: text/turtle or Accept: application/rdf+xml.