Sensitive data disclosure via hard-coded cryptographic key
Published Feb 11, 2025 · Updated Feb 11, 2025
Hard-coded key use in Ivanti Connect Secure before 22.7R2.3 and Policy Secure before 22.7R1.3 allows local users to read sensitive data. The published record identifies the embedded key as the faulty operation, but Ivanti has not disclosed the component containing it or how the key exposes data. Exploitation requires local authenticated access with administrative privileges, and the reported consequence is limited to reading sensitive data.
Summary
What happened
Hard-coded key use in Ivanti Connect Secure before 22.7R2.3 and Policy Secure before 22.7R1.3 allows local users to read sensitive data. The published record identifies the embedded key as the faulty operation, but Ivanti has not disclosed the component containing it or how the key exposes data. Exploitation requires local authenticated access with administrative privileges, and the reported consequence is limited to reading sensitive data.
The record
- CVE
- CVE-2024-13842
- Published
- Feb 11, 2025
- Updated
- Feb 11, 2025
- Vendor
- Ivanti
- Product
- Connect Secure
- Classifications
- CWE-321, T1005
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Feb 11, 2025CVE publishedPublication date reported by the CVE source.
- Feb 11, 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?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
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.
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