MongoDB version 2.0.1 is a minor patch release following closely after version 2.0.0, both serving as legacy driver emulation layers atop the mongodb-core driver. For developers relying on the older, familiar MongoDB driver API, these versions offer a bridge to more modern MongoDB deployments. The core functionality remains consistent between the two versions, focusing on facilitating interaction with MongoDB databases using the legacy driver style.
The primary difference lies in the dependency management for the underlying mongodb-core. Version 2.0.0 specifically requires mongodb-core version 1.0.0, while version 2.0.1 utilizes a more flexible dependency specification, "mongodb-core":"~1.0". This means 2.0.1 is compatible with mongodb-core versions 1.0.x, potentially including bug fixes and minor enhancements introduced in those patch releases.
Both versions share the same set of development dependencies like bson, jsdoc, integra, and optimist, utilized for tasks such as BSON serialization, documentation generation, integration testing, and argument parsing respectively. This consistent development environment suggests a focus on maintaining code quality and a stable developer workflow. The library is licensed under Apache 2.0, encouraging broad usage and modification. Ultimately, the choice between 2.0.0 and 2.0.1 depends on the desired level of control over mongodb-core versioning, with 2.0.1 offering potentially broader compatibility within the 1.0.x range.
All the vulnerabilities related to the version 2.0.1 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.
