dbcve.org
1763 L16awa Series AApplication · Rockwellautomation

CVE-2016-9334

HIGH · 7.3 CVSS v3.0 Published 2017-02-13
Fix available
A fix is available. Upgrade to after 14.000 or later.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An issue was discovered in Rockwell Automation Allen-Bradley MicroLogix 1100 controller 1763-L16AWA, Series A and B, Version 14.000 and prior versions; 1763-L16BBB, Series A and B, Version 14.000 and prior versions; 1763-L16BWA, Series A and B, Version 14.000 and prior versions; and 1763-L16DWD, Series A and B, Version 14.000 and prior versions. User credentials are sent to the web server in clear text, which may allow an attacker to discover the credentials if they are able to observe traffic between the web browser and the server.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Allen-Bradley MicroLogix 1100 PLC controllers (versions 14.000 and prior) transmit web interface credentials in cleartext over HTTP, enabling network eavesdropping attackers to capture valid user credentials by observing unencrypted browser-to-server traffic.

MitigationEnable TLS/HTTPS on the web server configuration, or implement network segmentation and traffic monitoring to protect credentials in transit; if encryption is unsupported by the controller firmware, consider network isolation or alternative authentication methods.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
1763 L16awa Series AApplication
Affected:<= 14.000
1763 L16awa Series BApplication
Affected:<= 14.000
1763 L16bbb Series AApplication
Affected:<= 14.000
1763 L16bbb Series BApplication
Affected:<= 14.000
1763 L16bwa Series AApplication
Affected:<= 14.000
1763 L16bwa Series BApplication
Affected:<= 14.000
1763 L16dwd Series AApplication
Affected:<= 14.000
1763 L16dwd Series BApplication
Affected:<= 14.000

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Locate the Allen-Bradley MicroLogix 1100 controller on the network or physically inspect the unit label. Confirm the model number matches one of the affected variants: 1763 L16awa, 1763 L16bbb, 1763 L16bwa, or 1763 L16dwd (Series A or Series B).
    Affected if The device model is any of the eight affected product numbers listed in the affected products range.
  2. Check firmware version
    Access the device web interface or use RSLinx Classic software to query the device firmware version. Navigate to the controller properties or system information section to retrieve the firmware revision number.
    Affected if The installed firmware version is 14.000 or any earlier version.
  3. Verify web server configuration
    Log into the device web interface and navigate to the web server settings or network configuration page. Check whether HTTP (port 80) is enabled and whether HTTPS/TLS (port 443) is available or enabled for the web interface.
    Affected if HTTP is enabled and HTTPS is disabled or unavailable on the controller.
  4. Inspect network traffic
    Use a network packet capture tool (such as Wireshark or tcpdump) on the same network segment as the PLC. Log into the web interface and observe the HTTP traffic between the browser and the controller. Verify if the login credentials are transmitted as plaintext rather than encrypted.
    Affected if Login credentials are observable in cleartext within captured HTTP packets.

The device is affected if it is an Allen-Bradley MicroLogix 1100 variant with firmware version 14.000 or lower, and the web interface is accessible via unencrypted HTTP with HTTPS either disabled or unavailable.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 14.000
Interim mitigation

Enable TLS/HTTPS on the web server configuration, or implement network segmentation and traffic monitoring to protect credentials in transit; if encryption is unsupported by the controller firmware, consider network isolation or alternative authentication methods.

Fix this in 1763 L16awa Series A Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-9334 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-9334 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data