MatrixSSL X.509 Certificate Verification crypto/pubkey/rsa_pub.c pubRsaDecryptSignedElementExt memory corruption
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
8.0 | $0-$5k | 0.00 |
A vulnerability, which was classified as critical, was found in MatrixSSL. This affects the function pubRsaDecryptSignedElementExt
of the file crypto/pubkey/rsa_pub.c of the component X.509 Certificate Verification. The manipulation as part of a Certificate leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
pubRsaDecryptSignedElementExt in MatrixSSL, as used in Inside Secure TLS Toolkit, through 4.0.2 Open has a stack-based buffer overflow during X.509 certificate verification because of missing validation in psRsaDecryptPubExt in crypto/pubkey/rsa_pub.c.
The bug was discovered 02/14/2019. The weakness was presented 04/08/2019. This vulnerability is uniquely identified as CVE-2019-10914 since 04/08/2019. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 53 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.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Affected
- Inside Secure TLS Toolkit up to 4.0.2
Product
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.0VulDB Meta Temp Score: 8.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
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: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
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: 🔍
Upgrade: github.com
Timeline
02/14/2019 🔍04/08/2019 🔍
04/08/2019 🔍
04/09/2019 🔍
08/27/2023 🔍
Sources
Advisory: 26Status: Not defined
CVE: CVE-2019-10914 (🔍)
GCVE (CVE): GCVE-0-2019-10914
GCVE (VulDB): GCVE-100-133113
Entry
Created: 04/09/2019 07:10 AMUpdated: 08/27/2023 11:08 AM
Changes: 04/09/2019 07:10 AM (56), 05/27/2020 11:14 AM (1), 08/27/2023 11:08 AM (5)
Complete: 🔍
Cache ID: 18:22E:40
No comments yet. Languages: en.
Please log in to comment.