Ibexa Kernel's files with blacklisted extensions can be still saved to drafts
The advisory, in context
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
Affected packages
Start with the recorded fix for your release branch. Check your installed version and test compatibility before upgrading. Fixing this advisory does not rule out other vulnerabilities in the release.
From 4.5.0 before 4.5.6
Fixed in 4.5.6
6 explicitly affected versions
v4.5.0, v4.5.1, v4.5.2, v4.5.3, v4.5.4, v4.5.5
View affected-version evidence
{
"ranges": [
{
"events": [
{
"introduced": "4.5.0"
},
{
"fixed": "4.5.6"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"v4.5.0",
"v4.5.1",
"v4.5.2",
"v4.5.3",
"v4.5.4",
"v4.5.5"
]
}From 4.6.0 before 4.6.2
Fixed in 4.6.2
2 explicitly affected versions
v4.6.0, v4.6.1
View affected-version evidence
{
"ranges": [
{
"events": [
{
"introduced": "4.6.0"
},
{
"fixed": "4.6.2"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"v4.6.0",
"v4.6.1"
]
}