CVE-2011-1390
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 the Maintenance tool in IBM Rational ClearQuest 7.1.1.x before 7.1.1.9, 7.1.2.x before 7.1.2.6, and 8.x before 8.0.0.2 allows remote attackers to execute arbitrary SQL commands by leveraging an error in the user-database upgrade feature.
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 confidenceSQL injection vulnerability in IBM Rational ClearQuest's Maintenance tool user-database upgrade feature allows unauthenticated remote attackers to execute arbitrary SQL commands by injecting malicious SQL payloads.
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= 7.1.1.1= 7.1.1.2= 7.1.1.3= 7.1.1.4= 7.1.1.5= 7.1.1.6= 7.1.1.7= 7.1.1.8= 7.1.2= 7.1.2.1= 7.1.2.2= 7.1.2.3CVSS 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
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/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 installed ClearQuest versionLocate the ClearQuest installation and check its version. On Windows, this is often available in Add/Remove Programs or the installation directory's version info. In Unix/Linux, check the installation path's version file or run 'cq lsversion' if available.Affected if The installed version matches any of: 7.1.1.1, 7.1.1.2, 7.1.1.3, 7.1.1.4, 7.1.1.5, 7.1.1.6, 7.1.1.7, 7.1.1.8, 7.1.2, 7.1.2.1, 7.1.2.2, or 7.1.2.3
-
Determine if Maintenance tool web interface is exposedIdentify the host running ClearQuest and check if the Maintenance tool HTTP port is reachable from the network. The Maintenance tool typically runs as a web service; scan common ClearQuest maintenance ports or check server configuration for exposed web interfaces.Affected if The Maintenance tool web interface is accessible from network locations, especially untrusted networks.
-
Verify the upgrade feature is accessibleAttempt to access the Maintenance tool's user-database upgrade endpoint, typically found at a URL path related to 'upgrade' or 'maintenance'. This is often a web form or API endpoint used for database schema updates.Affected if The user-database upgrade feature of the Maintenance tool is exposed and accessible without authentication.
-
Check network access controlsReview firewall rules, network segmentation, or access control lists that govern who can reach the Maintenance tool interface. Determine if the service is bound to localhost only, internal networks, or is openly accessible.Affected if The Maintenance tool interface can be reached by unauthenticated or untrusted network actors.
You are affected if you are running any of the listed versions AND the Maintenance tool user-database upgrade feature is network-accessible without authentication.
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 vendor patches (7.1.1.9, 7.1.2.6, or 8.0.0.2) to the affected ClearQuest installations. Additionally, restrict network access to the Maintenance tool interface to prevent external exploitation.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-1390 — 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-2011-1390 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