MongoDB 2.1.4 signifies a minor update over its predecessor, 2.1.3, primarily focusing on improvements and refinements within the core driver architecture. Both versions serve as an emulation layer, offering a legacy driver experience built upon the mongodb-core component. For developers utilizing MongoDB in Node.js environments, these versions provide access to familiar APIs while leveraging enhancements in the underlying core driver.
The key distinction lies in the updated dependency on mongodb-core, moving from version 1.2.31 in 2.1.3 to 1.2.32 in 2.1.4. This subtle change often encompasses bug fixes, performance optimizations, and potentially new features within the core driver itself. Developers should consult the mongodb-core changelog for a granular view of those specific updates.
Beyond the core driver, 2.1.4 introduces new development dependencies, specifically colors, cli-table, JSONStream, worker-farm, event-stream, ldjson-stream, and betterbenchmarks. The bson dependency also changes to ^0.4.20. These additions suggest a strengthened emphasis on testing, benchmarking, and potentially new development workflows. Users who depend on tools like colors or JSONStream in their development process might want to consider this version, but it's important to note that since these are *devDependencies* they will affect the development environment and build process, not the runtime environment of the built package. Finally, this version was released on January 12, 2016, about a week after version 2.1.3 which was released at January 4, 2016. Upgrading offers a potentially more stable and performant foundation, especially for those relying heavily on the driver's low-level operations.
All the vulnerabilities related to the version 2.1.4 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.
