CVE-2024-39229: n/a
An issue in GL-iNet products AR750/AR750S/AR300M/AR300M16/MT300N-V2/B1300/MT1300/SFT1200/X750 v4.3.11, MT3000/MT2500/AXT1800/AX1800/A1300/X300B v4.5.16, XE300 v4.3.16, E750 v4.3.12, AP1300/S1300 v4.3.13, XE3000/X3000 v4, and B2200/MV1000/MV1000W/USB150/N300/SF1200 v3.216 allows attackers to intercept communications via a man-in-the-middle attack when DDNS clients are reporting data to the server.
AI Analysis
Technical Summary
CVE-2024-39229 is a vulnerability identified in multiple GL-iNet router models, including AR750, AR750S, AR300M series, MT300N-V2, B1300, MT1300, SFT1200, and others, across various firmware versions (notably v3.x and v4.x). The flaw allows an unauthenticated remote attacker to intercept communications between the Dynamic DNS (DDNS) clients on these devices and their corresponding DDNS servers. This interception is possible due to improper security controls in the DDNS client reporting mechanism, which does not adequately protect the data in transit, enabling man-in-the-middle (MitM) attacks. The vulnerability is classified under CWE-924, which relates to improper protection of data in transit. The CVSS 3.1 base score of 6.5 indicates a medium severity, with attack vector being network-based, no privileges or user interaction required, and impacts on confidentiality and integrity but not availability. No patches or exploits are currently known, but the exposure is significant given the widespread use of these routers in consumer and small business environments. The vulnerability could allow attackers to eavesdrop on or manipulate DDNS update data, potentially leading to further attacks such as DNS hijacking or traffic redirection.
Potential Impact
The primary impact of CVE-2024-39229 is the compromise of confidentiality and integrity of communications between affected GL-iNet devices and DDNS servers. Attackers exploiting this vulnerability could intercept sensitive information, including device status and network configuration data. This could facilitate further attacks such as DNS spoofing, traffic interception, or redirection, undermining network security and user privacy. Organizations relying on these devices for remote access or dynamic DNS services may experience degraded trust in their network infrastructure. Although availability is not directly affected, the indirect consequences of MitM attacks could disrupt network operations or enable unauthorized access. The vulnerability affects a broad range of GL-iNet products, which are popular in various regions for their cost-effective networking solutions, thus potentially impacting numerous small businesses, remote workers, and IoT deployments globally.
Mitigation Recommendations
Until official patches are released by GL-iNet, organizations should implement network-level mitigations to reduce exposure. These include enforcing encrypted tunnels (e.g., VPNs) for remote access to devices, restricting DDNS traffic to trusted networks, and monitoring network traffic for unusual patterns indicative of MitM attempts. Disabling DDNS services on affected devices where feasible can eliminate the attack vector. Network segmentation and strict firewall rules should be applied to isolate vulnerable devices from untrusted networks. Additionally, organizations should subscribe to GL-iNet security advisories and promptly apply firmware updates once available. Employing DNS security extensions (DNSSEC) and validating DNS responses can help mitigate downstream DNS manipulation risks. Regular security audits and penetration testing focusing on network device communications are recommended to detect exploitation attempts.
Affected Countries
United States, Germany, United Kingdom, France, China, Japan, South Korea, India, Australia, Canada
CVE-2024-39229: n/a
Description
An issue in GL-iNet products AR750/AR750S/AR300M/AR300M16/MT300N-V2/B1300/MT1300/SFT1200/X750 v4.3.11, MT3000/MT2500/AXT1800/AX1800/A1300/X300B v4.5.16, XE300 v4.3.16, E750 v4.3.12, AP1300/S1300 v4.3.13, XE3000/X3000 v4, and B2200/MV1000/MV1000W/USB150/N300/SF1200 v3.216 allows attackers to intercept communications via a man-in-the-middle attack when DDNS clients are reporting data to the server.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2024-39229 is a vulnerability identified in multiple GL-iNet router models, including AR750, AR750S, AR300M series, MT300N-V2, B1300, MT1300, SFT1200, and others, across various firmware versions (notably v3.x and v4.x). The flaw allows an unauthenticated remote attacker to intercept communications between the Dynamic DNS (DDNS) clients on these devices and their corresponding DDNS servers. This interception is possible due to improper security controls in the DDNS client reporting mechanism, which does not adequately protect the data in transit, enabling man-in-the-middle (MitM) attacks. The vulnerability is classified under CWE-924, which relates to improper protection of data in transit. The CVSS 3.1 base score of 6.5 indicates a medium severity, with attack vector being network-based, no privileges or user interaction required, and impacts on confidentiality and integrity but not availability. No patches or exploits are currently known, but the exposure is significant given the widespread use of these routers in consumer and small business environments. The vulnerability could allow attackers to eavesdrop on or manipulate DDNS update data, potentially leading to further attacks such as DNS hijacking or traffic redirection.
Potential Impact
The primary impact of CVE-2024-39229 is the compromise of confidentiality and integrity of communications between affected GL-iNet devices and DDNS servers. Attackers exploiting this vulnerability could intercept sensitive information, including device status and network configuration data. This could facilitate further attacks such as DNS spoofing, traffic interception, or redirection, undermining network security and user privacy. Organizations relying on these devices for remote access or dynamic DNS services may experience degraded trust in their network infrastructure. Although availability is not directly affected, the indirect consequences of MitM attacks could disrupt network operations or enable unauthorized access. The vulnerability affects a broad range of GL-iNet products, which are popular in various regions for their cost-effective networking solutions, thus potentially impacting numerous small businesses, remote workers, and IoT deployments globally.
Mitigation Recommendations
Until official patches are released by GL-iNet, organizations should implement network-level mitigations to reduce exposure. These include enforcing encrypted tunnels (e.g., VPNs) for remote access to devices, restricting DDNS traffic to trusted networks, and monitoring network traffic for unusual patterns indicative of MitM attempts. Disabling DDNS services on affected devices where feasible can eliminate the attack vector. Network segmentation and strict firewall rules should be applied to isolate vulnerable devices from untrusted networks. Additionally, organizations should subscribe to GL-iNet security advisories and promptly apply firmware updates once available. Employing DNS security extensions (DNSSEC) and validating DNS responses can help mitigate downstream DNS manipulation risks. Regular security audits and penetration testing focusing on network device communications are recommended to detect exploitation attempts.
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- mitre
- Date Reserved
- 2024-06-21T00:00:00.000Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 699f6c86b7ef31ef0b565dbc
Added to database: 2/25/2026, 9:41:26 PM
Last enriched: 2/28/2026, 4:20:20 AM
Last updated: 4/12/2026, 7:53:45 AM
Views: 9
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.