MongoDB version 2.0.39 represents a minor update over its predecessor, version 2.0.38, within the established 2.0.x series of the MongoDB Node.js driver. Both versions retain the same core philosophy: providing a legacy driver emulation layer built atop the mongodb-core module. This means developers already familiar with older versions of the driver can transition more easily.
The most significant change lies in the updated dependency on mongodb-core. Version 2.0.39 depends on mongodb-core@1.2.6, while the prior version used mongodb-core@1.2.5. This subtle shift likely includes bug fixes, performance improvements, or minor feature enhancements within the core MongoDB driver logic. Developers should consult the mongodb-core changelog for a granular view of changes implemented between those specific versions.
While both versions share identical developer dependencies, including tools for linting, testing, and documentation (such as co, bson, jsdoc, and integra), the core API and overall approach to interacting with MongoDB databases remain consistent. Therefore, upgrading from 2.0.38 to 2.0.39 should generally be a seamless process, primarily delivering benefits related to underlying performance and bug fixes provided by the updated mongodb-core dependency. The update signifies a commitment to ongoing maintenance and refinement within the stable 2.0.x branch. Consider this an incremental upgrade, focusing on increased stability and reliability through core component improvements.
All the vulnerabilities related to the version 2.0.39 of the package
Denial of Service in mongodb
Versions of mongodb prior to 3.1.13 are vulnerable to Denial of Service. The package fails to properly catch an exception when a collection name is invalid and the DB does not exist, crashing the application.
Upgrade to version 3.1.13 or later.
Deserialization of Untrusted Data in bson
Incorrect parsing of certain JSON input may result in js-bson not correctly serializing BSON. This may cause unexpected application behaviour including data disclosure.
Deserialization of Untrusted Data in bson
All versions of bson before 1.1.4 are vulnerable to Deserialization of Untrusted Data. The package will ignore an unknown value for an object's _bsontype, leading to cases where an object is serialized as a document rather than the intended BSON type.
DLL Injection in kerberos
Version of kerberos prior to 1.0.0 are vulnerable to DLL Injection. The package loads DLLs without specifying a full path. This may allow attackers to create a file with the same name in a folder that precedes the intended file in the DLL path search. Doing so would allow attackers to execute arbitrary code in the machine.
Upgrade to version 1.0.0 or later.
