The npm package mongodb saw a minor version update from 2.0.36 to 2.0.37 in July 2015. Both versions serve as a legacy driver emulation layer built upon the mongodb-core package, offering developers a familiar interface for interacting with MongoDB databases. Key dependencies like es6-promise and readable-stream remain consistent between the two, ensuring compatibility and stable asynchronous operations. The core functionality is augmented with development dependencies such as co for generator-based control flow, bson for handling BSON data, and tools like integra and mongodb-tools that aid in testing and managing MongoDB instances during development.
The primary difference lies in the mongodb-core dependency, which updates from version 1.2.4 to 1.2.5. This indicates that 2.0.37 likely incorporates bug fixes, performance improvements, or minor feature enhancements within the underlying MongoDB driver implementation. For developers, this update suggests enhanced stability and potentially better performance when interacting with MongoDB servers. While the high-level API remains largely the same, upgrading to 2.0.37 will ensure you're leveraging the latest improvements and fixes within the core driver, providing a more robust and reliable MongoDB integration in your Node.js applications. The release date difference of roughly a week highlights a focused effort to address identified issues quickly.
All the vulnerabilities related to the version 2.0.37 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.
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.
