NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · Composer (PHP)

GHSA-9j39-4686-m3c4: Ibexa Kernel's files with blacklisted extensions can be still saved to drafts

medium

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.

Published Mar 20, 2024

Affected packages

ibexa/core

Ecosystem
Composer (PHP)
Affected
>= 4.5.0, < 4.5.6
Fixed in
4.5.6
Check
composer show ibexa/core

ibexa/core

Ecosystem
Composer (PHP)
Affected
>= 4.6.0, < 4.6.2
Fixed in
4.6.2
Check
composer show ibexa/core

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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/ibexa/core/commit/7e472317f7c75f45f72f74c38406952d8bea0de1

References

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

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology