Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2020-24660

Authentication Bypass in lemonldap-ng-handler (CVE-2020-24660)

Summary

Authentication bypass in lemonldap-ng-handler (CVE-2020-24660). Confidential information can be exposed externally. Mitigation: upgrade to 0.5.2 or later.

Original description

The description as published by the source.

Impact

When access rules are used inside a protected host, some URL encodings may bypass filtering system.

Patches

Version 0.5.2 includes a patch that fixes the vulnerability

Workarounds

No way for users to fix or remediate the vulnerability without upgrading

References

https://gitlab.ow2.org/lemonldap-ng/lemonldap-ng/-/issues/2290

For more information

If you have any questions or comments about this advisory:

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2020-24660 has been found in lemonldap-ng-handler.
Confidential information can be exposed externally.
What to do: upgrade lemonldap-ng-handler to 0.5.2 or later.
If unsure, ask your IT team or search "lemonldap-ng-handler CVE-2020-24660" on the vendor's site.

CVE-2020-24660 (lemonldap-ng-handler) — CWE-287
Attack vector: remote (network-reachable) / no user interaction
Patched: 0.5.2 — apply immediately
Workaround: No way for users to fix or remediate the vulnerability without upgrading
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Authentication bypass (CWE-287) exists in lemonldap-ng-handler.

📍 Affected scope

Check the vendor advisory for the affected versions of lemonldap-ng-handler.

🔥 Severity

Severity: ?. Confidential information can be exposed externally.

🔧 How to fix

Update to 0.5.2.

🛡️ Workaround

Workaround: No way for users to fix or remediate the vulnerability without upgrading

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'lemonldap-ng-handler' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'lemonldap-ng-handler' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で lemonldap-ng-handler を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate 
    No way for users to fix or remediate the vulnerability without upgrading

    パッチが適用されるまでの応急処置として、No way for users to fix or remediate the vulnerability without upgrading を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade lemonldap-ng-handler to 0.5.2

    ステージング環境で 0.5.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm lemonldap-ng-handler
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.5.2"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details