# 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 integrations.


- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Jan 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-jxm2-grrm-xcrf

## What is CVE-2021-3152?

CVE-2021-3152 is a medium-severity vulnerability in n/a, published on 21 Jan 2021. 

### Official 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

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2021-3152?

It affects 1 product.


Products: Home-Assistant Home-Assistant.

## How do I fix CVE-2021-3152?

No fix has been published for CVE-2021-3152 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-3152 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-3152 exists.

Public exploit code:

- Home Assistant HACS - Local File Inclusion (nuclei): http/cves/2021/CVE-2021-3152.yaml

## Other vulnerabilities in n/a

- [CVE-2023-27482](https://insights.sbomify.com/CVE-2023-27482/): Auth bypass in core (critical 10.0)
- [CVE-2023-41895](https://insights.sbomify.com/CVE-2023-41895/): Cross-site Scripting via auth_callback login in Home Assistant Core (high 8.8)
- [CVE-2023-41897](https://insights.sbomify.com/CVE-2023-41897/): Lack of XFO header allows clickjacking in Home Assistant Core (high 8.8)
- [CVE-2026-54317](https://insights.sbomify.com/CVE-2026-54317/): Home Assistant: Konnected alarm-panel switch state and zone topology disclosed to unauthenticated actors on the LAN (high 7.6)
- [CVE-2020-36517](https://insights.sbomify.com/CVE-2020-36517/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-3152 and fix it if it is affected.

What it is: CVE-2021-3152 is a medium-severity vulnerability in n/a, published on 21 Jan 2021. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-3152 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-3152/ (Markdown: https://insights.sbomify.com/CVE-2021-3152/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-3152
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-3152
- OSV: https://osv.dev/vulnerability/CVE-2021-3152

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-3152/
Summaries are generated and may contain mistakes; the official description above is the record.