Authentication bypass via unverified ID4me tokens
Published Jun 14, 2024 · Updated Aug 2, 2024
Improper signature verification in Nextcloud user_oidc before 1.3.5 allows remote authenticated users to submit forged ID4me tokens. Id4meController::code decoded the token payload and created or updated its named user without verifying the JWT signature or rejecting expired tokens. Exploitation requires low-privileged access and user interaction in an ID4me login flow, allowing forged identity claims to be accepted as authentic.
Summary
What happened
Improper signature verification in Nextcloud user_oidc before 1.3.5 allows remote authenticated users to submit forged ID4me tokens. Id4meController::code decoded the token payload and created or updated its named user without verifying the JWT signature or rejecting expired tokens. Exploitation requires low-privileged access and user interaction in an ID4me login flow, allowing forged identity claims to be accepted as authentic.
The record
- CVE
- CVE-2024-37886
- Published
- Jun 14, 2024
- Updated
- Aug 2, 2024
- Vendor
- Nextcloud GmbH
- Product
- Security Advisories
- Classifications
- CWE-347, T1606
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 14, 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=< 1.3.5
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
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