CVE-2015-5023
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 Curam Social Program Management 6.1 before 6.1.1 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 Curam Social Program Management version 6.1 allows remote authenticated users to execute arbitrary SQL commands through unspecified vectors. The vulnerability exists before version 6.1.1 and requires authentication but can lead to complete compromise of the database.
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.1= 6.0.2= 6.0.3= 6.0.4= 6.0.5= 6.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
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 the installed IBM Curam SPM versionLocate the product version through the admin console, version.info file, or by querying the application metadata. Common paths include the product installation directory or the administration interface under 'About' or 'System Information'.Affected if The installed version is 6.0, 6.0.1, 6.0.2, 6.0.3, 6.0.4, 6.0.5, or 6.1 (any version before 6.1.1).
-
Confirm remote authentication is enabledVerify whether the Curam application is configured to accept remote user connections. Check the application server configuration (typically WebSphere or similar) for exposed authentication endpoints or web services accessible over the network.Affected if Remote authentication is enabled and the application is accessible over the network to authenticated users.
-
Review audit and access logs for suspicious SQL patternsExamine the application logs, database audit trails, and web access logs for unusual or malformed SQL syntax in user-provided input fields. Look for patterns such as single quotes, UNION statements, or SQL comments in parameter values.Affected if Logs show SQL injection attempts or anomalous SQL queries originating from user input.
A system is affected if it runs IBM Curam Social Program Management version 6.0 through 6.1, has remote authentication enabled, and the vulnerability is reachable by authenticated remote users.
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 Curam Social Program Management version 6.1.1 or later to patch the SQL injection vulnerability. Alternatively, implement strict input validation and least-privilege database accounts as compensating controls until the patch can be applied.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.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 $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-5023 — 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-2015-5023 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