CVE-2013-5382: Medium severity ibm maximo asset management vulnerability

Published Oct 1, 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.

Affected Software

26 affected components
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

Event History

Oct 1, 2013
CVE Published
via MITRE·10:00 AM
Data Sourced
via MITRE·10:00 AM
Description

Frequently Asked Questions

1

What is the severity of CVE-2013-5382?

CVE-2013-5382 is categorized as a medium-severity vulnerability that allows privilege escalation for authenticated remote users.

2

How do I fix CVE-2013-5382?

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.

3

Who is affected by CVE-2013-5382?

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.

4

What types of attacks can exploit CVE-2013-5382?

CVE-2013-5382 can be exploited by remote authenticated users to gain higher privileges within the system.

5

Is there a workaround for CVE-2013-5382?

Currently, there are no recommended workarounds for CVE-2013-5382, and the only effective solution is to apply the necessary updates.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203