MongoDB Node.js driver underwent a minor version update from 1.1.0 to 1.1.1, released on July 27, 2012. While seemingly small, these point releases often contain crucial bug fixes and optimizations, making them important for developers utilizing the MongoDB database with Node.js. The core functionality remains the same, providing a robust interface for interacting with MongoDB databases.
The most significant difference lies in the updated dependency on the bson package. Version 1.1.1 relies on bson version 0.1.1, while version 1.1.0 used bson 0.1.0. BSON is a binary-encoded serialization of JSON-like documents, crucial for efficient data storage and retrieval in MongoDB. This update likely addresses improvements or bug fixes within the BSON serialization/deserialization process itself, potentially impacting performance or data integrity.
Both versions share identical developer dependencies, including tools for documentation generation (dox), templating (ejs), asynchronous control flow (step, async), memory leak detection (gleak), GitHub interaction (github3), Markdown processing (markdown), unit testing (nodeunit), and JavaScript minification (uglify-js). This consistency indicates a focus on maintaining a stable development environment and high code quality for both versions. Before upgrading, developers should review the bson changelog to understand the specific changes introduced in version 0.1.1 and their potential impact on their application. While the changes may be subtle, ensure compatibility with any critical BSON-related operations.
All the vulnerabilities related to the version 1.1.1 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.
