MongoDB version 2.0.6 represents a minor update to the 2.x legacy driver emulation layer, building upon the previous stable version 2.0.5. The core difference lies in its dependency on mongodb-core, the underlying driver implementation. Version 2.0.6 upgrades this dependency to version "1.1.1", while version 2.0.5 relied on a version within the "~1.0" range. This mongodb-core update likely contained bug fixes, performance improvements, and potentially new features at the lower level, all of which are indirectly inherited by users of mongodb. This is particularly significant for developers seeking stability and reliability, as updated core dependencies often address critical issues. Both versions share identical dependencies for readable-stream at version "1.0.31".
The developer tools, including bson, jsdoc, rimraf (present only in 2.0.6), semver (present only in 2.0.6), integra, and optimist, primarily serve for testing, documentation, and development workflows and don't directly impact runtime behavior for users integrating the library into their applications. The introduction of rimraf and semver in the newer version suggests possible changes to the build process and dependency management strategy. Both versions maintain the same license (Apache 2.0), repository, and author, indicating a continuity in project governance. Released approximately two weeks apart, these versions highlight the ongoing refinement of the mongodb legacy driver during that period. Developers should especially evaluate the changelog related to mongodb-core 1.1.1 to determine if upgrading from 2.0.5 to 2.0.6 addresses specific compatibility or functionality requirements within their MongoDB implementations.
All the vulnerabilities related to the version 2.0.6 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.
