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

Query, Visualize, & Monitor Data in Azure Sentinel

By Ashwin Venugopal -
Image
  Azure Sentinel Workbooks Several ready for use templates are provided by the Azure Sentinel that can be used to create your own workbook and then modify them as needed for Contoso. Most of the data connectors it uses to ingest data come with their own workbooks, but better insight can be obtained by simply looking into the data that is being ingested by using tables and visualizations, including bar and pie charts. You can also make your own workbook easily by using this data from the beginning instead of using the predefined templates. Workbook Page You can easily access the workbook page from the Azure Sentinel from the navigation pane which consists of the: Workbook header- You can add a new workbook and review the saved workbooks as well as templates that are available on the workbook page. Templates section- You can access existing workbook templates on the Templates tab. You can save some of the workbooks for quick access and they will appear on the My Workbooks tab.  From the
Read more

Planning for Implementing SAP Solutions on Azure (Part 2 of 5)

By Ashwin Venugopal -
Image
  To read part 1 please click  here To read part 3 please click  here To read part 4 please click  here To read part 5 please click  here Load Balancing The load balancer uses probe ports to determine as well as route the traffic to an active DBMS node, but of there's any failover then the most common SAP application architecture can automatically reconnect against the private virtual IP address without the need for the SAP application to reconfigure it, while the load balancer redirect the traffic against the private virtual IP address without any need for the SAP application to reconfigure. The loaf balancer also offers an option of DirectServerReturn which if configured, can help in directing the traffic from the DBMS VM to the SAP application layer directly to the application layer without routing through the load balancer. But, if it isn't configured, then the return traffic to the SAP application layer is routed through the load balancer. You can also use Azure Load Balan
Read more

Work with String Data Using KQL Statements

By Ashwin Venugopal -
Image
  Extract Data from Unstructured String Fields Unstructured string fields often contains the Security log data and requires parsing to extract data. There are multiple ways of pulling information from string fields in KQL and the two primary operators used are extract and parse.  Extract It gets a match for a regular expression from a text string. You can convert the extracted substring to the indicated type.  Arguments regex- A regular expression. captureGroup- A positive int constant indicating the capture group to extract. 0 stands for the entire match, 1 for the value matched by the first '('parenthesis')' in the regular expression, 2 or more for subsequent parenthesis.  text- A string to search. typeLiteral- An optional type literal. If provided, the extracted substring is converted to this type.  Returns If regex finds a match in text- the substring matched against the indicated capture group captureGroup, optionally converted to typeLiteral. If there's no mat
Read more