totolink x5000r firmware
ProduktUScpe:2.3:o:totolink:x5000r_firmware:*:*:*:*:*:*:*:*
Ein im Bedrohungsgraphen erfasstes Produkt; die Schwachstellen unten betreffen es bekanntermaßen.
nach Schweregrad
22critical30high0medium0low
aktualisiert 2026-10-29
| 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-2023-30013US | critical9.8 | 25.9% (98th) | Exploit | ✗kein Fix | 2023-05-05 | 2 Versionen |
| CVE-2025-67445US | high7.5 | 0.37% (31st) | Exploit | ✗kein Fix | 2026-02-24 | = 9.1.0cu.2415_b20250515 |
| CVE-2023-6612US | critical9.8 | 30.7% (98th) | — | ✗kein Fix | 2023-12-08 | = 9.1.0cu.2300_b20230112 |
| CVE-2022-26213US | critical9.8 | 25.6% (98th) | — | ✗kein Fix | 2022-03-15 | = 9.1.0u.6118_b20201102 |
| CVE-2025-13184US | —OT erhöht | 20.1% (97th) | — | ✗kein Fix | 2025-12-10 | = 9.1.0u.6369_b20230113 |
| CVE-2024-28640US | — | 14.2% (97th) | — | ✗kein Fix | 2024-03-16 | = 9.1.0u.6118_b20201102 |
| CVE-2024-34921US | — | 9.18% (95th) | — | ✗kein Fix | 2024-05-14 | = 9.1.0cu.2350_b20230313 |
| CVE-2021-27710US | critical9.8 | 7.90% (95th) | — | ✗kein Fix | 2021-04-14 | = 9.1.0u.6118_b20201102 |
| CVE-2021-27708US | critical9.8 | 7.61% (95th) | — | ✗kein Fix | 2021-04-14 | = 9.1.0u.6118_b20201102 |
| CVE-2022-27005US | critical9.8 | 5.46% (93rd) | — | ✗kein Fix | 2022-03-15 | = 9.1.0u.6118_b20201102 |
| CVE-2021-45738US | critical9.8 | 4.39% (91st) | — | ✗kein Fix | 2022-02-04 | = 9.1.0u.6118_b20201102 |
| CVE-2021-45733US | critical9.8 | 4.39% (91st) | — | ✗kein Fix | 2022-02-04 | = 9.1.0u.6118_b20201102 |
| CVE-2021-45735US | high7.5OT erhöht | 3.80% (90th) | — | ✗kein Fix | 2022-02-04 | = 9.1.0u.6118_b20201102 |
| CVE-2025-70329US | — | 3.44% (89th) | — | ✗kein Fix | 2026-02-23 | = 9.1.0cu.2415_b20250515 |
| CVE-2025-9934US | critical9.8 | 3.40% (89th) | — | ✗kein Fix | 2025-09-04 | = 9.1.0cu.2415_b20250515 |
| CVE-2023-31569US | critical9.8 | 3.06% (88th) | — | ✗kein Fix | 2023-06-06 | = 9.1.0cu.2350_b20230313 |
| CVE-2022-27004US | critical9.8 | 2.90% (87th) | — | ✗kein Fix | 2022-03-15 | = 9.1.0u.6118_b20201102 |
| CVE-2022-27003US | critical9.8 | 2.90% (87th) | — | ✗kein Fix | 2022-03-15 | = 9.1.0u.6118_b20201102 |
| CVE-2025-14586US | critical9.8 | 2.76% (86th) | — | ✗kein Fix | 2025-12-13 | = 9.1.0cu.2089_b20211224 |
| CVE-2024-42740US | — | 2.74% (86th) | — | ✗kein Fix | 2024-08-13 | = 9.1.0cu.2350_b20230313 |
| CVE-2024-32352US | — | 2.17% (82nd) | — | ✗kein Fix | 2024-05-14 | = 9.1.0cu.2350_b20230313 |
| CVE-2024-32351US | — | 2.17% (82nd) | — | ✗kein Fix | 2024-05-14 | = 9.1.0cu.2350_b20230313 |
| CVE-2024-32350US | — | 2.17% (82nd) | — | ✗kein Fix | 2024-05-14 | = 9.1.0cu.2350_b20230313 |
| CVE-2024-32353US | — | 2.09% (82nd) | — | ✗kein Fix | 2024-05-14 | = 9.1.0cu.2350_b20230313 |
| CVE-2024-32355US | — | 1.83% (79th) | — | ✗kein Fix | 2024-05-14 | = 9.1.0cu.2350_b20230313 |
| CVE-2024-57011US | high8.8 | 1.79% (78th) | — | ✗kein Fix | 2025-01-15 | = 9.1.0cu.2350_b20230313 |
| CVE-2023-39618US | critical9.8 | 1.74% (78th) | — | ✗kein Fix | 2023-08-21 | = b20210419 |
| CVE-2023-39617US | critical9.8 | 1.74% (78th) | — | ✗kein Fix | 2023-08-21 | 2 Versionen |
| CVE-2024-42737US | high8.8 | 1.66% (77th) | — | ✗kein Fix | 2024-08-13 | = 9.1.0u.6369_b20230113 |
| CVE-2024-42748US | high8.8 | 1.66% (77th) | — | ✗kein Fix | 2024-08-12 | = 9.1.0u.6369_b20230113 |
| CVE-2024-42745US | high8.8 | 1.66% (77th) | — | ✗kein Fix | 2024-08-12 | = 9.1.0u.6369_b20230113 |
| CVE-2024-57022US | high8.8 | 1.65% (76th) | — | ✗kein Fix | 2025-01-15 | = 9.1.0cu.2350_b20230313 |
| CVE-2024-57021US | high8.8 | 1.65% (76th) | — | ✗kein Fix | 2025-01-15 | = 9.1.0cu.2350_b20230313 |
| CVE-2024-57020US | high8.8 | 1.65% (76th) | — | ✗kein Fix | 2025-01-15 | = 9.1.0cu.2350_b20230313 |
| CVE-2024-57019US | high8.8 | 1.65% (76th) | — | ✗kein Fix | 2025-01-15 | = 9.1.0cu.2350_b20230313 |
| CVE-2024-57018US | high8.8 | 1.65% (76th) | — | ✗kein Fix | 2025-01-15 | = 9.1.0cu.2350_b20230313 |
| CVE-2024-57017US | high8.8 | 1.65% (76th) | — | ✗kein Fix | 2025-01-15 | = 9.1.0cu.2350_b20230313 |
| CVE-2024-57016US | high8.8 | 1.65% (76th) | — | ✗kein Fix | 2025-01-15 | = 9.1.0cu.2350_b20230313 |
| CVE-2024-57015US | high8.8 | 1.65% (76th) | — | ✗kein Fix | 2025-01-15 | = 9.1.0cu.2350_b20230313 |
| CVE-2024-57013US | high8.8 | 1.65% (76th) | — | ✗kein Fix | 2025-01-15 | = 9.1.0cu.2350_b20230313 |
| CVE-2024-57012US | high8.8 | 1.65% (76th) | — | ✗kein Fix | 2025-01-15 | = 9.1.0cu.2350_b20230313 |
| CVE-2024-42739US | high8.8 | 1.65% (76th) | — | ✗kein Fix | 2024-08-13 | = 9.1.0u.6369_b20230113 |
| CVE-2024-42738US | high8.8 | 1.65% (76th) | — | ✗kein Fix | 2024-08-13 | = 9.1.0u.6369_b20230113 |
| CVE-2024-42744US | high8.8 | 1.65% (76th) | — | ✗kein Fix | 2024-08-12 | = 9.1.0u.6369_b20230113 |
| CVE-2024-42743US | high8.8 | 1.65% (76th) | — | ✗kein Fix | 2024-08-12 | = 9.1.0u.6369_b20230113 |
| CVE-2024-42742US | high8.8 | 1.65% (76th) | — | ✗kein Fix | 2024-08-12 | = 9.1.0u.6369_b20230113 |
| CVE-2024-42736US | — | 1.62% (76th) | — | ✗kein Fix | 2024-08-13 | = 9.1.0cu.2350_b20230313 |
| CVE-2024-57024US | — | 1.55% (75th) | — | ✗kein Fix | 2025-01-15 | = 9.1.0cu.2350_b20230313 |
| CVE-2021-45734US | high7.5 | 1.47% (74th) | — | ✗kein Fix | 2022-02-04 | = 9.1.0u.6118_b20201102 |
| CVE-2023-33487US | critical9.8 | 1.41% (73rd) | — | ✗kein Fix | 2023-05-31 | 2 Versionen |
50 von 70 angezeigt