Account takeover via retained pre-linking password
Published Jun 18, 2024 · Updated Aug 2, 2024
Authentication bypass in PocketBase before 0.22.14 allows remote attackers to retain access to a victim account after OAuth2 linking. The OAuth2 autolinking flow associates a verified OAuth2 identity with an existing unverified email record without resetting that record's attacker-chosen password. Both password and OAuth2 authentication must be enabled, and the targeted user must complete OAuth2 sign-up with the same email before the attacker can log in as that user.
Summary
What happened
Authentication bypass in PocketBase before 0.22.14 allows remote attackers to retain access to a victim account after OAuth2 linking. The OAuth2 autolinking flow associates a verified OAuth2 identity with an existing unverified email record without resetting that record's attacker-chosen password. Both password and OAuth2 authentication must be enabled, and the targeted user must complete OAuth2 sign-up with the same email before the attacker can log in as that user.
The record
- CVE
- CVE-2024-38351
- Published
- Jun 18, 2024
- Updated
- Aug 2, 2024
- Vendor
- PocketBase
- Product
- PocketBase
- Classifications
- CWE-287, T1078
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 18, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 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=< 0.22.14
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.
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