{"answers":{"affected":"4 open source packages ship an affected version, including ibexa/core.","exploited":"There is no known exploitation of GHSA-9j39-4686-m3c4 in the wild and no public exploit code.","fix":"Upgrade ibexa/core to a fixed version for your release line: 4.5.6 or 4.6.2.","what":"GHSA-9j39-4686-m3c4 is a vulnerability in ibexa/core, published on 20 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-9j39-4686-m3c4 and fix it if it is affected.\n\nWhat it is: GHSA-9j39-4686-m3c4 is a vulnerability in ibexa/core, published on 20 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-9j39-4686-m3c4 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- ibexa/core (Packagist): affected from 4.5.0; fixed in 4.5.6\n- ibexa/core (Packagist): affected from 4.5.0; fixed in 4.5.6\n- ibexa/core (Packagist): affected from 4.6.0; fixed in 4.6.2\n- ibexa/core (Packagist): affected from 4.6.0; fixed in 4.6.2\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-9j39-4686-m3c4/ (Markdown: https://insights.sbomify.com/GHSA-9j39-4686-m3c4/index.md)","id":"GHSA-9j39-4686-m3c4","markdown":"https://insights.sbomify.com/GHSA-9j39-4686-m3c4/index.md","name":"GHSA-9j39-4686-m3c4","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"Ibexa CMS","requires_auth":"low_privilege","summary":"Attackers with content creation access can bypass file type restrictions by saving blacklisted files as drafts, storing unwanted files in the system.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### Impact\nFile 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.\n\n### Patches\nSee \"Patched versions\".\nCommit: https://github.com/ibexa/core/commit/7e472317f7c75f45f72f74c38406952d8bea0de1\n\n### References\nhttps://developers.ibexa.co/security-advisories/ibexa-sa-2024-002-file-validation-and-workflow-stages","ecosystems":["Packagist"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Ibexa Kernel's files with blacklisted extensions can be still saved to drafts","id":"GHSA-9j39-4686-m3c4","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"file_upload","year":"2024"},"n_packages":4,"n_references":null,"packages":[{"ecosystem":"Packagist","fixed":["4.5.6"],"introduced":["4.5.0"],"last_affected":[],"package":"ibexa/core","purl":null,"source":"GHSA-9j39-4686-m3c4"},{"ecosystem":"Packagist","fixed":["4.5.6"],"introduced":["4.5.0"],"last_affected":[],"package":"ibexa/core","purl":"pkg:composer/ibexa/core","source":"GHSA-9j39-4686-m3c4"},{"ecosystem":"Packagist","fixed":["4.6.2"],"introduced":["4.6.0"],"last_affected":[],"package":"ibexa/core","purl":null,"source":"GHSA-9j39-4686-m3c4"},{"ecosystem":"Packagist","fixed":["4.6.2"],"introduced":["4.6.0"],"last_affected":[],"package":"ibexa/core","purl":"pkg:composer/ibexa/core","source":"GHSA-9j39-4686-m3c4"}],"products":null,"published":"2024-03-20","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Attackers with content creation access can bypass file type restrictions by saving blacklisted files as drafts, storing unwanted files in the system.","url":"https://insights.sbomify.com/GHSA-9j39-4686-m3c4/"}