CVE-2012-0728
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 · uneditedSQL injection vulnerability in IBM Maximo Asset Management 7.1 through 7.5, as used in SmartCloud Control Desk, Tivoli Asset Management for IT, Tivoli Service Request Manager, Maximo Service Desk, and Change and Configuration Management Database (CCMDB), 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 confidenceSQL injection vulnerability in IBM Maximo Asset Management 7.1-7.5 allows remote authenticated users to execute arbitrary SQL commands through unspecified vectors. The flaw exists in the underlying Maximo framework used by multiple IBM products including SmartCloud Control Desk, Tivoli Asset Management for IT, Tivoli Service Request Manager, Maximo Service Desk, and CCMDB.
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= 6.0= 7.0= 7.1.0.0= 7.5.0.0= 6.2= 7.0= 6.0= 6.2= 7.0= 7.1= 7.2= 7.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed IBM product and versionCheck your installation for one of the affected products: Maximo Asset Management 7.1-7.5, SmartCloud Control Desk 7.0, Tivoli Asset Management for IT 6.0-7.2, Tivoli Service Request Manager 7.0, Change and Configuration Management Database 6.0-7.0, or Maximo Service Desk 6.2. Use the product-specific version check command or look in the installation directory for version files.Affected if The installed product matches one of the affected versions listed in the CVE.
-
Verify the Maximo web application is exposedDetermine if the Maximo web interface (typically on port 80/443 or custom ports like 9080) is accessible from the network. Check your web server configuration or firewall rules for exposed Maximo endpoints.Affected if The Maximo web interface is network-accessible, as this is required for remote authenticated exploitation.
-
Check external or database authentication configurationReview the Maximo system configuration to determine if external user authentication (LDAP, Active Directory) or direct database authentication is enabled. This is typically found in the MAXIMO system properties or the web.xml deployment descriptor.Affected if External or database authentication is enabled, allowing remote users to authenticate and potentially exploit the SQL injection vector.
-
Review custom integration or reporting modulesExamine any custom integrations, report configurations, or third-party modules that interface with the Maximo database. These may use direct SQL queries that could be exploitable.Affected if Custom code or integrations that pass user input to SQL queries are present in the Maximo environment.
Your environment is affected if you are running any of the listed product versions with the Maximo web interface accessible to remote authenticated users.
Generated from the published advisory. Verify against your own configuration.
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 dataApply IBM patches for this vulnerability or upgrade to a patched version of Maximo Asset Management. If patches are unavailable, implement strict input validation and parameterized queries in custom code, and restrict network access to the affected interfaces to reduce the attack surface for authenticated users.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-0728 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2012-0728 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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