It may be possible to have an extremely long aggregation pipeline in conjunction with a specific stage/operator and cause a stack overflow due to the size of the stack frames used by that stage. If an attacker could cause such an aggregation to occur, they could maliciously crash MongoDB in a DoS attack. This vulnerability affects MongoDB Server v4.4 versions prior to and including 4.4.28, MongoDB Server v5.0 versions prior to 5.0.4 and MongoDB Server v4.2 versions prior to 4.2.16.
Workaround: >= v4.2.16 users and all v4.4 users can add the --setParameter internalPipelineLengthLimit=50 instead of the default 1000 to mongod at startup to prevent a crash.
References
Link | Resource |
---|---|
https://jira.mongodb.org/browse/SERVER-58203 | Issue Tracking Patch Vendor Advisory |
https://jira.mongodb.org/browse/SERVER-59299 | Issue Tracking Patch Vendor Advisory |
https://jira.mongodb.org/browse/SERVER-60218 | Issue Tracking Patch Vendor Advisory |
https://security.netapp.com/advisory/ntap-20220609-0005/ | Third Party Advisory |
History
No history.
MITRE Information
Status: PUBLISHED
Assigner: mongodb
Published: 2022-04-12T00:00:00
Updated: 2024-02-23T16:04:43.143Z
Reserved: 2021-05-05T00:00:00
Link: CVE-2021-32040
JSON object: View
NVD Information
Status : Modified
Published: 2022-04-12T15:15:07.707
Modified: 2024-02-23T16:15:46.120
Link: CVE-2021-32040
JSON object: View
Redhat Information
No data.