UnratednpmAmendedPublished
Private Data Disclosure in express-restify-mongoose
CVE-2016-10533 · GHSA-cgjx-mwpx-47jv
- Affected
- npm express-restify-mongoose <= 2.4.2; >= 3.0.0, <= 3.0.1
- Fixed in
- 3.1.02.5.0· Vendor fix available
- Issue
- Affected versions of express-restify-mongoose are susceptible to an information leakage vulnerability which may allow an attacker to access fields on a model even if those fields are marked as private. Proof of Concept If you have a user model that you want to protect, such as the following User model: You would normally do something such as: This would hide the password field from people that send your application a GET /User and GET /User/some-user-id request. A malicious user can go to your application and send a request for GET /User?distinct=password and get all the passwords for all the users in the database, despite the field being set to private. This could be used for other private data, if the malicious user knew what was set as private for specific routes. Recommendation Version 2.x: Update to version 2.5.0 or later. Version 3.x: Update to version 3.1.0 or later.
Recommended action: Upgrade to 3.1.0 or 2.5.0 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.