CVE-2021-46835VulnerabilityPublished 20 Sep 2022Updated 28 May 2025

CVE-2021-46835: WS7200-10 · Traffic Hijacking

Affects WS7200-10Source CVE Database V5

Not known to be exploited · CVSS 4.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

4.3Medium

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:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

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

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

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
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: None: There is no loss of confidentiality within 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 20 Sep 2022
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 2026-10-26.

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 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
n/a WS7200-10	Affected =11.0.2.13	Fixed in–

AI-suggested

1. Network Segmentation: Isolate WS7200-10 devices in secure network segments with strict access controls to limit adjacent network access only to trusted devices and personnel. 2. Monitoring and Detection: Implement network traffic monitoring to detect unusual packet redirection or hijacking attempts around WS7200-10 devices. 3. Firmware Updates: Engage with the device vendor or manufacturer to obtain patches or firmware updates addressing CVE-2021-46835. 4. Access Controls: Enforce strict authentication and authorization policies on network management interfaces to prevent unauthorized configuration changes that could facilitate exploitation. 5. Incident Response Preparedness: Prepare incident response plans for potential traffic hijacking scenarios, including forensic capabilities to analyze network traffic integrity. 6. Network Hardening: Use encryption protocols (e.g., IPsec, TLS) for sensitive communications traversing the WS7200-10 to reduce the impact of traffic hijacking by ensuring data integrity and authenticity at higher layers.

Description

There is a traffic hijacking vulnerability in WS7200-10 11.0.2.13. Successful exploitation of this vulnerability can cause packets to be hijacked by attackers.

Impact

For European organizations, the impact of this vulnerability depends on the deployment of WS7200-10 devices within their network infrastructure. Organizations using this device in critical network segments could face risks of traffic interception and manipulation, leading to potential data tampering or unauthorized command injection in network communications. While confidentiality is not directly impacted, integrity loss can disrupt business operations, cause data corruption, or facilitate further attacks such as session hijacking or injection of malicious payloads. This is particularly concerning for sectors with high network security requirements such as finance, telecommunications, government, and critical infrastructure. The requirement for adjacent network access limits remote exploitation but insider threats or compromised internal networks could leverage this vulnerability. The absence of known exploits reduces immediate risk but does not eliminate the threat, especially if attackers develop exploits in the future. European organizations should assess their network architecture to identify WS7200-10 devices and evaluate exposure to adjacent network attackers.

CWE-294Authentication Bypass by Capture-replay (opens in a new tab)
Base weaknessLikelihood of exploit: HighOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
A capture-replay flaw exists when the design of the product makes it possible for a malicious user to sniff network traffic and bypass authentication by replaying it to the server in question to the same effect as the original message (or with minor changes).
Architecture and Design
Utilize some sequence or time stamping functionality along with a checksum which takes this into account in order to ensure that messages can be parsed only once.
Architecture and Design
Since any attacker who can listen to traffic can see sequence numbers, it is necessary to sign messages with some kind of cryptography to ensure that sequence numbers are not simply doctored along with content.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
V9.2.3 (opens in a new tab)
Attack patterns
Session Sidejacking (opens in a new tab)
Kerberoasting (opens in a new tab)
Remote Services with Stolen Credentials (opens in a new tab)
Windows Admin Shares with Stolen Credentials (opens in a new tab)
Reusing Session IDs (aka Session Replay) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

huawei.com/en/psirt/security-advisories/huawei-sa-20220831-01-5370a6df-en (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 7 Jul 2025, 07:56 UTC

WeaknessesCWE-294

Technical details

References

Community reviews

Related threats