CVE-2025-36023
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 24.0.0 through 24.0.0 IF005 and 24.0.1 through 24.0.1 IF002 could allow an authenticated user to view sensitive user and system information due to an indirect object reference through a user-controlled key.
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 confidenceIBM Cloud Pak for Business Automation versions 24.0.0 through 24.0.0 IF005 and 24.0.1 through 24.0.1 IF002 contains an Insecure Direct Object Reference (IDOR) vulnerability where an authenticated user can view sensitive user and system information by manipulating a user-controlled key that references internal objects without proper authorization validation.
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= 24.0.0= 24.0.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
- 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 IBM Cloud Pak for Business Automation versionUse the IBM Cloud Pak UI or CLI command (such as oc get icp4a -n <namespace>) to retrieve the deployed version of IBM Cloud Pak for Business AutomationAffected if The installed version is 24.0.0 or 24.0.1
-
Check if IF005 is applied for version 24.0.0Review the installed fix packs or interim fixes for IBM Cloud Pak for Business Automation 24.0.0 to determine if IF005 is presentAffected if Running version 24.0.0 without interim fix IF005 applied
-
Check if IF002 is applied for version 24.0.1Review the installed fix packs or interim fixes for IBM Cloud Pak for Business Automation 24.0.1 to determine if IF002 is presentAffected if Running version 24.0.1 without interim fix IF002 applied
-
Verify IDOR vulnerability applicabilityConfirm the application includes the endpoint or functionality that accepts user-controlled object references without proper authorization validationAffected if The specific endpoint or feature that accepts the manipulated key is accessible and lacks authorization checks
The environment is affected if IBM Cloud Pak for Business Automation version 24.0.0 without IF005 or version 24.0.1 without IF002 is deployed, and the vulnerable endpoint accepting object references is in use.
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 interim fix IF005 for version 24.0.0 or IF002 for version 24.0.1 as specified in IBM's security bulletin to address the improper access control.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36023 — 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-2025-36023 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