Cisco, Eltex, and MikroTik Switches Tested Against 90 DHCP Spoofing Attacks
DHCP spoofing remains one of the most common and disruptive Layer 2 attacks in local networks, where malicious packets impersonate legitimate DHCP servers to intercept or redirect traffic, much like social engineering scams that trick users into transferring funds.
In a new study, researchers evaluated three widely used switches under 90 simulated attacks to determine which hardware offers the strongest protection, with particular relevance for critical information infrastructure (CII) environments.
Devices Under Test
The team selected the Cisco 2960, a globally popular switch used for over a decade in banks, airports, and factories, featuring hardware-based security functions implemented in ASICs.
The Eltex MES1428 serves as a Russian alternative popular in government institutions and CII facilities, also relying on hardware chips for security features despite sanctions-related constraints on component sourcing.
The MikroTik CRS represents a budget option often found in regional providers, small offices, cafes, and occasionally larger enterprises due to cost savings, but with protection mechanisms handled by the central processor rather than dedicated hardware.
Experiment Setup
A pre-built university testbed allowed immediate testing. The legitimate DHCP server ran on ALT Linux, distributing addresses in the 192.168.1.100–200 range via gateway 192.168.1.1. The attacker used a Kali Linux laptop with a custom Scapy Python script to launch spoofing attempts, while the victim machine on ALT Linux requested configuration.
On Cisco and Eltex, DHCP snooping was enabled by designating trusted ports connected to the real server and treating all other ports as untrusted, causing the switch to drop unauthorized DHCP responses.
On MikroTik, protection was configured via Bridge Filter rules, a software-based approach executed by the CPU instead of specialized chips.
Results
Each device faced 30 attacks with protection active. Cisco blocked all 30 (100% effectiveness). Eltex blocked 28 (93.3%), and MikroTik blocked 24 (80%).
Detection times averaged 415 ms for Cisco, 650 ms for Eltex, and 1185 ms for MikroTik, with MikroTik showing high variance up to two seconds that allowed some attacks to succeed.
ROC analysis yielded AUC scores of 1.00 for Cisco, 0.98 for Eltex, and 0.90 for MikroTik. Latency increased by 18–22% across devices when protection was active, remaining acceptable for users.
CPU load rose modestly on Cisco (+3.1%) and Eltex (+5.1%), but MikroTik experienced nearly triple the increase (+8.9%, with peaks to +11%), potentially affecting other router functions such as VPN or internet speed.
Conclusion and Recommendations
The performance gap stems from hardware versus software implementation: Cisco and Eltex use dedicated ASICs, while MikroTik processes filters on the CPU.
For banks, large telecom operators, or CII objects, the study recommends Cisco or Eltex. For small offices, cafes, shops, or home networks, MikroTik may suffice but should be supplemented with Port Security, VLANs, and CPU monitoring rather than relying solely on Bridge Filter.
Related articles
Critical Vulnerability in JetBrains TeamCity Allows Unauthenticated Remote Code Execution
JetBrains has disclosed a critical vulnerability in its on-premises TeamCity CI/CD server that permits remote attackers to execute arbitrary operating system commands without authentication. The flaw, tracked as CVE-2026-63077, affects the agent polling protocol and can be exploited simply by accessing the TeamCity Server over HTTP or HTTPS. With a CVSSv3.1 base score of 9.8, the issue is rated Critical and could lead to data theft, configuration changes, or compromise of build artifacts and downstream pipelines. No in-the-wild exploitation had been observed at the time of disclosure. JetBrains has released fixed versions TeamCity 2026.1.3 and 2025.11.7, along with a patch plugin for all releases since 2017.1, and recommends restricting external access until updates can be applied.
Critical OS Command Injection Flaw in Arista VeloCloud Orchestrator Exploited in the Wild
Arista Networks has disclosed a critical vulnerability in the on-premises version of its VeloCloud Orchestrator product used for centralized SD-WAN management. The flaw, tracked as CVE-2026-16812, is an OS command injection issue that allows remote attackers to compromise the system without any authentication. Exploitation has already been confirmed, and the vulnerability carries the maximum CVSS base score of 10.0 in both version 4.0 and 3.1, classifying it as Critical. Successful attacks can impact the confidentiality, integrity, and availability of the orchestrator and all managed data. In addition, a compromised VeloCloud Orchestrator instance may grant attackers access to connected VeloCloud Edge devices across the network.
CISA Adds Exploited Flaws in FortiOS and VeloCloud Orchestrator to Known Exploited Vulnerabilities Catalog
The US Cybersecurity and Infrastructure Security Agency has added two actively exploited vulnerabilities to its Known Exploited Vulnerabilities catalog. CVE-2026-16812 affects the on-premises version of Arista VeloCloud Orchestrator and allows OS command injection that can lead to data leakage, tampering, and denial of service. The flaw carries a maximum CVSS v3.1 base score of 10.0 and is rated Critical. CVE-2025-68686 impacts Fortinet FortiOS and can be used to bypass specific patches and steal sensitive information when combined with another vulnerability that grants prior filesystem access. Federal agencies must remediate the VeloCloud issue by July 30 and the FortiOS issue by August 10.
Critical Vulnerabilities in JetBrains IntelliJ IDEA and TeamCity Enable Remote Code Execution
JetBrains has addressed multiple critical vulnerabilities in its IntelliJ IDEA and TeamCity products that could allow remote code execution, unauthorized file access, and sandbox escapes. The flaws affect remote development environments and require immediate patching, especially in shared setups. In IntelliJ IDEA, CVE-2026-59792 involves directory traversal during workspace identifier processing and carries a CVSS score of up to 9.8. TeamCity received fixes for several issues, including malicious Git repository configurations that enable code execution and a Kotlin DSL sandbox escape. Additional patches cover arbitrary file access through Perforce integration and a persistent cross-site scripting flaw on cloud profile pages. Administrators are urged to update IntelliJ IDEA to versions 2026.1.4 or 2026.2 and TeamCity to 2026.1.2 or 2025.11.6 depending on the release line in use.