CVE-2017-13130
First published: Wed Aug 23 2017(Updated: )
mcmnm in BMC Patrol allows local users to gain privileges via a crafted libmcmclnx.so file in the current working directory, because it is setuid root and the RPATH variable begins with the .: substring.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| BMC Patrol Agent |
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.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2017-13130?
CVE-2017-13130 is classified as a high severity vulnerability due to the potential for local privilege escalation.
How do I fix CVE-2017-13130?
To fix CVE-2017-13130, remove the setuid bit from the mcmnm binary and ensure that the RPATH variable does not start with .:.
Who is affected by CVE-2017-13130?
Local users of BMC Patrol are affected by CVE-2017-13130 if they can manipulate the libmcmclnx.so file in the current working directory.
What does CVE-2017-13130 exploit?
CVE-2017-13130 exploits the setuid root permission of the mcmnm binary, allowing users to run malicious code with elevated privileges.
Is there a workaround for CVE-2017-13130?
A workaround for CVE-2017-13130 includes restricting access to the directories where the mcmnm binary is executed to prevent untrusted users from creating malicious files.
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/severity
- agent/references
- agent/weakness
- agent/author
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- agent/softwarecombine
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/bmc
- canonical/bmc patrol agent