CVE-2024-39802 Details
Description
Multiple buffer overflow vulnerabilities exist in the qos.cgi qos_settings() functionality of Wavlink AC3000 M33A8.V5030.210505. A specially crafted HTTP request can lead to stack-based buffer overflow. An attacker can make an authenticated HTTP request to trigger these vulnerabilities.A buffer overflow vulnerability exists in the `qos_dat` POST parameter.
Multiple stack-based buffer overflow vulnerabilities have been identified in the QoS CGI 'qos_settings' function of the Wavlink AC3000 router, specifically in the firmware version M33A8.V5030.210505. These vulnerabilities can be triggered by authenticated users sending specially crafted HTTP requests. The 'qos_dat' POST parameter is one of the fields that can be exploited, leading to arbitrary code execution.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Jan 15, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://www.talosintelligence.com/vulnerability_reports/TALOS-2024-2049 | CVE | |
| https://talosintelligence.com/vulnerability_reports/TALOS-2024-2049 | [email protected] | ExploitThird Party Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-120 | Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| wavlink wl-wn533a8 firmware | m33a8.v5030.210505 |
CPE
Remediation
| |
| wavlink wl-wn533a8 | All versions |
CPE
Remediation
| |
Change History
5 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Nov 3, 2025 | CVE Modified | CVE |
| Aug 21, 2025 | Initial Analysis | [email protected] |
| Jan 14, 2025 | New CVE Received | [email protected] |