Authentication Bypass in alerta-server (CVE-2020-26214)
Summary
Authentication bypass in alerta-server (CVE-2020-26214). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 7.5.7 or later.
Original description
The description as published by the source.
In Alerta before version 8.1.0, users may be able to bypass LDAP authentication if they provide an empty password when Alerta server is configure to use LDAP as the authorization provider. Only deployments where LDAP servers are configured to allow unauthenticated authentication mechanism for anonymous authorization are affected. A fix has been implemented in version 8.1.0 that returns HTTP 401 Unauthorized response for any authentication attempts where the password field is empty. As a workaround LDAP administrators can disallow unauthenticated bind requests by clients.
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-26214 has been found in alerta-server.
Successful exploitation can lead to full system takeover.
What to do: upgrade alerta-server to 7.5.7 or later.
If unsure, ask your IT team or search "alerta-server CVE-2020-26214" on the vendor's site.
CVE-2020-26214 (alerta-server) — CWE-287
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 7.5.7 — apply immediately
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.
Authentication bypass (CWE-287) exists in alerta-server.
Check the vendor advisory for the affected versions of alerta-server.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 7.5.7.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'alerta-server' . 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
-
1Identify exposure identify
grep -r 'alerta-server' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
alerta-serverを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade alerta-server to 7.5.7ステージング環境で 7.5.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- advisory github.com
- advisory tools.ietf.org
- advisory pypi.org
- package github.com
- patch github.com
- web github.com
- web pypi.org