CVE-2014-3055
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 Unified Task List (UTL) Portlet for IBM WebSphere Portal 7.x and 8.x through 8.0.0.1 CF12 allows remote attackers 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 · high confidenceSQL injection vulnerability in IBM WebSphere Portal's Unified Task List (UTL) Portlet allows remote attackers to execute arbitrary SQL commands via unspecified vectors. The vulnerability affects versions 7.x and 8.x through cumulative fix 12 (CF12). This is a classic SQL injection flaw in the portlet's data handling logic.
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.0.0.0= 7.0.0.1= 7.0.0.2= 8.0.0.0= 8.0.0.1= 6.0.1CVSS 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.
-
Check WebSphere Portal versionLocate the WebSphere Portal installation directory and check the version file, or access the IBM WebSphere Application Server admin console to view the installed Portal versionAffected if Version is 7.0.0.0, 7.0.0.1, 7.0.0.2, 8.0.0.0, or 8.0.0.1 and cumulative fix is CF12 or earlier
-
Determine cumulative fix levelCheck the installed cumulative fix (CF) level via IBM Update Installer or by examining the fix metadata in the Portal update directoryAffected if CF12 or earlier is installed (CF13 and later contain the fix)
-
Verify UTL Portlet is deployedAccess the WebSphere Application Server admin console, navigate to Applications > WebSphere Portal, or list installed portlets via the Portal admin interface to see if Unified Task List is present and enabledAffected if UTL Portlet is installed and running
-
Check UTL Portlet versionExamine the portlet version in the WebSphere Portal administration console under Portlet Management, or inspect the portlet WAR file version metadataAffected if UTL Portlet version is 6.0.1
System is affected if WebSphere Portal version 7.0.0.0-8.0.0.1 with CF12 or earlier is running with the Unified Task List Portlet deployed and enabled.
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's security fix (PI19422) for this vulnerability or upgrade WebSphere Portal to a version beyond 8.0.0.1 CF12. If immediate patching is not possible, consider disabling or restricting access to the UTL Portlet until the fix can be deployed.
- 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-2014-3055 — 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-2014-3055 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