CVE-2011-1343
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 Web GUI in IBM Tivoli Netcool/OMNIbus before 7.3.0.4 allows remote attackers to execute arbitrary SQL commands via "dynamic SQL parameters."
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 the Web GUI of IBM Tivoli Netcool/OMNIbus versions prior to 7.3.0.4 allows remote unauthenticated attackers to inject arbitrary SQL commands through dynamic SQL parameters in the web interface.
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.2.1.10= 7.1.0.0= 7.1.0.11= 7.1.0.12= 7.1.0.13= 7.2.0.0= 7.2.0.7= 7.2.0.8= 7.2.0.9= 7.2.0.10= 7.2.1.0= 7.2.1.5CVSS 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 the installed IBM Tivoli Netcool/OMNIbus versionRun the command 'nco_patchversion' or check the installation directory for a version file. On Linux/Unix, the version may be listed in $NCHOME/etc/omni.dat or via 'omniversion' utility if available.Affected if The installed version matches any of these: 7.1.0.0, 7.1.0.11, 7.1.0.12, 7.1.0.13, 7.2.0.0, 7.2.0.7, 7.2.0.8, 7.2.0.9, 7.2.0.10, 7.2.1.0, 7.2.1.5, or any version 7.2.1.10 or earlier.
-
Confirm the Web GUI component is runningCheck if the Web GUI process (nco_gui or similar) is active. Look for Java processes related to the GUI, or check if port 8080 (default HTTP) or port 443 (default HTTPS) is listening using 'netstat -an | grep -E "(8080|443)"' or 'ss -tlnp | grep -E "(8080|443)"'Affected if The Web GUI service is exposed and listening on network ports accessible to remote attackers.
-
Verify the patch level if version appears in the 7.3.x rangeEven if running 7.3.x, verify the exact patch level. Check the patch status via 'nco_patchversion' output or look for files in $NCHOME/patch directory indicating whether patch 7.3.0.4 has been applied.Affected if Running version 7.3.0.0 through 7.3.0.3 without the 7.3.0.4 patch applied.
You are affected if the Web GUI is exposed and the installed version is 7.2.1.10 or earlier, or any of the specific affected versions listed, or 7.3.0.0-7.3.0.3 without the 7.3.0.4 patch.
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 dataUpgrade IBM Tivoli Netcool/OMNIbus to version 7.3.0.4 or later, or apply the vendor-supplied patch for this vulnerability to remediate the SQL injection vector.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-1343 — 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-1343 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