totolink a3700r firmware
ProduktUScpe:2.3:o:totolink:a3700r_firmware:*:*:*:*:*:*:*:*
Ein im Bedrohungsgraphen erfasstes Produkt; die Schwachstellen unten betreffen es bekanntermaßen.
nach Schweregrad
15critical14high1medium0low
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-46574US | critical9.8 | 64.9% (99th) | — | ✗kein Fix | 2023-10-25 | = 9.1.2u.6165_20211012 |
| CVE-2024-7156US | high7.5 | 13.3% (96th) | — | ✗kein Fix | 2024-07-28 | = 9.1.2u.5822_b20200513 |
| CVE-2025-3663US | high8.2 | 11.3% (96th) | — | ✗kein Fix | 2025-04-16 | = 9.1.2u.5822_b20200513 |
| CVE-2024-7160US | high8.8 | 3.00% (87th) | — | ✗kein Fix | 2024-07-28 | = 9.1.2u.5822_b20200513 |
| CVE-2024-22663US | critical9.8 | 1.74% (78th) | — | ✗kein Fix | 2024-01-23 | = 9.1.2u.6165_20211012 |
| CVE-2023-52029US | critical9.8 | 1.67% (77th) | — | ✗kein Fix | 2024-01-11 | = 9.1.2u.5822_b20200513 |
| CVE-2023-52028US | critical9.8 | 1.67% (77th) | — | ✗kein Fix | 2024-01-11 | = 9.1.2u.5822_b20200513 |
| CVE-2023-52027US | critical9.8 | 1.67% (77th) | — | ✗kein Fix | 2024-01-11 | = 9.1.2u.5822_b20200513 |
| CVE-2023-52031US | critical9.8 | 1.54% (75th) | — | ✗kein Fix | 2024-01-11 | = 9.1.2u.5822_b20200513 |
| CVE-2023-52030US | critical9.8 | 1.54% (75th) | — | ✗kein Fix | 2024-01-11 | = 9.1.2u.5822_b20200513 |
| CVE-2025-3668US | — | 1.38% (72nd) | — | ✗kein Fix | 2025-04-16 | = 9.1.2u.5822_b20200513 |
| CVE-2022-36461US | high7.8 | 1.20% (68th) | — | ✗kein Fix | 2022-08-25 | = 9.1.2u.6134_b20201202 |
| CVE-2023-50147US | critical9.8 | 1.18% (67th) | — | ✗kein Fix | 2023-12-22 | = 9.1.2u.5822_b20200513 |
| CVE-2022-36460US | high7.8 | 1.01% (63rd) | — | ✗kein Fix | 2022-08-25 | = 9.1.2u.6134_b20201202 |
| CVE-2022-36459US | high7.8 | 1.01% (63rd) | — | ✗kein Fix | 2022-08-25 | = 9.1.2u.6134_b20201202 |
| CVE-2022-36458US | high7.8 | 1.01% (63rd) | — | ✗kein Fix | 2022-08-25 | = 9.1.2u.6134_b20201202 |
| CVE-2024-22662US | critical9.8 | 0.86% (58th) | — | ✗kein Fix | 2024-01-23 | = 9.1.2u.6165_20211012 |
| CVE-2024-22660US | critical9.8 | 0.86% (58th) | — | ✗kein Fix | 2024-01-23 | = 9.1.2u.6165_20211012 |
| CVE-2023-43141US | critical9.8 | 0.79% (56th) | — | ✗kein Fix | 2023-09-25 | = 9.1.2u.6134_b20201202 |
| CVE-2026-1143US | — | 0.76% (55th) | — | ✗kein Fix | 2026-01-19 | = 9.1.2u.5822_b20200513 |
| CVE-2024-37637US | — | 0.67% (52nd) | — | ✗kein Fix | 2024-06-14 | = 9.1.2u.6165_20211012 |
| CVE-2024-37634US | — | 0.67% (52nd) | — | ✗kein Fix | 2024-06-13 | = 9.1.2u.6165_20211012 |
| CVE-2024-42545US | critical9.8 | 0.66% (52nd) | — | ✗kein Fix | 2024-08-12 | = 9.1.2u.5822_b20200513 |
| CVE-2024-42543US | critical9.8 | 0.66% (52nd) | — | ✗kein Fix | 2024-08-12 | = 9.1.2u.5822_b20200513 |
| CVE-2024-37635US | critical9.8 | 0.66% (52nd) | — | ✗kein Fix | 2024-06-13 | = 9.1.2u.6165_20211012 |
| CVE-2024-37632US | critical9.8 | 0.64% (51st) | — | ✗kein Fix | 2024-06-13 | = 9.1.2u.6165_20211012 |
| CVE-2025-3667US | — | 0.64% (50th) | — | ✗kein Fix | 2025-04-16 | = 9.1.2u.5822_b20200513 |
| CVE-2025-3666US | — | 0.64% (50th) | — | ✗kein Fix | 2025-04-16 | = 9.1.2u.5822_b20200513 |
| CVE-2025-3675US | medium5.3 | 0.62% (49th) | — | ✗kein Fix | 2025-04-16 | = 9.1.2u.5822_b20200513 |
| CVE-2024-37640US | — | 0.62% (49th) | — | ✗kein Fix | 2024-06-14 | = 9.1.2u.6165_20211012 |
| CVE-2024-37633US | — | 0.61% (49th) | — | ✗kein Fix | 2024-06-13 | = 9.1.2u.6165_20211012 |
| CVE-2024-37639US | — | 0.61% (49th) | — | ✗kein Fix | 2024-06-14 | = 9.1.2u.6165_20211012 |
| CVE-2024-37631US | — | 0.61% (49th) | — | ✗kein Fix | 2024-06-13 | = 9.1.2u.6165_20211012 |
| CVE-2025-3665US | — | 0.61% (49th) | — | ✗kein Fix | 2025-04-16 | = 9.1.2u.5822_b20200513 |
| CVE-2025-3664US | — | 0.61% (49th) | — | ✗kein Fix | 2025-04-16 | = 9.1.2u.5822_b20200513 |
| CVE-2025-3674US | — | 0.59% (48th) | — | ✗kein Fix | 2025-04-16 | = 9.1.2u.5822_b20200513 |
| CVE-2024-7154US | high7.5OT erhöht | 0.43% (37th) | — | ✗kein Fix | 2024-07-28 | = 9.1.2u.5822_b20200513 |
| CVE-2023-48192US | high7.8 | 0.35% (28th) | — | ✗kein Fix | 2023-11-20 | = 9.1.2u.6134_b20201202 |
| CVE-2022-36465US | high7.8 | 0.35% (28th) | — | ✗kein Fix | 2022-08-25 | = 9.1.2u.6134_b20201202 |
| CVE-2022-36464US | high7.8 | 0.35% (28th) | — | ✗kein Fix | 2022-08-25 | = 9.1.2u.6134_b20201202 |
| CVE-2022-36463US | high7.8 | 0.34% (28th) | — | ✗kein Fix | 2022-08-25 | = 9.1.2u.6134_b20201202 |
| CVE-2022-36466US | high7.8 | 0.34% (27th) | — | ✗kein Fix | 2022-08-25 | = 9.1.2u.6134_b20201202 |
| CVE-2022-36462US | high7.8 | 0.33% (26th) | — | ✗kein Fix | 2022-08-25 | = 9.1.2u.6134_b20201202 |