9.3
CVE-2014-0322
- EPSS 93.18%
- Veröffentlicht 14.02.2014 16:55:07
- Zuletzt bearbeitet 11.04.2025 00:51:21
- Quelle secure@microsoft.com
- Teams Watchlist Login
- Unerledigt Login
Use-after-free vulnerability in Microsoft Internet Explorer 9 and 10 allows remote attackers to execute arbitrary code via vectors involving crafted JavaScript code, CMarkup, and the onpropertychange attribute of a script element, as exploited in the wild in January and February 2014.
Daten sind bereitgestellt durch National Vulnerability Database (NVD)
Microsoft ≫ Internet Explorer Version9
Microsoft ≫ Windows 7 Version-
Microsoft ≫ Windows Server 2008 Version-
Microsoft ≫ Windows Server 2008 Versionr2
Microsoft ≫ Windows Vista Version-
Microsoft ≫ Windows Server 2008 Version-
Microsoft ≫ Windows Server 2008 Versionr2
Microsoft ≫ Windows Vista Version-
Microsoft ≫ Internet Explorer Version10
Microsoft ≫ Windows 7 Version-
Microsoft ≫ Windows 8 Version-
Microsoft ≫ Windows Rt Version-
Microsoft ≫ Windows Server 2008 Versionr2
Microsoft ≫ Windows Server 2012 Version-
Microsoft ≫ Windows 8 Version-
Microsoft ≫ Windows Rt Version-
Microsoft ≫ Windows Server 2008 Versionr2
Microsoft ≫ Windows Server 2012 Version-
04.05.2022: CISA Known Exploited Vulnerabilities (KEV) Catalog
Microsoft Internet Explorer Use-After-Free Vulnerability
SchwachstelleUse-after-free vulnerability in Microsoft Internet Explorer allows remote attackers to execute code.
BeschreibungApply updates per vendor instructions.
Erforderliche Maßnahmen| Typ | Quelle | Score | Percentile |
|---|---|---|---|
| EPSS | FIRST.org | 93.18% | 0.998 |
| Quelle | Base Score | Exploit Score | Impact Score | Vector String |
|---|---|---|---|---|
| nvd@nist.gov | 8.8 | 2.8 | 5.9 |
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
|
| nvd@nist.gov | 9.3 | 8.6 | 10 |
AV:N/AC:M/Au:N/C:C/I:C/A:C
|
| 134c704f-9b21-4f2e-91b3-4a467353bcc0 | 8.8 | 2.8 | 5.9 |
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
|
CWE-416 Use After Free
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.