MongoDB version 1.3.0 marks an incremental update to the popular Node.js driver for MongoDB, building upon the solid foundation of version 1.2.14. Developers migrating from the prior stable release will notice key differences primarily in dependency management. MongoDB 1.3.0 introduces kerberos as both a standard and optional dependency, offering enhanced authentication capabilities. This inclusion signifies a move towards strengthened security and potentially broader compatibility with secured MongoDB deployments, important for enterprise applications requiring robust access control mechanisms.
While the core API likely remains largely consistent, the updated dependencies may have implications for compatibility and performance. Developers should carefully examine release notes and changelogs for detailed information on potential breaking changes or performance enhancements related to the kerberos integration. Furthermore, the removal of github3 from the devDependencies suggests a change in the development or testing processes for the driver itself, though this is less relevant for end-users.
Both versions retain core dependencies like bson for efficient BSON serialization and utilize common development tools such as nodeunit for testing and uglify-js for minification. However, the addition of kerberos to version 1.3.0 is the prominent difference, particularly for developers needing secure authentication against Kerberos-enabled MongoDB instances. Always check against your project requirements and deployment constraints before upgrading.
All the vulnerabilities related to the version 1.3.0 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.