MongoDB's version 2.0.22 offers a subtle but crucial update over its predecessor, 2.0.21. Both versions serve as a legacy driver emulation layer built on top of the mongodb-core, providing developers with a familiar interface while leveraging the underlying core functionality. The key difference lies in the updated dependency on mongodb-core, moving from version 1.1.16 to 1.1.17. While seemingly minor, this update likely incorporates bug fixes, performance enhancements, or new features within the core driver, indirectly benefiting developers using the mongodb package.
Both versions share identical development dependencies including crucial tools for testing and documentation, such as bson, gleak, jsdoc, rimraf, semver, integra, optimist, mongodb-tools, and mongodb-version-manager, ensuring a consistent development experience. The license remains Apache 2.0, indicating permissive usage rights.
Developers considering an upgrade should evaluate the changelog of mongodb-core 1.1.17 to understand the particular benefits of the updated core. While the core dependencies have seen an update, developers can expect consistent usage when utilizing mongodb due to the shared development dependencies. While upgrading from 2.0.21 to 2.0.22, consider testing the application in a staging environment to identify any unexpected behavior arising from the updated underlying core driver. The 2.0.22 version was released on March 16, 2015, roughly ten days later than the 2.0.21 release.
All the vulnerabilities related to the version 2.0.22 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.
