← Back
CVE-2024-27287
Cross-Site Scripting (XSS) in esphome (CVE-2024-27287)
Summary
cross-site scripting in esphome (CVE-2024-27287). Confidential information can be exposed externally. Exploitable via `POST /edit`. Mitigation: upgrade to `2024.2.2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-27287** has been found in esphome.
Attackers can target a specific entry point like `POST /edit` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade esphome to **2024.2.2** or later.
If unsure, ask your IT team or search "esphome CVE-2024-27287" on the vendor's site.
CVE-2024-27287 (esphome) — CWE-79 /
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /edit / GET /edit
Patched: `2024.2.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.
❓ What is the problem
**Cross-site scripting (XSS)** (CWE-79) exists in esphome. Attackers reach the vulnerable code path via `POST /edit` without authentication.
📍 Affected scope
esphome — . Attack surface: POST /edit / GET /edit.
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **2024.2.2**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual `POST /edit` requests with malformed payloads or SQL meta-characters. Run `grep -r 'esphome' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'esphome' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `esphome` を grep し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'POST /edit' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `POST /edit` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade esphome to 2024.2.2ステージング環境で 2024.2.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against POST /edit on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
esphome
[{"type":"ECOSYSTEM","events":[{"introduced":"2023.12.9"},{"fixed":"2024.2.2"}]}]
References
- advisory https://github.com/advisories/GHSA-9p43-hj5j-96h5
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-27287
- package https://github.com/esphome/esphome
- package https://pypi.org/project/esphome
- web https://github.com/esphome/esphome/security/advisories/GHSA-9p43-hj5j-96h5
- web https://github.com/esphome/esphome/commit/37d2b3c7977a4ccbec59726ca7549cb776661455