CVE-2024-49348
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 · uneditedIBM Cloud Pak for Business Automation 18.0.0, 18.0.1, 18.0.2, 19.0.1, 19.0.2, 19.0.3, 20.0.1, 20.0.2, 20.0.3, 21.0.1, 21.0.2, 21.0.3, 22.0.1, and 22.0.2 allows restricting access to organizational data to valid contexts. The fact that tasks of type comment can be reassigned via API implicitly grants access to user queries in an unexpected context.
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 confidenceIBM Cloud Pak for Business Automation has an access control vulnerability where comment-type tasks can be reassigned via API, which implicitly grants users access to queries in unexpected organizational contexts. This bypasses the intended restriction of access to organizational data to valid contexts.
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= 18.0.0= 18.0.1= 18.0.2= 19.0.1= 19.0.2= 19.0.3= 20.0.1= 20.0.2= 20.0.3= 21.0.1= 21.0.2= 21.0.3CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed IBM Cloud Pak for Business Automation versionRun the IBM Cloud Pak version command or check the operator deployment manifests for the version labelAffected if The installed version matches one of the affected versions: 18.0.0-18.0.2, 19.0.1-19.0.3, 20.0.1-20.0.3, or 21.0.1-21.0.3
-
Verify if the Task Reassignment API endpoint is exposedCheck the API gateway or service configuration for exposed REST endpoints related to task management and reassignmentAffected if The task reassignment API is accessible without additional access controls beyond basic authentication
-
Identify comment-type tasks in the environmentQuery the task database or use the workflow API to list tasks of type 'comment' that support reassignmentAffected if Comment-type tasks exist and are configured with reassignment permissions enabled
-
Audit task reassignment logs for comment-type tasksReview API access logs and task audit logs for reassignment operations on comment-type tasks, particularly those changing ownership to users in different organizational contextsAffected if Reassignment events show comment-type tasks being reassigned to users outside their original organizational scope
A user is affected if they are running any of the listed affected versions AND have comment-type tasks that can be reassigned via API, allowing unauthorized access to organizational data contexts.
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 vendor-provided patches for affected versions (18.0.0-22.0.2) when available. Until then, restrict API access to trusted personnel and monitor for unauthorized task reassignments.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.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 $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-49348 — 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-2024-49348 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