# CVE-2022-48366: Timing attack in eZ Platform Ibexa

> An attacker can determine if user accounts exist in eZ Platform Ibexa Kernel by exploiting a timing side-channel vulnerability.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Mar 2023
- **Updated:** 4 Mar 2025
- **Also known as:** GHSA-66m4-gc8h-hpjx

## What is CVE-2022-48366?

CVE-2022-48366 is a low-severity vulnerability in n/a, published on 12 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in eZ Platform Ibexa Kernel before 1.3.19. It allows determining account existence via a timing attack.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2022-48366?

4 open source packages ship an affected version, including ezsystems/ezplatform-kernel and ezsystems/ezpublish-kernel. It affects 7 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ezsystems/ezplatform-kernel` | Packagist | From 1.3.0 | 1.3.19 |
| `ezsystems/ezplatform-kernel` | Packagist | From 1.3.0 | 1.3.19 |
| `ezsystems/ezpublish-kernel` | Packagist | From 7.5.0 | 7.5.29 |
| `ezsystems/ezpublish-kernel` | Packagist | From 7.5.0 | 7.5.29 |

Products: Ibexa Commerce, Ibexa Digital Experience Platform, Ibexa Ez Platform, Ibexa Ez Platform Kernel, Ibexa Ezplatform-Page-Builder, Ibexa Jmspaymentcorebundle, Ibexa Kernel.

## How do I fix CVE-2022-48366?

Upgrade ezsystems/ezplatform-kernel to 1.3.19 or later.

## Is CVE-2022-48366 being exploited?

There is no known exploitation of CVE-2022-48366 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-48366 and fix it if it is affected.

What it is: CVE-2022-48366 is a low-severity vulnerability in n/a, published on 12 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-48366 in the wild and no public exploit code.

Affected packages and fixed versions:
- ezsystems/ezplatform-kernel (Packagist): affected from 1.3.0; fixed in 1.3.19
- ezsystems/ezplatform-kernel (Packagist): affected from 1.3.0; fixed in 1.3.19
- ezsystems/ezpublish-kernel (Packagist): affected from 7.5.0; fixed in 7.5.29
- ezsystems/ezpublish-kernel (Packagist): affected from 7.5.0; fixed in 7.5.29

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/CVE-2022-48366/ (Markdown: https://insights.sbomify.com/CVE-2022-48366/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-48366
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-48366
- OSV: https://osv.dev/vulnerability/CVE-2022-48366

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-48366/
Summaries are generated and may contain mistakes; the official description above is the record.