Robotic Process AutomationApplication · Ibm

CVE-2024-51456

MEDIUM · 5.9 CVSS v3.1 Published 2025-01-12
Fix available
A fix is available. Upgrade to after 23.0.19 or later.
See remediation →
68/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 through 21.0.7.19 and 23.0.0 through 23.0.19 could allow a remote attacker to obtain sensitive data that may be exposed through certain crypto-analytic attacks.

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-21.0.7.19 and 23.0.0-23.0.19 contains a cryptographic vulnerability where certain crypto-analytic attacks could allow a remote attacker to obtain sensitive data. The specific cryptographic weakness and attack vector are not detailed in the available description.

MitigationContact IBM for the specific patch and remediation guidance; upgrade to a fixed version when available. Assess any exposed sensitive data for potential compromise.

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.7.19>= 23.0.0, <= 23.0.19

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

CVSS:3.1/AV:N/AC:H/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed IBM RPA version
    Locate the version through the IBM RPA management console, installation directory, or system registry. Typically found in the product UI under 'About' or in the installation path (e.g., /opt/ibm/rpa or C:\Program Files\IBM\RPA).
    Affected if Version matches 21.0.0 through 21.0.7.19, or 23.0.0 through 23.0.19
  2. Verify version is within affected range
    Compare your installed version number against the known affected ranges: 21.0.0-21.0.7.19 and 23.0.0-23.0.19.
    Affected if Installed version falls within either of these two ranges
  3. Confirm IBM RPA services are active
    Check if the IBM RPA server or related services are running. Use system process lists (task manager or systemctl) to verify the RPA platform is actively hosting or processing requests.
    Affected if The product is running and accessible to potential remote attackers

You are affected if IBM Robotic Process Automation is installed and running a version between 21.0.0-21.0.7.19 or 23.0.0-23.0.19.

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 23.0.19
Interim mitigation

Contact IBM for the specific patch and remediation guidance; upgrade to a fixed version when available. Assess any exposed sensitive data for potential compromise.

Recommended fix Moderate confidence

IBM RPA 21.0.8 or later / 23.0.20 or later (upgrade to the latest available stable release beyond the affected versions)

  1. Verify current IBM Robotic Process Automation version by accessing the IBM RPA dashboard or checking the installation
  2. Review IBM's official security bulletin for CVE-2024-51456 at www.ibm.com to obtain the specific fix/PF number
  3. Download and apply the interim fix (iFix) or upgrade to a fixed release version
  4. After applying the fix, restart the IBM RPA services to ensure the crypto library updates take effect
  5. Validate the fix by reviewing system logs to confirm no crypto-related errors are present
  6. Test critical RPA workflows that involve encryption/decryption operations to ensure proper functionality
Caveat Review IBM release notes for the target version as minor behavioral changes may exist; test in non-production environment before upgrading production systems

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

Fix this in Robotic Process Automation Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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 locally
dbcve dependency scanner

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