dbcve.org
SymfonyFramework / library · Sensiolabs

CVE-2018-11407

CRITICAL · 9.8 CVSS v3.0 Published 2018-06-13
Fix available
A fix is available. Upgrade to 2.8.37 / 3.3.17 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
An issue was discovered in the Ldap component in Symfony 2.8.x before 2.8.37, 3.3.x before 3.3.17, 3.4.x before 3.4.7, and 4.0.x before 4.0.7. It allows remote attackers to bypass authentication by logging in with a "null" password and valid username, which triggers an unauthenticated bind. NOTE: this issue exists because of an incomplete fix for CVE-2016-2403.

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 confidence

The Ldap component in Symfony allows authentication bypass via a null/empty password with a valid username, which triggers an unauthenticated LDAP bind. This is an incomplete fix for CVE-2016-2403, where the original patch did not properly handle empty password scenarios.

MitigationUpgrade Symfony to version 2.8.37+, 3.3.17+, 3.4.7+, or 4.0.7+ to obtain the complete fix. Additionally, ensure the LDAP server is configured to reject anonymous binds and empty password authentication attempts.

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
Affected:>= 2.8.0, < 2.8.37>= 3.3.0, < 3.3.17>= 3.4.0, < 3.4.7>= 4.0.0, < 4.0.7

CVSS 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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Symfony version
    Run 'composer show sensiolabs/symfony-bridge' or check the 'version' field in your composer.lock file for the symfony/symfony package
    Affected if The version is 2.8.0-2.8.36, 3.3.0-3.3.16, 3.4.0-3.4.6, or 4.0.0-4.0.6
  2. Verify LDAP authentication is configured
    Inspect your app's security configuration file (config/packages/security.yaml or app/config/security.yml) for any 'ldap' provider under the 'providers' section
    Affected if An LDAP provider is configured and the version from step 1 falls within the affected ranges
  3. Confirm LDAP bind behavior
    Review your LDAP server configuration to determine whether it accepts empty password binds or anonymous authentication
    Affected if Your LDAP server permits empty password authentication attempts and your Symfony version is within the affected ranges listed above

You are affected if your Symfony version is 2.8.0-2.8.36, 3.3.0-3.3.16, 3.4.0-3.4.6, or 4.0.0-4.0.6 AND you have an LDAP authentication provider configured in your security settings.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2.8.37 / 3.3.17 / 3.4.7 or later
Fixed in 2.8.373.3.173.4.7
Interim mitigation

Upgrade Symfony to version 2.8.37+, 3.3.17+, 3.4.7+, or 4.0.7+ to obtain the complete fix. Additionally, ensure the LDAP server is configured to reject anonymous binds and empty password authentication attempts.

Recommended fix High confidence

Upgrade to 2.8.37, 3.3.17, 3.4.7, or 4.0.7 (depending on your current branch)

  1. 1. Determine the current Symfony version by checking composer.json or running 'composer show symfony/symfony | grep version'
  2. 2. Identify which branch (2.8.x, 3.3.x, 3.4.x, or 4.0.x) is currently in use
  3. 3. Run 'composer require symfony/symfony:"<fixed_version>" --update-with-dependencies' replacing <fixed_version> with the appropriate minimum fixed version: 2.8.37 for 2.8.x, 3.3.17 for 3.3.x, 3.4.7 for 3.4.x, or 4.0.7 for 4.0.x
  4. 4. Test the authentication flow with the Ldap component after the upgrade to confirm the fix works correctly
Caveat Symfony patch releases typically include other bug fixes; review the changelog for your version branch before deploying to production

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Symfony Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-11407 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-11407 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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