Active Directory (Part 8)

By Ashwin Venugopal -

 





LDAP Bind Credentials

Lightweight Directory Access Protocol (LDAP) authentication is another way used by the applications to authenticate with AD. Although LDAP is same as NTLM, but the application directly verifies user credentials via a pair of AD credentials to query LDAP and then verify the AD user's credentials, instead of operating as a challenge-response protocol like NTLM. LDAP authentication is a popular mechanism with third-party applications that integrates with AD like gitlab, jenkins, and different kinds of VPNs. 

Every authentication protocol and security system contains some vulnerable ways to exploit them. Similarly, some of the LDAP authentication attack methods that a penetration tester can utilize are:

  • LDAP injection- In this attack, the tester injects malicious LDAP statements into an application's LDAP queries, allowing them to gain unauthorized access to network resources or manipulate data stored in AD. 

  • LDAP authentication bypass- In this one, the tester bypasses the LDAP authentication process to gain unauthorized access to network resources or manipulate data stored in AD.

  • LDAP enumeration- It is a type of attack in which the tester uses LDAP to gather information about the AD environment, like user accounts, group policies, and other objects, to gain unauthorized access to network resources or manipulate data stored in AD. 

  • LDAP pass-back attack- An attack in which the tester creates a rogue AD domain controller and uses LDAP to authenticate users and manage access to network resources, allowing them to gain unauthorized access to network resources or manipulate data stored in AD. 

Authentication Relays

To make use of an authentication relay, the client sends an authentication request to the relay, which in turn communicates with the AD domain controllers to verify the client's credentials. If the credentials are valid, the relay reverts the response to the client indicating the authentication was successful.

Authentication relay offers many benefits to an AD environment. It helps the organization in easy expansion of their Ad infrastructure to remote locations without having to setup extra domain controllers. It also allows the centralized management of AD environment, as all authentication requests are processed via relay rather than being handled individually by each domain controller.

There are a few ways to configure authentication relay according to the specific needs of an organization. Some of them includes dedicated authentication relay server, configuring an existing server as an authentication relay, or using a cloud-based authentication service.

A penetration tester can also leverage SMB protocol. It governs everything, from inner network file-sharing to remote administration. The security of older versions of this protocol was insufficient and many vulnerabilities as well as exploits were discovered. However, many of them has been resolved in its newer versions, often organization do not use them since legacy systems do not support them. The two different exploits of NetNTLM authentication with SMB are:

  • Since the NTLM Challenges can be intercepted, offline cracking techniques can be used to recover the password associated with the NTLM challenge. However, the cracking process is rather slower than cracking NTLM hashes directly. 

  • Use rogue device to stage a man in the middle attack, relaying the SMB authentication between the client and server which will provide an active authenticated session and access to the target server.

One of the most common tools used while executing the relay attacks is Responder. It allows Man-in-the-Middle attacks by poisoning the responses during NetNTLM authentication and tricking the client. It attempts to force the client into connecting with the attacker. Meanwhile, it also starts to host several servers, like SMB, SQL, HTTP, and others, to capture requests and force authentication.

Conclusion

Here, we discussed more about LDAP bind credentials and authentication relays. 










































Comments

Post a Comment

Popular posts from this blog

Deployment (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Microsoft Monitoring Agent (MMA) MMA is used across multiple Microsoft solutions and has undergone a few name changes as its features and functionality have evolved. If it is being considered to be used, then following areas should be covered during a Microsoft Sentinel deployment project: Consider the timelines and the strategy for a migration to AMA (Azure Monitor Agent) before the MMA end-of-life.  Consider the central deployment and management methodology for MMA. Determine which endpoints are in scope for deployment as these affect the log ingestion volume significantly.  Azure Monitor Agent (AMA) Organizations with MMA as the main Microsoft Sentinel agent should start planning the migration to AMA as soon as possible to avoid a rushed migration. One of the main advantages of AMA is the ability to control the log collection policy centrally and apply different policies against different...
Read more

Deployment (Part 1)

By Ashwin Venugopal -
Image
  To read part 2, please click  here To read part 3, please click  here Azure Resources Microsoft Sentinel needs following resources to be created: Subscription (if a dedicated subscription(s) will be used) Resource group(s) Log Analytics workspace(s) Automation rules/playbook Alert rules Workbooks Microsoft Sentinel offers hundreds of alert rules, workbooks, and automation playbook templates along with hunting scripts. The templates can be used to activate/deploy schedule alerts, create customized dashboards, create automation playbooks and perform threat-hunting activities. Generally, once deployed, the resources created have to be adjusted to match the existing environment, configure local credentials, etc. Methods of deployment: Manual- Administrator can manually configures the Microsoft Sentinel resources with the help of Azure portal. Any manual process has the inherent risks of human operator error, lack of compliance with potential change control procedures, and u...
Read more

Project Resourcing (Part 2)

By Ashwin Venugopal -
Image
  To read part 1, please click  here Engineering - SIEM The SIEM engineers configures Microsoft Sentinel, including Log Analytics, Logic Apps, workbooks, and playbooks. They are also responsible for the following high-level tasks: Initial configuration of Azure tenant, including provisioning required resources, assigning access roles, and configuring workspace parameters like log retention, resource tagging, and blueprints.  Deployment and configuration of syslog/CEF log collection agents in appropriate locations to collect logs from on-premises devices. Generally, it will be joint effort of both system engineer and SIEM engineer, involving configuration and potential troubleshooting.  Working with system owners to enable log forwarding and configuring any required parsing of log data in Log Analytics.  Working with security operations to create and deploy KQL analytic rules to offer detections for SOC/Computer Security Incident Response Team (CSRIT) use. Tuning...
Read more