CVE-2024-51456: IBM Robotic Process Automation information disclosure

Published Jan 11, 2025
·
Updated

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.

Other sources

IBM Robotic Process Automation could allow a remote attacker to obtain sensitive data that may be exposed through certain crypto-analytic attacks.

IBM

Affected Software

5 affected components
IBM Robotic Process Automation for Cloud Pak<=21.0.0 - 21.0.7.19, 23.0.0 - 23.0.19
IBM Robotic Process Automation<=21.0.0 - 21.0.7.19, 23.0.0 - 23.0.19
All of the following
Any of the following
IBM Robotic Process Automation>=21.0.0<=21.0.7.19
IBM Robotic Process Automation>=23.0.0<=23.0.19
Microsoft Windows

Event History

Jan 11, 2025
CVE Published
via IBM·12:00 AM
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software
Jan 12, 2025
CVE Published
via MITRE·01:26 PM
Data Sourced
via MITRE·01:26 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·02:15 PM
DescriptionSeverityWeakness

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-51456?

CVE-2024-51456 is classified as a high-severity vulnerability due to its potential to allow remote attackers to obtain sensitive data.

2

How do I fix CVE-2024-51456?

To fix CVE-2024-51456, upgrade IBM Robotic Process Automation to versions beyond 21.0.7.19 and 23.0.19.

3

Which versions of IBM Robotic Process Automation are affected by CVE-2024-51456?

Versions 21.0.0 through 21.0.7.19 and 23.0.0 through 23.0.19 of IBM Robotic Process Automation are affected by CVE-2024-51456.

4

What type of attacks does CVE-2024-51456 expose to?

CVE-2024-51456 could be exploited through certain crypto-analytic attacks that allow remote attackers to access sensitive data.

5

Is there a workaround for CVE-2024-51456?

Currently, the recommended approach for CVE-2024-51456 is to upgrade to a fixed version, as no official workaround is documented.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203