Authentication bypass via predictable CHAP challenges
Published Sep 6, 2024 · Updated Nov 30, 2024
CHAP authentication bypass in tgt before 1.0.93 allows remote attackers to gain an iSCSI user's privileges through response replay. The chap_initiator_auth_create_challenge function uses rand() without calling srand(), so each process restart repeats the same challenge sequence. Exploitation requires monitoring a valid initiator exchange and waiting for the target daemon or service to restart; the replay grants that iSCSI user's privileges.
Summary
What happened
CHAP authentication bypass in tgt before 1.0.93 allows remote attackers to gain an iSCSI user's privileges through response replay. The chap_initiator_auth_create_challenge function uses rand() without calling srand(), so each process restart repeats the same challenge sequence. Exploitation requires monitoring a valid initiator exchange and waiting for the target daemon or service to restart; the replay grants that iSCSI user's privileges.
The record
- CVE
- CVE-2024-45751
- Published
- Sep 6, 2024
- Updated
- Nov 30, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-338, T1040
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 6, 2024CVE publishedPublication date reported by the CVE source.
- Nov 30, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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