CVE-2015-6056
published 2015-10-14CVE-2015-6056: The (1) JScript and (2) VBScript engines in Microsoft Internet Explorer 9 through 11 allow remote attackers to execute arbitrary code or cause a denial of…
PriorityP350critical9.3CVSS 2.0
AVNACMAuNCCICAC
EPSS
12.68%
95.8th percentile
The (1) JScript and (2) VBScript engines in Microsoft Internet Explorer 9 through 11 allow remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted web site, aka "Scripting Engine Memory Corruption Vulnerability."
Affected
1 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| apache | tomcat | — | — |
CVSS provenance
nvdv2.09.3CRITICALAV:N/AC:M/Au:N/C:C/I:C/A:C
vendor_apache7.5HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-rv7r-2cq4-m967: The (1) JScript and (2) VBScript engines in Microsoft Internet Explorer 9 through 11 allow remote attackers to execute arbitrary code or cause a denia
ghsa_unreviewed·2022-05-14
CVE-2015-6056 [HIGH] CWE-119 GHSA-rv7r-2cq4-m967: The (1) JScript and (2) VBScript engines in Microsoft Internet Explorer 9 through 11 allow remote attackers to execute arbitrary code or cause a denia
The (1) JScript and (2) VBScript engines in Microsoft Internet Explorer 9 through 11 allow remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted web site, aka "Scripting Engine Memory Corruption Vulnerability."
Apache
Apache tomcat: CVE-2017-6056
vendor_apache·CVSS 7.5
CVE-2017-6056 [HIGH] Apache tomcat: CVE-2017-6056
Apache tomcat: CVE-2017-6056
In February 2015 a single user reported high CPU usage ( 57544 ) which was traced to a tight loop. However, it was not clear how the conditions necessary to enter the loop were being created. There was no evidence that indicated that the loop was user triggerable. The only potential paths identified by code inspection depended on application bugs (retaining references to request objects and accessing after the request had completed). It was (and still is) believed that an application bug was the most likely root cause. Therefore, 57544 was not treated as a DoS vulnerability. In November 2016,
Severity: high
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2015-10-14
Published