Linux Privilege Escalation (Part 1 of 3)

By Ashwin Venugopal -

 






Introduction

Viewing, editing, or modifying system files are common privileges. Privilege escalation happens when a user receives privileges they are not entitled to. Hence, they can easily delete files, view private information, or install viruses through these privileges. It is an act of exploiting a bug, design flaw, or configuration oversight in an operating system or software application to gain elevated access to resources that an application of user normally protects.

Linux Privilege Escalation

The penetration tester often acquires initial footing on a system as a non-privileged user and then obtain further access permissions. It is a necessary skill because "direct-to-root" compromises are very rare in modern environments. There are several common escalation techniques that can exploit misconfigured services, direct kernel vulnerabilities, sensitive data stored in local files, and whatnot.

Manual Enumeration

After successfully compromising a target and establishing as an unprivileged user, penetration tester go for enumeration and analyzation of the system to gain more information about that target. Enumerating a system manually might take a long time. However, this method can also provide greater control and may disclose even more privilege escalation techniques overlooked by the automated tools. The most likely steps to this enumeration process are-
  1. User enumeration
  2. Hostname enumeration
  3. Operating System Version and Architecture enumeration
  4. Running Processes and Services enumeration
  5. Networking Information enumeration
  6. Firewall Status and Rules enumeration
  7. Scheduled Tasks enumeration
  8. Installed Applications and Patch Levels enumeration
  9. Readable/Writeable Files and Directories enumeration
  10. Unmounted Disks enumeration
  11. Device Drivers and Kernel Modules enumeration
  12. Binaries That AutoElevate enumeration

Firstly, after gaining the initial access, the penetration tester will enumerate the users and identify the user context. The commands that can be used to reveal the information about the system's users are whoami, id, uname, -a, cat/etc/passwd. 

Automated Enumeration

Each operating system consists of a plethora of data that may be exploited to launch additional assaults. Thus, manually compiling everything may be very much time-consuming. However, this procedure can be automated via a variety of scripts. Some of the scripts that can do this process on Windows are WinPeas and windows-privesc-check, and Linux OS are LinPeas and unix-privesc-check.

Conclusion

This is an introductory part for Linux Privilege Escalation and more will be discussed in the next part.





























































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 groups of computers, re
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 of alert rule parameter
Read more

Design Planning (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Complex Organizational Structures SIEM can be an expensive security control, hence, it is common multiple businesses to contribute to the overall expense. Various organizational units may require a level of access to specific dashboards or sets of data. Microsoft Sentinel offers the ability to assign table-level permissions and limit the level of access to the minimum required to perform requisite job functions.  Role-based Access Control (RBAC) Requirements Microsoft Sentinel offers an extensive list of Azure built-in roles that can be used to provide granular access according to the job requirements and permitted level of access. Some of them are various Microsoft Sentinel dedicated roles: Microsoft Sentinel Contributor- Can perform all engineering-related configuration, such as creating alert rules, configuring data connectors, and additional similar tasks.  Microsoft Sentinel Reader- Can query the log data stor
Read more