OpenSC up to 0.19.x/0.20.0-rc3 CAC Certificate libopensc/card-cac1.c memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.5 | $0-$5k | 0.00 |
Summary
A vulnerability described as critical has been identified in OpenSC up to 0.19.x/0.20.0-rc3. Affected by this vulnerability is an unknown functionality of the file libopensc/card-cac1.c of the component CAC Certificate Handler. Such manipulation leads to memory corruption. This vulnerability is traded as CVE-2019-19481. An attack has to be approached locally. There is no exploit available.
Details
A vulnerability was found in OpenSC up to 0.19.x/0.20.0-rc3. It has been rated as critical. Affected by this issue is an unknown code block of the file libopensc/card-cac1.c of the component CAC Certificate Handler. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. CVE summarizes:
An issue was discovered in OpenSC through 0.19.0 and 0.20.x through 0.20.0-rc3. libopensc/card-cac1.c mishandles buffer limits for CAC certificates.
The weakness was shared 12/01/2019. This vulnerability is handled as CVE-2019-19481 since 12/01/2019. The attack needs to be approached locally. No form of authentication is required for exploitation. There are known technical details, but no exploit is available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-146563 and VDB-146562 are related to this item. Once again VulDB remains the best source for vulnerability data.
Product
Name
Version
License
Website
- Product: https://github.com/OpenSC/OpenSC/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.5
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.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: 🔍
Physical: Partially
Local: Yes
Remote: No
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
12/01/2019 🔍12/01/2019 🔍
12/04/2019 🔍
03/05/2024 🔍
Sources
Product: github.comAdvisory: b75c002cfb1fd61cd20ec938ff4937d7b1a94278
Status: Not defined
CVE: CVE-2019-19481 (🔍)
GCVE (CVE): GCVE-0-2019-19481
GCVE (VulDB): GCVE-100-146564
See also: 🔍
Entry
Created: 12/04/2019 07:59Updated: 03/05/2024 14:25
Changes: 12/04/2019 07:59 (36), 12/04/2019 08:04 (17), 03/05/2024 14:22 (5), 03/05/2024 14:25 (1)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.