{"items":[{"id":"NVI-00007218","kind":"vulnerability","title":"Symfony allows direct access of ESI URLs behind a trusted proxy","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-wvjv-p5rr-mmqm","CVE-2014-5245"],"plain_summary":"OSV carries this publisher advisory for symfony/http-kernel, symfony/http-kernel, symfony/http-kernel, symfony/symfony, symfony/symfony. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 2.3.19 for symfony/http-kernel. Confirm the publisher’s latest guidance.","source_ids":["sr-d3cff25c7043537c00e809268033eab3"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 2.4.9 for symfony/http-kernel. Confirm the publisher’s latest guidance.","source_ids":["sr-d3cff25c7043537c00e809268033eab3"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 2.5.4 for symfony/http-kernel. Confirm the publisher’s latest guidance.","source_ids":["sr-d3cff25c7043537c00e809268033eab3"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 2.3.19 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-d3cff25c7043537c00e809268033eab3"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 2.4.9 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-d3cff25c7043537c00e809268033eab3"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 2.5.4 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-d3cff25c7043537c00e809268033eab3"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-d3cff25c7043537c00e809268033eab3","url":"https://github.com/advisories/GHSA-wvjv-p5rr-mmqm","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-wvjv-p5rr-mmqm","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:51.435Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-d3cff25c7043537c00e809268033eab3"],"technology":"symfony/http-kernel","known_exclusions":[],"conditions_summary":"All 2.2.X, 2.3.X, 2.4.X, and 2.5.X versions of the Symfony HttpKernel component are affected by this security issue. Your application is vulnerable only if the ESI feature is enabled and there is a proxy in front of the web application.\n\nThis issue has been fixed in Symfony 2.3.19, 2.4.9, and 2.5.4. Note that no fixes are provided for Symfony 2.2 as it is not maintained anymore.\n\nDescription\nWhen you enable the ESI feature and when you are using a proxy like Varnish that you configured as a trusted proxy, the `FragmentHandler` considered requests to render fragments as coming from a trusted source, even if the client was requesting them directly. Symfony can not distinguish between ESI requests done on behalf of the client by Varnish and faked fragment requests coming directly from the client.\n\nTo mitigate this issue, and for not-supported Symfony versions, you can use the following workaround in your Varnish configuration (`/_fragment` being the URL path prefix configured under the `fragment` setting of the framework bundle configuration):\n\n Copy\nsub vcl_recv {\n    if (req.restarts == 0 && req.url ~ \"^/_fragment\") {\n        error 400;\n    }\n}\nResolution\nWe do not rely on trusted I","public_affected_ranges":["ECOSYSTEM: introduced 2.0.0; fixed 2.3.19"]},{"certainty":"source_listed","source_ids":["sr-d3cff25c7043537c00e809268033eab3"],"technology":"symfony/http-kernel","known_exclusions":[],"conditions_summary":"All 2.2.X, 2.3.X, 2.4.X, and 2.5.X versions of the Symfony HttpKernel component are affected by this security issue. Your application is vulnerable only if the ESI feature is enabled and there is a proxy in front of the web application.\n\nThis issue has been fixed in Symfony 2.3.19, 2.4.9, and 2.5.4. Note that no fixes are provided for Symfony 2.2 as it is not maintained anymore.\n\nDescription\nWhen you enable the ESI feature and when you are using a proxy like Varnish that you configured as a trusted proxy, the `FragmentHandler` considered requests to render fragments as coming from a trusted source, even if the client was requesting them directly. Symfony can not distinguish between ESI requests done on behalf of the client by Varnish and faked fragment requests coming directly from the client.\n\nTo mitigate this issue, and for not-supported Symfony versions, you can use the following workaround in your Varnish configuration (`/_fragment` being the URL path prefix configured under the `fragment` setting of the framework bundle configuration):\n\n Copy\nsub vcl_recv {\n    if (req.restarts == 0 && req.url ~ \"^/_fragment\") {\n        error 400;\n    }\n}\nResolution\nWe do not rely on trusted I","public_affected_ranges":["ECOSYSTEM: introduced 2.4.0; fixed 2.4.9"]},{"certainty":"source_listed","source_ids":["sr-d3cff25c7043537c00e809268033eab3"],"technology":"symfony/http-kernel","known_exclusions":[],"conditions_summary":"All 2.2.X, 2.3.X, 2.4.X, and 2.5.X versions of the Symfony HttpKernel component are affected by this security issue. Your application is vulnerable only if the ESI feature is enabled and there is a proxy in front of the web application.\n\nThis issue has been fixed in Symfony 2.3.19, 2.4.9, and 2.5.4. Note that no fixes are provided for Symfony 2.2 as it is not maintained anymore.\n\nDescription\nWhen you enable the ESI feature and when you are using a proxy like Varnish that you configured as a trusted proxy, the `FragmentHandler` considered requests to render fragments as coming from a trusted source, even if the client was requesting them directly. Symfony can not distinguish between ESI requests done on behalf of the client by Varnish and faked fragment requests coming directly from the client.\n\nTo mitigate this issue, and for not-supported Symfony versions, you can use the following workaround in your Varnish configuration (`/_fragment` being the URL path prefix configured under the `fragment` setting of the framework bundle configuration):\n\n Copy\nsub vcl_recv {\n    if (req.restarts == 0 && req.url ~ \"^/_fragment\") {\n        error 400;\n    }\n}\nResolution\nWe do not rely on trusted I","public_affected_ranges":["ECOSYSTEM: introduced 2.5.0; fixed 2.5.4"]},{"certainty":"source_listed","source_ids":["sr-d3cff25c7043537c00e809268033eab3"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"All 2.2.X, 2.3.X, 2.4.X, and 2.5.X versions of the Symfony HttpKernel component are affected by this security issue. Your application is vulnerable only if the ESI feature is enabled and there is a proxy in front of the web application.\n\nThis issue has been fixed in Symfony 2.3.19, 2.4.9, and 2.5.4. Note that no fixes are provided for Symfony 2.2 as it is not maintained anymore.\n\nDescription\nWhen you enable the ESI feature and when you are using a proxy like Varnish that you configured as a trusted proxy, the `FragmentHandler` considered requests to render fragments as coming from a trusted source, even if the client was requesting them directly. Symfony can not distinguish between ESI requests done on behalf of the client by Varnish and faked fragment requests coming directly from the client.\n\nTo mitigate this issue, and for not-supported Symfony versions, you can use the following workaround in your Varnish configuration (`/_fragment` being the URL path prefix configured under the `fragment` setting of the framework bundle configuration):\n\n Copy\nsub vcl_recv {\n    if (req.restarts == 0 && req.url ~ \"^/_fragment\") {\n        error 400;\n    }\n}\nResolution\nWe do not rely on trusted I","public_affected_ranges":["ECOSYSTEM: introduced 2.0.0; fixed 2.3.19"]},{"certainty":"source_listed","source_ids":["sr-d3cff25c7043537c00e809268033eab3"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"All 2.2.X, 2.3.X, 2.4.X, and 2.5.X versions of the Symfony HttpKernel component are affected by this security issue. Your application is vulnerable only if the ESI feature is enabled and there is a proxy in front of the web application.\n\nThis issue has been fixed in Symfony 2.3.19, 2.4.9, and 2.5.4. Note that no fixes are provided for Symfony 2.2 as it is not maintained anymore.\n\nDescription\nWhen you enable the ESI feature and when you are using a proxy like Varnish that you configured as a trusted proxy, the `FragmentHandler` considered requests to render fragments as coming from a trusted source, even if the client was requesting them directly. Symfony can not distinguish between ESI requests done on behalf of the client by Varnish and faked fragment requests coming directly from the client.\n\nTo mitigate this issue, and for not-supported Symfony versions, you can use the following workaround in your Varnish configuration (`/_fragment` being the URL path prefix configured under the `fragment` setting of the framework bundle configuration):\n\n Copy\nsub vcl_recv {\n    if (req.restarts == 0 && req.url ~ \"^/_fragment\") {\n        error 400;\n    }\n}\nResolution\nWe do not rely on trusted I","public_affected_ranges":["ECOSYSTEM: introduced 2.4.0; fixed 2.4.9"]},{"certainty":"source_listed","source_ids":["sr-d3cff25c7043537c00e809268033eab3"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"All 2.2.X, 2.3.X, 2.4.X, and 2.5.X versions of the Symfony HttpKernel component are affected by this security issue. Your application is vulnerable only if the ESI feature is enabled and there is a proxy in front of the web application.\n\nThis issue has been fixed in Symfony 2.3.19, 2.4.9, and 2.5.4. Note that no fixes are provided for Symfony 2.2 as it is not maintained anymore.\n\nDescription\nWhen you enable the ESI feature and when you are using a proxy like Varnish that you configured as a trusted proxy, the `FragmentHandler` considered requests to render fragments as coming from a trusted source, even if the client was requesting them directly. Symfony can not distinguish between ESI requests done on behalf of the client by Varnish and faked fragment requests coming directly from the client.\n\nTo mitigate this issue, and for not-supported Symfony versions, you can use the following workaround in your Varnish configuration (`/_fragment` being the URL path prefix configured under the `fragment` setting of the framework bundle configuration):\n\n Copy\nsub vcl_recv {\n    if (req.restarts == 0 && req.url ~ \"^/_fragment\") {\n        error 400;\n    }\n}\nResolution\nWe do not rely on trusted I","public_affected_ranges":["ECOSYSTEM: introduced 2.5.0; fixed 2.5.4"]}],"null_published_at":"2026-10-31T22:13:14.317Z","source_updated_at":"2024-05-30T04:26:51.101Z","source_disclosed_at":"2024-05-30T00:46:52.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T21:42:51.435Z"}],"next_cursor":null,"snapshot_revision":"42594"}