CVE-2021-47942: Home Assistant Community Store 1.10.0 Path Traversal Account Takeover
Home Assistant Community Store (HACS) 1.10.0 contains a path traversal vulnerability that allows unauthenticated attackers to read sensitive files by traversing directories via the /hacsfiles/ endpoint. Attackers can retrieve the .storage/auth file containing user credentials and refresh tokens, then craft valid JWT tokens to gain administrative access to Home Assistant instances.
Security readout for executives and security teams
Plain-English summary
HACS 1.10.0 for Home Assistant is reported to let unauthenticated attackers read sensitive files through path traversal. The described impact is account takeover because authentication storage may expose credentials and refresh tokens. This matters most for internet-reachable Home Assistant deployments.
Executive priority
Prioritize exposed Home Assistant instances because the reported outcome is administrative account takeover without authentication. Internal-only deployments still need assessment, but internet-facing systems should be reviewed and contained first.
Technical view
The issue is CWE-22 path traversal in the /hacsfiles/ endpoint. Sources state unauthenticated network attackers can read sensitive files, including Home Assistant authentication storage, and use recovered token material to gain administrative access. CVSS v4.0 is 8.7 high.
Likely exposure
Exposure is most likely where Home Assistant with HACS 1.10.0 is reachable from untrusted networks. The source bundle does not prove all HACS versions are affected, and the affected-version metadata appears inconsistent, so verify deployed versions directly.
Exploitation context
A public ExploitDB reference exists, but the CVE is not listed as KEV in the provided bundle. Treat exploit availability as public proof-of-concept risk, not confirmed active exploitation.
Researcher notes
The CVE description and VulnCheck advisory identify HACS 1.10.0 and path traversal leading to sensitive file disclosure. The provided affected field lists version "0", which conflicts with the title and description. Evidence does not establish active exploitation.
Mitigation direction
Inventory Home Assistant deployments using HACS and identify any HACS 1.10.0 installations.
Check HACS and Home Assistant vendor guidance for supported upgrade or removal instructions.
Restrict Home Assistant and HACS access from untrusted networks where possible.
Rotate Home Assistant credentials and tokens if sensitive file exposure is suspected.
Review logs for unusual /hacsfiles/ access or path traversal patterns.
Validation and detection
Confirm whether HACS is installed and record the exact installed version.
Determine whether Home Assistant is internet-facing or accessible from untrusted networks.
Check whether the /hacsfiles/ route is reachable without authentication from untrusted zones.
Review Home Assistant logs for suspicious requests targeting sensitive files.
Validate that credentials and refresh tokens were rotated after any suspected exposure.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-22 · source CWE mapping
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.