# GHSA-p9mp-vq4v-v5m5: eZ Publish Legacy Passwordless login for LDAP users > Attackers can bypass authentication and gain unauthorized access to eZ Publish Legacy installations using specific LDAP or TextFile login handlers. - **Severity:** Not scored - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 15 May 2024 ## What is GHSA-p9mp-vq4v-v5m5? GHSA-p9mp-vq4v-v5m5 is an authentication bypass vulnerability in ezsystems/ezpublish-legacy, published on 15 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description This security advisory fixes a vulnerability in eZ Publish Legacy, and we recommend that you install it as soon as possible if you are using Legacy. Installations that are using the legacy LDAP login handler or the TextFile login handler in combination with the standard legacy login handler, may in rare cases be vulnerable to a failure of the standard login handler to verify passwords correctly, allowing unauthorised access. If your installation has never used the LDAP or TextFile login handlers, or never used legacy login at all, then it is not affected. Still, we recommend installing the update, to be on the safe side. To install, use Composer to update to one of the "Resolving versions" mentioned above, or apply this patch manually: https://github.com/ezsystems/ezpublish-legacy/commit/13f03a2be6c0ee4d0caaafaef05904ea9b0c4d9d ## Which versions are affected by GHSA-p9mp-vq4v-v5m5? 10 open source packages ship an affected version, including ezsystems/ezpublish-legacy. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `ezsystems/ezpublish-legacy` | Packagist | From 2011.0.0 | 2017.12.4.1 | | `ezsystems/ezpublish-legacy` | Packagist | From 2011.0.0 | 2017.12.4.1 | | `ezsystems/ezpublish-legacy` | Packagist | From 2018.6.0 | 2018.6.1.2 | | `ezsystems/ezpublish-legacy` | Packagist | From 2018.6.0 | 2018.6.1.2 | | `ezsystems/ezpublish-legacy` | Packagist | From 2018.9.0 | 2018.9.1.1 | | `ezsystems/ezpublish-legacy` | Packagist | From 2018.9.0 | 2018.9.1.1 | | `ezsystems/ezpublish-legacy` | Packagist | From 5.3.0 | 5.3.12.4 | | `ezsystems/ezpublish-legacy` | Packagist | From 5.3.0 | 5.3.12.4 | | `ezsystems/ezpublish-legacy` | Packagist | From 5.4.0 | 5.4.12.1 | | `ezsystems/ezpublish-legacy` | Packagist | From 5.4.0 | 5.4.12.1 | ## How do I fix GHSA-p9mp-vq4v-v5m5? Upgrade ezsystems/ezpublish-legacy to a fixed version for your release line: 2017.12.4.1, 2018.6.1.2, 2018.9.1.1 or 5.3.12.4. ## Is GHSA-p9mp-vq4v-v5m5 being exploited? There is no known exploitation of GHSA-p9mp-vq4v-v5m5 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for GHSA-p9mp-vq4v-v5m5 and fix it if it is affected. What it is: GHSA-p9mp-vq4v-v5m5 is an authentication bypass vulnerability in ezsystems/ezpublish-legacy, published on 15 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of GHSA-p9mp-vq4v-v5m5 in the wild and no public exploit code. Affected packages and fixed versions: - ezsystems/ezpublish-legacy (Packagist): affected from 2011.0.0; fixed in 2017.12.4.1 - ezsystems/ezpublish-legacy (Packagist): affected from 2011.0.0; fixed in 2017.12.4.1 - ezsystems/ezpublish-legacy (Packagist): affected from 2018.6.0; fixed in 2018.6.1.2 - ezsystems/ezpublish-legacy (Packagist): affected from 2018.6.0; fixed in 2018.6.1.2 - ezsystems/ezpublish-legacy (Packagist): affected from 2018.9.0; fixed in 2018.9.1.1 - ezsystems/ezpublish-legacy (Packagist): affected from 2018.9.0; fixed in 2018.9.1.1 - ezsystems/ezpublish-legacy (Packagist): affected from 5.3.0; fixed in 5.3.12.4 - ezsystems/ezpublish-legacy (Packagist): affected from 5.3.0; fixed in 5.3.12.4 - ezsystems/ezpublish-legacy (Packagist): affected from 5.4.0; fixed in 5.4.12.1 - ezsystems/ezpublish-legacy (Packagist): affected from 5.4.0; fixed in 5.4.12.1 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/GHSA-p9mp-vq4v-v5m5/ (Markdown: https://insights.sbomify.com/GHSA-p9mp-vq4v-v5m5/index.md) ``` ## Sources - OSV: https://osv.dev/vulnerability/GHSA-p9mp-vq4v-v5m5 --- From sbomify Insights: https://insights.sbomify.com/GHSA-p9mp-vq4v-v5m5/ Summaries are generated and may contain mistakes; the official description above is the record.