# GHSA-2x4v-g8cx-jxrq: Login timing attack in ibexa/core

> Attackers can enumerate valid user accounts via timing side-channels in Ibexa DXP, compromising user privacy.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Jun 2022

## What is GHSA-2x4v-g8cx-jxrq?

GHSA-2x4v-g8cx-jxrq is a vulnerability in ibexa/core, published on 2 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

## Which versions are affected by GHSA-2x4v-g8cx-jxrq?

4 open source packages ship an affected version, including ibexa/core.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ibexa/core` | Packagist | From 4.0.0 | 4.0.7 |
| `ibexa/core` | Packagist | From 4.0.0 | 4.0.7 |
| `ibexa/core` | Packagist | From 4.1.0 | 4.1.4 |
| `ibexa/core` | Packagist | From 4.1.0 | 4.1.4 |

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

Upgrade ibexa/core to a fixed version for your release line: 4.0.7 or 4.1.4.

## Is GHSA-2x4v-g8cx-jxrq being exploited?

There is no known exploitation of GHSA-2x4v-g8cx-jxrq in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-2x4v-g8cx-jxrq and fix it if it is affected.

What it is: GHSA-2x4v-g8cx-jxrq is a vulnerability in ibexa/core, published on 2 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-2x4v-g8cx-jxrq in the wild and no public exploit code.

Affected packages and fixed versions:
- ibexa/core (Packagist): affected from 4.0.0; fixed in 4.0.7
- ibexa/core (Packagist): affected from 4.0.0; fixed in 4.0.7
- ibexa/core (Packagist): affected from 4.1.0; fixed in 4.1.4
- ibexa/core (Packagist): affected from 4.1.0; fixed in 4.1.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-2x4v-g8cx-jxrq/ (Markdown: https://insights.sbomify.com/GHSA-2x4v-g8cx-jxrq/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-2x4v-g8cx-jxrq

---
From sbomify Insights: https://insights.sbomify.com/GHSA-2x4v-g8cx-jxrq/
Summaries are generated and may contain mistakes; the official description above is the record.