MongoDB version 2.0.19 represents a minor update over its predecessor, version 2.0.18, in this legacy driver emulation layer. Both versions share the same core dependencies: mongodb-core at version 1.1.14 for fundamental MongoDB interactions and readable-stream at version 1.0.31 for handling data streams. The developer tooling remains consistent as well, with bson for handling BSON serialization, gleak for memory leak detection, jsdoc for API documentation generation, rimraf for file system cleanup, semver for semantic versioning checks, integra for integration testing, optimist for command-line argument parsing, mongodb-tools for MongoDB-related utilities, and mongodb-version-manager for managing different MongoDB server versions during testing.
Crucially, the underlying functionality provided by these versions appear to be identical, indicated by the matching dependency and development dependency specifications. There is no difference in the code used to emulate legacy drivers. The only notable distinction lies in the release date. Version 2.0.19 was published on March 3, 2015, while version 2.0.18 came out on February 27, 2015. For developers, this suggests that the update from 2.0.18 to 2.0.19 is likely a bug fix or a very small improvement. It would be recommend checking the release notes for any specific changes.
All the vulnerabilities related to the version 2.0.19 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.
