Version 2.0.11 of the MongoDB npm package, succeeding version 2.0.10, offers subtle yet potentially important refinements for developers utilizing the legacy driver emulation layer. Both versions maintain identical core dependencies, relying on "mongodb-core" version 1.1.6 and "readable-stream" version 1.0.31. Similarly, the development dependencies for tasks such as BSON handling, memory leak detection ("gleak"), documentation generation (JSDoc), and package cleanup ("rimraf") remain consistent. Development tools like "semver" for version management, "integra" for integration testing, "optimist" for argument parsing, and "mongodb-version-manager" are unchanged.
The key distinction lies solely in the release date. Version 2.0.11 was published on December 18, 2014, at 21:55:36.638Z, while version 2.0.10 appeared earlier that same day at 09:06:33.988Z. This suggests that version 2.0.11 likely incorporates minor bug fixes, documentation updates, or very targeted improvements identified and addressed within that 12-hour window. Given identical dependency specifications, developers already using 2.0.10 should carefully evaluate the changelog (if available) or release notes (if any) alongside this version change to ascertain if the contained fixes specifically address their use cases. Without official guidance and lacking explicit details, this update is minor, but may address a critical issue for some users. Developers should consider testing the new version in a non-production environment before deploying widespread upgrades.
All the vulnerabilities related to the version 2.0.11 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.
