How severe is GHSA-6mjq-9x4w-m3w9?

No CVSS score has been assigned to GHSA-6mjq-9x4w-m3w9 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-6mjq-9x4w-m3w9?

GHSA-6mjq-9x4w-m3w9 affects the following packages: friendsofsymfony/user-bundle (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-6mjq-9x4w-m3w9?

Update friendsofsymfony/user-bundle to 1.2.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6mjq-9x4w-m3w9 is resolved across your whole dependency graph.

How do I detect GHSA-6mjq-9x4w-m3w9 in my Packagist dependencies?

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

How do I mitigate GHSA-6mjq-9x4w-m3w9 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-6mjq-9x4w-m3w9?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-6mjq-9x4w-m3w9 can be triaged on real exposure rather than presence alone.

Is GHSA-6mjq-9x4w-m3w9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-6mjq-9x4w-m3w9 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-6mjq-9x4w-m3w9 published, and has it been updated?

GHSA-6mjq-9x4w-m3w9 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-6mjq-9x4w-m3w9 — friendsofsymfony/user-bun…

Fix: FriendsOfSymfony/FOSUserBundle@8e412a7

GHSA-6mjq-9x4w-m3w9 is a security vulnerability in friendsofsymfony/user-bundle. A fix is available for friendsofsymfony/user-bundle — see the affected versions and patch details below.

FOSUserBundle Session Hijacking Vulnerability

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/user-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

Versions of FOSUserBundle from 1.2.x to 1.2.4 have been found to contain a security vulnerability related to session hijacking. This issue has been addressed in version 1.2.4, and users are strongly advised to upgrade to the latest version to prevent potential session-related security risks.

Affected Packages

1 total 1 fixed

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

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for friendsofsymfony/user-bundle, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update friendsofsymfony/user-bundle to 1.2.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6mjq-9x4w-m3w9 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-6mjq-9x4w-m3w9 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-6mjq-9x4w-m3w9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-6mjq-9x4w-m3w9 in your dependencies?

O3 Security finds GHSA-6mjq-9x4w-m3w9 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