Description
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HWeakness enumeration
Affected software
| Vendor | Product | Versions |
|---|---|---|
| MongoDB Inc. | MongoDB Server | >= 5.0, < 5.0.4; >= 4.4, <= 4.4.28; >= 4.2, < 4.2.16 |
| mongodb | mongodb | >= 5.0, < 5.0.4; >= 4.4, <= 4.4.28; >= 4.2, < 4.2.16 |
References
- https://jira.mongodb.org/browse/SERVER-58203Issue Tracking, Patch, Vendor Advisory
- https://jira.mongodb.org/browse/SERVER-59299Issue Tracking, Patch, Vendor Advisory
- https://jira.mongodb.org/browse/SERVER-60218Issue Tracking, Patch, Vendor Advisory
- https://security.netapp.com/advisory/ntap-20220609-0005/Third Party Advisory
- https://jira.mongodb.org/browse/SERVER-58203Issue Tracking, Patch, Vendor Advisory
- https://jira.mongodb.org/browse/SERVER-59299Issue Tracking, Patch, Vendor Advisory
- https://jira.mongodb.org/browse/SERVER-60218Issue Tracking, Patch, Vendor Advisory
- https://security.netapp.com/advisory/ntap-20220609-0005/Third Party Advisory
Timeline
- Published
- Apr 12, 2022
- Last modified
- Jun 17, 2026
- NVD status
- Modified