CVE-2017-9947
A public proof of concept exists; no exploitation attested.
- Published2017-10-23
- Fixed in3.5
- WeaknessCWE-22 · CWE-538
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
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.
Timeline
dates in UTC- 2017-10-2308:29CVE publishedNVD
- 2026-10-2319:23First public proof of conceptPoC-in-GitHub
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2017-9947?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2017-9947?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 3.5 | < 3.5 | 3.5 | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 3.5 | < 3.5 | 3.5 | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 3.5 | < 3.5 | 3.5 | NVD |
1 more product in the sources.
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Vendor advisories
Siemens BACnet Field Panels (Update A)
APOGEE PXC Compact (BACnet) · APOGEE PXC Compact (P2 Ethernet) · APOGEE PXC Modular (BACnet) · +3 more
Fix
- Update Siemens apogee pxc firmware to 3.5
- Vendor fix CISA ICSA-17-285-05 · 4 productsUpdate to V3.5 or later version
- Mitigation from the vendor CISA ICSA-17-285-05 · 2 productsDisable the integrated webserver
- Mitigation from the vendor CISA ICSA-17-285-05 · 6 productsSiemens recommends to disable the integrated webserver when not in use
- Mitigation from the vendor CISA ICSA-17-285-05 · 6 productsPlease contact your local Siemens office for additional support
- No fix planned, says the vendor CISA ICSA-17-285-05 · 2 productsCurrently no fix is planned
Advisories and patches
- cert-portal.siemens.comVendor Advisory
- www.siemens.comVendor Advisory
Detection
read 2026-10-23 19:23 UTC- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
Sources
- CISA-ADPSSVC decisionpoc2026-06-02
- OpenCVESSVC decisionpoc—
- CISA-ADPCVSS 3.15.32026-06-02
- NVDCVSS 3.15.3read 2026-10-23
- NVDCVSS 2.05read 2026-10-23
- CNAweakness (CWE)CWE-538read 2026-10-23
- NVDweakness (CWE)CWE-22read 2026-10-23
- FIRST EPSSEPSS score8.3 %2026-10-22
- PoC-in-GitHubproof of concept1read 2026-10-23
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- Published
- 2017-10-23
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2017-9947?
Is CVE-2017-9947 actively exploited?
What is the CVSS score for CVE-2017-9947?
Running Siemens APOGEE PXC and TALON TC? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.