express-restify-mongoose up to 2.4.2/3.0.1 REST Interface /User?distinct=password Password information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in express-restify-mongoose up to 2.4.2/3.0.1. It has been declared as critical. This vulnerability affects unknown code of the file /User?distinct=password of the component REST Interface. Such manipulation leads to information disclosure (Password). This vulnerability is listed as CVE-2016-10533. The attack may be performed from remote. There is no available exploit. Restrictive firewalling should be applied.
Details
A vulnerability was found in express-restify-mongoose up to 2.4.2/3.0.1 and classified as critical. Affected by this issue is some unknown processing of the file /User?distinct=password of the component REST Interface. The manipulation with an unknown input leads to a information disclosure vulnerability (Password). Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. CVE summarizes:
express-restify-mongoose is a module to easily create a flexible REST interface for mongoose models. express-restify-mongoose 2.4.2 and earlier and 3.0.X through 3.0.1 allows a malicious user to 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 can be used for other private data if the malicious user knew what was set as private for specific routes.
The bug was discovered 04/19/2016. The weakness was presented 05/31/2018 (Website). The advisory is available at github.com. This vulnerability is handled as CVE-2016-10533 since 10/29/2017. The exploitation is known to be easy. The attack may be launched remotely. Required for exploitation is a simple authentication. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1592 by the MITRE ATT&CK project.
The vulnerability was handled as a non-public zero-day exploit for at least 772 days. During that time the estimated underground price was around $0-$5k.
Addressing this vulnerability is possible by firewalling .
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.6VulDB Meta Temp Score: 6.5
VulDB Base Score: 4.3
VulDB Temp Score: 4.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Name: PasswordClass: Information disclosure / Password
CWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: FirewallStatus: 🔍
0-Day Time: 🔍
Timeline
04/19/2016 🔍10/29/2017 🔍
05/31/2018 🔍
05/31/2018 🔍
06/01/2018 🔍
03/17/2023 🔍
Sources
Advisory: 252Status: Not defined
CVE: CVE-2016-10533 (🔍)
GCVE (CVE): GCVE-0-2016-10533
GCVE (VulDB): GCVE-100-118418
Entry
Created: 06/01/2018 09:32Updated: 03/17/2023 20:16
Changes: 06/01/2018 09:32 (59), 02/10/2020 10:39 (1), 03/17/2023 20:16 (4)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.