Memory exhaustion via abandoned far-future read-concern waiters in disaggregated storage
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 | MongoDB Server | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Mongodb | Mongodb Server |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.479% probability within 30 days)
Key SSVC decision points have not yet been added.
| Link | Providers |
|---|---|
| https://jira.mongodb.org/browse/SERVER-138119 |
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Mongodb
Mongodb mongodb Server |
|
| Vendors & Products |
Mongodb
Mongodb mongodb Server |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A replica-set database server node does not limit or reclaim internal wait records created while handling a client-supplied read option that names a point in time the node will never reach. A party with network access and no credentials can cause these records to accumulate without bound and persist after the requests end, which may make the server run out of memory and become unavailable. | |
| Title | Memory exhaustion via abandoned far-future read-concern waiters in disaggregated storage | |
| Weaknesses | CWE-770 | |
| References |
| |
| Metrics |
cvssV3_1
|