CVE-2018-16150

Name: CVE-2018-16150
Creator: NVD / NIST
Published: 2018-11-07T20:29:00.62+00:00
License: https://creativecommons.org/publicdomain/zero/1.0/

UnknownEPSS 0.59%

Last modified Jun 17, 2026

CVE-2018-16150 is a vulnerability of currently unknown severity. In sig_verify() in x509.c in axTLS version 2.1.3 and before, the PKCS#1 v1.5 signature verification does not reject excess data after the hash value. Consequently, a remote attacker can forge signatures when small public exponents are being used, which could lead to impersonation through fake X.509 certificates. EPSS estimates a 0.59% chance of exploitation in the next 30 days.

Description

In sig_verify() in x509.c in axTLS version 2.1.3 and before, the PKCS#1 v1.5 signature verification does not reject excess data after the hash value. Consequently, a remote attacker can forge signatures when small public exponents are being used, which could lead to impersonation through fake X.509 certificates. This is a variant of CVE-2006-4340.

Metrics

EPSS Probability

0.59%

43.8th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

CWE-347

Affected Software

Vendor	Product	Versions
Axtls Project	Axtls	<= 2.1.3

References

https://github.com/igrr/axtls-8266/commit/5efe2947ab45e81d84b5f707c51d1c64be52f36cPatch, Third Party Advisory
https://sourceforge.net/p/axtls/mailman/message/36459928/Third Party Advisory
https://github.com/igrr/axtls-8266/commit/5efe2947ab45e81d84b5f707c51d1c64be52f36cPatch, Third Party Advisory
https://sourceforge.net/p/axtls/mailman/message/36459928/Third Party Advisory

Timeline

Published: Nov 7, 2018
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2018-16150?

How severe is CVE-2018-16150?

Severity scoring for CVE-2018-16150 is pending analysis. The EPSS model estimates a 0.59% probability of exploitation in the next 30 days.

How do I fix CVE-2018-16150?

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-2018-16150?

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

Scan your code now

Source: NVD / NIST