dbcve.org
Maximo Application SuiteApplication · Ibm

CVE-2024-35144

MEDIUM · 5.3 CVSS v3.1 Published 2025-01-25
Fix available
A fix is available. Upgrade to 8.10.14 / 8.11.11 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, 8.11, and 9.0 - Monitor Component stores source code on the web server that could aid in further attacks against the system.

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 of IBM Maximo Application Suite versions 8.10, 8.11, and 9.0 improperly stores source code on the web server, exposing application logic and implementation details that could aid attackers in understanding the system and identifying additional vulnerabilities.

MitigationDisable directory listings and restrict web access to the Monitor Component directory, remove exposed source code files from web-accessible locations, or apply vendor patches when available.

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.10.14>= 8.11, < 8.11.11= 9.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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 installed Maximo Application Suite version
    Check the installed version of IBM Maximo Application Suite in the system inventory, admin console, or deployment metadata. Common locations include the installation directory, the Maximo admin interface, or the IBM Installation Manager.
    Affected if Version is 8.10.x where x < 14, OR 8.11.x where x < 11, OR exactly 9.0
  2. Verify Monitor Component deployment
    Confirm that the Monitor Component is deployed as part of the Maximo Application Suite installation. Check the component list in the Maximo admin console or deployment configuration.
    Affected if Monitor Component is present and deployed in the environment
  3. Check web accessibility of Monitor Component directory
    Attempt to access the Monitor Component endpoint via HTTP/HTTPS using a web browser or curl command. Look for URLs typically under /maximo/monitor or similar paths defined in the deployment.
    Affected if Monitor Component is accessible over the network via web protocols (HTTP/HTTPS)
  4. Test for source code exposure in Monitor Component
    Attempt to access common source code file extensions in the Monitor Component web directory, such as .java, .jsp, .js, .class, .jar, or source map files (.map). Try accessing known source file paths or directory listings.
    Affected if Source code files (.java, .jsp, .js source files, .class files, or similar) are returned by the web server when requested, or directory listings show source files

The environment is affected if the installed Maximo Application Suite version falls within 8.10.x < 8.10.14, 8.11.x < 8.11.11, or 9.0, AND the Monitor Component is deployed and web-accessible with exposed source code files.

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.14 / 8.11.11 or later
Fixed in 8.10.148.11.11
Interim mitigation

Disable directory listings and restrict web access to the Monitor Component directory, remove exposed source code files from web-accessible locations, or apply vendor patches when available.

Recommended fix Moderate confidence

Upgrade to Maximo Application Suite 8.10.14, 8.11.11, or latest available release beyond 9.0

  1. 1. Review IBM Maximo Application Suite upgrade documentation before proceeding
  2. 2. Ensure you have a complete backup of your current Maximo configuration and database
  3. 3. Test the upgrade in a non-production environment first
  4. 4. Schedule a maintenance window for the production upgrade
  5. 5. Follow IBM's standard upgrade procedure to update to the fixed version (8.10.14, 8.11.11, or subsequent release for 9.0)
  6. 6. After upgrade, verify the Monitor Component is functioning correctly and source code is no longer exposed
Caveat Review IBM's release notes for each target version for potential breaking changes; test thoroughly in non-production environment

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

Fix this in Maximo Application Suite Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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