MongoDB version 2.0.55 represents a minor update over its predecessor, version 2.0.54, primarily focusing on internal improvements and bug fixes rather than introducing significant new features for developers. Both versions serve as a legacy driver emulation layer built upon mongodb-core, providing a familiar interface for users accustomed to older MongoDB driver versions. Examining the dependency changes reveals the core difference: version 2.0.55 upgrades mongodb-core from version 1.2.30 to 1.2.31.
While seemingly small, this mongodb-core update likely addresses bug fixes, performance enhancements, or minor compatibility adjustments within the underlying database interaction layer. Developers might not directly observe drastic changes in functionality when upgrading from 2.0.54 to 2.0.55. However, such incremental upgrades are crucial for maintaining stability and ensuring optimal performance, particularly within high-traffic or mission-critical applications. Both depend on packages like es6-promise and readable-stream to ease development. The development dependencies show the tooling used to build the library, including testing and documentation.
The release date difference of approximately one hour between the two versions indicates a quick follow-up release, possibly to address an urgent issue discovered shortly after publishing 2.0.54. For users of the 2.0.x series, upgrading to 2.0.55 is a recommended practice to benefit from the latest maintenance and refinements within the mongodb-core layer. Developers who relied on the prior version will benefit of a more stable and fast version of the MongoDB driver library.
All the vulnerabilities related to the version 2.0.55 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.
