{"answers":{"affected":"6 open source packages ship an affected version, including ezsystems/ezpublish-kernel.","exploited":"There is no known exploitation of GHSA-3vwr-jj4f-h98x in the wild and no public exploit code.","fix":"Upgrade ezsystems/ezpublish-kernel to a fixed version for your release line: 5.4.14.1, 6.13.6.2 or 7.5.6.2.","what":"GHSA-3vwr-jj4f-h98x is a vulnerability in ezsystems/ezpublish-kernel, published on 15 May 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-3vwr-jj4f-h98x and fix it if it is affected.\n\nWhat it is: GHSA-3vwr-jj4f-h98x is a vulnerability in ezsystems/ezpublish-kernel, published on 15 May 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-3vwr-jj4f-h98x in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- ezsystems/ezpublish-kernel (Packagist): affected from 5.4.0; fixed in 5.4.14.1\n- ezsystems/ezpublish-kernel (Packagist): affected from 5.4.0; fixed in 5.4.14.1\n- ezsystems/ezpublish-kernel (Packagist): affected from 6.13.0; fixed in 6.13.6.2\n- ezsystems/ezpublish-kernel (Packagist): affected from 6.13.0; fixed in 6.13.6.2\n- ezsystems/ezpublish-kernel (Packagist): affected from 7.5.0; fixed in 7.5.6.2\n- ezsystems/ezpublish-kernel (Packagist): affected from 7.5.0; fixed in 7.5.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-3vwr-jj4f-h98x/ (Markdown: https://insights.sbomify.com/GHSA-3vwr-jj4f-h98x/index.md)","id":"GHSA-3vwr-jj4f-h98x","markdown":"https://insights.sbomify.com/GHSA-3vwr-jj4f-h98x/index.md","name":"GHSA-3vwr-jj4f-h98x","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"eZ Publish CMS","requires_auth":"low_privilege","summary":"Attackers with upload permissions can execute remote code via malicious files if server configuration allows PHP execution in upload directories.","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":"This Security Advisory is about a vulnerability in the way eZ Platform and eZ Publish Legacy handles file uploads, which can in the worst case lead to remote code execution (RCE), a very serious threat. An attacker would need access to uploading files to be able to exploit the vulnerability, so if you have strict controls on this and trust all who have this permission, you're not affected. On the basis of the tests we have made, we also believe the vulnerability cannot be exploited as long as our recommended vhost configuration is used. Here is the v2.5 recommendation for Nginx, as an example:\n\nhttps://github.com/ezsystems/ezplatform/blob/2.5/doc/nginx/vhost.template#L31\n\nThis vhost template specifies that only the file app.php in the web root is executed, while vulnerable configurations allow execution of any php file. Apache is affected in the same way as Nginx, and is also protected by using the recommended configuration. The build-in webserver in PHP stays vulnerable, as it doesn't use this type of configuration (this webserver should only be used for development, never for production). We cannot be 100% certain our configuration is not vulnerable. We also do not know if all our users use the recommended configuration, so we send out this fix to be on the safe side.\n\nThe fix includes a blacklist feature for uploaded filenames, such as \".php\". The file types on the blacklist cannot be uploaded. The blacklist is configurable. In eZ Platform you will find it as ezsettings.default.io.file_storage.file_type_blacklist in eZ/Bundle/EzPublishCoreBundle/Resources/config/default_settings.yml in vendors/ezsystems/ezpublish-kernel. In eZ Publish Legacy you will find it as FileExtensionBlackList in settings/file.ini. By default it blocks these file types: php, php3, phar, phpt, pht, phtml, pgif. The fix also inclues a new block against path traversal attacks, though this kind of attack was not reproducible in our tests.","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":"eZ Publish Remote code execution in file uploads","id":"GHSA-3vwr-jj4f-h98x","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"file_upload","year":"2024"},"n_packages":6,"n_references":null,"packages":[{"ecosystem":"Packagist","fixed":["5.4.14.1"],"introduced":["5.4.0"],"last_affected":[],"package":"ezsystems/ezpublish-kernel","purl":null,"source":"GHSA-3vwr-jj4f-h98x"},{"ecosystem":"Packagist","fixed":["5.4.14.1"],"introduced":["5.4.0"],"last_affected":[],"package":"ezsystems/ezpublish-kernel","purl":"pkg:composer/ezsystems/ezpublish-kernel","source":"GHSA-3vwr-jj4f-h98x"},{"ecosystem":"Packagist","fixed":["6.13.6.2"],"introduced":["6.13.0"],"last_affected":[],"package":"ezsystems/ezpublish-kernel","purl":null,"source":"GHSA-3vwr-jj4f-h98x"},{"ecosystem":"Packagist","fixed":["6.13.6.2"],"introduced":["6.13.0"],"last_affected":[],"package":"ezsystems/ezpublish-kernel","purl":"pkg:composer/ezsystems/ezpublish-kernel","source":"GHSA-3vwr-jj4f-h98x"},{"ecosystem":"Packagist","fixed":["7.5.6.2"],"introduced":["7.5.0"],"last_affected":[],"package":"ezsystems/ezpublish-kernel","purl":null,"source":"GHSA-3vwr-jj4f-h98x"},{"ecosystem":"Packagist","fixed":["7.5.6.2"],"introduced":["7.5.0"],"last_affected":[],"package":"ezsystems/ezpublish-kernel","purl":"pkg:composer/ezsystems/ezpublish-kernel","source":"GHSA-3vwr-jj4f-h98x"}],"products":null,"published":"2024-05-15","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 upload permissions can execute remote code via malicious files if server configuration allows PHP execution in upload directories.","url":"https://insights.sbomify.com/GHSA-3vwr-jj4f-h98x/"}