Information disclosure and service interruption via username enumeration
Published May 7, 2021 · Updated Sep 17, 2024
Username enumeration in IBM Robotic Process Automation with Automation Anywhere 11.0 allows remote attackers to obtain sensitive information. IBM identifies username enumeration as the cause but does not disclose the affected endpoint or the response difference used to distinguish valid accounts. The interface is reachable without authentication from an adjacent network, and repeated requests can interrupt service without changing data.
Summary
What happened
Username enumeration in IBM Robotic Process Automation with Automation Anywhere 11.0 allows remote attackers to obtain sensitive information. IBM identifies username enumeration as the cause but does not disclose the affected endpoint or the response difference used to distinguish valid accounts. The interface is reachable without authentication from an adjacent network, and repeated requests can interrupt service without changing data.
The record
- CVE
- CVE-2020-4901
- Published
- May 7, 2021
- Updated
- Sep 17, 2024
- Vendor
- IBM
- Product
- IBM Robotic Process Automation with Automation Anywhere
- Classifications
- T1087
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 7, 2021CVE publishedPublication date reported by the CVE source.
- Sep 17, 2024Record 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=11.0
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