SymfonyFramework / library · Sensiolabs
CVE-2018-11385
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 · uneditedAn issue was discovered in the Security component in Symfony 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. A session fixation vulnerability within the "Guard" login feature may allow an attacker to impersonate a victim towards the web application if the session id value was previously known to the attacker.
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 confidenceSession fixation vulnerability in Symfony's Guard authentication component allows an attacker who knows a victim's session ID to impersonate that victim after successful login, because the session ID is not regenerated upon authentication as it should be in secure implementations.
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.0= 9.0
FedoraOperating system
= 28CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Determine Symfony framework versionInspect the composer.json file in your project root for the symfony/symfony or symfony/framework-bundle version entry under "require", or check the vendor/symfony/symfony/CHANGELOG.md file for the installed versionAffected if The 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 Guard authentication is in useInspect your security configuration file (config/packages/security.yaml or app/config/security.yml) and look for a "guard" key under any firewall definitionAffected if A firewall entry contains a "guard" key with authenticator definitions, indicating the Guard component is enabled
-
Confirm session regeneration is not configuredIn the same security configuration file, check whether the firewall using Guard has "session_fixation_strategy: none" explicitly set, or lacks any session fixation protectionAffected if The Guard-protected firewall either has "session_fixation_strategy: none" or has no session fixation strategy configured at all
Your environment is affected if you are running a Symfony version within the affected ranges AND you are using the Guard authentication component without proper session fixation protection configured.
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
Upgrade Symfony to version 2.7.48, 2.8.41, 3.3.17, 3.4.11, 4.0.11 or later to receive the patch that implements proper session regeneration on login.
Fix this in Symfony
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-11385 — 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-11385 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