NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐘 Packagist
Not in CISA KEV

Ibexa Kernel's files with blacklisted extensions can be still saved to draftsGHSA-mwvh-p3hx-x4gg

Fix: ezsystems/ezplatform-kernel@7e47231

GHSA-mwvh-p3hx-x4gg is a security vulnerability in ezsystems/ezplatform-kernel. A fix is available for ezsystems/ezplatform-kernel — see the affected versions and patch details below.

Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 29, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🐘ezsystems/ezplatform-kernel

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

Impact

File validation can be configured to reject certain files by file type. When this happens, validation fails, and the content can't be published. However, the file can be saved when saving the content draft. This means unwanted files can be present in storage, even if they are not easily accessible due to the content not being published. The fix ensures these unwanted file types are never stored. An attacker would need to have existing access to create content with a file field type to exploit this.

Patches

See "Patched versions". Commit: https://github.com/ezsystems/ezplatform-kernel/commit/7e472317f7c75f45f72f74c38406952d8bea0de1

References

https://developers.ibexa.co/security-advisories/ibexa-sa-2024-002-file-validation-and-workflow-stages

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistezsystems/ezplatform-kernel≥ 1.3.0&&< 1.3.351.3.35composer require ezsystems/ezplatform-kernel:^1.3.35

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update ezsystems/ezplatform-kernel to 1.3.35 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mwvh-p3hx-x4gg is resolved across your whole dependency graph.

  3. 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

### Impact File validation can be configured to reject certain files by file type. When this happens, validation fails, and the content can't be published. However, the file can be saved when saving the content draft. This means unwanted files can be present in storage, even if they are not easily accessible due to the content not being published. The fix ensures these unwanted file types are never stored. An attacker would need to have existing access to create content with a file field type to exploit this. ### Patches See "Patched versions". Commit: https://github.com/ezsystems/ezplatform-
O3 Security · Impact-Aware SCA

Is GHSA-mwvh-p3hx-x4gg in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works
Ibexa Kernel's files with blacklisted extensions can be still…