Curam Social Program ManagementApplication · Ibm

CVE-2020-4776

HIGH · 7.5 CVSS v3.1 Published 2020-10-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
A path traversal vulnerability may impact IBM Curam Social Program Management 7.0.9 and 7.0.10, which could allow a remote attacker to traverse directories on the system. An attacker could send a specially-crafted file path in URL request to view arbitrary files on the system. IBM X-Force ID: 189154.

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 confidence

A path traversal vulnerability in IBM Curam Social Program Management versions 7.0.9 and 7.0.10 allows remote attackers to access arbitrary files on the system by sending specially-crafted file path sequences (e.g., ../) in URL requests, exploiting insufficient input validation on file path parameters.

MitigationApply vendor-provided patches for IBM Curam Social Program Management. If no patch is immediately available, implement WAF rules or URL filtering to block directory traversal patterns and validate all file path inputs server-side.

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
Curam Social Program ManagementApplication
Affected:= 7.0.9.0= 7.0.10.0

CVSS 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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed IBM Curam version
    Locate the version information in the IBM Curam installation directory, typically found in version manifest files, About dialog, or administrative console. Common locations include installation logs, config files, or the SPM version file.
    Affected if The installed version matches exactly 7.0.9.0 or 7.0.10.0
  2. Confirm web interface is accessible
    Verify that the IBM Curam web application is exposed and reachable via HTTP/HTTPS. This typically runs on application servers like WebSphere. Check if the Curam servlets and endpoints are publicly or internally accessible.
    Affected if The web interface is accessible and the version is 7.0.9.0 or 7.0.10.0
  3. Inspect URL parameter handling for path traversal patterns
    Review web server or application server access logs for requests containing directory traversal sequences such as ../, ../.., or absolute path patterns in URL parameters. Check the configuration of the web application to see how file path parameters are validated.
    Affected if Requests with traversal patterns are being processed by the application without rejection, and the version is 7.0.9.0 or 7.0.10.0
  4. Check for input validation on file path parameters
    Examine the web application configuration and servlet filters to determine whether input validation is implemented for file path parameters in URL requests. Look for path normalization or whitelist-based validation logic.
    Affected if No input validation exists for file path parameters and the version is 7.0.9.0 or 7.0.10.0

You are affected if IBM Curam Social Program Management version 7.0.9.0 or 7.0.10.0 is installed and the web interface processes file path parameters without proper validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-provided patches for IBM Curam Social Program Management. If no patch is immediately available, implement WAF rules or URL filtering to block directory traversal patterns and validate all file path inputs server-side.

Fix this in Curam Social Program Management Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-4776 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-4776 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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