# CVE-2017-9947: Path traversal in APOGEE PXC and TALON TC BACnet Automation Controllers All versions <V3.5

> Remote attackers can exploit directory traversal to read file system structures on Siemens BACnet controllers via the web server.

- **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
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Oct 2017
- **Updated:** 2 Jun 2026
- **Also known as:** GHSA-m28r-jg2j-26cv

## What is CVE-2017-9947?

CVE-2017-9947 is a medium-severity path traversal vulnerability in APOGEE PXC and TALON TC BACnet Automation Controllers All versions <V3.5, published on 23 Oct 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability has been identified in Siemens APOGEE PXC and TALON TC BACnet Automation Controllers in all versions <V3.5. A directory traversal vulnerability could allow a remote attacker with network access to the integrated web server (80/tcp and 443/tcp) to obtain information on the structure of the file system of the affected devices.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), CWE-538 (Insertion of Sensitive Information into Externally-Accessible File or Directory)

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

It affects 4 products.


Products: Siemens Apogee Pxc Firmware, Siemens Apogee Pxc Modular Firmware, Siemens Talon Tc Compact Firmware, Siemens Talon Tc Modular Firmware.

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

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

## Is CVE-2017-9947 being exploited?

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

Public exploit code:

- APOLOGEE is a Python script and Metasploit module that enumerates a hidden directory on Siemens APOGEE PXC BACnet Automation Controllers (all versions prior to V3.5) and TALON TC BACnet Automation Controllers (all versions prior to V3.5). With a 7.5 CVSS, this exploit allows for an attacker to perform an authentication bypass using an alternate path or channel to access hidden directories in the web server.  This repository takes advantage of CVE-2017-9947. (github_poc): https://github.com/RoseSecurity/APOLOGEE

## Other vulnerabilities in APOGEE PXC and TALON TC BACnet Automation Controllers All versions <V3.5

- [CVE-2017-9946](https://insights.sbomify.com/CVE-2017-9946/): Auth bypass in APOGEE PXC and TALON TC BACnet Automation Controllers All versions <V3.5 (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-9947 is a medium-severity path traversal vulnerability in APOGEE PXC and TALON TC BACnet Automation Controllers All versions <V3.5, published on 23 Oct 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-9947 exists.

Affected product: APOGEE PXC and TALON TC BACnet Automation Controllers All versions <V3.5. 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-9947/ (Markdown: https://insights.sbomify.com/CVE-2017-9947/index.md)
```

## Sources

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

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