Skip to content

Timing attack in eZ Platform Ibexa

Low severity GitHub Reviewed Published Mar 12, 2023 to the GitHub Advisory Database • Updated Mar 16, 2023

Package

composer ezsystems/ezplatform-kernel (Composer)

Affected versions

>= 1.3.0, < 1.3.19

Patched versions

1.3.19
composer ezsystems/ezpublish-kernel (Composer)
>= 7.5.0, < 7.5.29
7.5.29

Description

Ibexa DXP is using random execution time to hinder timing attacks against user accounts, a method of discovering whether a given account exists in a system without knowing its password, thus affecting privacy. This implementation was found to not be good enough in some situations. The fix replaces this with constant time functionality, configured in the new security.yml parameter 'ibexa.security.authentication.constant_auth_time'. It will log a warning if the constant time is exceeded. If this happens the setting should be increased.

References

Published by the National Vulnerability Database Mar 12, 2023
Published to the GitHub Advisory Database Mar 12, 2023
Reviewed Mar 13, 2023
Last updated Mar 16, 2023

Severity

Low

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
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
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:N/S:U/C:L/I:N/A:N

EPSS score

0.088%
(38th percentile)

Weaknesses

CVE ID

CVE-2022-48366

GHSA ID

GHSA-66m4-gc8h-hpjx

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.