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

CVE-2013-4016

MEDIUM · 6.5 CVSS v2.0 Published 2014-05-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/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.x before 7.1.1.7 LAFIX.20140319-0837, 7.1.1.11 before IFIX.20140323-0749, 7.1.1.12 before IFIX.20140321-1336, 7.5.x before 7.5.0.3 IFIX027, 7.5.0.4 before IFIX011, and 7.5.0.5 before IFIX006; SmartCloud Control Desk 7.x before 7.5.0.3 and 7.5.1.x before 7.5.1.2; and Tivoli IT Asset Management for IT, Tivoli Service Request Manager, Maximo Service Desk, and Change and Configuration Management Database (CCMDB) 7.x before 7.1.1.7 LAFIX.20140319-0837, 7.1.1.11 before IFIX.20140207-1801, and 7.1.1.12 before IFIX.20140218-1510 allows remote authenticated users to execute arbitrary SQL commands via a Birt report with a WHERE clause in plain text.

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

SQL injection vulnerability in IBM Maximo Asset Management and related products allows remote authenticated users to execute arbitrary SQL commands through Birt reports that include a WHERE clause in plain text without proper parameterization.

MitigationApply the specific IBM IFIX updates for each affected version (LAFIX.20140319-0837, IFIX.20140323-0749, IFIX.20140321-1336, IFIX027, IFIX011, IFIX006) and ensure reports use parameterized queries instead of plain text WHERE clauses.

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.1.7= 7.1.1.11= 7.1.1.12
Maximo Service DeskApplication
Affected:= 7.1.1.7= 7.1.1.11= 7.1.1.12
Tivoli Asset Management For ItApplication
Affected:= 7.0= 7.1
Tivoli It Asset Management For ItApplication
Affected:= 7.1.1.7= 7.1.1.11= 7.1.1.12
Tivoli Service Request ManagerApplication
Affected:= 7.1.1= 7.1.1.7= 7.1.1.11= 7.1.1.12
Smartcloud Control DeskApplication
Affected:= 7.0= 7.5= 7.5.0.0= 7.5.0.1= 7.5.0.2= 7.5.1.0= 7.5.1.1
Maximo Asset ManagementApplication
Affected:= 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.1= 7.1.1= 7.1.1.1= 7.1.1.2= 7.1.1.5= 7.1.1.6

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
Authentication
Single
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:S/C:P/I:P/A:P

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 product and version
    Check the Maximo/CCMDB/SmartCloud Control Desk installation directory for version files, or use the system information screen (System Configuration > Platform Installation > System Info in Maximo)
    Affected if The installed version matches any of the affected versions listed in the CVE (7.1.1.7, 7.1.1.11, 7.1.1.12, 7.1.1, 7.5.0.0-7.5.0.5, 7.0, 7.1)
  2. Verify Birt reporting module is enabled
    Confirm the Birt report module is installed and active in the Maximo/SmartCloud environment by checking the system modules or report configuration settings
    Affected if Birt reports are enabled and accessible in the environment
  3. Check report execution permissions
    Review user accounts and roles in the system to determine which users have access to create or run Birt reports (typically found in Security Groups or Users application)
    Affected if There are authenticated users with permission to create or modify Birt reports
  4. Inspect custom Birt reports for plain text WHERE clauses
    Open existing Birt report definition files (.rptdesign) or report configurations and examine the query structure to see if WHERE clauses are constructed as plain text rather than using parameterized query bindings
    Affected if Any Birt reports use plain text WHERE clauses without parameter binding in their SQL queries
  5. Review report query parameterization settings
    Check the Birt report data source configuration in the Maximo administration area to verify whether reports are configured to use parameterized queries or direct SQL input
    Affected if Reports allow direct SQL input in WHERE clause parameters without parameterization

The environment is affected if it runs one of the listed vulnerable versions, has Birt reporting enabled, and contains reports using plain text WHERE clauses without parameter binding.

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 specific IBM IFIX updates for each affected version (LAFIX.20140319-0837, IFIX.20140323-0749, IFIX.20140321-1336, IFIX027, IFIX011, IFIX006) and ensure reports use parameterized queries instead of plain text WHERE clauses.

Fix this in Change And Configuration Management Database Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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