CVE-2018-16253

UnknownEPSS 0.62%

Last modified

CVE-2018-16253 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 properly verify the ASN.1 metadata. 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.62% 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 properly verify the ASN.1 metadata. 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 an even more permissive variant of CVE-2006-4790 and CVE-2014-1568.

Metrics

EPSS Probability
0.62%

45.0th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
Axtls ProjectAxtls<= 2.1.3

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2018-16253?
In sig_verify() in x509.c in axTLS version 2.1.3 and before, the PKCS#1 v1.5 signature verification does not properly verify the ASN.1 metadata. 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 an even more permissive variant of CVE-2006-4790 and CVE-2014-1568.
How severe is CVE-2018-16253?
Severity scoring for CVE-2018-16253 is pending analysis. The EPSS model estimates a 0.62% probability of exploitation in the next 30 days.
How do I fix CVE-2018-16253?
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-16253?

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

Scan your code now

Source: NVD / NIST