Version 2.0.27 of the mongodb npm package represents a minor version bump over its predecessor, 2.0.26, both designed as a legacy driver emulation layer built upon mongodb-core. Examining their package data reveals a singular, yet crucial, distinction: the release date. Version 2.0.27 was published on April 7th, 2015 at 14:29:30 UTC, approximately five hours after version 2.0.26, which was released at 09:37:22 UTC on the same day.
In practical development terms, this suggests that 2.0.27 likely incorporates bug fixes, minor enhancements, or incremental refinements addressing issues identified shortly after the initial 2.0.26 release. For developers, upgrading from 2.0.26 to 2.0.27 would be advisable to inherit these stability and performance improvements. The core functionality and API exposed to users remain largely consistent between the two versions, implying a risk-free update path.
Both versions rely on the same dependencies (mongodb-core at version 1.1.21 and readable-stream at 1.0.31) and development dependencies indicating similar testing and build processes. The shared license (Apache 2.0), repository, and author information further emphasize continuity. Therefore, opting for the slightly newer 2.0.27 is the recommended practice to ensure the most up-to-date and reliable experience within the 2.0.x release family.
All the vulnerabilities related to the version 2.0.27 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.
