axTLS up to 2.1.3 PKCS #1 x509.c sig_verify Certificate Impersonation signature verification
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in axTLS up to 2.1.3 and classified as critical. Affected is the function sig_verify of the file x509.c of the component PKCS #1 Handler. The manipulation as part of Certificate leads to signature verification (Impersonation).
This vulnerability is documented as CVE-2018-16150. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability was found in axTLS up to 2.1.3. It has been rated as critical. This issue affects the function sig_verify of the file x509.c of the component PKCS #1 Handler. The manipulation as part of a Certificate leads to a signature verification vulnerability (Impersonation). Using CWE to declare the problem leads to CWE-347. The product does not verify, or incorrectly verifies, the cryptographic signature for data. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
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.
The bug was discovered 11/05/2018. The weakness was released 11/07/2018 (Website). The advisory is shared at sourceforge.net. The identification of this vulnerability is CVE-2018-16150 since 08/29/2018. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 2 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Entries connected to this vulnerability are available at VDB-126520 and VDB-126522. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.6VulDB Meta Temp Score: 6.6
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.9
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Name: ImpersonationClass: Signature verification / Impersonation
CWE: CWE-347 / CWE-345
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Patch: github.com
Timeline
08/29/2018 🔍11/05/2018 🔍
11/07/2018 🔍
11/07/2018 🔍
11/08/2018 🔍
06/05/2023 🔍
Sources
Advisory: 5efe2947ab45e81d84b5f707c51d1c64be52f36cStatus: Not defined
Confirmation: 🔍
CVE: CVE-2018-16150 (🔍)
GCVE (CVE): GCVE-0-2018-16150
GCVE (VulDB): GCVE-100-126521
See also: 🔍
Entry
Created: 11/08/2018 07:45Updated: 06/05/2023 07:15
Changes: 11/08/2018 07:45 (62), 04/10/2020 16:20 (1), 06/05/2023 07:15 (4)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.