CVE-2013-3163
High 8.8KEV · exploitedPublic exploitFix status unknownMicrosoft Internet Explorer Memory Corruption Vulnerability
Record last updated
CVSS score
High on a 0 to 10 scale
EPSS, chance of exploitation in 30 days
Higher than 99% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Passed 1311 days ago for U.S. federal agencies
Description
Microsoft Internet Explorer 8 through 10 allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted web site, aka "Internet Explorer Memory Corruption Vulnerability," a different vulnerability than CVE-2013-3144 and CVE-2013-3151.
Weakness: CWE-94
Patching and mitigation
- Patch status
- Unknown: no source documents a fix
- Mitigation
- None documented
- Vendor guidance
- docs.microsoft.com (opens in a new tab)
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| Microsoft | Internet Explorer | Not documented | Not documented | CISA KEV |
Timeline
Disclosure
CVE record published by microsoft
Source: CVE Program (opens in a new tab)
30 Mar 2023KEV
Added to the CISA Known Exploited Vulnerabilities catalog
Source: CISA KEV (opens in a new tab)
30 Mar 2023Exploitation
Exploitation confirmed by CISA KEV
Source: CISA KEV (opens in a new tab)
Vendor guidance and references
- MS13-055 (opens in a new tab)vendor-advisory, x_refsource_ms, x_transferred
- https://learn.microsoft.com/en-us/security-updates/securitybulletins/2013/ms13-055 (opens in a new tab)vendor-advisory
- TA13-190A (opens in a new tab)third-party-advisory, x_refsource_cert, x_transferred
- https://nvd.nist.gov/vuln/detail/CVE-2013-3163 (opens in a new tab)government
- oval:org.mitre.oval:def:17363 (opens in a new tab)signature, vdb-entry, x_refsource_oval, x_transferred
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2013-3163 (opens in a new tab)government-resource
Public exploit code
Exploit or proof-of-concept code is publicly available on Exploit-DB. Shown as a prioritization and defensive-testing signal — treat exploit code as hostile and run it only against systems you are authorized to test.