Monday, January 13, 2025
HomeCVE/vulnerabilityIBM Robotic Process Automation Vulnerability Let Attackers Obtain Sensitive Data

IBM Robotic Process Automation Vulnerability Let Attackers Obtain Sensitive Data

Published on

A newly disclosed security vulnerability in IBM Robotic Process Automation (RPA) has raised concerns about potential data breaches.

The vulnerability, tracked as CVE-2024-51456, could allow remote attackers to exploit cryptographic weaknesses and access sensitive information.

IBM has released a security bulletin detailing the issue, alongside remediation measures to address the risk.

IBM Robotic Process Automation Vulnerability

The vulnerability arises due to the insecure implementation of the RSA algorithm without Optimal Asymmetric Encryption Padding (OAEP), classified under CWE-780 (Use of RSA Algorithm without OAEP).

By exploiting this weakness, a remote attacker may execute a crypto-analytic attack to intercept or retrieve sensitive data processed by the affected software.

Investigate Real-World Malicious Links, Malware & Phishing Attacks With ANY.RUN – Try for Free

The vulnerability, identified as CVE-2024-51456, has been assigned a CVSS Base Score of 5.9, indicating moderate severity.

Its vector is defined as CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N, reflecting a network-based attack with high attack complexity, requiring no privileges or user interaction.

The primary impact is on confidentiality, rated as high, while there is no effect on integrity or availability.

Affected Products and Versions

The vulnerability affects several versions of IBM Robotic Process Automation for both standalone deployments and deployments with IBM Cloud Pak. A detailed breakdown is provided in the table below:

Affected ProductVersion(s)
IBM Robotic Process Automation21.0.0 – 21.0.7.19, 23.0.0 – 23.0.19
IBM Robotic Process Automation for Cloud Pak21.0.0 – 21.0.7.19, 23.0.0 – 23.0.19

IBM has addressed the vulnerability by releasing updated versions of its affected products. Users are strongly recommended to upgrade to version 23.0.20 or later to eliminate the risk posed by CVE-2024-51456.

For those using IBM Robotic Process Automation (RPA) versions 23.0.0 to 23.0.19, the fix involves downloading the updated release and following IBM’s remediation instructions.

Similarly, users of IBM Robotic Process Automation for Cloud Pak within the same version range should update to version 23.0.20 or higher.

For older versions, specifically 21.0.0 to 21.0.7.19, IBM has provided detailed mitigation steps as a temporary measure until the software can be upgraded to a secure version.

Applying these remedies promptly is essential for protecting sensitive data and ensuring the security of the organization’s automation workflows.

Find this News Interesting! Follow us on Google NewsLinkedIn, and X to Get Instant Updates!

Divya
Divya
Divya is a Senior Journalist at GBhackers covering Cyber Attacks, Threats, Breaches, Vulnerabilities and other happenings in the cyber world.

Latest articles

PoC Exploit Released for Critical macOS Sandbox Vulnerability (CVE-2024-54498)

A proof-of-concept (PoC) exploit has been publicly disclosed for a critical vulnerability impacting macOS...

Credit Card Skimmer Hits WordPress Checkout Pages, Stealing Payment Data

Researchers analyzed a new stealthy credit card skimmer that targets WordPress checkout pages by...

Hackers Exploiting YouTube to Spread Malware That Steals Browser Data

Malware actors leverage popular platforms like YouTube and social media to distribute fake installers....

Furry Hacker Breaches Scholastic – Exposes Data of 8 Million People

The education and publishing giant Scholastic has fallen victim to a significant data breach...

API Security Webinar

72 Hours to Audit-Ready API Security

APIs present a unique challenge in this landscape, as risk assessment and mitigation are often hindered by incomplete API inventories and insufficient documentation.

Join Vivek Gopalan, VP of Products at Indusface, in this insightful webinar as he unveils a practical framework for discovering, assessing, and addressing open API vulnerabilities within just 72 hours.

Discussion points

API Discovery: Techniques to identify and map your public APIs comprehensively.
Vulnerability Scanning: Best practices for API vulnerability analysis and penetration testing.
Clean Reporting: Steps to generate a clean, audit-ready vulnerability report within 72 hours.

More like this

PoC Exploit Released for Critical macOS Sandbox Vulnerability (CVE-2024-54498)

A proof-of-concept (PoC) exploit has been publicly disclosed for a critical vulnerability impacting macOS...

Credit Card Skimmer Hits WordPress Checkout Pages, Stealing Payment Data

Researchers analyzed a new stealthy credit card skimmer that targets WordPress checkout pages by...

Hackers Exploiting YouTube to Spread Malware That Steals Browser Data

Malware actors leverage popular platforms like YouTube and social media to distribute fake installers....