totolink a3002ru firmware
ProduktUScpe:2.3:o:totolink:a3002ru_firmware:*:*:*:*:*:*:*:*
Ein im Bedrohungsgraphen erfasstes Produkt; die Schwachstellen unten betreffen es bekanntermaßen.
nach Schweregrad
8critical8high8medium1low
aktualisiert 2026-10-28
| ID | Schweregrad CVSS-Basis-Schweregrad und -Wert (0–10). | EPSS FIRST.org-Wahrscheinlichkeit einer Ausnutzung in den nächsten 30 Tagen, mit Perzentil-Rang unter allen CVEs. | ausnutzbar Auf CISAs Liste bekannter ausgenutzter Schwachstellen (KEV) oder ein öffentlicher Exploit liegt vor. | behoben Ob für einen betroffenen Bereich eine behobene Version vorliegt. | veröffentlicht | betroffen |
|---|
| CVE-2019-19825US | critical9.8 | 29.6% (98th) | — | ✗kein Fix | 2020-01-27 | ≤ 2.0.0 |
| CVE-2019-19824US | high8.8 | 25.1% (98th) | — | ✗kein Fix | 2020-01-27 | ≤ 2.0.0 |
| CVE-2019-19822US | high7.5OT erhöht | 8.67% (95th) | — | ✗kein Fix | 2020-01-27 | ≤ 2.0.0 |
| CVE-2019-19823US | high7.5 | 6.41% (94th) | — | ✗kein Fix | 2020-01-27 | ≤ 2.0.0 |
| CVE-2018-13316US | critical9.8 | 3.19% (88th) | — | ✗kein Fix | 2018-11-27 | = 1.0.8 |
| CVE-2018-13314US | critical9.8 | 3.19% (88th) | — | ✗kein Fix | 2018-11-27 | = 1.0.8 |
| CVE-2018-13307US | critical9.8 | 3.19% (88th) | — | ✗kein Fix | 2018-11-27 | = 1.0.8 |
| CVE-2018-13306US | critical9.8 | 3.19% (88th) | — | ✗kein Fix | 2018-11-27 | = 1.0.8 |
| CVE-2018-13311US | critical9.8 | 2.50% (85th) | — | ✗kein Fix | 2018-11-26 | = 1.0.8 |
| CVE-2018-13315US | critical9.8 | 1.55% (75th) | — | ✗kein Fix | 2018-11-26 | = 1.0.8 |
| CVE-2025-4729US | — | 1.22% (69th) | — | ✗kein Fix | 2025-05-16 | = 3.0.0-b20230809.1615 |
| CVE-2023-48859US | high8.8OT erhöht | 1.20% (68th) | — | ✗kein Fix | 2023-12-06 | = 2.0.0-b20190902.1958 |
| CVE-2025-6393US | high7.5 | 1.05% (64th) | — | ✗kein Fix | 2025-06-21 | = 3.0.0-b20230809.1615 |
| CVE-2025-6148US | — | 1.04% (64th) | — | ✗kein Fix | 2025-06-17 | = 3.0.0-b20230809.1615 |
| CVE-2018-13313US | medium6.5 | 1.01% (63rd) | — | ✗kein Fix | 2020-02-24 | = 1.0.8 |
| CVE-2018-13317US | medium6.1 | 0.99% (62nd) | — | ✗kein Fix | 2018-11-26 | = 1.0.8 |
| CVE-2025-6337US | — | 0.98% (62nd) | — | ✗kein Fix | 2025-06-20 | 2 Versionen |
| CVE-2025-6163US | — | 0.98% (62nd) | — | ✗kein Fix | 2025-06-17 | = 3.0.0-b20230809.1615 |
| CVE-2025-6953US | — | 0.96% (61st) | — | ✗kein Fix | 2025-07-01 | = 3.0.0-b20230809.1615 |
| CVE-2025-6939US | — | 0.96% (61st) | — | ✗kein Fix | 2025-07-01 | = 3.0.0-b20230809.1615 |
| CVE-2022-35491US | critical9.8OT erhöht | 0.88% (59th) | — | ✗kein Fix | 2022-08-10 | = 3.0.0-b20220304.1804 |
| CVE-2025-4835US | — | 0.85% (58th) | — | ✗kein Fix | 2025-05-17 | = 3.0.0-b20230809.1615 |
| CVE-2025-4834US | — | 0.85% (58th) | — | ✗kein Fix | 2025-05-17 | = 3.0.0-b20230809.1615 |
| CVE-2025-4833US | — | 0.85% (58th) | — | ✗kein Fix | 2025-05-17 | = 3.0.0-b20230809.1615 |
| CVE-2025-4832US | — | 0.85% (58th) | — | ✗kein Fix | 2025-05-17 | = 3.0.0-b20230809.1615 |
| CVE-2025-4831US | — | 0.85% (58th) | — | ✗kein Fix | 2025-05-17 | = 3.0.0-b20230809.1615 |
| CVE-2025-4830US | — | 0.85% (58th) | — | ✗kein Fix | 2025-05-17 | = 3.0.0-b20230809.1615 |
| CVE-2025-4829US | — | 0.85% (58th) | — | ✗kein Fix | 2025-05-17 | = 3.0.0-b20230809.1615 |
| CVE-2025-4827US | — | 0.85% (58th) | — | ✗kein Fix | 2025-05-17 | = 3.0.0-b20230809.1615 |
| CVE-2025-4826US | — | 0.85% (58th) | — | ✗kein Fix | 2025-05-17 | = 3.0.0-b20230809.1615 |
| CVE-2025-4825US | — | 0.85% (58th) | — | ✗kein Fix | 2025-05-17 | = 3.0.0-b20230809.1615 |
| CVE-2025-4824US | — | 0.85% (58th) | — | ✗kein Fix | 2025-05-17 | = 3.0.0-b20230809.1615 |
| CVE-2025-4823US | — | 0.85% (58th) | — | ✗kein Fix | 2025-05-17 | = 3.0.0-b20230809.1615 |
| CVE-2025-4733US | — | 0.85% (58th) | — | ✗kein Fix | 2025-05-16 | = 3.0.0-b20230809.1615 |
| CVE-2025-4732US | — | 0.85% (58th) | — | ✗kein Fix | 2025-05-16 | = 3.0.0-b20230809.1615 |
| CVE-2025-4731US | — | 0.85% (58th) | — | ✗kein Fix | 2025-05-16 | = 3.0.0-b20230809.1615 |
| CVE-2025-4730US | — | 0.85% (58th) | — | ✗kein Fix | 2025-05-16 | = 3.0.0-b20230809.1615 |
| CVE-2018-13309US | medium6.1 | 0.71% (53rd) | — | ✗kein Fix | 2018-11-26 | = 1.0.8 |
| CVE-2018-13312US | medium6.1 | 0.69% (53rd) | — | ✗kein Fix | 2018-11-26 | = 1.0.8 |
| CVE-2018-13308US | medium6.1 | 0.69% (53rd) | — | ✗kein Fix | 2018-11-26 | = 1.0.8 |
| CVE-2018-13310US | medium6.1 | 0.67% (52nd) | — | ✗kein Fix | 2018-11-26 | = 1.0.8 |
| CVE-2024-34198US | — | 0.66% (52nd) | — | ✗kein Fix | 2024-08-28 | = 2.1.1-b20230720.1011 |
| CVE-2026-26736US | high8.8 | 0.55% (46th) | — | ✗kein Fix | 2026-02-17 | ≤ 3.0.0-b20220304.1804 |
| CVE-2026-26731US | high8.8 | 0.52% (44th) | — | ✗kein Fix | 2026-02-17 | = 2.1.1-b20211108.1455 |
| CVE-2025-5505US | — | 0.43% (37th) | — | ✗kein Fix | 2025-06-03 | = 2.1.1-b20230720.1011 |
| CVE-2025-5508US | low3.4 | 0.41% (35th) | — | ✗kein Fix | 2025-06-03 | = 2.1.1-b20230720.1011 |
| CVE-2026-26732US | high8.8 | 0.38% (32nd) | — | ✗kein Fix | 2026-02-17 | = 2.1.1-b20211108.1455 |
| CVE-2025-5507US | medium5.4 | 0.36% (30th) | — | ✗kein Fix | 2025-06-03 | = 2.1.1-b20230720.1011 |
| CVE-2025-5506US | medium5.4 | 0.36% (30th) | — | ✗kein Fix | 2025-06-03 | = 2.1.1-b20230720.1011 |