CVE-2017-9833 is a path traversal (CWE-22) in a /cgi-bin/wapopen program on devices that run the Boa web server: "../.." in the FILECAMERA parameter returns any file, read with root privileges. NVD scores it 7.5. The record is disputed, because Boa itself ships no wapopen program, so the fix belongs to the device vendor.
Vulnerability summary
CVSS base score
7.5
High severity
EPSS score (FIRST)
68.2%
Probability of exploitation in the wild in the next 30 days
CISA KEV catalog
No
Not listed
Published
Vulnerability ID: CVE-2017-9833 · Source: NVD
Affected components
| Component | CPE | Version range |
|---|---|---|
| Boa web server (as named in the CVE record) | cpe:2.3:a:boa:boa:0.94.14.21:*:*:*:*:*:*:* | NVD CPE version 0.94.14.21 (the upstream build is named 0.94.14rc21); disputed: the flaw is in a vendor wapopen CGI program |
| Device firmware with a /cgi-bin/wapopen program | — | any build whose wapopen CGI passes FILECAMERA to a file read without path checks; no vendor advisory names the products |
What does this mean for affected devices?
NVD's description says that /cgi-bin/wapopen in Boa 0.94.14rc21 "allows the injection of" ../.. "using the FILECAMERA variable (sent by GET) to read files with root privileges." It continues: "NOTE: multiple third parties report that this is a system-integrator issue (e.g., a vulnerability on one type of camera) because Boa does not include any wapopen program or any code to read a FILECAMERA variable." NVD's Primary score is CVSS v3.1 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N), with CVSS v2 7.8 and CWE-22. The CPE configuration names boa:boa version 0.94.14.21, a string that does not match the upstream 0.94.14rc21. The record was published on 2017-06-24 (NVD).
Is the flaw in Boa?
No. We downloaded the 0.94.14rc21 and 0.94.13 source tarballs from the Boa home page, the last development and release builds, and neither contains a wapopen program or the string FILECAMERA. The original report, Exploit-DB 42290, shows the request as /cgi-bin/wapopen?...&FILECAMERA=../../etc/shadow%00&... with camera parameters such as NO=CAM_16, which fits the system-integrator reading. Boa runs CGI programs that the device maker adds; the traversal is in that program. Microsoft Threat Intelligence's November 2022 report describes the same pattern: Boa ships inside chip-vendor SDKs, and "additional vendor and device specific vulnerabilities exist across a range of devices including routers."
How do you triage a scanner hit?
A version match on Boa says little here. Unpack the firmware and look for wapopen under the web root's cgi-bin. If it is absent, CVE-2017-9833 does not apply to the image, whatever Boa version it reports. If it is present, test whether FILECAMERA reaches a file open without path checks, and check whether the CGI runs as root, which the report's root-privilege file read implies. Our embedded web server firmware guide covers finding Boa and its CGI directory in an image.
How do you fix it?
Fix the CGI program: resolve the requested path against a fixed directory, reject .. and NUL bytes, and run CGI programs as an unprivileged user. The path traversal fix guide covers the code pattern, and two server-side cases, CVE-2018-18778 in mini_httpd and CVE-2018-19052 in lighttpd, show it in maintained servers. The other disputed Boa record, CVE-2021-33558, is also in vendor files.
An EPSS score in the 99th percentile on a disputed record shows that scanners and exploit kits still probe for this URL. CVE-2017-9833 is not in the CISA KEV catalog as of 2026-11-18 (catalog version 2026.11.17). FIRST EPSS gives it 0.68243, the 99.3rd percentile, in the 2026-11-17 dataset (CISA KEV, FIRST EPSS).
Evidence
- NVD: /cgi-bin/wapopen in Boa 0.94.14rc21, '../..' via FILECAMERA (GET), read files with root privileges; NOTE third parties report a system-integrator issue because Boa has no wapopen program or FILECAMERA code; Primary CVSS v3.1 7.5 C:H, v2 7.8; CWE-22; CPE cpe:2.3:a:boa:boa:0.94.14.21; published 2017-06-24. — NVD
- boa-0.94.14rc21.tar.gz and boa-0.94.13.tar.gz from boa.org contain no file or string 'wapopen' or 'FILECAMERA' (checked 2026-11-18). — Boa project
- Exploit-DB 42290 (2017-06-20, Miguel Mendez Z): PoC /cgi-bin/wapopen?B1=OK&NO=CAM_16&...&FILECAMERA=../../etc/shadow%00&... — Exploit-DB
- Microsoft Threat Intelligence (2022): Boa in IoT devices and SDKs; 'Additional vendor and device specific vulnerabilities exist across a range of devices including routers.' — Microsoft Security blog
- CVE-2017-9833 is not in the CISA KEV catalog, version 2026.11.17 (1,782 entries), checked 2026-11-18. — CISA KEV
- EPSS 0.68243, percentile 0.99342, dataset 2026-11-17. — FIRST EPSS

Related advisories
Sources
Frequently asked questions
Does every device with Boa 0.94.14rc21 have CVE-2017-9833?
No. The flaw is in a /cgi-bin/wapopen program, and NVD notes that Boa includes no wapopen program or FILECAMERA code. The Boa 0.94.14rc21 and 0.94.13 source tarballs contain neither, so only firmware that ships such a CGI is affected (per NVD and the Boa source).
Why does NVD list version 0.94.14.21 for CVE-2017-9833?
NVD's CPE configuration uses the string 0.94.14.21, while the Boa project names the build 0.94.14rc21. A scanner that compares version strings exactly may match one form and not the other (per NVD and the Boa home page).
How do I fix CVE-2017-9833 in my product?
Fix or remove the wapopen CGI program: resolve the FILECAMERA path inside a fixed directory, reject .. and NUL bytes, and stop running CGI programs as root. Updating Boa does not help, because Boa has had no release since 2005 and does not contain the program (per NVD and the Boa home page).
Is CVE-2017-9833 in the CISA KEV catalog?
No, not as of 2026-11-18 (catalog version 2026.11.17). FIRST EPSS gives it 0.68243, the 99.3rd percentile, in the 2026-11-17 dataset (per CISA KEV and FIRST EPSS).
Questions about this page?