dbcve.org
RiosOperating system · Riverbed

CVE-2017-7307

MEDIUM · 6.8 CVSS v3.0 Published 2017-04-04
Fix available
A fix is available. Upgrade to after 9.0.0b or later.
See remediation →
73/100
Remediation priority · Elevated
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Riverbed RiOS before 9.0.1 does not properly restrict shell access in single-user mode, which makes it easier for physically proximate attackers to obtain root privileges and access decrypted data by replacing the /opt/tms/bin/cli file.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Riverbed RiOS before 9.0.1 fails to properly restrict shell access when the system boots into single-user mode. A physically proximate attacker with console access can exploit this by replacing the /opt/tms/bin/cli binary to escalate privileges to root and access decrypted data on the appliance.

MitigationUpgrade to RiOS 9.0.1 or later. Additionally, enforce physical security controls on the appliance and consider disabling or password-protecting single-user mode in the boot configuration.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
RiosOperating system
Affected:<= 9.0.0b

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Physical
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed RiOS version
    Log into the appliance CLI and run 'show version' or check the system management interface for the firmware version
    Affected if The version is 9.0.0b or any version lower than 9.0.1
  2. Verify single-user mode accessibility
    During system boot, observe whether single-user mode can be accessed without requiring authentication or if console access is unrestricted
    Affected if Single-user mode is accessible without a password or additional authentication controls
  3. Inspect the cli binary integrity
    Check the file /opt/tms/bin/cli for unexpected modifications by comparing its hash or checking file permissions and ownership
    Affected if The binary has been replaced, has unusual permissions, or shows signs of tampering indicating privilege escalation has occurred

You are affected if your RiOS version is 9.0.0b or lower AND an attacker with console access could reach single-user mode without restriction.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 9.0.0b
Interim mitigation

Upgrade to RiOS 9.0.1 or later. Additionally, enforce physical security controls on the appliance and consider disabling or password-protecting single-user mode in the boot configuration.

Fix this in Rios Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-7307 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-7307 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data