totolink x2000r firmware
ProduktUScpe:2.3:o:totolink:x2000r_firmware:*:*:*:*:*:*:*:*
Ein im Bedrohungsgraphen erfasstes Produkt; die Schwachstellen unten betreffen es bekanntermaßen.
nach Schweregrad
31critical1high6medium0low
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-2025-5504US | — | 13.2% (96th) | — | ✗kein Fix | 2025-06-03 | = 1.0.0-b20230726.1108 |
| CVE-2025-5515US | — | 3.26% (88th) | — | ✗kein Fix | 2025-06-03 | = 1.0.0-b20230726.1108 |
| CVE-2024-0579US | critical9.8 | 2.22% (83rd) | — | ✗kein Fix | 2024-01-16 | = 1.0.0-b20221212.1452 |
| CVE-2023-7208US | critical9.8 | 1.75% (78th) | — | ✗kein Fix | 2024-01-07 | = 2.0.0-b20230727.10434 |
| CVE-2024-22529US | critical9.8 | 1.73% (78th) | — | ✗kein Fix | 2024-01-25 | = 2.0.0-b20230727.10434 |
| CVE-2023-7222US | critical9.8 | 1.32% (71st) | — | ✗kein Fix | 2024-01-09 | = 1.0.0-b20221212.1452 |
| CVE-2023-46546US | critical9.8 | 1.28% (70th) | — | ✗kein Fix | 2023-10-25 | = 1.0.0-b20230221.0948 |
| CVE-2023-46545US | critical9.8 | 1.28% (70th) | — | ✗kein Fix | 2023-10-25 | = 1.0.0-b20230221.0948 |
| CVE-2023-46544US | critical9.8 | 1.28% (70th) | — | ✗kein Fix | 2023-10-25 | = 1.0.0-b20230221.0948 |
| CVE-2023-46547US | critical9.8 | 1.26% (70th) | — | ✗kein Fix | 2023-10-25 | = 1.0.0-b20230221.0948 |
| CVE-2023-46543US | critical9.8 | 1.26% (70th) | — | ✗kein Fix | 2023-10-25 | = 1.0.0-b20230221.0948 |
| CVE-2023-46542US | critical9.8 | 1.26% (70th) | — | ✗kein Fix | 2023-10-25 | = 1.0.0-b20230221.0948 |
| CVE-2023-46541US | critical9.8 | 1.26% (70th) | — | ✗kein Fix | 2023-10-25 | = 1.0.0-b20230221.0948 |
| CVE-2023-46540US | critical9.8 | 1.26% (70th) | — | ✗kein Fix | 2023-10-25 | = 1.0.0-b20230221.0948 |
| CVE-2025-8181US | — | 1.12% (66th) | — | ✗kein Fix | 2025-07-26 | = 1.0.0 |
| CVE-2023-46558US | critical9.8 | 1.01% (63rd) | — | ✗kein Fix | 2023-10-25 | = 1.0.0-b20230221.0948 |
| CVE-2023-46557US | critical9.8 | 1.01% (63rd) | — | ✗kein Fix | 2023-10-25 | = 1.0.0-b20230221.0948 |
| CVE-2023-46556US | critical9.8 | 1.01% (63rd) | — | ✗kein Fix | 2023-10-25 | = 1.0.0-b20230221.0948 |
| CVE-2023-46555US | critical9.8 | 1.01% (63rd) | — | ✗kein Fix | 2023-10-25 | = 1.0.0-b20230221.0948 |
| CVE-2023-46554US | critical9.8 | 1.01% (63rd) | — | ✗kein Fix | 2023-10-25 | = 1.0.0-b20230221.0948 |
| CVE-2023-46551US | critical9.8 | 1.01% (63rd) | — | ✗kein Fix | 2023-10-25 | = 1.0.0-b20230221.0948 |
| CVE-2023-46550US | critical9.8 | 1.01% (63rd) | — | ✗kein Fix | 2023-10-25 | = 1.0.0-b20230221.0948 |
| CVE-2023-46549US | critical9.8 | 1.01% (63rd) | — | ✗kein Fix | 2023-10-25 | = 1.0.0-b20230221.0948 |
| CVE-2023-46548US | critical9.8 | 1.01% (63rd) | — | ✗kein Fix | 2023-10-25 | = 1.0.0-b20230221.0948 |
| CVE-2023-46564US | critical9.8 | 0.98% (62nd) | — | ✗kein Fix | 2023-10-25 | = 1.0.0-b20230221.0948 |
| CVE-2023-46563US | critical9.8 | 0.98% (62nd) | — | ✗kein Fix | 2023-10-25 | = 1.0.0-b20230221.0948 |
| CVE-2023-46562US | critical9.8 | 0.98% (62nd) | — | ✗kein Fix | 2023-10-25 | = 1.0.0-b20230221.0948 |
| CVE-2023-46560US | critical9.8 | 0.98% (62nd) | — | ✗kein Fix | 2023-10-25 | = 1.0.0-b20230221.0948 |
| CVE-2023-46559US | critical9.8 | 0.98% (62nd) | — | ✗kein Fix | 2023-10-25 | = 1.0.0-b20230221.0948 |
| CVE-2023-46553US | critical9.8 | 0.98% (62nd) | — | ✗kein Fix | 2023-10-25 | = 1.0.0-b20230221.0948 |
| CVE-2023-46552US | critical9.8 | 0.98% (62nd) | — | ✗kein Fix | 2023-10-25 | = 1.0.0-b20230221.0948 |
| CVE-2023-51136US | critical9.8 | 0.64% (51st) | — | ✗kein Fix | 2023-12-30 | = 1.0.0-b20230221.0948.web |
| CVE-2023-51135US | critical9.8 | 0.64% (51st) | — | ✗kein Fix | 2023-12-30 | = 1.0.0-b20230221.0948.web |
| CVE-2023-51133US | critical9.8 | 0.64% (51st) | — | ✗kein Fix | 2023-12-30 | = 1.0.0-b20230221.0948.web |
| CVE-2024-33433US | — | 0.63% (50th) | — | ✓1.0.0-b20231213.1013 | 2024-05-14 | < 1.0.0-b20231213.1013 |
| CVE-2025-57579US | —OT erhöht | 0.61% (49th) | — | ✗kein Fix | 2025-09-12 | = 2.0.0-b20230727.1043.web |
| CVE-2024-28404US | — | 0.48% (41st) | — | ✓1.0.0-b20231213.1013 | 2024-03-15 | < 1.0.0-b20231213.1013 |
| CVE-2024-28402US | — | 0.43% (37th) | — | ✓1.0.0-b20231213.1013 | 2024-04-11 | < 1.0.0-b20231213.1013 |
| CVE-2024-29419US | medium5.4 | 0.39% (33rd) | — | ✓1.0.0-b20231213.1013 | 2024-03-20 | < 1.0.0-b20231213.1013 |
| CVE-2024-28401US | medium5.4 | 0.39% (33rd) | — | ✓1.0.0-b20231213.1013 | 2024-03-15 | < 1.0.0-b20231213.1013 |
| CVE-2024-28403US | medium5.4 | 0.39% (33rd) | — | ✓1.0.0-b20231213.1013 | 2024-03-15 | < 1.0.0-b20231213.1013 |
| CVE-2025-5516US | medium4.8 | 0.36% (29th) | — | ✗kein Fix | 2025-06-03 | = 1.0.0-b20230726.1108 |
| CVE-2025-5543US | medium4.8 | 0.33% (26th) | — | ✗kein Fix | 2025-06-03 | = 1.0.0-b20230726.1108 |
| CVE-2025-5542US | medium4.8 | 0.33% (26th) | — | ✗kein Fix | 2025-06-03 | = 1.0.0-b20230726.1108 |
| CVE-2025-9577US | high7.0OT erhöht | 0.22% (13th) | — | ✗kein Fix | 2025-08-28 | = 2.0.0-b20230727.1043.web |