Information Disclosure in weblate (CVE-2017-5537)
Summary
Vulnerability in weblate (CVE-2017-5537). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to abe0d2a29a1d8e896bfe829c8461bf8b391f1079, 2.10.1 or later.
Original description
The description as published by the source.
The password reset form in Weblate before 2.10.1 provides different error messages depending on whether the email address is associated with an account, which allows remote attackers to enumerate user accounts via a series of requests.
Source: NIST National Vulnerability Database NVD GitHub Advisory
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-2017-5537 has been found in weblate.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade weblate to abe0d2a29a1d8e896bfe829c8461bf8b391f1079, 2.10.1 or later.
If unsure, ask your IT team or search "weblate CVE-2017-5537" on the vendor's site.
CVE-2017-5537 (weblate) — CWE-200 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: abe0d2a29a1d8e896bfe829c8461bf8b391f1079, 2.10.1 — 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.
Information disclosure (CWE-200) exists in weblate.
Check the vendor advisory for the affected versions of weblate.
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.
Update to abe0d2a29a1d8e896bfe829c8461bf8b391f1079, 2.10.1.
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 'weblate' . 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 'weblate' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
weblateを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade weblate to abe0d2a29a1d8e896bfe829c8461bf8b391f1079, 2.10.1ステージング環境で abe0d2a29a1d8e896bfe829c8461bf8b391f1079, 2.10.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory securityfocus.com
- advisory github.com
- patch openwall.com
- patch openwall.com
- patch github.com
- patch github.com
- patch github.com