CVE-2017-13683

UnknownEPSS 0.28%

Last modified

CVE-2017-13683 is a vulnerability of currently unknown severity. In Symantec Endpoint Encryption before SEE 11.1.3HF3, a kernel memory leak is a type of resource leak that can occur when a computer program incorrectly manages memory allocations in such a way that memory which is no longer needed is not released. In object-oriented programming, a memory leak may happen when an object is stored in memory but cannot be accessed by the running code.. EPSS estimates a 0.28% chance of exploitation in the next 30 days.

Description

In Symantec Endpoint Encryption before SEE 11.1.3HF3, a kernel memory leak is a type of resource leak that can occur when a computer program incorrectly manages memory allocations in such a way that memory which is no longer needed is not released. In object-oriented programming, a memory leak may happen when an object is stored in memory but cannot be accessed by the running code.

Metrics

EPSS Probability
0.28%

19.7th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
SymantecEndpoint Encryption11.0.0
SymantecEndpoint Encryption11.1.0
SymantecEndpoint Encryption11.1.1
SymantecEndpoint Encryption11.1.2

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2017-13683?
In Symantec Endpoint Encryption before SEE 11.1.3HF3, a kernel memory leak is a type of resource leak that can occur when a computer program incorrectly manages memory allocations in such a way that memory which is no longer needed is not released. In object-oriented programming, a memory leak may happen when an object is stored in memory but cannot be accessed by the running code.
How severe is CVE-2017-13683?
Severity scoring for CVE-2017-13683 is pending analysis. The EPSS model estimates a 0.28% probability of exploitation in the next 30 days.
How do I fix CVE-2017-13683?
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-2017-13683?

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

Scan your code now

Source: NVD / NIST