{"answers":{"affected":"4 open source packages ship an affected version, including symfony/symfony.","exploited":"There is no known exploitation of GHSA-hx53-jchx-cr52 in the wild and no public exploit code.","fix":"Upgrade symfony/symfony to a fixed version for your release line: 2.0.19 or 2.1.4.","what":"GHSA-hx53-jchx-cr52 is a vulnerability in symfony/symfony, published on 30 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-hx53-jchx-cr52 and fix it if it is affected.\n\nWhat it is: GHSA-hx53-jchx-cr52 is a vulnerability in symfony/symfony, published on 30 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-hx53-jchx-cr52 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- symfony/symfony (Packagist): affected from 2.0.0; fixed in 2.0.19\n- symfony/symfony (Packagist): affected from 2.0.0; fixed in 2.0.19\n- symfony/symfony (Packagist): affected from 2.1.0; fixed in 2.1.4\n- symfony/symfony (Packagist): affected from 2.1.0; fixed in 2.1.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-hx53-jchx-cr52/ (Markdown: https://insights.sbomify.com/GHSA-hx53-jchx-cr52/index.md)","id":"GHSA-hx53-jchx-cr52","markdown":"https://insights.sbomify.com/GHSA-hx53-jchx-cr52/index.md","name":"GHSA-hx53-jchx-cr52","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Symfony PHP framework","requires_auth":"none","summary":"Attackers can bypass IP-based access controls in Symfony applications using trust proxy mode by spoofing client IPs.","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":"Damien Tournoud, from the Drupal security team, contacted us two days ago about a security issue in the Request::getClientIp() method when the trust proxy mode is enabled (Request::trustProxyData()).\n\nAn application is vulnerable if it uses the client IP address as returned by the Request::getClientIp() method for sensitive decisions like IP based access control.\n\nTo fix this security issue, the following changes have been made to all versions of Symfony2:\n\nA new Request::setTrustedProxies() method has been introduced and should be used intead of Request::trustProxyData() to enable the trust proxy mode. It takes an array of trusted proxy IP addresses as its argument:\n```\n// before (probably in your front controller script)\nRequest::trustProxyData();\n```\n```\n// after\nRequest::setTrustedProxies(array('1.1.1.1'));\n// 1.1.1.1 being the IP address of a trusted reverse proxy\n```\nThe Request::trustProxyData() method has been deprecated (when used, it automatically trusts the latest proxy in the chain -- which is the current remote address):\n```\nRequest::trustProxyData();\n```\n```\n// is equivalent to\nRequest::setTrustedProxies(array($request-\u003eserver-\u003eget('REMOTE_ADDR')));\n```\nWe encourage all Symfony2 users to upgrade as soon as possible. It you don't want to upgrade to the latest version yet, you can also apply the following patches:\n\n[Patch](https://github.com/symfony/symfony/compare/fc89d6b...9ce892c.patch) for Symfony 2.0.19\n[Patch](https://github.com/symfony/symfony/compare/922c201...e5536f0.patch) for Symfony 2.1.4","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":"Symfony2 improper IP based access control","id":"GHSA-hx53-jchx-cr52","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"security_feature_bypass","year":"2024"},"n_packages":4,"n_references":null,"packages":[{"ecosystem":"Packagist","fixed":["2.0.19"],"introduced":["2.0.0"],"last_affected":[],"package":"symfony/symfony","purl":null,"source":"GHSA-hx53-jchx-cr52"},{"ecosystem":"Packagist","fixed":["2.0.19"],"introduced":["2.0.0"],"last_affected":[],"package":"symfony/symfony","purl":"pkg:composer/symfony/symfony","source":"GHSA-hx53-jchx-cr52"},{"ecosystem":"Packagist","fixed":["2.1.4"],"introduced":["2.1.0"],"last_affected":[],"package":"symfony/symfony","purl":null,"source":"GHSA-hx53-jchx-cr52"},{"ecosystem":"Packagist","fixed":["2.1.4"],"introduced":["2.1.0"],"last_affected":[],"package":"symfony/symfony","purl":"pkg:composer/symfony/symfony","source":"GHSA-hx53-jchx-cr52"}],"products":null,"published":"2024-05-30","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 IP-based access controls in Symfony applications using trust proxy mode by spoofing client IPs.","url":"https://insights.sbomify.com/GHSA-hx53-jchx-cr52/"}