Curam Social Program ManagementApplication · Ibm

CVE-2018-1362

MEDIUM · 5.0 CVSS v3.0 Published 2018-01-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
56/100
Remediation priority · Elevated
Remotely reachable 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
IBM Curam Social Program Management 6.0.5, 6.1.1, 6.2.0, and 7.0.1 within Citizen Portal could allow an authenticated user to withdraw other user's submitted applications from the system and possibly obtain privileges. IBM X-Force ID: 137380.

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

This is an insecure direct object reference (IDOR) or broken access control vulnerability in IBM Curam Social Program Management's Citizen Portal. An authenticated user can withdraw other users' submitted applications by manipulating application identifiers, indicating the system fails to verify ownership or authorization before allowing the withdrawal action. This allows unauthorized modification of other users' data and potential privilege escalation.

MitigationImplement proper authorization checks ensuring users can only withdraw applications they own or are explicitly authorized to manage. Add ownership validation before executing any withdrawal operation.

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:= 6.0.5= 6.1.1.0= 6.2.0.0= 7.0.1

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L

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. Determine installed IBM Curam version
    Check the IBM Curam Social Program Management version through the product's about page, installation directory metadata, or administrative console. Common locations include the server properties files or the Curam administrator interface.
    Affected if The installed version matches 6.0.5, 6.1.1.0, 6.2.0.0, or 7.0.1 exactly.
  2. Verify Citizen Portal is enabled
    Confirm that the Citizen Portal web application module is deployed and accessible in the IBM Curam environment. Check the web application server configuration for the Curam Citizen Portal application.
    Affected if Citizen Portal is deployed and active in the environment.
  3. Review application audit logs for withdrawal actions
    Examine IBM Curam audit and application logs for withdrawal operations on applications. Look for the withdrawal action/API calls and correlate with the user performing them.
    Affected if Logs show withdrawal actions performed by users on applications they do not own.
  4. Inspect application authorization configuration
    Review the Curam application configuration and security settings related to the withdrawal functionality. Check if ownership validation is properly configured in the application access control settings.
    Affected if No explicit ownership verification is configured for the withdrawal operation, or the authorization rules allow users to withdraw any application by ID.

You are affected if you run IBM Curam Social Program Management versions 6.0.5, 6.1.1.0, 6.2.0.0, or 7.0.1 with the Citizen Portal enabled, and your application lacks proper ownership validation for withdrawal operations.

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

Implement proper authorization checks ensuring users can only withdraw applications they own or are explicitly authorized to manage. Add ownership validation before executing any withdrawal operation.

Fix this in Curam Social Program Management Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-1362 — 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-2018-1362 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