# CVE-2017-5670: Information disclosure in n/a

> Physically proximate attackers can recover sensitive data from raw disk blocks because the secure vault is deleted using rm instead of a secure deletion tool.

- **Severity:** Medium 4.6 (`CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **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-hcf7-f32r-4jgm

## What is CVE-2017-5670?

CVE-2017-5670 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 through 9.6.0 deletes the secure vault with the rm program (not shred or srm), which makes it easier for physically proximate attackers to obtain sensitive information by reading raw disk blocks.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Riverbed Rios.

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

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

## Is CVE-2017-5670 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-7307](https://insights.sbomify.com/CVE-2017-7307/): Privilege escalation in n/a (medium 6.8)
- [CVE-2017-7306](https://insights.sbomify.com/CVE-2017-7306/): Hardcoded credentials in n/a (medium 6.4)
- [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-5670 and fix it if it is affected.

What it is: CVE-2017-5670 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-5670 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-5670/ (Markdown: https://insights.sbomify.com/CVE-2017-5670/index.md)
```

## Sources

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

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