Ldap \/ Sso AuthenticationTYPO3 extension · Ldap \/ Sso Authentication Project
CVE-2015-1401
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 · uneditedImproper Authentication vulnerability in the "LDAP / SSO Authentication" (ig_ldap_sso_auth) extension 2.0.0 for TYPO3.
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 confidenceImproper authentication vulnerability in the LDAP/SSO Authentication extension (ig_ldap_sso_auth) version 2.0.0 for TYPO3 allows attackers to bypass authentication mechanisms, potentially gaining unauthorized access to the CMS by exploiting flaws in how the extension validates LDAP/SSO credentials.
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
Ldap \/ Sso AuthenticationTYPO3 extension
= 2.0.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Verify ig_ldap_sso_auth extension is installedCheck your TYPO3 extension manager or list of installed extensions for 'ig_ldap_sso_auth' or 'LDAP/SSO Authentication'Affected if The extension is present in the TYPO3 installation
-
Confirm the installed version is 2.0.0View the extension version in the TYPO3 extension manager or check the extension's composer.json/ext_emconf.php for version 2.0.0Affected if The installed version is exactly 2.0.0
-
Check if LDAP or SSO authentication is enabledInspect the extension configuration in TYPO3 admin panel or check LocalConfiguration.php for 'ig_ldap_sso_auth' settings where enableLDAP or enableSSO is set to trueAffected if LDAP or SSO authentication is actively enabled in the extension settings
-
Review authentication method configurationExamine the authentication services configuration file for the extension to verify the extension is handling authentication workflowsAffected if The extension is configured as an active authentication provider
You are affected if the ig_ldap_sso_auth extension version 2.0.0 is installed with LDAP or SSO authentication enabled in your TYPO3 environment.
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 dataUpdate the ig_ldap_sso_auth extension to a patched version if available, or disable the extension until a fix is released; review authentication logs for suspicious access attempts.
Fix this in Ldap \/ Sso Authentication
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.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 $4,416.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-1401 — 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-2015-1401 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