CVE-2017-16923
No exploitation reported by the sources we read.
- Published2017-11-21
- WeaknessCWE-78
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
Command Injection vulnerability in app_data_center on Shenzhen Tenda Ac9 US_AC9V1.0BR_V15.03.05.14_multi_TD01, Ac9 ac9_kf_V15.03.05.19(6318_)_cn, Ac15 US_AC15V1.0BR_V15.03.05.18_multi_TD01, Ac15 US_AC15V1.0BR_V15.03.05.19_multi_TD01, Ac18 US_AC18V1.0BR_V15.03.05.05_multi_TD01, and Ac18 ac18_kf_V15.03.05.19(6318_)_cn devices allows remote unauthenticated attackers to execute arbitrary OS commands via a crafted cgi-bin/luci/usbeject?dev_name= GET request from the LAN. This occurs because the "sub_A6E8 usbeject_process_entry" function executes a system function with untrusted input.
Timeline
dates in UTC- 2017-11-2114:29CVE publishedNVD
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-16923?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2017-16923?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 |
|---|---|---|---|
| — | = us_ac15v1.0br_v15.03.05.18_multi_td01 | no fix published | NVD |
| — | = us_ac15v1.0br_v15.03.05.19_multi_td01 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| — | = us_ac18v1.0br_v15.03.05.05_multi_td01 | no fix published | NVD |
| — | = ac18_kf_v15.03.05.19\(6318_\)_cn | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| — | = us_ac9v1.0br_v15.03.05.14_multi_td01 | no fix published | NVD |
| — | = ac9_kf_v15.03.05.19\(6318_\)_cn | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
No fix published by the sources we read yet. NVD record
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
- NVDCVSS 3.08.8read 2026-10-23
- NVDCVSS 2.08.3read 2026-10-23
- NVDweakness (CWE)CWE-78read 2026-10-23
- FIRST EPSSEPSS score2.6 %2026-10-22
Technical details
- CVSS v3 Vector
- CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Published
- 2017-11-21
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2017-16923?
Is CVE-2017-16923 actively exploited?
What is the CVSS score for CVE-2017-16923?
Hear about the next vulnerability in your software
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.