dbcve.org
Maximo Application SuiteApplication · Ibm

CVE-2023-32335

HIGH · 7.5 CVSS v3.1 Published 2024-03-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

IBM Maximo Application Suite and Asset Management versions 8.10, 8.11, and 7.6.1.3 improperly store sensitive information (such as credentials, tokens, or PII) in URL query parameters. This data is then exposed through server access logs, browser history, and HTTP Referrer headers, allowing unauthorized parties to potentially access the sensitive information.

MitigationRefactor the application to transmit sensitive data via POST request bodies, session cookies, or server-side state instead of URL parameters. Additionally, audit and purge historical data from server logs, browser histories, and proxy logs to eliminate exposure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Maximo Application SuiteApplication
Affected:= 8.10= 8.11
Maximo Asset ManagementApplication
Affected:= 7.6.1.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed IBM Maximo version
    Access the Maximo System Information page or check the installation directory for version metadata. In Maximo Application Suite, go to the 'About' section in the admin menu. For Asset Management, check the maximo.properties file or the System Information application.
    Affected if The installed version matches 8.10, 8.11, or 7.6.1.3
  2. Review server access logs for sensitive URL parameters
    Examine the HTTP server access logs (typically located in the web server log directory or IBM WebSphere/HttpServer logs) for GET requests containing sensitive-looking query parameters such as 'password=', 'token=', 'credential=', 'ssn=', or 'pin=' in the URL string.
    Affected if Sensitive data such as passwords, tokens, or PII appear in URL query parameters within server access logs
  3. Inspect browser history and proxy logs
    Review browser history captures, enterprise proxy logs, or web application firewall (WAF) logs for requests to Maximo URLs that contain sensitive information in the query string.
    Affected if Sensitive credentials or personal information are found in browser history, proxy logs, or WAF logs associated with Maximo URLs
  4. Check HTTP Referrer header logging
    Examine server logs or application monitoring tools to determine if HTTP Referrer headers are being logged, particularly when users navigate away from pages containing sensitive data in URLs.
    Affected if Referrer logs contain URLs with sensitive query parameters that could expose credentials or PII to third parties

A user is affected if they run IBM Maximo Application Suite 8.10/8.11 or Asset Management 7.6.1.3 AND sensitive authentication or personal data is being transmitted via URL query parameters and subsequently exposed in logs or browser history.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Refactor the application to transmit sensitive data via POST request bodies, session cookies, or server-side state instead of URL parameters. Additionally, audit and purge historical data from server logs, browser histories, and proxy logs to eliminate exposure.

Recommended fix Moderate confidence

Upgrade to Maximo Application Suite 8.11.0.0+ or Maximo Asset Management 7.6.1.4+ (or latest available stable release)

  1. 1. Identify the current Maximo Application Suite or Maximo Asset Management version in use
  2. 2. Review server logs and browser history for any potentially exposed sensitive URL parameters
  3. 3. Upgrade to a fixed version of Maximo Application Suite or Maximo Asset Management that addresses CVE-2023-32335
  4. 4. After upgrade, verify that sensitive information is no longer transmitted via URL parameters
  5. 5. Clear any existing server logs, browser history, or referrer logs that may contain sensitive URL parameters from the vulnerable versions
Caveat Review IBM upgrade documentation for your specific product version to check for any breaking changes or required migration steps between versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Maximo Application Suite Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA6.0 h
50.0 hours of engineering $8,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,080.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-32335 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-32335 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data