LiveActive security incident?Get immediate response
CVE Record

CVE-2024-6858: In Arista’s EOS when in 802.1X mode, multi-auth unauthenticated hosts might be allowed access to a switch port if there exists an EAPOL capable device in the fallback VLAN.

In Arista’s EOS when in 802.1X mode, multi-auth unauthenticated hosts might be allowed access to a switch port if there exists an EAPOL capable device in the fallback VLAN.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

Certain Arista EOS switch configurations may let unauthenticated devices gain port access when 802.1X multi-auth is used and an EAPOL-capable device exists in the fallback VLAN. The business risk is unauthorized network access at affected switch ports, but public severity, CVSS, patch, and exploitation evidence are incomplete in the supplied sources.

Executive priority

Prioritize asset identification and vendor-guidance review for network access switches. Escalate faster where affected Arista switches protect sensitive office, datacenter, or production network segments, because the issue concerns unauthorized physical or local network access.

Technical view

CVE-2024-6858 affects Arista EOS 4.31.0, 4.30.0, 4.29.0, and 4.28.10 in 802.1X mode with multi-auth. The failure condition involves unauthenticated hosts being allowed switch-port access when an EAPOL-capable device is present in the fallback VLAN. The CVE maps to CWE-1287.

Likely exposure

Exposure appears limited to Arista EOS deployments on the listed versions that use 802.1X multi-auth with fallback VLAN behavior. Environments without these versions or without this access-control configuration are not indicated as affected by the supplied bundle.

Exploitation context

The source bundle does not show CISA KEV listing, active exploitation, public exploit details, or confirmed weaponization. Treat this as a configuration-dependent network access-control bypass until Arista guidance clarifies severity and remediation.

Researcher notes

Evidence is sparse: no CVSS vector, no vendor mitigation details in the provided bundle, and no KEV signal. Research should focus on reproducing the stated 802.1X multi-auth and fallback VLAN condition in an authorized lab, without assuming broader EOS exposure.

Mitigation direction

  • Review Arista advisory 0103 for official fixed releases and configuration guidance.
  • Inventory EOS 4.31.0, 4.30.0, 4.29.0, and 4.28.10 switches.
  • Prioritize devices using 802.1X multi-auth and fallback VLANs.
  • Limit fallback VLAN privileges until vendor guidance is applied.
  • Monitor switch authentication and port access events for anomalies.

Validation and detection

  • Confirm EOS versions on access-layer switches.
  • Identify ports using 802.1X multi-auth mode.
  • Check whether fallback VLANs contain EAPOL-capable devices.
  • Review authentication logs for unauthenticated host access on affected ports.
  • Track remediation status against Arista advisory 0103.
Prepared
Confidence
medium
Sources
3

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-1287: 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-2024-6858 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
3Timeline events
0ADP providers
2Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Arista NetworksEOS4.31.0, 4.30.0, 4.29.0, 4.28.10unaffected
Weakness

CWE details

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

CWE-1287 · source CWE mapping

Improper Validation of Specified Type of Input

Improper Validation of Specified Type of Input represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.