Kerberos ticket theft via unauthorized push notifications
Published Jan 28, 2022 · Updated Aug 4, 2024
Broken access control in VeridiumAD 2.5.3.0 allows remote authenticated users to obtain another user's Kerberos TGT via a push request. The login push-notification HTTP request accepts any enrolled target and attacker-controlled notification text without enforcing authorization. A valid VeridiumAD account and the target user's acceptance are required; acceptance gives the requester the target user's login ticket.
Summary
What happened
Broken access control in VeridiumAD 2.5.3.0 allows remote authenticated users to obtain another user's Kerberos TGT via a push request. The login push-notification HTTP request accepts any enrolled target and attacker-controlled notification text without enforcing authorization. A valid VeridiumAD account and the target user's acceptance are required; acceptance gives the requester the target user's login ticket.
The record
- CVE
- CVE-2021-42791
- Published
- Jan 28, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-444, T1558
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 28, 2022CVE publishedPublication date reported by the CVE source.
- Aug 4, 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.
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