dbcve.org
Maximo Application SuiteApplication · Ibm

CVE-2024-35150

MEDIUM · 5.3 CVSS v3.1 Published 2025-01-25
Fix available
A fix is available. Upgrade to 8.10.15 / 8.11.13 or later.
See remediation →
62/100
Remediation priority · Elevated
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.12, 8.11.0, 9.0.1, and 9.1.0 - Monitor Component does not neutralize output that is written to logs, which could allow an attacker to inject false log entries.

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

The Monitor Component in IBM Maximo Application Suite versions 8.10.12, 8.11.0, 9.0.1, and 9.1.0 does not properly neutralize or sanitize output before writing to log files, allowing an attacker to inject arbitrary content into application logs (log injection/log forging vulnerability).

MitigationApply IBM's security patch for this vulnerability and implement proper output encoding for all log output in the Monitor Component to prevent injection of false log entries.

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.12, < 8.10.15>= 8.11, < 8.11.13>= 9.0.1, < 9.0.5= 9.1.0

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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 Application Suite version
    Check the product version through the Maximo administration interface, installation logs, or system information panel. This is typically visible in the 'System Information' or 'About' section of the administration console.
    Affected if The installed version falls within these ranges: 8.10.12 through 8.10.14.x, 8.11.0 through 8.11.12.x, 9.0.1 through 9.0.4.x, or exactly 9.1.0
  2. Confirm the Monitor Component is in use
    Review the active components in your IBM Maximo Application Suite deployment. The Monitor Component is typically listed in the component inventory or configuration settings of the suite.
    Affected if The Monitor Component is installed and active in the environment
  3. Compare your version against the fixed releases
    Reference the version numbering to determine if your deployment is running a version that contains the patch. The fixed versions are: 8.10.15 and later, 8.11.13 and later, 9.0.5 and later, or any version after 9.1.0.
    Affected if Your installed version is earlier than the fixed releases listed above and matches one of the affected version ranges
  4. Inspect application log files for anomalous entries
    Review logs generated by the Monitor Component for entries that contain unexpected content such as multiple newlines, fake timestamps, or suspicious data that does not correspond to known application behavior.
    Affected if Log files contain entries that appear forged or include unexpected content that was not generated by your legitimate applications

You are affected if the Monitor Component is running and your IBM Maximo Application Suite version falls within 8.10.12 to 8.10.14.x, 8.11.0 to 8.11.12.x, 9.0.1 to 9.0.4.x, or is exactly 9.1.0.

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
Upgrade available Upgrade to 8.10.15 / 8.11.13 / 9.0.5 or later
Fixed in 8.10.158.11.139.0.5
Interim mitigation

Apply IBM's security patch for this vulnerability and implement proper output encoding for all log output in the Monitor Component to prevent injection of false log entries.

Recommended fix High confidence

8.10.15 (for 8.10.x), 8.11.13 (for 8.11.x), 9.0.5 (for 9.0.x), or latest 9.1.x fix pack

  1. Identify the currently installed Maximo Application Suite version by checking the deployment configuration or IBM fix pack documentation
  2. Determine which version branch you are on (8.10.x, 8.11.x, 9.0.x, or 9.1.0)
  3. For 8.10.x branch: Upgrade to version 8.10.15 or later
  4. For 8.11.x branch: Upgrade to version 8.11.13 or later
  5. For 9.0.x branch: Upgrade to version 9.0.5 or later
  6. For 9.1.0: Upgrade to the next available fix pack that addresses CVE-2024-35150
  7. After upgrade, verify the Monitor Component log output is properly neutralized per IBM's security guidelines
Caveat Review IBM's migration guide for your version path as minor version upgrades may include configuration or compatibility changes; test in non-production environment first

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

Fix this in Maximo Application Suite Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-35150 — 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-2024-35150 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