LiveActive security incident?Get immediate response
CVE Record

CVE-2021-27861: L2 network filtering bypass using stacked VLAN0 and LLC/SNAP headers with invalid lengths

Layer 2 network filtering capabilities such as IPv6 RA guard can be bypassed using LLC/SNAP headers with invalid length (and optionally VLAN0 headers)

MediumCVSS 4.7Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Traffic from the same local network can be shaped so Layer 2 filters, including IPv6 Router Advertisement Guard, may fail to recognize it. The business risk is integrity impact: a LAN-adjacent attacker could influence network control behavior. This is not described as an internet-remote vulnerability.

Executive priority

Prioritize review for shared LANs, guest networks, campus access layers, and virtualized networks where untrusted devices coexist. The score is medium, but the issue can undermine network policy assumptions in exposed local segments.

Technical view

CVE-2021-27861 is a Layer 2 filtering bypass using LLC/SNAP headers with invalid length fields, optionally combined with VLAN 0 headers. The CVSS vector is AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N. The sources identify affected standards and drafts, not named vendor device models.

Likely exposure

Exposure is most likely on networks relying on RA Guard or similar Layer 2 filtering, especially where untrusted users share a broadcast domain. Actual exposure depends on switch, router, virtual switch, or security-device implementation details not fully listed in the source bundle.

Exploitation context

The provided sources do not show CISA KEV listing or confirmed active exploitation. The required position is adjacent network access, with no privileges or user interaction. Public research exists, so defenders should treat it as a practical LAN-segment bypass risk.

Researcher notes

Evidence centers on standards-level behavior and CERT/public research, not a comprehensive vendor matrix. Track implementation-specific advisories before declaring systems affected or remediated. Do not infer product exposure solely from support for VLANs, LLC/SNAP, or RA Guard.

Mitigation direction

  • Check vendor advisories for affected network devices and filtering implementations.
  • Apply relevant firmware, software, or configuration updates from vendors.
  • Avoid relying on RA Guard as the only protection on untrusted LANs.
  • Restrict untrusted hosts to segmented networks where feasible.
  • Monitor for unexpected IPv6 router advertisements or routing changes.

Validation and detection

  • Inventory segments that depend on RA Guard or Layer 2 filtering.
  • Map switches, routers, virtual switches, and security appliances on those segments.
  • Confirm vendor status for LLC/SNAP and VLAN 0 filtering behavior.
  • Review logs for unexpected IPv6 RA or neighbor-discovery activity.
  • Perform controlled validation only with approved defensive test procedures.
Prepared
Confidence
medium
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-130: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-290: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-27861 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.7 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
7Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.7CVSS 3.1MediumCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.7Medium
CVSS 3.1 vector shape for CVE-2021-27861Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
IEEE802.2802.2h-1997Listed
IETFdraft-ietf-v6ops-ra-guard08Listed
IETFP802.1QD1.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-130 · source CWE mapping

Improper Handling of Length Parameter Inconsistency

Improper Handling of Length Parameter Inconsistency represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

CWE-290 · source CWE mapping

Authentication Bypass by Spoofing

Authentication Bypass by Spoofing represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.