dbcve.org
Rv132w FirmwareOperating system · Cisco

CVE-2021-1308

HIGH · 7.4 CVSS v3.1 Published 2021-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
79/100
Remediation priority · High
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
Multiple vulnerabilities exist in the Link Layer Discovery Protocol (LLDP) implementation for Cisco Small Business RV Series Routers. An unauthenticated, adjacent attacker could execute arbitrary code or cause an affected router to leak system memory or reload. A memory leak or device reload would cause a denial of service (DoS) condition on an affected device. For more information about these vulnerabilities, see the Details section of this advisory. Note: LLDP is a Layer 2 protocol. To exploit these vulnerabilities, an attacker must be in the same broadcast domain as the affected device (Layer 2 adjacent).

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

Multiple vulnerabilities exist in the LLDP implementation of Cisco Small Business RV Series Routers. An unauthenticated, Layer 2-adjacent attacker can exploit these flaws to execute arbitrary code, leak system memory, or cause device reload, resulting in denial of service.

MitigationApply Cisco firmware updates for RV Series Routers when available; if no patch exists, consider disabling LLDP on untrusted network segments or implementing network segmentation to limit exposure to adjacent attackers.

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
Rv132w FirmwareOperating system
Affected:= 1.0.0.14= 1.0.1.14= 1.0.1.20
Rv134w FirmwareOperating system
Affected:= 1.0.0.14= 1.0.1.14= 1.0.1.20
Rv160 FirmwareOperating system
Affected:= 1.0.0.14= 1.0.1.14= 1.0.1.20
Rv160w FirmwareOperating system
Affected:= 1.0.0.14= 1.0.1.14= 1.0.1.20
Rv260 FirmwareOperating system
Affected:= 1.0.0.14= 1.0.1.14= 1.0.1.20
Rv260p FirmwareOperating system
Affected:= 1.0.0.14= 1.0.1.14= 1.0.1.20
Rv260w FirmwareOperating system
Affected:= 1.0.0.14= 1.0.1.14= 1.0.1.20
Rv340 FirmwareOperating system
Affected:= 1.0.0.14= 1.0.1.14= 1.0.1.20

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/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 the router model
    Access the router administration web interface or CLI and locate the device model information, typically found in the Dashboard, Status, or System Summary page
    Affected if The device model is one of: RV132w, RV134w, RV160, RV160w, RV260, RV260p, RV260w, or RV340
  2. Check the installed firmware version
    In the router web interface, navigate to Administration, Firmware Upgrade, or System Summary to view the current firmware version. Alternatively, use the CLI command 'show version' if SSH/Telnet access is available
    Affected if The firmware version is exactly 1.0.0.14, 1.0.1.14, or 1.0.1.20
  3. Verify if LLDP is enabled
    In the router web interface, go to Layer 2 or Network Settings and locate the LLDP (Link Layer Discovery Protocol) configuration section. Check whether LLDP is enabled or disabled
    Affected if LLDP is currently enabled on the device

The device is affected if it is an RV Series router (RV132w, RV134w, RV160, RV160w, RV260, RV260p, RV260w, or RV340) running firmware version 1.0.0.14, 1.0.1.14, or 1.0.1.20, and LLDP is enabled on the network interface.

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

Apply Cisco firmware updates for RV Series Routers when available; if no patch exists, consider disabling LLDP on untrusted network segments or implementing network segmentation to limit exposure to adjacent attackers.

Fix this in Rv132w Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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