VulnerabilityPublished 27 May 2025

CVE-2024-11185: Arista Networks EOS · CWE-1189

Affects Arista Networks EOSSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 May 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Arista Networks EOS	Affected 4.29.0 – 4.33.0 5 affected builds	Fixed in–

AI-suggested

Organizations should immediately inventory their network devices to identify Arista EOS versions 4.29.0 through 4.33.0 in use. Until patches are available, network administrators should implement strict ingress filtering and VLAN access control lists (ACLs) to enforce segmentation at multiple layers, including physical port security and 802.1X authentication where feasible. Monitoring for anomalous VLAN traffic patterns and employing network segmentation validation tools can help detect exploitation attempts. Segregating critical VLANs on separate physical switches or using private VLANs may reduce exposure. Coordination with Arista Networks for timely patch deployment is essential once fixes are released. Additionally, updating network device configurations to disable unused ports and applying best practices for VLAN tagging and trunk port configuration can minimize risk.

Description

On affected platforms running Arista EOS, ingress traffic on Layer 2 ports may, under certain conditions, be improperly forwarded to ports associated with different VLANs, resulting in a breach of VLAN isolation and segmentation boundaries.

Impact

For European organizations, this vulnerability poses a significant risk to network segmentation and data confidentiality, especially in environments relying on Arista EOS for critical infrastructure such as financial institutions, telecommunications providers, cloud service operators, and large enterprises. Breach of VLAN isolation can lead to unauthorized data exposure, compliance violations (e.g., GDPR), and facilitate advanced persistent threats by enabling attackers to move laterally across segmented network zones. The risk is heightened in multi-tenant data centers and environments with strict segmentation policies. While availability is not directly affected, the compromise of VLAN boundaries undermines trust in network security controls and can lead to broader security incidents.

CWE-1189Improper Isolation of Shared Resources on System-on-a-Chip (SoC) (opens in a new tab)
Base weakness
The System-On-a-Chip (SoC) does not properly isolate shared resources between trusted and untrusted agents.
Architecture and Design · Separation of Privilege
When sharing resources, avoid mixing agents of varying trust levels.
Attack patterns
Shared Resource Manipulation (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

https//www.arista.com/en/support/advisories-notices/security-advisory/21411-security-advisory-0118 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 6 Jul 2025, 01:27 UTC

WeaknessesCWE-1189

Technical details

References

Community reviews

Related threats