Which of the following application attacks is used against a corporate directory service where
there are unknown servers on the network?
A.
Rogue access point
B.
Zero day attack
C.
Packet sniffing
D.
LDAP injection
Get 50% Discount on All Your Purchases
at PrepAway.com - Latest Exam Questions
This is ONE TIME OFFER
50%
Since we are talking about a “ CORPORATE DIRECTORY” we we are either talking about Microsoft AD or LDAP.
Before we continue, it is important to know that LDAP and AD are both software implementations of directory services. They are also both hosted on-premises, in most cases. Further, both Microsoft Active Directory and LDAP are fundamentally based on the LDAP protocol. Although most people don’t know that because AD mostly authenticates leveraging Kerberos. However, AD does have the capability to authenticate via LDAP as well. Both directories struggle connecting users to cloud computing infrastructure such as IaaS or Web-based applications.
All the answers provided bar one are plainly wrong.
The correct answer is therefore: D.LDAP injection
A directory service is accessed by using LDAP (Lightweight Directory Access Protocol).
LDAP injection is an attack against a directory service.
Just as SQL injection attacks take statements that are input by users and exploit weaknesses within, an LDAP injection attack exploits weaknesses in LDAP (Lightweight Directory Access
Protocol) implementations. This can occur when the user’s input is not properly filtered, and the result can be executed commands, modified content, or results returned to unauthorized queries.
The best way to prevent LDAP injection attacks is to filter the user input and to use a validation scheme to make certain that queries do not contain exploits.
One of the most common uses of LDAP is associated with user information.
Numerous applications exist–such as employee directories–where users find other users by typing in a portion of their name. These queries are looking at the cn value or other fields (those defined for department, home directory, and so on). Someone attempting LDAP injection could feed unexpected values to the query to see what results are returned. All too often, finding employee information equates to finding usernames and values about those users that could be portions of their passwords.
0
0