CVE-2012-0747
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 6.2 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 versions 6.2 through 7.5 allows remote authenticated users to execute arbitrary SQL commands via unspecified vectors. The flaw affects multiple IBM enterprise management products built on the Maximo platform.
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= 6.2.0.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 productDetermine if your environment includes any of the following Maximo-based products: IBM Maximo Asset Management, IBM Maximo Service Desk, IBM Smartcloud Control Desk, IBM Change and Configuration Management Database, IBM Tivoli Asset Management for IT, or IBM Tivoli Service Request Manager. Check your installed applications or licensing documentation to confirm the product name.Affected if The product is one of the listed Maximo-based products.
-
Check the installed product versionLocate the version information for your installed Maximo-based product. This is typically accessible through the product's About screen, installation directory, or administrative console. Common locations include the version info in the Maximo application header or system information module.Affected if The version matches 6.0, 6.2, 7.0, 7.1.0.0, 7.1, 7.2, 7.5.0.0, or falls within the 6.2 through 7.5 range.
-
Verify remote access is enabledDetermine if the Maximo application is configured to accept remote network connections. Check if the web interface or API endpoints are exposed to network access beyond the local intranet. Review your firewall rules, load balancer configurations, or reverse proxy settings that expose the Maximo application.Affected if The application is accessible from network locations beyond trusted internal networks.
-
Confirm user authentication is in useVerify that the Maximo application has user authentication enabled and accepts logins from remote users. SQL injection in this CVE requires an authenticated session, so confirm that the application is configured to allow user logins rather than being fully public or fully isolated.Affected if Remote user authentication is enabled and users can log in to the application from network-accessible interfaces.
Your environment is affected if you are running any of the listed Maximo-based products at versions 6.0 through 7.5 and the application is accessible to authenticated remote users over the network.
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 security patches for CVE-2012-0747; upgrade to a patched version of Maximo Asset Management. If immediate patching is not possible, restrict network access to the application and review application logs for suspicious SQL-like activity.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-0747 — 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-0747 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