# CVE-2024-36814: Adguard Home arbitrary file read vulnerability

> Authenticated attackers can read arbitrary files as root on the underlying OS via a crafted file in a readable directory.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Oct 2024
- **Updated:** 9 Oct 2024
- **Also known as:** GHSA-9cp9-8gw2-8v7m, GO-2024-3184

## What is CVE-2024-36814?

CVE-2024-36814 is a medium-severity path traversal vulnerability in n/a, published on 8 Oct 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An arbitrary file read vulnerability in Adguard Home before v0.107.52 allows authenticated attackers to access arbitrary files as root on the underlying Operating System via placing a crafted file into a readable directory.

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

## Which versions are affected by CVE-2024-36814?

3 open source packages ship an affected version, including github.com/AdguardTeam/AdGuardHome.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/AdguardTeam/AdGuardHome` | Go | All versions | 0.107.53 |
| `github.com/AdguardTeam/AdGuardHome` | Go | All versions | 0.107.53 |
| `github.com/AdguardTeam/AdGuardHome` | Go | All versions | 0.107.53 |

## How do I fix CVE-2024-36814?

Upgrade github.com/AdguardTeam/AdGuardHome to 0.107.53 or later.

## Is CVE-2024-36814 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-36814 and fix it if it is affected.

What it is: CVE-2024-36814 is a medium-severity path traversal vulnerability in n/a, published on 8 Oct 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-36814 exists.

Affected packages and fixed versions:
- github.com/AdguardTeam/AdGuardHome (Go): affected all versions; fixed in 0.107.53
- github.com/AdguardTeam/AdGuardHome (Go): affected all versions; fixed in 0.107.53
- github.com/AdguardTeam/AdGuardHome (Go): affected all versions; fixed in 0.107.53

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-2024-36814/ (Markdown: https://insights.sbomify.com/CVE-2024-36814/index.md)
```

## Sources

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

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