MongoDB version 2.0.52 is a minor patch release following 2.0.51, both iterations built as a legacy driver emulation layer operating on top of the mongodb-core. For developers familiar with the MongoDB Node.js driver, these versions provide a familiar API while leveraging the performance improvements and modular architecture introduced with the core driver. The core dependencies, es6-promise, mongodb-core, and readable-stream, remain consistent between the two, ensuring basic functionality remains unchanged. Similarly, the development dependencies, including tools for co-routine support (co), BSON handling (bson), memory leak detection (gleak), documentation generation (jsdoc), and testing infrastructure (integra, bluebird, optimist, and mongodb-version-manager), haven't been altered.
The primary differentiating factor is the release date; version 2.0.52 was published on December 14, 2015, shortly after the December 13, 2015 release of version 2.0.51. This tight release window suggests that 2.0.52 likely contains bug fixes or minor adjustments discovered post-release of 2.0.51. Developers should upgrade to the latest patch version (2.0.52) to benefit from the latest refinements. Since the dependencies remained the same between these versions, the changes are expected to be narrow, focusing on fixing potential issues without introducing new features or breaking changes. Therefore, the update from 2.0.51 to 2.0.52 should be a low-risk and generally recommended procedure.
All the vulnerabilities related to the version 2.0.52 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.
