mongodb 2.0.15 represents a minor update over its predecessor, version 2.0.14, primarily focusing on enhancements and bug fixes within its core dependencies. Both versions serve as a legacy driver emulation layer bridging older MongoDB driver APIs with the more modern mongodb-core. A key difference lies in the mongodb-core dependency. Version 2.0.15 upgrades to mongodb-core version 1.1.11, while 2.0.14 relies on version 1.1.9. This seemingly small change likely incorporates crucial improvements, bug fixes, and performance optimizations delivered within the updated core library.
Developers utilizing mongodb should recognize that this focuses on legacy driver compatibility. It eases transitions for applications built on older driver versions. The consistent maintenance reflects a commitment to stability and backwards compatibility. The enduring dependencies like readable-stream and various development tools ensure a robust development and testing environment. The shift to the newer mongodb-core means developers get access to potential benefits without making large code modifications. This careful update strategy is beneficial for applications needing older driver features or gradually migrating to modern alternatives. Developers should check mongodb-core release for specifics on the updates. Release dates show active maintenance in early 2015.
All the vulnerabilities related to the version 2.0.15 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.
