CVE-2023-32335: IBM Maximo Application Suite information disclosure

Published Mar 12, 2024
·
Updated

IBM Maximo Application Suite 8.10, 8.11 and IBM Maximo Asset Management 7.6.1.3 stores sensitive information in URL parameters. This may lead to information disclosure if unauthorized parties have access to the URLs via server logs, referrer header or browser history. IBM X-Force ID: 255075.

Other sources

IBM Maximo Asset Management stores sensitive information in URL parameters. This may lead to information disclosure if unauthorized parties have access to the URLs via server logs, referrer header or browser history.

IBM

Affected Software

4 affected components
IBM Maximo Application Suite - Manage Component<=MAS 8.10.0 - Manage 8.6.0
IBM Maximo Application Suite=8.10
IBM Maximo Application Suite=8.11
IBM Maximo Asset Management=7.6.1.3

Event History

Mar 12, 2024
CVE Published
via IBM·12:00 AM
Mar 13, 2024
CVE Published
via MITRE·09:23 AM
Data Sourced
via MITRE·09:23 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·10:15 AM
DescriptionSeverityWeakness

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2023-32335?

The severity of CVE-2023-32335 is categorized as a medium risk due to potential information disclosure.

2

How do I fix CVE-2023-32335?

To fix CVE-2023-32335, ensure sensitive information is not stored in URL parameters and consider implementing better access controls.

3

What types of systems are affected by CVE-2023-32335?

CVE-2023-32335 affects IBM Maximo Application Suite versions 8.10, 8.11 and IBM Maximo Asset Management version 7.6.1.3.

4

What can happen if CVE-2023-32335 is exploited?

If CVE-2023-32335 is exploited, unauthorized parties may gain access to sensitive information through URL parameters.

5

Is there a known workaround for CVE-2023-32335?

There is no specific workaround for CVE-2023-32335 other than following best practices to avoid exposing sensitive data.

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