# CVE-2017-13709: Path traversal in n/a

> Attackers can overwrite arbitrary files via crafted resources in the FlightGear simulator's logger subsystem, potentially compromising system integrity.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Aug 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-13709, GHSA-v6cf-m8q2-vx93, MGASA-2017-0362, UBUNTU-CVE-2017-13709

## What is CVE-2017-13709?

CVE-2017-13709 is a high-severity path traversal vulnerability in n/a, published on 27 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In FlightGear before version 2017.3.1, Main/logger.cxx in the FGLogger subsystem allows one to overwrite any file via a resource that affects the contents of the global Property Tree.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Flightgear Flightgear.

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

Upgrade to a fixed version.

## Is CVE-2017-13709 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-2090](https://insights.sbomify.com/CVE-2012-2090/): Other in n/a (critical 9.3)
- [CVE-2012-2091](https://insights.sbomify.com/CVE-2012-2091/): Memory corruption in n/a (critical 9.3)
- [CVE-2017-8921](https://insights.sbomify.com/CVE-2017-8921/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-13709 is a high-severity path traversal vulnerability in n/a, published on 27 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-13709 in the wild and no public exploit code.

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

## Sources

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

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