wavlink wl-wn533a8 firmware
ProduktUScpe:2.3:o:wavlink:wl-wn533a8_firmware:*:*:*:*:*:*:*:*
Ein im Bedrohungsgraphen erfasstes Produkt; die Schwachstellen unten betreffen es bekanntermaßen.
nach Schweregrad
8critical50high1medium0low
aktualisiert 2026-10-27
| 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-2024-39363US | medium6.1 | 49.0% (99th) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
| CVE-2024-39280US | — | 35.0% (98th) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
| CVE-2024-37186US | high7.2 | 23.4% (98th) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
| CVE-2024-36295US | high7.2 | 21.3% (98th) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
| CVE-2024-21797US | high7.2 | 21.3% (98th) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
| CVE-2024-38666US | — | 19.4% (97th) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
| CVE-2024-39760US | critical9.8 | 17.8% (97th) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
| CVE-2024-34166US | critical9.8 | 16.2% (97th) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
| CVE-2024-39288US | high7.2 | 13.8% (97th) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
| CVE-2024-36258US | critical9.8 | 12.8% (96th) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
| CVE-2024-39360US | high7.2 | 12.0% (96th) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
| CVE-2024-37357US | high7.2 | 9.96% (96th) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
| CVE-2024-34544US | high7.2 | 8.73% (95th) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
| CVE-2024-39367US | high7.2 | 8.48% (95th) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
| CVE-2024-39761US | critical9.8 | 8.40% (95th) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
| CVE-2024-39759US | critical9.8 | 8.40% (95th) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
| CVE-2024-39785US | high7.2 | 6.37% (94th) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
| CVE-2024-39784US | high7.2 | 6.37% (94th) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
| CVE-2024-39762US | high7.2 | 6.04% (93rd) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
| CVE-2024-39765US | high7.2 | 5.36% (93rd) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
| CVE-2024-39763US | high7.2 | 4.95% (92nd) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
| CVE-2024-39783US | high7.2 | 4.60% (92nd) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
| CVE-2024-39781US | high7.2 | 4.60% (92nd) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
| CVE-2024-39764US | high7.2 | 4.28% (91st) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
| CVE-2024-39782US | high7.2 | 3.82% (90th) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
| CVE-2022-48164US | high7.5 | 3.10% (88th) | — | ✗kein Fix | 2023-02-06 | = m33a8.v5030.190716 |
| CVE-2024-39787US | high7.2 | 2.59% (85th) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
| CVE-2024-39786US | high7.2 | 2.59% (85th) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
| CVE-2024-39757US | high7.2 | 2.47% (84th) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
| CVE-2024-39603US | high7.2 | 2.47% (84th) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
| CVE-2024-39359US | high7.2 | 2.47% (84th) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
| CVE-2024-39357US | high7.2 | 2.47% (84th) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
| CVE-2024-39602US | — | 2.38% (84th) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
| CVE-2024-39370US | high7.2 | 2.24% (83rd) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
| CVE-2024-36493US | high7.2 | 2.08% (81st) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
| CVE-2024-39604US | high8.1 | 1.99% (81st) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
| CVE-2024-39756US | high7.2 | 1.93% (80th) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
| CVE-2024-39358US | high7.2 | 1.93% (80th) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
| CVE-2024-39800US | high7.2 | 1.92% (80th) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
| CVE-2024-39798US | high7.2 | 1.92% (80th) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
| CVE-2024-39299US | high7.2 | 1.58% (75th) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
| CVE-2024-39294US | high7.2 | 1.58% (75th) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
| CVE-2024-39795US | high7.2 | 1.56% (75th) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
| CVE-2024-39793US | high7.2 | 1.56% (75th) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
| CVE-2024-39790US | high7.2 | 1.56% (75th) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
| CVE-2024-39788US | high7.2 | 1.56% (75th) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
| CVE-2024-39608US | critical9.8OT erhöht | 1.46% (73rd) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
| CVE-2024-36290US | critical9.8 | 1.45% (73rd) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
| CVE-2024-39801US | high7.2 | 1.38% (72nd) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
| CVE-2024-37184US | high7.2 | 1.35% (71st) | — | ✗kein Fix | 2025-01-14 | = m33a8.v5030.210505 |
50 von 63 angezeigt