MongoDB version 2.0.50 represents a minor update to the popular Node.js driver for MongoDB, building upon the foundation laid by version 2.0.49. Both versions function as a legacy driver emulation layer, providing a familiar interface on top of the mongodb-core library. Key dependencies like es6-promise and readable-stream remain consistent between the two, ensuring continued compatibility and functionality.
However, a significant difference lies in the core driver dependency: version 2.0.50 upgrades to mongodb-core version 1.2.26, whereas version 2.0.49 relies on mongodb-core version 1.2.24. This update likely includes bug fixes, performance improvements, or new features within the core MongoDB interaction layer.
Furthermore, the developer tooling sees a change. Version 2.0.49 includes mongodb-tools as a development dependency, specifying a version constraint of ~1.0. This dependency is absent in version 2.0.50, where instead mongodb-topology-manager is added with a verion constraint of 1.0.x. These types of tool help developers set staging environments for testing changes in the driver.
Developers considering upgrading should primarily evaluate the changelog and release notes for mongodb-core 1.2.26 to understand the specific benefits and potential breaking changes introduced by that update. Although a minor version bump, the underlying mongodb-core update could have implications for specific use cases and server configurations. Evaluating the differences in tooling is also important to identify if the new tools are compatible and suit developer preferences.
All the vulnerabilities related to the version 2.0.50 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.
