dbcve.org
Change And Configuration Management DatabaseDatabase / datastore · Ibm

CVE-2015-7448

MEDIUM · 5.4 CVSS v3.0 Published 2016-03-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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
SQL injection vulnerability in IBM Maximo Asset Management 7.1 through 7.1.1.13, 7.5.0 before 7.5.0.9 IFIX003, and 7.6.0 before 7.6.0.3 IFIX001; Maximo Asset Management 7.5.0 before 7.5.0.9 IFIX003, 7.5.1, and 7.6.0 before 7.6.0.3 IFIX001 for SmartCloud Control Desk; and Maximo Asset Management 7.1 through 7.1.1.13 and 7.2 for Tivoli IT Asset Management for IT and certain other products allows remote authenticated users to execute arbitrary SQL commands via unspecified vectors.

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 · moderate confidence

SQL injection vulnerability in IBM Maximo Asset Management allows remote authenticated users to execute arbitrary SQL commands via unspecified vectors. The vulnerability affects versions 7.1 through 7.1.1.13, 7.5.0 before 7.5.0.9 IFIX003, and 7.6.0 before 7.6.0.3 IFIX001 across multiple Maximo product lines including SmartCloud Control Desk and Tivoli IT Asset Management.

MitigationApply the vendor-supplied IFIX patches (7.5.0.9 IFIX003 for version 7.5.0, 7.6.0.3 IFIX001 for version 7.6.0) or upgrade to supported patched versions. Additionally, implement input validation and parameterized queries as defense-in-depth while patching.

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
Change And Configuration Management DatabaseDatabase / datastore
Affected:= 7.1= 7.1.1= 7.1.1.2= 7.1.1.3= 7.1.1.4= 7.1.1.5= 7.1.1.6= 7.2= 7.2.0.1= 7.2.0.2= 7.2.1= 7.2.1.1
Maximo Asset ManagementApplication
Affected:= 7.1= 7.1.1= 7.1.1.1= 7.1.1.2= 7.1.1.5= 7.1.1.6= 7.1.1.7= 7.1.1.8= 7.1.1.9= 7.1.1.10= 7.1.1.11= 7.1.1.12
Maximo Asset Management EssentialsApplication
Affected:= 7.1= 7.5= 7.5.0.0= 7.5.0.1= 7.5.0.2= 7.5.0.3= 7.5.0.4= 7.5.0.5= 7.5.0.6= 7.5.0.7= 7.5.0.8= 7.5.0.9
Maximo For Energy OptimizationApplication
Affected:= 7.1
Maximo For GovernmentApplication
Affected:= 7.1= 7.1.1= 7.5
Maximo For Life SciencesApplication
Affected:= 7.1= 7.5= 7.6
Maximo For Nuclear PowerApplication
Affected:= 7.1= 7.1.1= 7.5= 7.5.0.1= 7.5.1
Maximo For Oil And GasApplication
Affected:= 7.1= 7.1.0.1= 7.1.1.0= 7.1.2= 7.5= 7.5.1

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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 Maximo product version
    Check the Maximo installation directory for version information. Common locations include the maximo.properties file, the about dialog in the Maximo application, or query the MAXVERSION system property in the Maximo database.
    Affected if The installed version falls within 7.1 to 7.1.1.13, 7.5.0 through 7.5.0.8, or 7.6.0 through 7.6.0.2 and the corresponding IFIX patches are not applied.
  2. Determine if IFIX003 for version 7.5.0 is applied
    Check the maximo/ifxtemp directory or examine the Maximo system information for installed IFIX packages. Look for IFIX003 specifically for the 7.5.0.x line.
    Affected if Running version 7.5.0.x and IFIX003 is NOT installed.
  3. Determine if IFIX001 for version 7.6.0 is applied
    Check the maximo/ifxtemp directory or examine the Maximo system information for installed IFIX packages. Look for IFIX001 specifically for the 7.6.0.x line.
    Affected if Running version 7.6.0.x and IFIX001 is NOT installed.
  4. Confirm network accessibility of the Maximo application
    Verify that the Maximo web interface or API endpoints are accessible from the network. The vulnerability requires remote authenticated access.
    Affected if The Maximo application is exposed to the network without proper network segmentation or authentication controls.

You are affected if you are running any IBM Maximo product version 7.1 through 7.1.1.13, 7.5.0.x before 7.5.0.9 IFIX003, or 7.6.0.x before 7.6.0.3 IFIX001 and the application is network-accessible to authenticated users.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied IFIX patches (7.5.0.9 IFIX003 for version 7.5.0, 7.6.0.3 IFIX001 for version 7.6.0) or upgrade to supported patched versions. Additionally, implement input validation and parameterized queries as defense-in-depth while patching.

Fix this in Change And Configuration Management Database Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing12.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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