2FA bypass via missing registry verification
Published Dec 3, 2023 · Updated Aug 2, 2024
Incorrect authorization in Forgejo before 1.20.5-1 allows remote attackers to bypass 2FA during Docker registry login. The Docker registry Basic Authentication endpoint accepts a valid username and password without invoking the additional 2FA verification required for enrolled accounts. Exploitation requires valid primary credentials for a 2FA-enabled account and grants registry access as that user.
Summary
What happened
Incorrect authorization in Forgejo before 1.20.5-1 allows remote attackers to bypass 2FA during Docker registry login. The Docker registry Basic Authentication endpoint accepts a valid username and password without invoking the additional 2FA verification required for enrolled accounts. Exploitation requires valid primary credentials for a 2FA-enabled account and grants registry access as that user.
The record
- CVE
- CVE-2023-49947
- Published
- Dec 3, 2023
- Updated
- Aug 2, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-863, T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 3, 2023CVE 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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