{"answers":{"affected":"6 open source packages ship an affected version, including ezsystems/ezplatform.","exploited":"There is no known exploitation of GHSA-qhjc-hg94-245v in the wild and no public exploit code.","fix":"Upgrade ezsystems/ezplatform to a fixed version for your release line: 1.13.5.1, 1.7.9.1 or 2.5.4.","what":"GHSA-qhjc-hg94-245v is a vulnerability in ezsystems/ezplatform, published on 15 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-qhjc-hg94-245v and fix it if it is affected.\n\nWhat it is: GHSA-qhjc-hg94-245v is a vulnerability in ezsystems/ezplatform, published on 15 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-qhjc-hg94-245v in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- ezsystems/ezplatform (Packagist): affected from 1.13.0; fixed in 1.13.5.1\n- ezsystems/ezplatform (Packagist): affected from 1.13.0; fixed in 1.13.5.1\n- ezsystems/ezplatform (Packagist): affected from 1.7.0; fixed in 1.7.9.1\n- ezsystems/ezplatform (Packagist): affected from 1.7.0; fixed in 1.7.9.1\n- ezsystems/ezplatform (Packagist): affected from 2.5.0; fixed in 2.5.4\n- ezsystems/ezplatform (Packagist): affected from 2.5.0; fixed in 2.5.4\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-qhjc-hg94-245v/ (Markdown: https://insights.sbomify.com/GHSA-qhjc-hg94-245v/index.md)","id":"GHSA-qhjc-hg94-245v","markdown":"https://insights.sbomify.com/GHSA-qhjc-hg94-245v/index.md","name":"GHSA-qhjc-hg94-245v","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"eZ Platform CMS","requires_auth":"none","summary":"Attackers can bypass caching security rules by accessing the front controller directly on Platform.sh deployments, potentially exposing cached data.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"The recommended rewrite rules in eZ Platform prevent users from including the front-controller script (normally \"app.php\") in URLs. This prevents certain vulnerabilities related to caching. However, this is not possible when using eZ Platform Cloud (i.e. running eZ Platform on the Platform.sh cloud service), nor can it be done within the .platform.app.yaml configuration file. Therefore we need to reject such requests in the application itself. This advisory adds the prevention within the front controller script itself.\n \nIf you use eZ Platform Cloud / Platform.sh we recommend that you install this security update as soon as possible. It is distributed via Composer as ezsystems/ezplatform 1.7.9.1, and 1.13.5.1, and 2.5.4. This is the commit: https://github.com/ezsystems/ezplatform/commit/34ce86722b36a172e587068fe64a84faa7320cc2","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 Platform Prevent accepting app.php in URL in Platform.sh","id":"GHSA-qhjc-hg94-245v","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"security_feature_bypass","year":"2024"},"n_packages":6,"n_references":null,"packages":[{"ecosystem":"Packagist","fixed":["1.13.5.1"],"introduced":["1.13.0"],"last_affected":[],"package":"ezsystems/ezplatform","purl":null,"source":"GHSA-qhjc-hg94-245v"},{"ecosystem":"Packagist","fixed":["1.13.5.1"],"introduced":["1.13.0"],"last_affected":[],"package":"ezsystems/ezplatform","purl":"pkg:composer/ezsystems/ezplatform","source":"GHSA-qhjc-hg94-245v"},{"ecosystem":"Packagist","fixed":["1.7.9.1"],"introduced":["1.7.0"],"last_affected":[],"package":"ezsystems/ezplatform","purl":null,"source":"GHSA-qhjc-hg94-245v"},{"ecosystem":"Packagist","fixed":["1.7.9.1"],"introduced":["1.7.0"],"last_affected":[],"package":"ezsystems/ezplatform","purl":"pkg:composer/ezsystems/ezplatform","source":"GHSA-qhjc-hg94-245v"},{"ecosystem":"Packagist","fixed":["2.5.4"],"introduced":["2.5.0"],"last_affected":[],"package":"ezsystems/ezplatform","purl":null,"source":"GHSA-qhjc-hg94-245v"},{"ecosystem":"Packagist","fixed":["2.5.4"],"introduced":["2.5.0"],"last_affected":[],"package":"ezsystems/ezplatform","purl":"pkg:composer/ezsystems/ezplatform","source":"GHSA-qhjc-hg94-245v"}],"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 can bypass caching security rules by accessing the front controller directly on Platform.sh deployments, potentially exposing cached data.","url":"https://insights.sbomify.com/GHSA-qhjc-hg94-245v/"}