Sensitive-data decryption via static keys and CBC
Published Jan 3, 2024 · Updated Jun 18, 2025
Cryptographic failure in HCL Software MyXalytics 5.9 through 6.1 allows remote attackers to decrypt sensitive information. The Encryption Decryption Service uses a static master key and salt stored in a text file, a static initialization vector in code, and AES-CBC to protect secrets. Exploitation requires access to protected ciphertext or configuration material; successful decryption exposes plaintext and the vendor assessment also permits limited integrity loss.
Summary
What happened
Cryptographic failure in HCL Software MyXalytics 5.9 through 6.1 allows remote attackers to decrypt sensitive information. The Encryption Decryption Service uses a static master key and salt stored in a text file, a static initialization vector in code, and AES-CBC to protect secrets. Exploitation requires access to protected ciphertext or configuration material; successful decryption exposes plaintext and the vendor assessment also permits limited integrity loss.
The record
- CVE
- CVE-2023-50350
- Published
- Jan 3, 2024
- Updated
- Jun 18, 2025
- Vendor
- HCL Software
- Product
- MyXalytics
- Classifications
- CWE-327
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 3, 2024CVE publishedPublication date reported by the CVE source.
- Jun 18, 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=5.9, 6.0, 6.1
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