Advisory Published
Updated

CVE-2013-4020

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.3 allows remote authenticated users to bypass intended access restrictions via unspecified vectors.

Credit: psirt@us.ibm.com

Affected SoftwareAffected VersionHow to fix
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=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=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

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-2013-4020?

    CVE-2013-4020 has a medium severity rating that reflects the potential for unauthorized access to sensitive data.

  • How do I fix CVE-2013-4020?

    To fix CVE-2013-4020, upgrade IBM Maximo Asset Management to version 7.5.0.3 or later.

  • What impact does CVE-2013-4020 have on IBM Maximo Asset Management users?

    CVE-2013-4020 allows remote authenticated users to bypass access restrictions, posing a significant security risk.

  • Which versions of IBM Maximo Asset Management are affected by CVE-2013-4020?

    CVE-2013-4020 affects IBM Maximo Asset Management versions 6.2 to 6.2.8, 7.1 to 7.1.1.12, and versions prior to 7.5.0.3.

  • Is there a workaround for CVE-2013-4020?

    There are no documented workarounds for CVE-2013-4020; upgrading to a fixed version is recommended.

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.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203