MongoDB version 2.0.3 represents a minor iteration over its predecessor, 2.0.2, within the legacy driver emulation layer designed to operate on top of mongodb-core. Both versions share a common foundation, maintaining identical dependencies including mongodb-core ("~1.0") for core MongoDB functionality and readable-stream ("1.0.31") for handling streams. The development dependencies, crucial for testing and documentation, also remain consistent, featuring bson ("~0.2") for BSON serialization, jsdoc ("3.3.0-alpha9") for API documentation generation, integra ("0.1.7") for integration testing, and optimist ("0.6.1") for command-line argument parsing. The licensing (Apache 2.0), repository URL, and author ("Christian Kvalheim") details are also unchanged, indicating continuity in the project's management and distribution. The key difference between the two versions lies in their release date. Version 2.0.3 was released on October 14, 2014, while 2.0.2 came out on October 8, 2014. This timestamp difference suggests that 2.0.3 likely incorporates minor bug fixes, performance tweaks, or refinements that didn't warrant a major or minor version bump. Also, since the dependencies are exactly the same, upgrading from 2.0.2 to 2.0.3 should be relatively safe and straightforward, minimizing the risk of breaking changes for developers already using the library. Users should still consult the release notes if available to confirm the exact nature of the improvements and ensure compatibility within their specific application context.
All the vulnerabilities related to the version 2.0.3 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.
