totolink a3002r firmware
ProduktUScpe:2.3:o:totolink:a3002r_firmware:*:*:*:*:*:*:*:*
Ein im Bedrohungsgraphen erfasstes Produkt; die Schwachstellen unten betreffen es bekanntermaßen.
nach Schweregrad
6critical4high6medium1low
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-2021-34228US | medium6.1 | 29.2% (98th) | — | ✗kein Fix | 2021-08-20 | = 1.1.1-b20200824 |
| CVE-2025-45858US | — | 11.1% (96th) | — | ✗kein Fix | 2025-05-13 | = 4.0.0-b20230531.1404 |
| CVE-2025-25579US | — | 10.4% (96th) | — | ✗kein Fix | 2025-03-28 | = 4.0.0-b20230531.1404 |
| CVE-2025-6485US | — | 9.34% (95th) | — | ✗kein Fix | 2025-06-22 | = 1.1.1-b20200824.0128 |
| CVE-2025-55591US | — | 7.75% (95th) | — | ✗kein Fix | 2025-08-18 | = 4.0.0-b20230531.1404 |
| CVE-2025-45859US | — | 5.21% (92nd) | — | ✗kein Fix | 2025-05-13 | = 4.0.0-b20230531.1404 |
| CVE-2025-45867US | — | 5.06% (92nd) | — | ✗kein Fix | 2025-05-13 | = 4.0.0-b20230531.1404 |
| CVE-2025-45864US | — | 5.06% (92nd) | — | ✗kein Fix | 2025-05-13 | = 4.0.0-b20230531.1404 |
| CVE-2020-25499US | high8.8OT erhöht | 4.20% (91st) | — | ✓1.1.1-b20200824.0128 | 2020-12-09 | < 1.1.1-b20200824.0128 |
| CVE-2025-4729US | — | 1.22% (69th) | — | ✗kein Fix | 2025-05-16 | = 3.0.0-b20230809.1615 |
| CVE-2024-54907US | — | 1.13% (66th) | — | ✗kein Fix | 2024-12-26 | = 4.0.0-b20230531.1404 |
| CVE-2025-55589US | — | 1.05% (64th) | — | ✗kein Fix | 2025-08-18 | = 4.0.0-b20230531.1404 |
| CVE-2025-6393US | high7.5 | 1.05% (64th) | — | ✗kein Fix | 2025-06-21 | = 4.0.0-b20230531.1404 |
| CVE-2025-6149US | — | 1.04% (64th) | — | ✗kein Fix | 2025-06-17 | = 4.0.0-b20230531.1404 |
| CVE-2025-6487US | — | 1.02% (63rd) | — | ✗kein Fix | 2025-06-22 | = 1.1.1-b20200824.0128 |
| CVE-2025-6486US | — | 1.02% (63rd) | — | ✗kein Fix | 2025-06-22 | = 1.1.1-b20200824.0128 |
| CVE-2025-6337US | — | 0.98% (62nd) | — | ✗kein Fix | 2025-06-20 | 2 Versionen |
| CVE-2025-6164US | — | 0.98% (62nd) | — | ✗kein Fix | 2025-06-17 | = 4.0.0-b20230531.1404 |
| CVE-2024-34195US | critical9.8 | 0.94% (61st) | — | ✗kein Fix | 2024-08-28 | = 1.1.1-b20200824 |
| CVE-2022-40111US | critical9.8OT erhöht | 0.88% (59th) | — | ✗kein Fix | 2022-09-06 | = 1.1.1-b20200824.0128 |
| CVE-2022-40109US | critical9.8OT erhöht | 0.86% (58th) | — | ✗kein Fix | 2022-09-06 | = 1.1.1-b20200824.0128 |
| 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-2022-40112US | high7.5 | 0.83% (57th) | — | ✗kein Fix | 2022-09-06 | = 1.1.1-b20200824.0128 |
| CVE-2022-40110US | high7.5 | 0.83% (57th) | — | ✗kein Fix | 2022-09-06 | = 1.1.1-b20200824.0128 |
| CVE-2025-55590US | — | 0.82% (57th) | — | ✗kein Fix | 2025-08-18 | = 4.0.0-b20230531.1404 |
| CVE-2021-34218US | medium5.3 | 0.81% (57th) | — | ✗kein Fix | 2021-08-20 | = 1.1.1-b20200824 |
| CVE-2021-34223US | medium6.1 | 0.66% (52nd) | — | ✗kein Fix | 2021-08-20 | = 1.1.1-b20200824 |
| CVE-2021-34220US | medium6.1 | 0.66% (52nd) | — | ✗kein Fix | 2021-08-20 | = 1.1.1-b20200824 |
| CVE-2021-34215US | medium6.1 | 0.66% (52nd) | — | ✗kein Fix | 2021-08-20 | = 1.1.1-b20200824 |
| CVE-2021-34207US | medium6.1 | 0.66% (52nd) | — | ✗kein Fix | 2021-08-20 | = 1.1.1-b20200824 |
| CVE-2025-45863US | — | 0.63% (50th) | — | ✗kein Fix | 2025-05-13 | = 4.0.0-b20230531.1404 |
| CVE-2025-45865US | critical9.8 | 0.63% (50th) | — | ✗kein Fix | 2025-05-13 | = 4.0.0-b20230531.1404 |
| CVE-2025-45861US | critical9.8 | 0.63% (50th) | — | ✗kein Fix | 2025-05-13 | = 4.0.0-b20230531.1404 |
| CVE-2024-42520US | critical9.8 | 0.63% (50th) | — | ✗kein Fix | 2024-08-12 | = 4.0.0-b20230531.1404 |
| CVE-2024-33820US | — | 0.55% (46th) | — | ✗kein Fix | 2024-05-01 | = 4.0.0-b20230531.1404 |
50 von 61 angezeigt