CVE-2017-7540

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.

Category

9.8
CVSS
Severity: Critical
CVSS 3.0 •
CVSS 2.0 •
EPSS 0.29%
Affected: Red Hat, Inc. rubygem-safemode
Published at:
Updated at:

References

Link Tags
https://github.com/svenfuchs/safemode/pull/23 issue tracking

Frequently Asked Questions

What is the severity of CVE-2017-7540?
CVE-2017-7540 has been scored as a critical severity vulnerability.
How to fix CVE-2017-7540?
To fix CVE-2017-7540, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2017-7540 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2017-7540 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2017-7540?
CVE-2017-7540 affects Red Hat, Inc. rubygem-safemode.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.