Security Resilience

CVE-2024-51456

Crypto Weakness in Ibm Robotic Process Automation 21.0.0 – 21.0.7.19

Published
12 January 2025
Modified
28 March 2025
Patch / advisory
CVSS Score v3.1 5.9
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0028 19th percentile
Risk Priority 45 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2024-51456 is a medium-severity Use of RSA Algorithm without OAEP (CWE-780) vulnerability in Ibm Robotic Process Automation. Its CVSS base score is 5.9 (Medium).

Operationally, ranked at the 19th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-13 (Cryptographic Protection) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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.

CWE(s)

Related Threats

CVEs Like This One

CVE-2023-38733Same product: Ibm Robotic Process Automation
CVE-2024-28780Same product: Microsoft Windows
CVE-2025-14806Same product: Microsoft Windows
CVE-2026-13473Same product: Microsoft Windows
CVE-2023-38734Same product: Ibm Robotic Process Automation
CVE-2023-28956Same product: Microsoft Windows
CVE-2024-28777Same product: Microsoft Windows
CVE-2023-47160Same product: Microsoft Windows
CVE-2024-25037Same product: Microsoft Windows
CVE-2024-28778Same product: Microsoft Windows

Affected Assets

ibm
robotic process automation
21.0.0 — 21.0.7.19 · 23.0.0 — 23.0.19

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 2 hardening rules · 1 OS baseline
Validate
Prove the fix (OWASP ASVS)

—

Mitigating Controls (NIST 800-53 r5) AI

SC-13 requires selection and implementation of specific cryptography types, directly stopping use of broken algorithms.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
blocks

Secure SDLC practices directly prevent weak cryptographic implementations like RSA without OAEP.

PR.DS-01 partial match
blocks

Proper encryption of data-at-rest requires correct RSA padding such as OAEP.

PR.DS-02 partial match
blocks

Proper encryption of data-in-transit requires correct RSA padding such as OAEP.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

blocks

Mandates proper use of cryptography, directly requiring OAEP with RSA.

finds

Security testing can detect use of RSA without OAEP during development.

prevents

Requires secure coding practices that would prevent missing OAEP padding.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (higher-evidence rows only; rows rated `none` are excluded).

Oracle Linux 8 (1 rule)
  • V-248524 OL 8 must implement NIST FIPS-validated cryptography for the following: To provision digital signatures, to generate cryptographic hashes, and to protect data requiring data-at-rest protections in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. blocks CWE-780

References