The npm package mongodb saw a minor version bump from 2.0.25 to 2.0.26 in early April 2015, representing a patch release focused on stability and potential bug fixes. Both versions share a common foundation, acting as a legacy driver emulation layer built upon the mongodb-core package (version 1.1.21), providing a familiar interface for developers accustomed to older MongoDB driver APIs. They also both depend on readable-stream 1.0.31.
The core functionality and dependencies remain identical between the two releases, using the same utilities and development dependencies such as bson, gleak, jsdoc, rimraf, semver, integra, optimist, mongodb-tools, and mongodb-version-manager. The license continues to be Apache 2.0, and the source code resides in the same GitHub repository. Both versions were authored by Christian Kvalheim.
The primary distinction lies in the release date, with version 2.0.26 arriving on April 7th, 2015, subsequent to version 2.0.25, released on March 26th, 2015. This suggests that version 2.0.26 likely includes minor bug fixes, performance improvements, or small compatibility adjustments identified and addressed after the 2.0.25 release. For developers using the mongodb package to interact with MongoDB databases, upgrading from 2.0.25 to 2.0.26 is recommended for enhanced stability and access to the latest refinements, assuming no breaking changes were introduced. While specific fixes are not explicitly detailed, the updated release date signifies an iteration aimed at providing a more robust experience. Always check release notes (if available) when upgrading.
All the vulnerabilities related to the version 2.0.26 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.
