dbcve.org
Robotic Process AutomationApplication · Ibm

CVE-2023-23468

MEDIUM · 5.5 CVSS v3.1 Published 2023-06-27
Fix available
A fix is available. Upgrade to after 23.0.3 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click Patch available

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 Robotic Process Automation for Cloud Pak 21.0.1 through 21.0.7.3 and 23.0.0 through 23.0.3 is vulnerable to insufficient security configuration which may allow creation of namespaces within a cluster. IBM X-Force ID: 244500.

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

A detailed technical summary for this CVE is being prepared.

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
Robotic Process AutomationApplication
Affected:>= 21.0.1, <= 21.0.7.3>= 23.0.0, <= 23.0.3

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

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

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.

dbcve · scoped
Upgrade available Upgrade to a release after 23.0.3
Vendor patch www.ibm.com →
Recommended fix Moderate confidence

IBM RPA 21.0.7.4+ or 23.0.4+ (check vendor page for exact fixed releases)

  1. 1. Identify the currently installed IBM Robotic Process Automation for Cloud Pak version using the IBM RPA management console or command line tools
  2. 2. Navigate to the IBM Support page at https://www.ibm.com/support/pages/node/7005999 to obtain the specific patch or fixed version information
  3. 3. If upgrading: Schedule a maintenance window and backup all RPA configurations and data
  4. 4. For version 21.x: Upgrade to IBM RPA 21.0.7.4 or later (the next version after the affected range ending at 21.0.7.3)
  5. 5. For version 23.x: Upgrade to IBM RPA 23.0.4 or later (the next version after the affected range ending at 23.0.3)
  6. 6. Apply the upgrade following IBM's standard upgrade procedures for Cloud Pak deployments
  7. 7. Verify the installation of the fixed version and confirm namespace creation restrictions are properly enforced
Caveat Standard IBM RPA upgrade considerations apply - review migration guides for breaking changes between minor versions

Generated from the published advisory — verify against the referenced sources before acting.

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-23468 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2023-23468 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