Rockwell MicroLogix up to 1766-L32BXBA SNMP Service access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.2 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Rockwell MicroLogix up to 1766-L32BXBA. Affected is an unknown function of the component SNMP Service. This manipulation causes access control. This vulnerability is registered as CVE-2016-5645. Remote exploitation of the attack is possible. No exploit is available. It is suggested to update the configuration settings.
Details
A vulnerability was found in Rockwell MicroLogix up to 1766-L32BXBA. It has been declared as critical. Affected by this vulnerability is some unknown functionality of the component SNMP Service. The manipulation with an unknown input leads to a access control vulnerability. The CWE definition for the vulnerability is CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Rockwell Automation MicroLogix 1400 PLC 1766-L32BWA, 1766-L32AWA, 1766-L32BXB, 1766-L32BWAA, 1766-L32AWAA, and 1766-L32BXBA devices have a hardcoded SNMP community, which makes it easier for remote attackers to load arbitrary firmware updates by leveraging knowledge of this community.
The weakness was published 08/24/2016 by Cisco with Cisco Talos (Website). The advisory is shared at ics-cert.us-cert.gov. This vulnerability is known as CVE-2016-5645 since 06/16/2016. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
It is possible to mitigate the problem by applying the configuration setting .
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 92428†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.2
VulDB Base Score: 7.3
VulDB Temp Score: 7.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.3
NVD Vector: 🔍
ADP CISA Base Score: 7.3
ADP CISA Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Access controlCWE: CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
OpenVAS ID: 802243
OpenVAS Name: Report default community names of the SNMP Agent
OpenVAS File: 🔍
OpenVAS Family: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: ConfigStatus: 🔍
Timeline
06/16/2016 🔍08/11/2016 🔍
08/23/2016 🔍
08/24/2016 🔍
08/24/2016 🔍
06/03/2026 🔍
Sources
Advisory: ics-cert.us-cert.govResearcher: Cisco
Organization: Cisco Talos
Status: Not defined
CVE: CVE-2016-5645 (🔍)
GCVE (CVE): GCVE-0-2016-5645
GCVE (VulDB): GCVE-100-90925
SecurityFocus: 92428 - Rockwell Automation MicroLogix 1400 Products CVE-2016-5645 Remote Privilege Escalation Vulnerability
Entry
Created: 08/24/2016 19:02Updated: 06/03/2026 18:28
Changes: 08/24/2016 19:02 (54), 04/01/2019 21:59 (13), 06/03/2026 18:28 (27)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.