ghsa-cgjx-mwpx-47jv
Vulnerability from github
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:
const User = mongoose.model('User', new mongoose.Schema({
name: String,
password: String,
}));
You would normally do something such as:
restify.serve(router, User, {
private: ['password'], // Set the password part of User as private, so outside people can't read it
})
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.
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 3.0.1"
},
"package": {
"ecosystem": "npm",
"name": "express-restify-mongoose"
},
"ranges": [
{
"events": [
{
"introduced": "3.0.0"
},
{
"fixed": "3.1.0"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 2.4.2"
},
"package": {
"ecosystem": "npm",
"name": "express-restify-mongoose"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.5.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2016-10533"
],
"database_specific": {
"cwe_ids": [
"CWE-200"
],
"github_reviewed": true,
"github_reviewed_at": "2020-06-16T21:31:33Z",
"nvd_published_at": null,
"severity": "HIGH"
},
"details": "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.\n\n\n## Proof of Concept\n\nIf you have a user model that you want to protect, such as the following User model:\n```\nconst User = mongoose.model(\u0027User\u0027, new mongoose.Schema({\n name: String,\n password: String,\n}));\n```\n\nYou would normally do something such as:\n```\nrestify.serve(router, User, {\n private: [\u0027password\u0027], // Set the password part of User as private, so outside people can\u0027t read it\n})\n```\n\nThis would hide the password field from people that send your application a `GET /User` and `GET /User/some-user-id` request. \n\nA 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.\n\n\n## Recommendation\n\nVersion 2.x: Update to version 2.5.0 or later.\nVersion 3.x: Update to version 3.1.0 or later.",
"id": "GHSA-cgjx-mwpx-47jv",
"modified": "2020-08-31T18:10:32Z",
"published": "2018-10-23T17:14:57Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2016-10533"
},
{
"type": "WEB",
"url": "https://github.com/florianholzapfel/express-restify-mongoose/issues/252"
},
{
"type": "WEB",
"url": "https://github.com/florianholzapfel/express-restify-mongoose/pull/253"
},
{
"type": "WEB",
"url": "https://github.com/florianholzapfel/express-restify-mongoose/commit/23ccb247d0074bfaca6737cdff52d89c6d6e4a7c"
},
{
"type": "WEB",
"url": "https://github.com/florianholzapfel/express-restify-mongoose/commit/746defcd808e2ed1e8931dc36702b25b7db0e94b"
},
{
"type": "ADVISORY",
"url": "https://github.com/advisories/GHSA-cgjx-mwpx-47jv"
},
{
"type": "WEB",
"url": "https://www.npmjs.com/advisories/92"
}
],
"schema_version": "1.4.0",
"severity": [],
"summary": "Private Data Disclosure in express-restify-mongoose"
}
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.