Sensitive-data disclosure and modification via broken cryptography
Published Aug 9, 2023 · Updated Oct 29, 2024
Broken cryptography in HCL DRYiCE iAutomate 6.0 through 6.2 allows local users to compromise sensitive-data confidentiality and integrity. HCL has not disclosed the affected component, algorithm, protected data, or operation that applies the broken cryptography. Exploitation requires low-privileged local access and high-complexity conditions; the reported impact is limited to unauthorized disclosure and modification, with no service interruption reported.
Summary
What happened
Broken cryptography in HCL DRYiCE iAutomate 6.0 through 6.2 allows local users to compromise sensitive-data confidentiality and integrity. HCL has not disclosed the affected component, algorithm, protected data, or operation that applies the broken cryptography. Exploitation requires low-privileged local access and high-complexity conditions; the reported impact is limited to unauthorized disclosure and modification, with no service interruption reported.
The record
- CVE
- CVE-2023-23347
- Published
- Aug 9, 2023
- Updated
- Oct 29, 2024
- Vendor
- HCL Software
- Product
- HCL DRYiCE iAutomate
- Classifications
- CWE-327
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 9, 2023CVE publishedPublication date reported by the CVE source.
- Oct 29, 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=6..0, 6.1, 6.2
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