# CVE-2017-7307: Privilege escalation in n/a

> Physically proximate attackers can gain root privileges and access decrypted data by replacing a CLI file in single-user mode.

- **Severity:** Medium 6.8 (`CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Apr 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-5xh4-q744-67gj

## What is CVE-2017-7307?

CVE-2017-7307 is a medium-severity vulnerability in n/a, published on 4 Apr 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2017-7307?

It affects 1 product.


Products: Riverbed Rios.

## How do I fix CVE-2017-7307?

No fix has been published for CVE-2017-7307 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-7307 being exploited?

There is no known exploitation of CVE-2017-7307 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2017-7306](https://insights.sbomify.com/CVE-2017-7306/): Hardcoded credentials in n/a (medium 6.4)
- [CVE-2017-5670](https://insights.sbomify.com/CVE-2017-5670/): Information disclosure in n/a (medium 4.6)
- [CVE-2017-7305](https://insights.sbomify.com/CVE-2017-7305/): Security feature bypass in n/a (medium 4.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-7307 and fix it if it is affected.

What it is: CVE-2017-7307 is a medium-severity vulnerability in n/a, published on 4 Apr 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-7307 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-7307/ (Markdown: https://insights.sbomify.com/CVE-2017-7307/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-7307
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-7307
- OSV: https://osv.dev/vulnerability/CVE-2017-7307

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-7307/
Summaries are generated and may contain mistakes; the official description above is the record.