Version 2.0.8 of the mongodb npm package represents a minor update over its predecessor, version 2.0.7. Both versions serve as a legacy driver emulation layer built on top of the mongodb-core package, providing an interface for interacting with MongoDB databases. They share identical core dependencies, namely mongodb-core version 1.1.2 and readable-stream version 1.0.31, maintaining a consistent foundation for database operations. Furthermore, the development dependencies remain consistent, encompassing tools like bson, jsdoc, rimraf, semver, integra, and optimist, suggesting stability in the development and testing pipeline.
The principal distinction between the two versions lies in their release date. Version 2.0.8 was published on November 28, 2014, approximately a week after version 2.0.7, which was released on November 20, 2014. Given that the dependencies and development dependencies are identical, the update likely encompasses bug fixes, performance tweaks, or minor compatibility adjustments that don't necessitate changes to the core API or development tools.
For developers considering using this library, it's crucial to understand that it's a legacy driver emulation layer. The provided data does not specify the exact changes, users should consult the commit historyor release notes between the version to evaluate the impact according to their specific context. It is recommended to prefer the 2.0.8 over the 2.0.7 given the small time frame.
All the vulnerabilities related to the version 2.0.8 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.
