CVE-2017-10686

UnknownEPSS 2.95%

Last modified

CVE-2017-10686 is a vulnerability of currently unknown severity. In Netwide Assembler (NASM) 2.14rc0, there are multiple heap use after free vulnerabilities in the tool nasm. The related heap is allocated in the token() function and freed in the detoken() function (called by pp_getline()) - it is used again at multiple positions later that could cause multiple damages. EPSS estimates a 2.95% chance of exploitation in the next 30 days.

Description

In Netwide Assembler (NASM) 2.14rc0, there are multiple heap use after free vulnerabilities in the tool nasm. The related heap is allocated in the token() function and freed in the detoken() function (called by pp_getline()) - it is used again at multiple positions later that could cause multiple damages. For example, it causes a corrupted double-linked list in detoken(), a double free or corruption in delete_Token(), and an out-of-bounds write in detoken(). It has a high possibility to lead to a remote code execution attack.

Metrics

EPSS Probability
2.95%

85.4th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersionsUpdate
NasmNetwide Assembler2.14Rc0
CanonicalUbuntu Linux14.04

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2017-10686?
In Netwide Assembler (NASM) 2.14rc0, there are multiple heap use after free vulnerabilities in the tool nasm. The related heap is allocated in the token() function and freed in the detoken() function (called by pp_getline()) - it is used again at multiple positions later that could cause multiple damages. For example, it causes a corrupted double-linked list in detoken(), a double free or corruption in delete_Token(), and an out-of-bounds write in detoken(). It has a high possibility to lead to a remote code execution attack.
How severe is CVE-2017-10686?
Severity scoring for CVE-2017-10686 is pending analysis. The EPSS model estimates a 2.95% probability of exploitation in the next 30 days.
How do I fix CVE-2017-10686?
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-10686?

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

Scan your code now

Source: NVD / NIST