MongoDB version 2.0.14 is a minor update to the 2.0.x series, building upon the legacy driver emulation layer that leverages mongodb-core. Comparing it to its predecessor, version 2.0.13, the most notable change lies in the updated dependency on mongodb-core, moving from version 1.1.8 to 1.1.9. This seemingly small increment in the core driver likely includes bug fixes, performance improvements, and potentially new features within the underlying database interaction layer.
For developers using the MongoDB library, this update translates to a potentially more stable and efficient experience when connecting to and interacting with MongoDB databases. Although the API remains largely the same, benefiting from the stable base provided by the legacy emulation layer ensures continued compatibility and familiar usage patterns. The update is focused on the underlying connection with the database.
Developers should upgrade to version 2.0.14 to take advantage of these improvements baked into mongodb-core, addressing potential vulnerabilities or inefficiencies present in the previous version. While the other dependencies like bson, gleak, jsdoc, rimraf, semver, integra, optimist, and mongodb-version-manager remain consistent, confirming the stability and focus of this release. Remember to audit the changes in mongodb-core 1.1.9 for a deeper understanding of the specific enhancements included.
All the vulnerabilities related to the version 2.0.14 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.
