MongoDB version 2.0.2 represents a minor update to the 2.0.x series, building upon the legacy driver emulation layer built on top of the mongodb-core driver. Both versions, 2.0.1 and 2.0.2, maintain the same core dependencies, relying on mongodb-core version ~1.0 and readable-stream version 1.0.31. This signifies that the fundamental architecture and streaming capabilities remain consistent between the two releases.
The primary difference lies in the devDependencies section, specifically the integra version. Version 2.0.1 uses integra 0.1.6, while version 2.0.2 updates this to integra 0.1.7. Integra is likely used for integration testing, suggesting that version 2.0.2 includes improved or expanded integration tests compared to the previous version. Developers might find this relevant if they're contributing to the library or need highly robust integration testing. The release date also indicates a very small time to market between the two, likely indicating a bug fix or very small feature updates when comparing the two versions.
For developers already using version 2.0.1, upgrading to 2.0.2 should be straightforward, as the core dependencies haven't changed. The updated integra version implies enhanced stability and potentially better test coverage. However, the mongodb legacy driver is not actively maintained, consider migrating to the latest maintained version of the driver.
All the vulnerabilities related to the version 2.0.2 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.
