MongoDB version 2.0.5 represents a minor update to the 2.0.x series of the legacy MongoDB driver for Node.js, building upon the foundation established in version 2.0.4. Both versions maintain a consistent API, offering developers a legacy emulation layer on top of the mongodb-core driver. This allows for continued compatibility with older applications expecting a specific driver interface while leveraging the performance improvements and advancements in the underlying mongodb-core module.
A key aspect for developers is the stability and reliability of this legacy driver. Both versions share identical core dependencies, relying on mongodb-core for database interactions and readable-stream for stream handling. The development dependencies, including bson for BSON handling, jsdoc for documentation, integra for integration testing, and optimist for command-line argument parsing, are also consistent, indicating a focus on maintaining code quality and test coverage across these releases. The license remains Apache 2.0, offering developers flexibility in their projects.
The primary difference lies in the release date, with version 2.0.5 being released on October 29, 2014, a few days after 2.0.4, which came out on October 23, 2014. While the provided metadata doesn't explicitly detail the nature of the changes between these versions, the close release dates suggest that 2.0.5 likely contains bug fixes, minor performance tweaks, or refinements to improve overall stability compared to 2.0.4. Developers primarily using the 2.0.x series should consider upgrading to the latest patch version available within the line for the most stable and performant experience.
All the vulnerabilities related to the version 2.0.5 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.
