| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Puppetlabs Puppet up to 2.7.2. It has been rated as problematic. This affects an unknown function of the component Console. This manipulation causes cryptographic issue. This vulnerability appears as CVE-2013-2716. There is no available exploit. Upgrading the affected component is advised.
Details
A vulnerability classified as problematic was found in Puppetlabs Puppet up to 2.7.2 (Service Management Software). Affected by this vulnerability is an unknown function of the component Console. The manipulation with an unknown input leads to a cryptographic issue vulnerability. The CWE definition for the vulnerability is CWE-310. As an impact it is known to affect integrity. The summary by CVE is:
Puppet Labs Puppet Enterprise before 2.8.0 does not use a "randomized secret" in the CAS client config file (cas_client_config.yml) when upgrading from older 1.2.x or 2.0.x versions, which allows remote attackers to obtain console access via a crafted cookie.
The weakness was presented 04/10/2013 (Website). The advisory is shared at puppetlabs.com. This vulnerability is known as CVE-2013-2716 since 03/27/2013. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1600 for this issue.
The vulnerability scanner Nessus provides a plugin with the ID 66235 (Puppet Enterprise Console Authentication Bypass (intrusive check)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family CGI abuses.
Upgrading to version 2.5.0 eliminates this vulnerability.
The vulnerability is also documented in the databases at X-Force (83171), Tenable (66235), SecurityFocus (BID 58811†), Secunia (SA52862†) and Vulnerability Center (SBV-39528†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://puppet.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: Cryptographic issueCWE: CWE-310
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 |
Nessus ID: 66235
Nessus Name: Puppet Enterprise Console Authentication Bypass (intrusive check)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Puppet 2.5.0
Timeline
03/27/2013 🔍03/28/2013 🔍
03/28/2013 🔍
04/02/2013 🔍
04/10/2013 🔍
04/10/2013 🔍
04/26/2013 🔍
05/13/2013 🔍
03/24/2015 🔍
01/02/2022 🔍
Sources
Vendor: puppet.comAdvisory: puppetlabs.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2013-2716 (🔍)
GCVE (CVE): GCVE-0-2013-2716
GCVE (VulDB): GCVE-100-63973
X-Force: 83171
SecurityFocus: 58811 - Puppet CVE-2013-2716 Authentication Bypass Weakness
Secunia: 52862 - Puppet Console Authentication Bypass Weakness, Not Critical
Vulnerability Center: 39528 - Puppet Labs Puppet Enterprise Remote Authentication Bypass due to No Use of a Randomized Secret While Upgrading, Medium
Entry
Created: 03/24/2015 15:54Updated: 01/02/2022 08:59
Changes: 03/24/2015 15:54 (63), 04/29/2017 20:43 (6), 01/02/2022 08:59 (3)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.