Improper Signature Verification in axTLS x509 PKCS#1 v1.5
CVE-2018-16150 is a vulnerability in the sig_verify() function in x509.c of axTLS version 2.1.3 and earlier. The implementation of PKCS#1 v1.5 signature verification fails to reject excess data appended after the hash value in a signature. This flaw allows an attacker to forge signatures, especially when small public exponents are used, enabling the creation of fake X.509 certificates and impersonation attacks. This issue is a variant of the earlier CVE-2006-4340.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
A remote attacker can exploit this vulnerability to forge valid signatures on X.509 certificates, potentially impersonating trusted entities. This undermines the trust model of PKI, allowing man-in-the-middle attacks, spoofing, and unauthorized access to systems relying on axTLS for certificate validation.
If you can’t patch tonight, do this now.
If immediate upgrade is not possible, restrict the use of small public exponents in certificates and consider disabling or limiting the acceptance of untrusted certificates. Monitor for suspicious certificate activity and consider additional certificate validation checks in the application layer.
Patch, then assume compromise.
Upgrade to a version of axTLS where the PKCS#1 v1.5 signature verification properly rejects excess data after the hash value. Ensure that the signature verification code strictly adheres to the PKCS#1 v1.5 specification and validates the entire structure of the signature.
No public exploits tracked yet. Mallory keeps watching.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.