Selmelc

**Name of the Vulnerable Software and Affected Versions** libbson versions prior to 1.27.5 MongoDB Server v8.0 versions prior to 8.0.1 MongoDB Server v7.0 versions prior to 7.0.16 **Description** The various `bson append` functions in the MongoDB C driver library may be susceptible to buffer overflow when performing operations that could result in a final BSON document which exceeds the maximum allowable size (INT32 MAX), resulting in a segmentation fault and possible application crash. **Recommendations** For libbson versions prior to 1.27.5, update to version 1.27.5 or later. For MongoDB Server v8.0 versions prior to 8.0.1, update to version 8.0.1 or later. For MongoDB Server v7.0 versions prior to 7.0.16, update to version 7.0.16 or later. As a temporary workaround, consider disabling the `bson append` functions until a patch is available. Restrict access to the vulnerable `bson append` functions to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** libbson versions prior to 1.27.1 **Description** The issue is related to a potential buffer overflow in the `bson string append` function, which may lead to memory corruption of neighbouring heap memory. This occurs when the function attempts to allocate too small of a buffer. **Recommendations** For versions prior to 1.27.1, update to version 1.27.1 or later to resolve the issue.

**Name of the Vulnerable Software and Affected Versions** MongoDB C Driver versions prior to 1.25.0 **Description** The issue is related to the `bson utf8 validate()` function in the MongoDB C Driver, which can cause an infinite loop when called with certain inputs. This may allow a remote attacker to cause a denial of service. **Recommendations** For MongoDB C Driver versions prior to 1.25.0, update to version 1.25.0 or later to resolve the issue. As a temporary workaround, consider restricting the use of the `bson utf8 validate()` function until a patch is available.

**Name of the Vulnerable Software and Affected Versions** curl versions prior to 8.4.0 **Description** The issue is related to the handling of HTTP headers by the curl utility. When curl retrieves an HTTP response, it stores the incoming headers so that they can be accessed later via the libcurl headers API. However, curl did not have a limit on the size or quantity of headers it would accept in a response, allowing a malicious server to stream an endless series of headers and eventually cause curl to run out of heap memory. This can lead to a denial of service. A malicious server can exploit this issue, and it is estimated that a significant number of devices may be affected. **Recommendations** For versions prior to 8.4.0, update to curl version 8.4.0 to resolve the issue. As a temporary workaround, consider restricting the size and quantity of HTTP headers accepted by curl to minimize the risk of exploitation.