Vulnerability in lemur (CVE-2023-30797)
Summary
Vulnerability in lemur (CVE-2023-30797). Confidential information can be exposed externally. Exploitable via SECRET_KEY. Mitigation: upgrade to 1.3.2 or later.
Original description
The description as published by the source.
Netflix Lemur before version 1.3.2 used insufficiently random values when generating default credentials. The insufficiently random values may allow an attacker to guess the credentials and gain access to resources managed by Lemur.
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-2023-30797 has been found in lemur.
Attackers can target a specific entry point like SECRET_KEY over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: upgrade lemur to 1.3.2 or later.
If unsure, ask your IT team or search "lemur CVE-2023-30797" on the vendor's site.
CVE-2023-30797 (lemur) — CWE-330 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: SECRET_KEY / LEMUR_TOKEN_SECRET / LEMUR_ENCRYPTION_KEYS / OAUTH_STATE_TOKEN_SECRET
Patched: 1.3.2 — 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.
A vulnerability (CWE-330) exists in lemur. Attackers reach the vulnerable code path via SECRET_KEY without authentication.
Check the vendor advisory for the affected versions of lemur. Attack surface: SECRET_KEY / LEMUR_TOKEN_SECRET / LEMUR_ENCRYPTION_KEYS / OAUTH_STATE_TOKEN_SECRET.
Severity: High (CVSS 7.5/10). Confidential information can be exposed externally.
Update to 1.3.2.
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 'lemur' . 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 'lemur' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
lemurを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade lemur to 1.3.2ステージング環境で 1.3.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory vulncheck.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- package pypi.org
- patch github.com
- web github.com
- web github.com