CVE Intelligence
Skip to main content
MEDIUM

CVE-2021-27853

CVE-2021-27853 — L2 network filtering can be bypassed using stacked VLAN0 and LLC/SNAP headers

Layer 2 network filtering capabilities such as IPv6 RA guard or ARP inspection can be bypassed using combinations of VLAN 0 headers and LLC/SNAP headers.

Published Updated Sources: cvelistV5, certcc

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

1%

chance of exploitation in 30 days

Affects

ieee

3 products listed

CVSS base

4.7

MEDIUM

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

None

none · proof-of-concept · active

Automatable

No

can an attacker script all four kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (2)

Products (3)

802 2draft ietf v6ops ra guardp802 1q

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
4.7CVSS 3.1MEDIUMcvelistV5

Weakness & attack patterns

  • CWE-290

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

  • T1134Access Token Manipulation
  • T1528Steal Application Access Token
  • T1539Steal Web Session Cookie

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

  • Search application, proxy, and WAF logs for requests touching /SNAP.

References

7 on the record

Elsewhere on this site

  • ieeeevery CVE for this vendor
  • ietfevery CVE for this vendor
  • CWE-290other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.