CVE-2016-9343
No exploitation reported by the sources we read.
- Published2017-02-13
- WeaknessCWE-787
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
An issue was discovered in Rockwell Automation Logix5000 Programmable Automation Controller FRN 16.00 through 21.00 (excluding all firmware versions prior to FRN 16.00, which are not affected). By sending malformed common industrial protocol (CIP) packet, an attacker may be able to overflow a stack-based buffer and execute code on the controller or initiate a nonrecoverable fault resulting in a denial of service.
Timeline
dates in UTC- 2017-02-1321:59CVE publishedNVD
- 2026-10-2319:23EPSS crossed 10 %FIRST EPSS
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2016-9343?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2016-9343?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 |
|---|---|---|---|
| 16.0 | = 16.00 | no fix published | NVD |
| 16.20 | = 16.020 | no fix published | NVD |
| 16.25 | = 16.025 | no fix published | NVD |
| 17.0 | = 17.00 | no fix published | NVD |
| 18.0 | = 18.00 | no fix published | NVD |
| 19.0 | = 19.00 | no fix published | NVD |
| 20.0 | = 20.00 | no fix published | NVD |
| 20.11 | = 20.011 | no fix published | NVD |
| 20.16 | = 20.016 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 16.0 | = 16.00 | no fix published | NVD |
| 16.20 | = 16.020 | no fix published | NVD |
| 16.23 | = 16.023 | no fix published | NVD |
| 17.0 | = 17.00 | no fix published | NVD |
| 18.0 | = 18.00 | no fix published | NVD |
| 19.0 | = 19.00 | no fix published | NVD |
| 20.0 | = 20.00 | no fix published | NVD |
| 20.10 | = 20.010 | no fix published | NVD |
| 20.13 | = 20.013 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 16.0 | = 16.00 | no fix published | NVD |
| 16.20 | = 16.020 | no fix published | NVD |
| 16.22 | = 16.022 | no fix published | NVD |
| 17.0 | = 17.00 | no fix published | NVD |
| 18.0 | = 18.00 | no fix published | NVD |
| 19.0 | = 19.00 | no fix published | NVD |
| 20.0 | = 20.00 | no fix published | NVD |
| 20.10 | = 20.010 | no fix published | NVD |
| 20.13 | = 20.013 | no fix published | NVD |
13 more products in the sources.
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.110read 2026-10-23
- NVDCVSS 2.07.5read 2026-10-23
- NVDweakness (CWE)CWE-787read 2026-10-23
- FIRST EPSSEPSS score10.5 %read 2026-10-23
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
- Published
- 2017-02-13
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2016-9343?
Is CVE-2016-9343 actively exploited?
What is the CVSS score for CVE-2016-9343?
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.