Headline
GHSA-mwvh-p3hx-x4gg: Ibexa Kernel's files with blacklisted extensions can be still saved to drafts
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
Package
composer ezsystems/ezplatform-kernel (Composer)
Affected versions
>= 1.3.0, < 1.3.35
Patched versions
1.3.35
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: ezsystems/ezplatform-kernel@7e47231
References
https://developers.ibexa.co/security-advisories/ibexa-sa-2024-002-file-validation-and-workflow-stages
References
- GHSA-mwvh-p3hx-x4gg
- ezsystems/ezplatform-kernel@7e47231
- https://developers.ibexa.co/security-advisories/ibexa-sa-2024-002-file-validation-and-workflow-stages
glye published to ezsystems/ezplatform-kernel
Mar 20, 2024
Published to the GitHub Advisory Database
Mar 20, 2024
Reviewed
Mar 20, 2024
Last updated
Mar 20, 2024