CVSS 3.1
9.8 criticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HCritical (9.8) in totolink. EPSS 30% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExplain CVE-2019-19825 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2019-19825?via=ask-ai-copy and https://cve.bz/cve/CVE-2019-19825?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2019-19825 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| totolink:a3002ru_firmware | through 2.0.0 |
| totolink:a702r_firmware | through 2.1.3 |
| totolink:n301rt_firmware | through 2.1.6 |
| totolink:n302r_firmware | through 3.4.0 |
| totolink:n300rt_firmware | through 3.4.0 |
| totolink:n200re_firmware | through 4.0.0 |
| totolink:n150rt_firmware | through 3.4.0 |
| totolink:n100re_firmware | through 3.4.0 |
Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.