CVE-2024-0571 json
Totolink LR1200GB cstecgi.cgi setSmsCfg stack-based overflow
published 2024-01-16 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-16364
- cvss
- 8.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 71%
- public exploits
- 0
- none known
Summary
A vulnerability, which was classified as critical, has been found in Totolink LR1200GB 9.1.0u.6619_B20230130. This issue affects the function setSmsCfg of the file /cgi-bin/cstecgi.cgi. The manipulation of the argument text leads to stack-based buffer overflow. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-250787. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 16 mo ago
Exploit prediction
1.33% chance of exploitation in the next 30 days, higher than 71% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/jylsec/vuldb/blob/main/TOTOLINK/LR1200GB/1/README.md referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| CNA | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| CNA | 2.0 | 9.0 | AV:N/AC:L/Au:S/C:C/I:C/A:C |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Totolink LR1200GB
Classification
- Weakness
-
- CWE-121 Stack-based Buffer Overflow
References
-
github.com
/jylsec/vuldb/blob/main/TOTOLINK/LR1200GB/1/README.md
broken-link, exploit
-
vuldb.com
/?id.250787
vdb-entry, technical-description, permissions-required, third-party-advisory
-
vuldb.com
/?ctiid.250787
signature, permissions-required, third-party-advisory
Sources
- CVE List CVE-2024-0571
- NVD CVE-2024-0571
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.