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

CVE-2022-48366 · Severity: low · CVSS 3.1 · Published 2023-03-12

Timing attack in eZ Platform Ibexa

Technologies: ezsystems/ezplatform-kernel (Packagist), ezsystems/ezpublish-kernel (Packagist). Vendors: Packagist.

Quick answers

Is CVE-2022-48366 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2022-48366 being exploited in the wild.
How severe is CVE-2022-48366?
Low severity, with a CVSS score of 3.1, published 12 March 2023.
Which products and versions are affected?
ezsystems/ezplatform-kernel (Packagist) ECOSYSTEM:introduced=1.3.0,fixed=1.3.19; ezsystems/ezpublish-kernel (Packagist) ECOSYSTEM:introduced=7.5.0,fixed=7.5.29.
Is there a fix for CVE-2022-48366?
Yes. ezsystems/ezplatform-kernel (Packagist): upgrade to 1.3.19 or later; ezsystems/ezpublish-kernel (Packagist): upgrade to 7.5.29 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2022-48366?
Check whether you run ezsystems/ezplatform-kernel (Packagist) or ezsystems/ezpublish-kernel (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • ezsystems/ezplatform-kernel (Packagist): upgrade to 1.3.19 or later
    composer require ezsystems/ezplatform-kernel:^1.3.19
  • ezsystems/ezpublish-kernel (Packagist): upgrade to 7.5.29 or later
    composer require ezsystems/ezpublish-kernel:^7.5.29

Affected products

  • ezsystems/ezplatform-kernel (Packagist) ECOSYSTEM:introduced=1.3.0,fixed=1.3.19
  • ezsystems/ezpublish-kernel (Packagist) ECOSYSTEM:introduced=7.5.0,fixed=7.5.29

Identifiers

  • CVE-2022-48366
  • GHSA-66m4-gc8h-hpjx

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.