CVE-2024-37663VulnerabilityPublished 17 Jun 2024Updated 22 Nov 2024

CVE-2024-37663: n/a

Source CVE Database V5

Not known to be exploited · CVSS 4.1 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

4.1Medium

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

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

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

Attack Vector: Adjacent
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
Scope: Unchanged
Confidentiality: Low
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: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
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 17 Jun 2024
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-25.

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

AI-suggested

To mitigate CVE-2024-37663, organizations and users should take the following specific actions: 1) Monitor official Redmi or Xiaomi channels for firmware updates addressing this vulnerability and apply patches promptly once available. 2) Restrict WLAN access by implementing strong authentication mechanisms such as WPA3 or WPA2-Enterprise to prevent unauthorized local network access. 3) Segment wireless networks to isolate critical devices and sensitive traffic from general user access, reducing the attack surface. 4) Deploy network monitoring tools capable of detecting anomalous ICMP redirect messages or unusual routing changes within the WLAN. 5) Educate users about the risks of connecting to untrusted or public Wi-Fi networks where attackers could exploit this vulnerability. 6) Consider disabling ICMP redirect acceptance on client devices where feasible, to prevent processing of forged redirect messages. 7) Use VPNs to encrypt traffic, mitigating the risk of interception even if routing is manipulated. 8) Conduct regular security assessments of WLAN environments to identify and remediate potential weaknesses that could facilitate local attacker presence. These targeted measures go beyond generic advice by focusing on controlling local network access, monitoring ICMP traffic, and preparing for vendor patch deployment.

Description

Redmi router RB03 v1.0.57 is vulnerable to forged ICMP redirect message attacks. An attacker in the same WLAN as the victim can hijack the traffic between the victim and any remote server by sending out forged ICMP redirect messages.

Impact

The primary impact of CVE-2024-37663 is the potential compromise of confidentiality and integrity of network traffic for users connected to vulnerable Redmi RB03 routers. By exploiting forged ICMP redirect messages, an attacker can perform man-in-the-middle attacks, intercepting or altering data transmitted between victims and remote servers. This can lead to exposure of sensitive information such as credentials, personal data, or business communications. Although availability is not affected, the integrity and confidentiality breaches can have serious consequences, including data theft, session hijacking, or injection of malicious content. The requirement for local network access limits the scope to environments where attackers can connect to the same WLAN, such as public Wi-Fi hotspots, corporate wireless networks, or shared residential networks. Organizations with Redmi RB03 routers in such environments face increased risk, especially if WLAN access controls are weak. The absence of known exploits in the wild reduces immediate risk but does not eliminate the threat, as attackers could develop exploits rapidly. Overall, the vulnerability could facilitate targeted espionage, data exfiltration, or lateral movement within compromised networks.

CWE-940Improper Verification of Source of a Communication Channel (opens in a new tab)
Base weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product establishes a communication channel to handle an incoming request that has been initiated by an actor, but it does not properly verify that the request is coming from the expected origin.
Architecture and Design
Use a mechanism that can validate the identity of the source, such as a certificate, and validate the integrity of data to ensure that it cannot be modified in transit using an Adversary-in-the-Middle (AITM) attack.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V1.14.1 (opens in a new tab)
V14.5.2 (opens in a new tab)
V14.5.3 (opens in a new tab)
Attack patterns
WebView Injection (opens in a new tab)
Connection Reset (opens in a new tab)
TCP RST Injection (opens in a new tab)
Traffic Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/ouuan/router-vuln-report/blob/master/icmp-redirect/redmi-rb03-redirect.md (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 26 Feb 2026, 05:17 UTC

WeaknessesCWE-940

Technical details

References

Community reviews

Related threats