Strix
26.1K

CVE-2016-1715

UnknownEPSS 2.31%

Last modified

CVE-2016-1715 is a vulnerability of currently unknown severity. The swin.sys kernel driver in McAfee Application Control (MAC) 6.1.0 before build 706, 6.1.1 before build 404, 6.1.2 before build 449, 6.1.3 before build 441, and 6.2.0 before build 505 on 32-bit Windows platforms allows local users to cause a denial of service (memory corruption and system crash) or gain privileges via a 768 syscall, which triggers a zero to be written to an arbitrary kernel memory location.. EPSS estimates a 2.31% chance of exploitation in the next 30 days.

Description

The swin.sys kernel driver in McAfee Application Control (MAC) 6.1.0 before build 706, 6.1.1 before build 404, 6.1.2 before build 449, 6.1.3 before build 441, and 6.2.0 before build 505 on 32-bit Windows platforms allows local users to cause a denial of service (memory corruption and system crash) or gain privileges via a 768 syscall, which triggers a zero to be written to an arbitrary kernel memory location.

Metrics

EPSS Probability
2.31%

81.2th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
MicrosoftWindowsAll versions
McafeeApplication Control6.1.0
McafeeApplication Control6.1.1
McafeeApplication Control6.1.2
McafeeApplication Control6.1.3
McafeeApplication Control6.2.0

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2016-1715?
The swin.sys kernel driver in McAfee Application Control (MAC) 6.1.0 before build 706, 6.1.1 before build 404, 6.1.2 before build 449, 6.1.3 before build 441, and 6.2.0 before build 505 on 32-bit Windows platforms allows local users to cause a denial of service (memory corruption and system crash) or gain privileges via a 768 syscall, which triggers a zero to be written to an arbitrary kernel memory location.
How severe is CVE-2016-1715?
Severity scoring for CVE-2016-1715 is pending analysis. The EPSS model estimates a 2.31% probability of exploitation in the next 30 days.
How do I fix CVE-2016-1715?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2016-1715?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST