axTLS up to 2.1.3 ASN.1 x509.c sig_verify Certificate signature verification
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, was found in axTLS up to 2.1.3. This impacts the function sig_verify of the file x509.c of the component ASN.1 Handler. Executing a manipulation as part of Certificate can lead to signature verification.
This vulnerability is registered as CVE-2018-16149. It is possible to launch the attack remotely. No exploit is available.
Details
A vulnerability was found in axTLS up to 2.1.3. It has been declared as problematic. This vulnerability affects the function sig_verify of the file x509.c of the component ASN.1 Handler. The manipulation as part of a Certificate leads to a signature verification vulnerability. The CWE definition for the vulnerability is CWE-347. The product does not verify, or incorrectly verifies, the cryptographic signature for data. As an impact it is known to affect availability. CVE summarizes:
In sig_verify() in x509.c in axTLS version 2.1.3 and before, the PKCS#1 v1.5 signature verification blindly trusts the declared lengths in the ASN.1 structure. Consequently, when small public exponents are being used, a remote attacker can generate purposefully crafted signatures (and put them on X.509 certificates) to induce illegal memory access and crash the verifier.
The bug was discovered 11/05/2018. The weakness was published 11/07/2018 (Website). The advisory is shared for download at sourceforge.net. This vulnerability was named CVE-2018-16149 since 08/29/2018. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are known technical details, 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.
Similar entries are available at VDB-126521 and VDB-126522. VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.8VulDB Meta Temp Score: 4.8
VulDB Base Score: 3.7
VulDB Temp Score: 3.7
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
Class: Signature verificationCWE: 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-16149 (🔍)
GCVE (CVE): GCVE-0-2018-16149
GCVE (VulDB): GCVE-100-126520
See also: 🔍
Entry
Created: 11/08/2018 07:45Updated: 06/05/2023 07:10
Changes: 11/08/2018 07:45 (60), 04/10/2020 16:18 (1), 06/05/2023 07:10 (4)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.