MongoDB version 2.0.29 represents a minor update to the popular Node.js driver for MongoDB, building upon the foundation laid by its predecessor, version 2.0.28. While the core functionality remains largely consistent, a key difference lies in the updated dependency on mongodb-core. Version 2.0.29 utilizes mongodb-core version 1.1.26, whereas 2.0.28 relies on version 1.1.25. This seemingly small increment in mongodb-core likely incorporates bug fixes, performance improvements, or minor feature enhancements within the lower-level driver component.
For developers using the MongoDB Node.js driver, this update suggests improved stability and potentially better performance when interacting with MongoDB databases. While the API exposed to developers remains similar, upgrading to 2.0.29 ensures you are benefiting from the latest improvements and fixes to the underlying driver. The consistent dependencies on tools like bson for data serialization, readable-stream for stream handling, and development tools like jsdoc and semver highlight the project's commitment to maintaining code quality and adhering to semantic versioning. Developers should review the changelog of mongodb-core from 1.1.25 and 1.1.26 to understand the specific alterations packed into version 2.0.29 of the primary MongoDB Node.js driver. The release date of May 7th, 2015 indicates a mature update.
All the vulnerabilities related to the version 2.0.29 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.
DLL Injection in kerberos
Version of kerberos prior to 1.0.0 are vulnerable to DLL Injection. The package loads DLLs without specifying a full path. This may allow attackers to create a file with the same name in a folder that precedes the intended file in the DLL path search. Doing so would allow attackers to execute arbitrary code in the machine.
Upgrade to version 1.0.0 or later.
