synology diskstation manager
ProduktUScpe:2.3:o:synology:diskstation_manager:*:*:*:*:*:*:*:*
Ein im Bedrohungsgraphen erfasstes Produkt; die Schwachstellen unten betreffen es bekanntermaßen.
nach Schweregrad
16critical43high27medium2low
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-3156US | high7.8OT kritisch | 100.0% (100th) | KEV | ✗kein Fix | 2021-01-26 | = 6.2 |
| CVE-2017-5753US | medium5.6 | 93.8% (100th) | Exploit | ✓6.2.2-24922 | 2018-01-04 | 5.2 → 6.2.2-24922 |
| CVE-2018-1160US | critical9.8 | 86.5% (100th) | Exploit | ✓6.1.7-15284-3 | 2018-12-20 | 3 Versionen |
| CVE-2017-14491US | critical9.8 | 86.5% (100th) | Exploit | ✗kein Fix | 2017-10-04 | 3 Versionen |
| CVE-2013-6955US | high10.0 | 84.6% (100th) | Exploit | ✗kein Fix | 2014-01-09 | 4 Versionen |
| CVE-2017-9554US | medium5.3 | 76.7% (100th) | Exploit | ✗kein Fix | 2017-07-24 | ≤ 6.1.1-15101-4 |
| CVE-2017-15889US | high8.8 | 73.7% (99th) | Exploit | ✓5.2-5967-5 | 2017-12-04 | < 5.2-5967-5 |
| CVE-2019-9511US | high7.5 | 59.5% (99th) | Exploit | ✗kein Fix | 2019-08-13 | = 6.2 |
| CVE-2024-50629US | — | 31.9% (98th) | Exploit | ✓7.2.1-69057-6 | 2025-03-19 | 4 Versionen |
| CVE-2018-8897US | high7.8 | 18.5% (97th) | Exploit | ✗kein Fix | 2018-05-08 | 3 Versionen |
| CVE-2013-6987US | high7.5 | 14.9% (97th) | Exploit | ✗kein Fix | 2013-12-31 | = 4.3-3810 |
| CVE-2024-10441US | — | 1.25% (69th) | Exploit | ✓7.2.2-72806-1 | 2025-03-19 | 3 Versionen |
| CVE-2019-9515US | high7.5 | 87.3% (100th) | — | ✗kein Fix | 2019-08-13 | = 6.2 |
| CVE-2019-9514US | high7.5 | 82.8% (100th) | — | ✗kein Fix | 2019-08-13 | = 6.2 |
| CVE-2019-9513US | high7.5 | 81.6% (100th) | — | ✗kein Fix | 2019-08-13 | = 6.2 |
| CVE-2019-9516US | medium6.5 | 56.3% (99th) | — | ✗kein Fix | 2019-08-13 | = 6.2 |
| CVE-2019-9517US | high7.5 | 27.9% (98th) | — | ✗kein Fix | 2019-08-13 | = 6.2 |
| CVE-2019-9518US | high7.5 | 25.4% (98th) | — | ✗kein Fix | 2019-08-13 | = 6.2 |
| CVE-2018-7185US | high7.5 | 9.00% (95th) | — | ✓6.1.6-15266 | 2018-03-06 | 5.2 → 6.1.6-15266 |
| CVE-2018-7184US | high7.5 | 8.63% (95th) | — | ✗kein Fix | 2018-03-06 | 3 Versionen |
| CVE-2021-27646US | critical9.8 | 3.92% (90th) | — | ✓6.2.3-25426-3 | 2021-03-12 | < 6.2.3-25426-3 |
| CVE-2015-2809US | medium5.0 | 3.55% (89th) | — | ✗kein Fix | 2015-04-01 | ≤ 3.0 |
| CVE-2021-27647US | critical9.8 | 3.25% (88th) | — | ✓6.2.3-25426-3 | 2021-03-12 | < 6.2.3-25426-3 |
| CVE-2019-14907US | medium6.5 | 3.15% (88th) | — | ✗kein Fix | 2020-01-21 | = 6.2 |
| CVE-2019-19344US | medium6.5 | 2.76% (86th) | — | ✗kein Fix | 2020-01-21 | = 6.2 |
| CVE-2021-29083US | high7.2 | 2.71% (86th) | — | ✓6.2.3-25426-3 | 2021-04-01 | < 6.2.3-25426-3 |
| CVE-2018-7170US | medium5.3 | 2.69% (86th) | — | ✓6.1.6-15266 | 2018-03-06 | 5.2 → 6.1.6-15266 |
| CVE-2022-22687US | critical9.8 | 2.43% (84th) | — | ✓6.2.3-25426-3 | 2022-03-25 | 6.2 → 6.2.3-25426-3 |
| CVE-2021-31439US | high8.8 | 2.33% (83rd) | — | ✓6.2.3-25426-3 | 2021-05-21 | 6.2 → 6.2.3-25426-3 |
| CVE-2018-13284US | high8.8 | 2.31% (83rd) | — | ✓6.1.7-15284-1 | 2019-04-01 | 4 Versionen |
| CVE-2021-26569US | high8.1 | 2.25% (83rd) | — | ✓6.2.3-25426-3 | 2021-03-12 | < 6.2.3-25426-3 |
| CVE-2021-26561US | high8.1 | 2.06% (81st) | — | ✓6.2.3-25426-3 | 2021-02-26 | < 6.2.3-25426-3 |
| CVE-2021-27649US | critical9.8 | 2.01% (81st) | — | ✓6.2.3-25426-3 | 2021-06-23 | 6.2 → 6.2.3-25426-3 |
| CVE-2017-15894US | medium6.5 | 1.97% (80th) | — | ✓5.2-5967-6 | 2017-12-08 | 2 Versionen |
| CVE-2017-12075US | high7.2 | 1.94% (80th) | — | ✓6.2-23739 | 2018-06-08 | < 6.2-23739 |
| CVE-2021-26562US | high8.1 | 1.90% (80th) | — | ✓6.2.3-25426-3 | 2021-02-26 | < 6.2.3-25426-3 |
| CVE-2022-27625US | critical9.8 | 1.79% (78th) | — | ✓7.1.1-42962-2 | 2022-10-20 | < 7.1.1-42962-2 |
| CVE-2022-27624US | critical9.8 | 1.79% (78th) | — | ✓7.1.1-42962-2 | 2022-10-20 | < 7.1.1-42962-2 |
| CVE-2022-27616US | high7.2 | 1.69% (77th) | — | ✓6.2.4-25556-5 | 2022-08-03 | 2 Versionen |
| CVE-2014-2264US | high7.8 | 1.65% (76th) | — | ✗kein Fix | 2014-03-02 | = 4.3-3810 |
| CVE-2022-22684US | high8.8 | 1.60% (76th) | — | ✓6.2.4-25553 | 2022-07-28 | < 6.2.4-25553 |
| CVE-2022-22688US | high8.8 | 1.60% (76th) | — | ✓6.2.4-25556-2 | 2022-03-25 | 6.2 → 6.2.4-25556-2 |
| CVE-2021-26566US | critical9.0 | 1.51% (74th) | — | ✓6.2.3-25426-3 | 2021-02-26 | < 6.2.3-25426-3 |
| CVE-2018-8919US | critical9.8 | 1.44% (73rd) | — | ✓6.1.6-15266 | 2018-12-24 | < 6.1.6-15266 |
| CVE-2017-12076US | medium4.9 | 1.43% (73rd) | — | ✗kein Fix | 2017-08-28 | 2 Versionen |
| CVE-2017-9553US | high7.5 | 1.43% (73rd) | — | ✗kein Fix | 2017-07-24 | ≤ 6.1.1-15101-4 |
| CVE-2015-4655US | medium4.3 | 1.42% (73rd) | — | ✗kein Fix | 2015-06-18 | ≤ 5.2-5565 |
| CVE-2021-29087US | high7.5 | 1.40% (72nd) | — | ✓6.2.3-25426-3 | 2021-06-23 | 6.2 → 6.2.3-25426-3 |
| CVE-2021-29085US | high7.5 | 1.33% (71st) | — | ✓6.2.3-25426-3 | 2021-06-23 | 6.2 → 6.2.3-25426-3 |
| CVE-2021-29084US | high7.5 | 1.33% (71st) | — | ✓6.2.3-25426-3 | 2021-06-23 | 6.2 → 6.2.3-25426-3 |
50 von 94 angezeigt