Account access via reusable login CAPTCHA
Published Nov 1, 2024 · Updated Nov 4, 2024
Authentication-control weakness in Felix Luo oasys 1.1 allows remote attackers to obtain account access through repeated password guesses. LoginsControler.loginCheck validates the session CAPTCHA but does not invalidate or rotate it, so one solved challenge authorizes repeated password attempts. No prior authentication or user interaction is required, but attackers still need a valid session CAPTCHA and a correct account password guess.
Summary
What happened
Authentication-control weakness in Felix Luo oasys 1.1 allows remote attackers to obtain account access through repeated password guesses. LoginsControler.loginCheck validates the session CAPTCHA but does not invalidate or rotate it, so one solved challenge authorizes repeated password attempts. No prior authentication or user interaction is required, but attackers still need a valid session CAPTCHA and a correct account password guess.
The record
- CVE
- CVE-2024-48270
- Published
- Nov 1, 2024
- Updated
- Nov 4, 2024
- Vendor
- Felix Luo
- Product
- oasys
- Classifications
- T1110.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 1, 2024CVE publishedPublication date reported by the CVE source.
- Nov 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.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
- Verification Code Reuse proof of conceptfunctional · demonstrated
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