Authenticated login bypass via unconfirmed accounts
Published Jan 2, 2020 · Updated Aug 7, 2024
Incorrect authorization in obs-server before 1.7.7 allows remote authenticated users with unconfirmed accounts to log in through the REST API. The REST API login path accepts an account whose confirmation state should prevent authentication, but public records do not identify the faulty check. Possession of credentials for an unconfirmed account is required; successful exploitation grants application access reserved for confirmed accounts.
Summary
What happened
Incorrect authorization in obs-server before 1.7.7 allows remote authenticated users with unconfirmed accounts to log in through the REST API. The REST API login path accepts an account whose confirmation state should prevent authentication, but public records do not identify the faulty check. Possession of credentials for an unconfirmed account is required; successful exploitation grants application access reserved for confirmed accounts.
The record
- CVE
- CVE-2010-3782
- Published
- Jan 2, 2020
- Updated
- Aug 7, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-863, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 2, 2020CVE publishedPublication date reported by the CVE source.
- Aug 7, 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.
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