SymfonyFramework / library · Sensiolabs
CVE-2018-11408
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 · uneditedThe security handlers in the Security component in Symfony in 2.7.x before 2.7.48, 2.8.x before 2.8.41, 3.3.x before 3.3.17, 3.4.x before 3.4.11, and 4.0.x before 4.0.11 have an Open redirect vulnerability when security.http_utils is inlined by a container. NOTE: this issue exists because of an incomplete fix for CVE-2017-16652.
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 confidenceOpen redirect vulnerability in Symfony Security component's security handlers when security.http_utils is inlined by a container. Attackers can craft malicious URLs to redirect users to arbitrary external sites. This is an incomplete fix for CVE-2017-16652, indicating the original patch did not fully address the root cause.
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
>= 2.7.0, < 2.7.48>= 2.8.0, < 2.8.41>= 3.3.0, < 3.3.17>= 3.4.0, < 3.4.11>= 4.0.0, < 4.0.11
Debian LinuxOperating system
= 8.0CVSS 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.0/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.
-
Check Symfony framework versionLocate the Symfony version file (e.g., vendor/symfony/version) or check composer.json/composer.lock for symfony/symfony versionAffected if Installed version falls within 2.7.0 to 2.7.47, 2.8.0 to 2.8.40, 3.3.0 to 3.3.16, 3.4.0 to 3.4.10, or 4.0.0 to 4.0.10
-
Verify security.http_utils container configurationInspect the dependency injection container configuration (e.g., container XML/YAML files in app/config or config/packages) for security.http_utils service definition and confirm whether it is inlined (e.g., defined inline rather than as a service reference)Affected if security.http_utils is defined inline within the container configuration and the application uses security handlers performing redirects
-
Review security authentication handlersExamine security configuration (security.yml or security.yaml) for authentication success handlers, specifically any handler that performs redirection logic using the http_utils serviceAffected if Application configures authentication handlers that redirect users and rely on security.http_utils for URL generation without additional validation
-
Check for unvalidated redirect targetsSearch application code for security handler implementations that call http_utils->redirect() or similar methods without validating the target URL (e.g., no scheme check, no allowlist validation)Affected if Code exists that uses security.http_utils for redirection without validating that the target URL is internal or matches expected patterns
A system is affected if it runs a vulnerable Symfony version (2.7.x before 2.7.48, 2.8.x before 2.8.41, 3.3.x before 3.3.17, 3.4.x before 3.4.11, or 4.0.x before 4.0.11) AND uses the security component with security.http_utils inlined in the container, allowing authentication handlers to perform unvalidated redirects to external sites.
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.
From vendor data2.7.482.8.413.3.17
Update Symfony to version 2.7.48, 2.8.41, 3.3.17, 3.4.11, 4.0.11 or later. Verify that security.http_utils handling does not allow unvalidated redirect targets in affected applications.
Fix this in Symfony
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-11408 — 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-2018-11408 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