How severe is GHSA-p9fg-j6ww-953m?

No CVSS score has been assigned to GHSA-p9fg-j6ww-953m yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-p9fg-j6ww-953m?

GHSA-p9fg-j6ww-953m affects the following packages: friendsofsymfony/rest-bundle (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-p9fg-j6ww-953m?

Update friendsofsymfony/rest-bundle to 1.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p9fg-j6ww-953m is resolved across your whole dependency graph.

How do I detect GHSA-p9fg-j6ww-953m in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for friendsofsymfony/rest-bundle, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-p9fg-j6ww-953m if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-p9fg-j6ww-953m?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-p9fg-j6ww-953m can be triaged on real exposure rather than presence alone.

Is GHSA-p9fg-j6ww-953m actively exploited in the wild?

No public exploit code has been indexed for GHSA-p9fg-j6ww-953m yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-p9fg-j6ww-953m published, and has it been updated?

GHSA-p9fg-j6ww-953m was published on May 15, 2024 and was last updated on November 29, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

GHSA-p9fg-j6ww-953m — friendsofsymfony/rest-bun…

Fix: FriendsOfSymfony/FOSRestBundle@3dd7d40

GHSA-p9fg-j6ww-953m is a security vulnerability in friendsofsymfony/rest-bundle. A fix is available for friendsofsymfony/rest-bundle — see the affected versions and patch details below.

FOSRestBundle issue with broken validation of JSONP callbacks

Published

May 15, 2024

Updated

Nov 29, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 29, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐘friendsofsymfony/rest-bundle

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Starting with FOSRestBundle 1.2 we switched to using willdurand/jsonp-callback-validator for validation of JSONP callbacks. However the change was implemented incorrectly validating the callback query param name, rather than its value. Anyone using the JSONP handler (which is off by default) together with FOSRestBundle 1.2.0 or 1.2.1 should update to FOSRestBundle 1.2.2.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`friendsofsymfony/rest-bundle`	≥ 1.2.0&&< 1.2.2	1.2.2`composer require friendsofsymfony/rest-bundle:^1.2.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for friendsofsymfony/rest-bundle, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update friendsofsymfony/rest-bundle to 1.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p9fg-j6ww-953m is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-p9fg-j6ww-953m can be triaged on real exposure rather than presence alone.

Tailored to GHSA-p9fg-j6ww-953m. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Starting with FOSRestBundle 1.2 we [switched](https://github.com/FriendsOfSymfony/FOSRestBundle/pull/642/files#diff-431bc57ca9ca16332c0cff43ad45263cR37) to using [willdurand/jsonp-callback-validator](https://github.com/willdurand/JsonpCallbackValidator) for validation of JSONP callbacks. However [the change was implemented](https://github.com/FriendsOfSymfony/FOSRestBundle/pull/665) incorrectly validating the callback query param name, rather than its value. Anyone using the JSONP handler (which is off by default) together with FOSRestBundle 1.2.0 or 1.2.1 should update to FOSRestBundle [1.2.2

O3 Security · Impact-Aware SCA

Is GHSA-p9fg-j6ww-953m in your dependencies?

O3 Security finds GHSA-p9fg-j6ww-953m across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works