First published: Tue Oct 01 2013(Updated: )
IBM Maximo Asset Management 6.2 through 6.2.8, 7.1 before 7.1.1.12, and 7.5 before 7.5.0.5 allows remote authenticated users to gain privileges via unspecified vectors, a different vulnerability than CVE-2013-5383.
Credit: psirt@us.ibm.com
Affected Software | Affected Version | How to fix |
---|---|---|
IBM Maximo Asset Management | =6.2 | |
IBM Maximo Asset Management | =6.2.1 | |
IBM Maximo Asset Management | =6.2.2 | |
IBM Maximo Asset Management | =6.2.3 | |
IBM Maximo Asset Management | =6.2.4 | |
IBM Maximo Asset Management | =6.2.5 | |
IBM Maximo Asset Management | =6.2.6 | |
IBM Maximo Asset Management | =6.2.6.1 | |
IBM Maximo Asset Management | =6.2.7 | |
IBM Maximo Asset Management | =6.2.8 | |
IBM Maximo Asset Management | =7.1 | |
IBM Maximo Asset Management | =7.1.1 | |
IBM Maximo Asset Management | =7.1.1.1 | |
IBM Maximo Asset Management | =7.1.1.2 | |
IBM Maximo Asset Management | =7.1.1.5 | |
IBM Maximo Asset Management | =7.1.1.6 | |
IBM Maximo Asset Management | =7.1.1.7 | |
IBM Maximo Asset Management | =7.1.1.8 | |
IBM Maximo Asset Management | =7.1.1.9 | |
IBM Maximo Asset Management | =7.1.1.10 | |
IBM Maximo Asset Management | =7.1.1.11 | |
IBM Maximo Asset Management | =7.5.0.0 | |
IBM Maximo Asset Management | =7.5.0.1 | |
IBM Maximo Asset Management | =7.5.0.2 | |
IBM Maximo Asset Management | =7.5.0.3 | |
IBM Maximo Asset Management | =7.5.0.4 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2013-5382 is categorized as a medium-severity vulnerability that allows privilege escalation for authenticated remote users.
To mitigate CVE-2013-5382, update IBM Maximo Asset Management to the latest version that addresses this vulnerability, specifically version 7.1.1.12 or higher and 7.5.0.5 or higher.
CVE-2013-5382 affects IBM Maximo Asset Management versions 6.2 through 6.2.8, 7.1 prior to 7.1.1.12, and 7.5 prior to 7.5.0.5.
CVE-2013-5382 can be exploited by remote authenticated users to gain higher privileges within the system.
Currently, there are no recommended workarounds for CVE-2013-5382, and the only effective solution is to apply the necessary updates.