MCollective up to 0.5.0 mcollective-sshkey-security Filename input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in MCollective up to 0.5.0. It has been rated as critical. The affected element is an unknown function of the component mcollective-sshkey-security. The manipulation with the input example.txt_pub.pem as part of Filename leads to input validation.
This vulnerability is uniquely identified as CVE-2017-2298. The attack is possible to be carried out remotely. No exploit exists.
Upgrading the affected component is advised.
Details
A vulnerability was found in MCollective up to 0.5.0. It has been rated as critical. This issue affects an unknown function of the component mcollective-sshkey-security. The manipulation with the input value example.txt_pub.pem leads to a input validation vulnerability. Using CWE to declare the problem leads to CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. Impacted is integrity, and availability. The summary by CVE is:
The mcollective-sshkey-security plugin before 0.5.1 for Puppet uses a server-specified identifier as part of a path where a file is written. A compromised server could use this to write a file to an arbitrary location on the client with the filename appended with the string "_pub.pem".
The bug was discovered 06/30/2017. The weakness was disclosed 06/30/2017 (GitHub Repository). The advisory is shared at github.com. The identification of this vulnerability is CVE-2017-2298 since 12/01/2016. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.
Upgrading to version 0.5.1 eliminates this vulnerability.
The entry VDB-102976 is pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.9VulDB Meta Temp Score: 5.6
VulDB Base Score: 5.4
VulDB Temp Score: 4.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.5
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
Class: Input validationCWE: CWE-20
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: MCollective 0.5.1
Patch: github.com
Timeline
12/01/2016 🔍06/30/2017 🔍
06/30/2017 🔍
06/30/2017 🔍
07/01/2017 🔍
12/09/2022 🔍
Sources
Advisory: 3388a3109f4fb1c69fa8505e991bf59ca20d19a2Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-2298 (🔍)
GCVE (CVE): GCVE-0-2017-2298
GCVE (VulDB): GCVE-100-102977
See also: 🔍
Entry
Created: 07/01/2017 07:38Updated: 12/09/2022 14:51
Changes: 07/01/2017 07:38 (59), 10/21/2019 16:44 (2), 12/09/2022 14:51 (5)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.