Sensitive-data disclosure via RSA without OAEP
Published Jan 12, 2025 · Updated Jan 13, 2025
IBM Robotic Process Automation 21.0.0 through 21.0.7.19 and 23.0.0 through 23.0.19 exposes sensitive data to remote attackers. The product uses RSA encryption without OAEP, but IBM has not identified the affected data path or RSA operation that handles attacker-influenced input. Exploitation requires a complex network attack without credentials or user interaction and affects confidentiality without reported data modification or service interruption.
Summary
What happened
IBM Robotic Process Automation 21.0.0 through 21.0.7.19 and 23.0.0 through 23.0.19 exposes sensitive data to remote attackers. The product uses RSA encryption without OAEP, but IBM has not identified the affected data path or RSA operation that handles attacker-influenced input. Exploitation requires a complex network attack without credentials or user interaction and affects confidentiality without reported data modification or service interruption.
The record
- CVE
- CVE-2024-51456
- Published
- Jan 12, 2025
- Updated
- Jan 13, 2025
- Vendor
- IBM
- Product
- IBM Robotic Process Automation
- Classifications
- CWE-780
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 12, 2025CVE publishedPublication date reported by the CVE source.
- Jan 13, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=21.0.0 <=21.0.7.19
- Affected versionversion=23.0.0 <=23.0.19
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo