First published: Tue Oct 01 2013(Updated: )
IBM Maximo Asset Management 6.2 through 6.2.8, 7.1 through 7.1.1.12, and 7.5 before 7.5.0.5 allows remote authenticated users to bypass intended access restrictions via unspecified vectors.
Credit: psirt@us.ibm.com
Affected Software | Affected Version | How to fix |
---|---|---|
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.1.1.12 | |
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 | |
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 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2013-4027 is considered to have a medium severity level due to its potential impact on unauthorized access.
To fix CVE-2013-4027, update IBM Maximo Asset Management to versions 7.5.0.5 or later, or apply the relevant security patches.
CVE-2013-4027 affects authenticated users of IBM Maximo Asset Management versions 6.2 through 7.1.1.12 and 7.5 before 7.5.0.5.
CVE-2013-4027 can be exploited to bypass intended access restrictions, leading to unauthorized actions within the application.
There are no known workarounds for CVE-2013-4027 other than applying the necessary updates or patches.