MFA bypass via spoofed trusted-device address
Published Nov 9, 2023 · Updated Feb 26, 2025
Improper authentication in Apereo CAS through 7.0.0-RC7 allows remote attackers to bypass MFA by spoofing a trusted device. Trusted-device verification relies on the address returned by HttpServletRequest.getRemoteAddr without establishing that the address authentically identifies the saved device. Exploitation requires valid primary credentials, enabled trusted-device recognition, and control of the evaluated address; success skips the second factor.
Summary
What happened
Improper authentication in Apereo CAS through 7.0.0-RC7 allows remote attackers to bypass MFA by spoofing a trusted device. Trusted-device verification relies on the address returned by HttpServletRequest.getRemoteAddr without establishing that the address authentically identifies the saved device. Exploitation requires valid primary credentials, enabled trusted-device recognition, and control of the evaluated address; success skips the second factor.
The record
- CVE
- CVE-2023-4612
- Published
- Nov 9, 2023
- Updated
- Feb 26, 2025
- Vendor
- Apereo
- Product
- Apereo CAS
- Classifications
- CWE-302
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 9, 2023CVE publishedPublication date reported by the CVE source.
- Feb 26, 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=0 <=7.0.0-RC7
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.
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