Ibexa Kernel's files with blacklisted extensions can be still saved to drafts

published 2024-03-20 2y ago modified 2024-11-29 last yr.

cvss: —; not scored
cisa kev: Not listed; not in CISA's catalog
epss: —; no score, EPSS covers CVEs only
public exploits: 0; none known

### 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

Patch / fix

fixed in 1 links 1

packagist ibexa/core 4.5.6, 4.6.2

github.com/ibexa/core@7e47231 commit

Is GHSA-9j39-4686-m3c4 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem	package	affected	fixed in
packagist	ibexa/core	>=4.5.0, <4.5.6 >=4.6.0, <4.6.2	4.5.6 4.6.2

Classification

Weakness

CWE-434 Unrestricted Upload of File with Dangerous Type

References

Sources

GitHub Advisory GHSA-9j39-4686-m3c4

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.