The mongodb npm package saw a minor version bump from 2.0.12 to 2.0.13, representing incremental improvements to this legacy driver emulation layer for MongoDB built atop mongodb-core. This update, released on January 8, 2015, follows the previous version's release on December 22, 2014.
A key difference lies in the updated dependency on mongodb-core, moving from version 1.1.6 to 1.1.8. This suggests bug fixes including potential enhancements within the core MongoDB driver implementation, which directly benefits developers employing the mongodb package. While the readable-stream dependency remained consistent at version 1.0.31, the updated mongodb-core is the primary change to take note of.
For developers utilizing the mongodb package, this upgrade signifies potentially improved stability and performance inherited from the underlying mongodb-core update. Before upgrading, it's advisable to review the changelog or release notes for mongodb-core version 1.1.8 to understand specific fixes or features incorporated. The remaining development dependencies, including tools for testing, documentation generation, and code analysis, remain unchanged, signalling a focused update on the core driver interaction rather than broader toolchain modifications. This version continued to be licensed under Apache 2.0.
All the vulnerabilities related to the version 2.0.13 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.
