NASM asm/labels.c null pointer dereference

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.

A vulnerability, which was classified as problematic, has been found in NASM (Programming Tool Software) (affected version not known). Affected by this issue is an unknown code of the file asm/labels.c. The manipulation with an unknown input leads to a denial of service vulnerability. Using CWE to declare the problem leads to CWE-476. Impacted is availability.

The bug was discovered 09/05/2018. The weakness was published 09/06/2018 as Bug 3392513 as not defined bug report (Bugzilla). The advisory is shared for download at This vulnerability is handled as CVE-2018-16517 since 09/05/2018. The attack may be launched remotely. No form of authentication is required for exploitation. Successful exploitation requires user interaction by the victim. Technical details as well as a public exploit are known.

A public exploit has been developed by Fakhri Zulkifli in ANSI C and been published 9 months after the advisory. It is declared as proof-of-concept. The exploit is available at The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $0-$5k. The code used by the exploit is:

if (i == TOKEN_ID || (insn_is_label && i == TOKEN_INSN)) {    <-- not taken
	/* there's a label here */
	first = false;
	result->label = tokval.t_charptr;
	i = stdscan(NULL, &tokval);
	if (i == ':') {         /* skip over the optional colon */
		i = stdscan(NULL, &tokval);
	} else if (i == 0) {
			  "label alone on a line without a colon might be in error");
	if (i != TOKEN_INSN || tokval.t_integer != I_EQU) {
		 * FIXME: location.segment could be NO_SEG, in which case
		 * it is possible we should be passing 'absolute.segment'. Look into this.
		 * Work out whether that is *really* what we should be doing.
		 * Generally fix things. I think this is right as it is, but
		 * am still not certain.
					 in_absolute ? absolute.segment : location.segment,
					 location.offset, true);

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at Exploit-DB (46726).




CPE 2.3infoedit

CPE 2.2infoedit


VulDB Meta Base Score: 4.4
VulDB Meta Temp Score: 4.3

VulDB Base Score: 3.3
VulDB Temp Score: 3.2
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 5.5
NVD Vector: 🔍



VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍


Class: Denial of service
CWE: CWE-476
ATT&CK: Unknown

Local: No
Remote: Yes

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Author: Fakhri Zulkifli
Programming Language: 🔍
Download: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍


Exploit-DB: 🔍

Threat Intelligenceinfoedit

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍


Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍
Exploit Delay Time: 🔍


09/05/2018 🔍
09/05/2018 +0 days 🔍
09/06/2018 +0 days 🔍
09/06/2018 +0 days 🔍
09/07/2018 +1 days 🔍
04/18/2019 +223 days 🔍
04/18/2019 +0 days 🔍
05/31/2020 +409 days 🔍


Advisory: Bug 3392513
Status: Not defined

CVE: CVE-2018-16517 (🔍)
scip Labs:


Created: 09/07/2018 07:47 AM
Updated: 05/31/2020 10:16 PM
Changes: (1) vulnerability_discoverydate
Complete: 🔍


No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!