SymfonyFramework / library · Sensiolabs
CVE-2024-50345
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedsymfony/http-foundation is a module for the Symphony PHP framework which defines an object-oriented layer for the HTTP specification. The `Request` class, does not parse URI with special characters the same way browsers do. As a result, an attacker can trick a validator relying on the `Request` class to redirect users to another domain. The `Request::create` methods now assert the URI does not contain invalid characters as defined by https://url.spec.whatwg.org/. This issue has been patched in versions 5.4.46, 6.4.14, and 7.1.7. Users are advised to upgrade. There are no known workarounds for this vulnerability.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Symfony HttpFoundation Request class parses URIs with special characters differently from browsers, allowing attackers to craft malicious URIs that bypass validator checks and redirect users to attacker-controlled domains. The fix adds URI validation against the WHATWG spec in the Request::create methods.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
SymfonyFramework / library
< 5.4.46>= 6.0.0, < 6.4.14>= 7.0.0, < 7.1.7CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify symfony/http-foundation versionRun `composer show symfony/http-foundation` or check your composer.lock file for the installed version of the symfony/http-foundation packageAffected if The installed version is less than 5.4.46, or between 6.0.0 and 6.4.13, or between 7.0.0 and 7.1.6
-
Locate usage of Request::createSearch your codebase for calls to Symfony\Component\HttpFoundation\Request::create method, which parses and creates request objects from URIsAffected if Your application calls Request::create with user-supplied URI input without additional validation
-
Check for custom URI validation before Request::createAudit code that passes URIs to Request::create to determine if WHATWG-compliant URI validation is performed beforehandAffected if URIs are passed directly to Request::create without validation against RFC 3986 or WHATWG URL standard
-
Review redirect logic using Request objectsExamine code paths that use Request objects for redirects or URI-based operations, as the vulnerability allows crafted URIs to bypass validationAffected if Your application performs redirects or URI checks using Request objects derived from untrusted input
You are affected if your installed symfony/http-foundation version falls within the vulnerable ranges AND your code uses Request::create with unvalidated URI input from external sources.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped5.4.466.4.147.1.7
Upgrade symfony/http-foundation to version 5.4.46, 6.4.14, or 7.1.7 or later to patch the URI parsing vulnerability.
Upgrade to Symfony http-foundation 5.4.46 (for 5.x), 6.4.14 (for 6.x), or 7.1.7 (for 7.x) matching your current major version
- Identify the current Symfony framework version in use by checking composer.json or composer.lock
- For Symfony 5.x users: Run `composer require symfony/http-foundation:5.4.46`
- For Symfony 6.x users: Run `composer require symfony/http-foundation:6.4.14`
- For Symfony 7.x users: Run `composer require symfony/http-foundation:7.1.7`
- Run `composer update symfony/http-foundation` to apply the patched version
- Verify the upgrade by running application tests to ensure no regressions
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Symfony
Scoped from the published advisory
- Consultation3.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,840.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-50345 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-50345 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data