MongoDB version 2.0.20 represents a minor update to the 2.0.x series, building upon the previous stable version 2.0.19 of the legacy driver emulation layer. Both versions maintain the same core function: providing an emulation layer on top of mongodb-core, allowing for smoother transitions and continued compatibility with older MongoDB driver APIs.
The primary difference lies in the updated dependency on the low-level driver mongodb-core. Version 2.0.20 upgrades this dependency from 1.1.14 to 1.1.15. While seemingly a small increment, this update to mongodb-core likely includes bug fixes, performance improvements, or minor feature enhancements within the core database interaction logic. Developers should consult the mongodb-core changelog for specific details on these internal changes.
Both versions share the same development dependencies, including tools for testing, documentation generation (jsdoc), and cleaning (rimraf). They also utilize the same testing utilities like integra, optimist, mongodb-tools, and mongodb-version-manager, indicating a consistent development and testing process.
For developers using the mongodb package, upgrading from 2.0.19 to 2.0.20 should be relatively seamless, provided mongodb-core's update doesn't introduce any unforeseen compatibility issues in very specific use cases of the underlying database interaction. Careful consideration of the mongodb-core changelog is advised. Otherwise, developers can expect mainly performance improvements and potentially some bug-fixes.
All the vulnerabilities related to the version 2.0.20 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.
