MongoDB version 2.0.16 represents a minor update in the 2.0.x series of the legacy driver emulation layer built upon mongodb-core. Released on February 16, 2015, it follows version 2.0.15, which was released roughly two weeks prior, on February 2, 2015. The core difference between these versions lies in the updated dependency on mongodb-core. Version 2.0.16 relies on mongodb-core version 1.1.12, while the predecessor, 2.0.15, depends on mongodb-core version 1.1.11.
For developers using the MongoDB Node.js driver, this implies potential bug fixes, performance improvements, and new features within the underlying mongodb-core library. While the high-level API remains consistent, this dependency update is crucial for ensuring compatibility, stability, and optimal performance when interacting with MongoDB databases. Both versions share the same set of development dependencies, including tools for BSON handling, leak detection, documentation generation, and testing, indicating a focus on maintaining code quality and developer experience across these minor releases. The mongodb-legacy repository on GitHub serves as the central source for accessing the code and contributing to the project. Developers are encouraged to upgrade to the latest version within the 2.0.x series to benefit from the underlying improvements in the core MongoDB driver functionalities.
All the vulnerabilities related to the version 2.0.16 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.
Prototype Pollution in minimist
Affected versions of minimist are vulnerable to prototype pollution. Arguments are not properly sanitized, allowing an attacker to modify the prototype of Object, causing the addition or modification of an existing property that will exist on all objects.
Parsing the argument --__proto__.y=Polluted adds a y property with value Polluted to all objects. The argument --__proto__=Polluted raises and uncaught error and crashes the application.
This is exploitable if attackers have control over the arguments being passed to minimist.
Upgrade to versions 0.2.1, 1.2.3 or later.
Prototype Pollution in minimist
Minimist prior to 1.2.6 and 0.2.4 is vulnerable to Prototype Pollution via file index.js, function setKey() (lines 69-95).
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.
