dbcve.org
iOSOperating system · Cisco

CVE-2016-1333

MEDIUM · 6.5 CVSS v3.0 Published 2016-02-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
Cisco IOS 15.5(3)M and 15.6(1)T0a on Cisco 1000 Connected Grid routers allows remote authenticated users to cause a denial of service (device reload) via an SNMP request for unspecified BRIDGE MIB OIDs, aka Bug ID CSCux89878.

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 · moderate confidence

This vulnerability in Cisco IOS 15.5(3)M and 15.6(1)T0a on Cisco 1000 Connected Grid routers allows remote authenticated attackers to cause device reload via crafted SNMP requests targeting unspecified BRIDGE MIB OIDs. The attack exploits improper input validation in the SNMP subsystem, leading to a denial of service condition.

MitigationDisable SNMP if not required, or restrict SNMP access using ACLs to trusted management hosts and implement SNMPv3 with authentication/encryption. Apply the vendor patch when available from Cisco.

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
iOSOperating system
Affected:= 15.5\(3\)m= 15.6\(1\)t0a

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

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
    Use 'show version' command or check device inventory to confirm the hardware is a Cisco 1000 Series Connected Grid Router (CGR1000)
    Affected if Device is not a Cisco 1000 Connected Grid router - vulnerability does not apply
  2. Check IOS version
    Execute 'show version' and locate the IOS software version string in the output. Compare the full version number against 15.5(3)M or 15.6(1)T0a
    Affected if IOS version is exactly 15.5(3)M or 15.6(1)T0a - these are the only affected versions listed
  3. Verify SNMP is enabled
    Run 'show snmp' or 'show snmp group' to check if the SNMP server is running and configured
    Affected if SNMP is disabled or not configured - the vulnerability cannot be exploited without SNMP access
  4. Check SNMP community and access controls
    Use 'show running-config | include snmp-server' to view SNMP community strings and access list bindings
    Affected if SNMP is exposed to untrusted networks - the flaw is exploitable via crafted BRIDGE MIB OID requests over SNMP

The environment is affected only if the device is a Cisco 1000 Connected Grid Router running IOS version 15.5(3)M or 15.6(1)T0a with SNMP enabled and accessible to the attacker.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable SNMP if not required, or restrict SNMP access using ACLs to trusted management hosts and implement SNMPv3 with authentication/encryption. Apply the vendor patch when available from Cisco.

Fix this in iOS Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-1333 — 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-1333 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