Vulnerability Details : CVE-2021-20330
An attacker with basic CRUD permissions on a replicated collection can run the applyOps command with specially malformed oplog entries, resulting in a potential denial of service on secondaries. This issue affects MongoDB Server v4.0 versions prior to 4.0.27; MongoDB Server v4.2 versions prior to 4.2.16; MongoDB Server v4.4 versions prior to 4.4.9.
Vulnerability category: Denial of service
Products affected by CVE-2021-20330
- cpe:2.3:a:mongodb:mongodb:*:*:*:*:*:*:*:*
- cpe:2.3:a:mongodb:mongodb:*:*:*:*:*:*:*:*
- cpe:2.3:a:mongodb:mongodb:*:*:*:*:*:*:*:*
Threat overview for CVE-2021-20330
Top countries where our scanners detected CVE-2021-20330
Top open port discovered on systems with this issue
27017
IPs affected by CVE-2021-20330 11,681
Threat actors abusing to this issue?
Yes
Find out if you* are
affected by CVE-2021-20330!
*Directly or indirectly through your vendors, service providers and 3rd parties.
Powered by
attack surface intelligence
from SecurityScorecard.
Exploit prediction scoring system (EPSS) score for CVE-2021-20330
0.09%
Probability of exploitation activity in the next 30 days
EPSS Score History
~ 37 %
Percentile, the proportion of vulnerabilities that are scored at or less
CVSS scores for CVE-2021-20330
Base Score | Base Severity | CVSS Vector | Exploitability Score | Impact Score | Score Source | First Seen |
---|---|---|---|---|---|---|
4.0
|
MEDIUM | AV:N/AC:L/Au:S/C:N/I:N/A:P |
8.0
|
2.9
|
NIST | |
6.5
|
MEDIUM | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
2.8
|
3.6
|
MongoDB, Inc. | |
6.5
|
MEDIUM | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
2.8
|
3.6
|
NIST |
CWE ids for CVE-2021-20330
-
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.Assigned by:
- cna@mongodb.com (Secondary)
- nvd@nist.gov (Primary)
References for CVE-2021-20330
-
https://jira.mongodb.org/browse/SERVER-36263
[SERVER-36263] Bypassing operation validation in applyOps should require special privilege - MongoDB JiraIssue Tracking;Patch;Vendor Advisory
Jump to