# CVE-2017-12074: Path traversal in Synology DNS Server

> Authenticated attackers can write arbitrary files via directory traversal in Synology DNS Server, potentially compromising system integrity.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Aug 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-mqph-37g3-x4m7

## What is CVE-2017-12074?

CVE-2017-12074 is a medium-severity path traversal vulnerability in Synology DNS Server, published on 24 Aug 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Directory traversal vulnerability in the SYNO.DNSServer.Zone.MasterZoneConf in Synology DNS Server before 2.2.1-3042 allows remote authenticated attackers to write arbitrary files via the domain_name parameter.

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

## Which versions are affected by CVE-2017-12074?

It affects 1 product.


Products: Synology Dns Server.

## How do I fix CVE-2017-12074?

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

## Is CVE-2017-12074 being exploited?

There is no known exploitation of CVE-2017-12074 in the wild and no public exploit code.

## Other vulnerabilities in Synology DNS Server

- [CVE-2022-27615](https://insights.sbomify.com/CVE-2022-27615/): Path traversal in DNS Server (high 7.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-12074 and fix it if it is affected.

What it is: CVE-2017-12074 is a medium-severity path traversal vulnerability in Synology DNS Server, published on 24 Aug 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-12074 in the wild and no public exploit code.

Affected product: Synology DNS Server. 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-2017-12074/ (Markdown: https://insights.sbomify.com/CVE-2017-12074/index.md)
```

## Sources

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

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