CVE-2014-4843
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 · uneditedCuram Universal Access in IBM Curam Social Program Management (SPM) 6.0 SP2 before EP26, 6.0.4 before 6.0.4.6, and 6.0.5 before 6.0.5.5 iFix5 allows remote attackers to obtain sensitive information about internal caseworker usernames via vectors related to a URL.
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 confidenceThis is an information disclosure vulnerability in IBM Curam Social Program Management where remote unauthenticated attackers can obtain sensitive caseworker usernames through specific URL vectors. The vulnerability affects multiple 6.0.x versions of Curam Universal Access.
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= 6.0.4.0= 6.0.4.1= 6.0.4.2= 6.0.4.3= 6.0.4.4= 6.0.4.5= 6.0.5.0= 6.0.5.1= 6.0.5.2= 6.0.5.3= 6.0.5.4CVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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 IBM Curam SPM installation and versionLocate the Curam installation directory and check version files such as version.properties, about.jsp, or the IBM Curam administration console. Alternatively, query the database for version metadata if accessible.Affected if The installed version matches any of the following: 6.0, 6.0.4.0, 6.0.4.1, 6.0.4.2, 6.0.4.3, 6.0.4.4, 6.0.4.5, 6.0.5.0, 6.0.5.1, 6.0.5.2, 6.0.5.3, or 6.0.5.4
-
Confirm Universal Access module is enabledCheck the Curam application configuration or web.xml deployment descriptor for the Universal Access servlet or filter. Verify that the /curam/ua/ path is accessible in the deployed web application.Affected if Universal Access (UA) is deployed and accessible via web interface on the target server
-
Test for username disclosure via URL vectorUsing a web browser or HTTP client, submit a request to the Universal Access endpoint with crafted parameters known to leak caseworker usernames. Observe if usernames appear in the response or URL parameters.Affected if Sensitive caseworker usernames are returned in the HTTP response or visible in URL parameters after the request
You are affected if IBM Curam SPM version 6.0.x (specifically the listed 6.0, 6.0.4.x, or 6.0.5.x versions) is installed with Universal Access enabled, and the specific URL vector returns caseworker usernames 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 the appropriate IBM fixes: EP26 for version 6.0 SP2, 6.0.4.6 for version 6.0.4, or 6.0.5.5 iFix5 for version 6.0.5. Validate that username information is no longer exposed via URL parameters after patching.
- 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-2014-4843 — 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-4843 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