CVE-2012-5477
First published: Thu May 08 2014(Updated: )
The smart proxy in Foreman before 1.1 uses a umask set to 0, which allows local users to modify files created by the daemon via unspecified vectors.
Credit: secalert@redhat.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| The Foreman | <=1.0 | |
| <=1.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Frequently Asked Questions
What is the severity of CVE-2012-5477?
The severity of CVE-2012-5477 is classified as medium due to the potential for local users to modify critical files.
How do I fix CVE-2012-5477?
To fix CVE-2012-5477, update Foreman to version 1.1 or later to ensure the umask is set properly.
Who is affected by CVE-2012-5477?
CVE-2012-5477 affects users of Foreman versions before 1.1 that allow local access.
What type of vulnerability is CVE-2012-5477?
CVE-2012-5477 is a local privilege escalation vulnerability due to improper file permissions.
Can CVE-2012-5477 be exploited remotely?
CVE-2012-5477 cannot be exploited remotely as it requires local access to the affected systems.
- agent/references
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/severity
- agent/author
- agent/description
- agent/first-publish-date
- collector/nvd-index
- agent/software-canonical-lookup-request
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/last-modified-date
- agent/source
- agent/tags
- agent/softwarecombine
- agent/event
- vendor/theforeman
- canonical/the foreman
- version/the foreman/1.0