Skip to content

TYPO3-EXT-SA-2025-001: Account Takeover in extension "OpenID Connect Authentication" (oidc)

Moderate severity GitHub Reviewed Published Jan 28, 2025 to the GitHub Advisory Database • Updated Jan 28, 2025

Package

composer causal/oidc (Composer)

Affected versions

>= 3.0.0, < 4.0.0

Patched versions

4.0.0

Description

Problem Description

A vulnerability in the account linking logic of the extension allows a pre-hijacking attack leading to Account Takeover. The attack can only be exploited if the following requirements are met:

  • An attacker can anticipate the email address of the user.
  • An attacker can register a public frontend user account using that email address before the user's first OIDC login.
  • The IDP returns the field email containing the email address of the user

Solution

An updated versions 4.0.0 is available from the TYPO3 extension manager, packagist and at
https://extensions.typo3.org/extension/download/oidc/4.0.0/zip

Users of the extension are advised to update the extension as soon as possible.

References

Published to the GitHub Advisory Database Jan 28, 2025
Reviewed Jan 28, 2025
Last updated Jan 28, 2025

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N

EPSS score

Weaknesses

CVE ID

CVE-2025-24856

GHSA ID

GHSA-hj78-p4h7-m5fv

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.