dbcve.org
Robotic Process AutomationApplication · Ibm

CVE-2022-41294

MEDIUM · 6.5 CVSS v3.1 Published 2022-10-06
Fix available
A fix is available. Upgrade to after 21.0.4 or later.
See remediation →
74/100
Remediation priority · Elevated
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
IBM Robotic Process Automation 21.0.0, 21.0.1, 21.0.2, 21.0.3, and 21.0.4 is vulnerable to cross origin resource sharing using the bot api. IBM X-Force ID: 236807.

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

IBM Robotic Process Automation versions 21.0.0 through 21.0.4 contain a CORS (Cross-Origin Resource Sharing) misconfiguration that allows the bot API to be accessed from unauthorized origins. This could enable a malicious website to make cross-origin requests on behalf of authenticated users, potentially leading to unauthorized actions through the RPA bot API.

MitigationConfigure strict CORS policies to whitelist only trusted origins for the bot API endpoint, and update to a patched version if available from IBM.

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
Robotic Process AutomationApplication
Affected:>= 21.0.0, <= 21.0.4

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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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. Check installed IBM RPA version
    Access the IBM RPA admin console or check the product information page (typically via /web/console or theAbout section in the IBM RPA Dashboard). Confirm the exact version number displayed.
    Affected if The installed version is 21.0.0, 21.0.1, 21.0.2, 21.0.3, or 21.0.4 (any version from 21.0.0 through 21.0.4 inclusive).
  2. Locate CORS configuration for bot API
    In the IBM RPA admin console, navigate to the Security or API Settings section. Look for CORS (Cross-Origin Resource Sharing) configuration settings associated with the bot API endpoint (typically named Bot API, RPA API, or similar).
    Affected if CORS settings exist and are configurable for the bot API endpoint.
  3. Examine allowed origins in CORS policy
    Review the CORS allowed origins list. Check if the configuration shows a wildcard (*), multiple unspecified origins, or origins that are not explicitly trusted internal domains.
    Affected if The CORS policy allows all origins (*) or includes origins that are not explicitly whitelisted trusted domains (e.g., any external or unverified domain).

You are affected if your IBM RPA version is 21.0.0 through 21.0.4 AND the CORS configuration for the bot API permits unauthorized or wildcard origins.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 21.0.4
Interim mitigation

Configure strict CORS policies to whitelist only trusted origins for the bot API endpoint, and update to a patched version if available from IBM.

Recommended fix Moderate confidence

IBM Robotic Process Automation 21.0.5 or later

  1. 1. Identify the current IBM Robotic Process Automation version by accessing the IBM RPA dashboard or checking the installation details
  2. 2. Download IBM Robotic Process Automation version 21.0.5 or later from IBM Fix Central or the official IBM support portal
  3. 3. Before upgrading, backup the current IBM RPA configuration, workflows, and any custom bot configurations
  4. 4. Stop all running IBM RPA services and bot executions
  5. 5. Install the upgraded version (21.0.5 or later) following IBM's standard upgrade procedures
  6. 6. Verify the installation was successful and the CORS vulnerability is resolved
  7. 7. Restart IBM RPA services and validate that bot API functionality works correctly
Caveat Review IBM release notes for version 21.0.5 for any configuration or behavioral changes that may affect existing bots

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

Fix this in Robotic Process Automation Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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