How severe is GHSA-2x4v-g8cx-jxrq?

No CVSS score has been assigned to GHSA-2x4v-g8cx-jxrq yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2x4v-g8cx-jxrq?

GHSA-2x4v-g8cx-jxrq affects the following packages: ibexa/core (Packagist), ibexa/core (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-2x4v-g8cx-jxrq?

Update ibexa/core to 4.0.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2x4v-g8cx-jxrq is resolved across your whole dependency graph.

How do I detect GHSA-2x4v-g8cx-jxrq in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ibexa/core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-2x4v-g8cx-jxrq if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-2x4v-g8cx-jxrq actively exploited in the wild?

No public exploit code has been indexed for GHSA-2x4v-g8cx-jxrq yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-2x4v-g8cx-jxrq published, and has it been updated?

GHSA-2x4v-g8cx-jxrq was published on June 2, 2022 and was last updated on December 7, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Login timing attack in ibexa/core

Real-World Exposure

2 pkgs affected

🐘ibexa/core🐘ibexa/core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`ibexa/core`	≥ 4.0.0&&< 4.0.7	4.0.7`composer require ibexa/core:^4.0.7`
🐘Packagist	`ibexa/core`	≥ 4.1.0&&< 4.1.4	4.1.4`composer require ibexa/core:^4.1.4`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ibexa/core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ibexa/core to 4.0.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2x4v-g8cx-jxrq is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-2x4v-g8cx-jxrq in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

Login timing attack in ibexa/coreGHSA-2x4v-g8cx-jxrq