MongoDB version 2.0.12 represents a minor update to the widely used Node.js driver, building upon the foundation of version 2.0.11. Both versions serve as legacy driver emulation layers, leveraging mongodb-core (version 1.1.6) for core functionality and relying on readable-stream (version 1.0.31) for stream processing. Examining the dependencies and development dependencies reveals no changes between the two versions; they share the same versions of bson, gleak, jsdoc, rimraf, semver, integra, optimist, and mongodb-version-manager.
The key difference lies in the release date. Version 2.0.12 was released on December 22, 2014, a few days after version 2.0.11 released on December 18, 2014. Given identical dependencies, it is likely that version 2.0.12 includes bug fixes, performance enhancements, or minor internal adjustments not reflected in dependency bumps.
For developers using the mongodb package, upgrading from 2.0.11 to 2.0.12 is recommended. Although the changes are subtle, it benefits from the latest refinements and potential stability improvements. As both versions share a common base, the upgrade is usually seamless. Review the changelog or release notes (if available) for more specific details on the exact changes implemented in version 2.0.12. This attention to detail ensures that you're working with the most reliable and optimized version of the driver for your MongoDB interactions within your Node.js applications.
All the vulnerabilities related to the version 2.0.12 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.
