adobe air desktop runtime
ProduktUScpe:2.3:a:adobe:air_desktop_runtime:*:*:*:*:*:*:*:*
Ein im Bedrohungsgraphen erfasstes Produkt; die Schwachstellen unten betreffen es bekanntermaßen.
nach Schweregrad
7critical81high0medium0low
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-2016-0984US | high8.8OT kritisch | 54.5% (99th) | KEV | ✗kein Fix | 2016-02-10 | ≤ 20.0.0.233 |
| CVE-2016-1019US | critical9.8OT kritisch | 22.3% (98th) | KEV | ✗kein Fix | 2016-04-07 | ≤ 21.0.0.176 |
| CVE-2016-1010US | high8.8OT kritisch | 19.3% (97th) | KEV | ✗kein Fix | 2016-03-12 | ≤ 20.0.0.260 |
| CVE-2014-0569US | high9.3 | 91.3% (100th) | Exploit | ✗kein Fix | 2014-10-15 | ≤ 15.0.0.249 |
| CVE-2016-0971US | high8.8 | 33.5% (98th) | Exploit | ✗kein Fix | 2016-02-10 | ≤ 20.0.0.233 |
| CVE-2016-0974US | high8.8 | 30.8% (98th) | Exploit | ✗kein Fix | 2016-02-10 | ≤ 20.0.0.233 |
| CVE-2016-1000US | high8.8 | 28.6% (98th) | Exploit | ✗kein Fix | 2016-03-12 | ≤ 20.0.0.260 |
| CVE-2016-0999US | high8.8 | 28.6% (98th) | Exploit | ✗kein Fix | 2016-03-12 | ≤ 20.0.0.260 |
| CVE-2016-0997US | high8.8 | 28.5% (98th) | Exploit | ✗kein Fix | 2016-03-12 | ≤ 20.0.0.260 |
| CVE-2016-0998US | high8.8 | 28.3% (98th) | Exploit | ✗kein Fix | 2016-03-12 | ≤ 20.0.0.260 |
| CVE-2016-0985US | high8.8 | 26.1% (98th) | Exploit | ✗kein Fix | 2016-02-10 | ≤ 20.0.0.233 |
| CVE-2016-1001US | high8.8 | 25.1% (98th) | Exploit | ✗kein Fix | 2016-03-12 | ≤ 20.0.0.260 |
| CVE-2016-1011US | high8.8 | 24.9% (98th) | Exploit | ✗kein Fix | 2016-04-09 | ≤ 21.0.0.176 |
| CVE-2016-1013US | high8.8 | 21.8% (98th) | Exploit | ✗kein Fix | 2016-04-09 | ≤ 21.0.0.176 |
| CVE-2016-1002US | high8.8 | 19.7% (97th) | Exploit | ✗kein Fix | 2016-03-12 | ≤ 20.0.0.260 |
| CVE-2016-0967US | high8.8 | 19.7% (97th) | Exploit | ✗kein Fix | 2016-02-10 | ≤ 20.0.0.233 |
| CVE-2016-0965US | high8.8 | 19.7% (97th) | Exploit | ✗kein Fix | 2016-02-10 | ≤ 20.0.0.233 |
| CVE-2016-0964US | high8.8 | 19.7% (97th) | Exploit | ✗kein Fix | 2016-02-10 | ≤ 20.0.0.233 |
| CVE-2016-4121US | critical9.8 | 10.0% (96th) | — | ✗kein Fix | 2016-06-16 | ≤ 21.0.0.198 |
| CVE-2016-1018US | high8.8 | 8.29% (95th) | — | ✗kein Fix | 2016-04-09 | ≤ 21.0.0.176 |
| CVE-2016-0994US | high8.8 | 8.04% (95th) | — | ✗kein Fix | 2016-03-12 | ≤ 20.0.0.260 |
| CVE-2015-8655US | high8.8 | 7.93% (95th) | — | ✗kein Fix | 2016-03-04 | ≤ 19.0.0.241 |
| CVE-2015-8653US | high8.8 | 7.93% (95th) | — | ✗kein Fix | 2016-03-04 | ≤ 19.0.0.241 |
| CVE-2015-8821US | high8.8 | 7.66% (95th) | — | ✗kein Fix | 2016-03-04 | ≤ 19.0.0.241 |
| CVE-2016-0990US | high8.8 | 7.25% (94th) | — | ✗kein Fix | 2016-03-12 | ≤ 20.0.0.260 |
| CVE-2015-8658US | high8.8 | 7.15% (94th) | — | ✗kein Fix | 2016-03-04 | ≤ 19.0.0.241 |
| CVE-2015-8657US | high8.8 | 7.15% (94th) | — | ✗kein Fix | 2016-03-04 | ≤ 19.0.0.241 |
| CVE-2015-8656US | high8.8 | 7.15% (94th) | — | ✗kein Fix | 2016-03-04 | ≤ 19.0.0.241 |
| CVE-2016-0996US | high8.8 | 7.14% (94th) | — | ✗kein Fix | 2016-03-12 | ≤ 20.0.0.260 |
| CVE-2016-1015US | high8.8 | 7.13% (94th) | — | ✗kein Fix | 2016-04-09 | ≤ 21.0.0.176 |
| CVE-2015-8820US | high8.8 | 7.08% (94th) | — | ✗kein Fix | 2016-03-04 | ≤ 19.0.0.241 |
| CVE-2015-8822US | high8.8 | 6.52% (94th) | — | ✗kein Fix | 2016-03-04 | ≤ 19.0.0.241 |
| CVE-2016-0995US | high8.8 | 6.42% (94th) | — | ✗kein Fix | 2016-03-12 | ≤ 20.0.0.260 |
| CVE-2016-0987US | high8.8 | 6.42% (94th) | — | ✗kein Fix | 2016-03-12 | ≤ 20.0.0.260 |
| CVE-2015-8654US | high8.8 | 6.29% (94th) | — | ✗kein Fix | 2016-03-04 | ≤ 19.0.0.241 |
| CVE-2015-8652US | high8.8 | 6.29% (94th) | — | ✗kein Fix | 2016-03-04 | ≤ 19.0.0.241 |
| CVE-2016-4163US | critical9.8 | 6.27% (94th) | — | ✗kein Fix | 2016-06-16 | ≤ 21.0.0.198 |
| CVE-2016-4162US | critical9.8 | 6.27% (94th) | — | ✗kein Fix | 2016-06-16 | ≤ 21.0.0.198 |
| CVE-2016-4161US | critical9.8 | 6.27% (94th) | — | ✗kein Fix | 2016-06-16 | ≤ 21.0.0.198 |
| CVE-2016-4160US | critical9.8 | 6.27% (94th) | — | ✗kein Fix | 2016-06-16 | ≤ 21.0.0.198 |
| CVE-2016-4120US | critical9.8 | 6.27% (94th) | — | ✗kein Fix | 2016-06-16 | ≤ 21.0.0.198 |
| CVE-2014-0564US | high10.0 | 6.19% (93rd) | — | ✗kein Fix | 2014-10-15 | ≤ 15.0.0.249 |
| CVE-2016-1017US | high8.8 | 6.10% (93rd) | — | ✗kein Fix | 2016-04-09 | ≤ 21.0.0.176 |
| CVE-2016-1016US | high8.8 | 6.10% (93rd) | — | ✗kein Fix | 2016-04-09 | ≤ 21.0.0.176 |
| CVE-2016-0983US | high8.8 | 5.93% (93rd) | — | ✗kein Fix | 2016-02-10 | ≤ 20.0.0.233 |
| CVE-2016-0982US | high8.8 | 5.93% (93rd) | — | ✗kein Fix | 2016-02-10 | ≤ 20.0.0.233 |
| CVE-2016-0993US | high8.8 | 5.66% (93rd) | — | ✗kein Fix | 2016-03-12 | ≤ 20.0.0.260 |
| CVE-2016-0963US | high8.8 | 5.66% (93rd) | — | ✗kein Fix | 2016-03-12 | ≤ 20.0.0.260 |
| CVE-2016-0975US | high8.8 | 5.50% (93rd) | — | ✗kein Fix | 2016-02-10 | ≤ 20.0.0.233 |
| CVE-2016-0973US | high8.8 | 5.50% (93rd) | — | ✗kein Fix | 2016-02-10 | ≤ 20.0.0.233 |
50 von 88 angezeigt