Description
A memory management flaw in the MongoDB C Driver's handling of compressed responses may cause the client library to hold on to memory that is never released. An unauthenticated party that controls the database endpoint a client application connects to may cause repeated, unbounded memory growth in that application, which may result in the application becoming unavailable. No credentials, transport security settings, or user interaction are required.
Mitigation
Minimal update. May introduce new vulnerabilities or breaking changes.
|
 debian 12 | | =1.23.1-1 || =1.23.1-1+deb12u1 || =1.23.1-1+deb12u2 || =1.23.1-1+deb12u3 || =1.24.1-1 || =1.24.2-1 || =1.24.3-1 || =1.24.4-1 || =1.25.0-1 || =1.25.1-1 || =1.25.2-1 || =1.25.4-1 || =1.25.4-1.1~exp1 || =1.26.0-1 || =1.26.0-1.1 || =1.26.0-1.1~exp1 || =1.26.1-1 || =1.26.2-1 || =1.27.0-1 || =1.27.1-1 || =1.27.2-1 || =1.27.3-1 || =1.27.4-1 || =1.27.5-1 || =1.27.6-1 || =1.28.0-1 || =1.28.1-1 || =1.29.0-1 || =1.29.1-1 || =1.29.2-1 || =1.30.0-1 || =1.30.1-1 || =1.30.2-1 || =1.30.3-1 || =1.30.4-1 || =2.0.2-1 || =2.1.0-1 || =2.1.1-1 || =2.1.2-1 || =2.2.0-1 || =2.2.1-1 || =2.2.2-1 || =2.2.3-1 || =2.2.4-1 || =2.3.0-1 || =2.3.1-1 || =2.3.2-1 || =2.3.3-1 || =2.4.0-1 || =2.5.0-1 || =2.5.1-1 || =2.5.2-1 || =2.5.3-1 || =2.5.5-1 || =2.5.6-1 || =2.5.7-1 || =2.5.8-1 | - |
 debian 13 | | =1.30.4-1 || =1.30.4-1+deb13u1 || =1.30.4-1+deb13u2 || =1.30.4-1+deb13u3 || =2.0.2-1 || =2.1.0-1 || =2.1.1-1 || =2.1.2-1 || =2.2.0-1 || =2.2.1-1 || =2.2.2-1 || =2.2.3-1 || =2.2.4-1 || =2.3.0-1 || =2.3.1-1 || =2.3.2-1 || =2.3.3-1 || =2.4.0-1 || =2.5.0-1 || =2.5.1-1 || =2.5.2-1 || =2.5.3-1 || =2.5.5-1 || =2.5.6-1 || =2.5.7-1 || =2.5.8-1 | - |
 debian 14 | | =1.30.4-1 || =2.0.2-1 || =2.1.0-1 || =2.1.1-1 || =2.1.2-1 || =2.2.0-1 || =2.2.1-1 || =2.2.2-1 || =2.2.3-1 || =2.2.4-1 || =2.3.0-1 || =2.3.1-1 || =2.3.2-1 || =2.3.3-1 || =2.4.0-1 || =2.5.0-1 || =2.5.1-1 || =2.5.2-1 || =2.5.3-1 || =2.5.5-1 || =2.5.6-1 || =2.5.7-1 || >=0 <2.5.8-1 | 2.5.8-1 |