Heap corruption via duplicate masterKey fields in MongoDB libmongocrypt
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| MongoDB | libmongocrypt | unaffected |
|
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Mongodb | Libmongocrypt |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.261% probability within 30 days)
| Link | Providers |
|---|---|
| https://jira.mongodb.org/browse/MONGOCRYPT-964 |
|
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:mongodb:libmongocrypt:*:*:*:*:*:*:*:* |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Mongodb
Mongodb libmongocrypt |
|
| Vendors & Products |
Mongodb
Mongodb libmongocrypt |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Improper state management in MongoDB libmongocrypt can cause provider-specific data to be treated as an incompatible type when cleaning up a key document containing duplicate masterKey fields. An authenticated actor who can modify key vault documents, or a server that returns such a key document, can cause invalid memory access and invalid frees in the client process. This can terminate the application or corrupt process memory. | |
| Title | Heap corruption via duplicate masterKey fields in MongoDB libmongocrypt | |
| Weaknesses | CWE-843 | |
| References |
| |
| Metrics |
cvssV3_1
|