InfoSec LAB

Reconstruction_Recon

Created: 2 min read

RustScan

┌──(kali㉿kali)-[~/PEN-200/PG_PRACTICE/reconstruction]
└─$ rustscan -a $IP
________________________________________
: http://discord.skerritt.blog         :
: https://github.com/RustScan/RustScan :
 --------------------------------------
I scanned my computer so many times, it thinks we're dating.
 
[~] The config file is expected to be at "/home/kali/.rustscan.toml"
[~] Automatically increasing ulimit value to 10000.
Open 192.168.209.103:21
Open 192.168.209.103:22
Open 192.168.209.103:8080

Nmap

┌──(kali㉿kali)-[~/PEN-200/PG_PRACTICE/reconstruction]
└─$ nmap -T4 -sT -p- $IP
Starting Nmap 7.94SVN ( https://nmap.org ) at 2025-02-07 00:27 CET
Stats: 0:00:04 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 48.06% done; ETC: 00:27 (0:00:04 remaining)
Nmap scan report for 192.168.209.103
Host is up (0.025s latency).
Not shown: 65532 closed tcp ports (conn-refused)
PORT     STATE SERVICE
21/tcp   open  ftp
22/tcp   open  ssh
8080/tcp open  http-proxy
 
Nmap done: 1 IP address (1 host up) scanned in 7.85 seconds
 
┌──(kali㉿kali)-[~/PEN-200/PG_PRACTICE/reconstruction]
└─$ nmap -sS -sC -sV -p 21,22,8080 $IP
Starting Nmap 7.94SVN ( https://nmap.org ) at 2025-02-06 23:01 CET
Nmap scan report for 192.168.209.103
Host is up (0.73s latency).
 
PORT     STATE SERVICE VERSION
21/tcp   open  ftp     vsftpd 3.0.3
| ftp-anon: Anonymous FTP login allowed (FTP code 230)
| drwxr-xr-x    2 0        0            4096 Apr 29  2020 WebSOC
|_-rw-r--r--    1 0        0             137 Apr 29  2020 note.txt
| ftp-syst: 
|   STAT: 
| FTP server status:
|      Connected to 192.168.45.215
|      Logged in as ftp
|      TYPE: ASCII
|      No session bandwidth limit
|      Session timeout in seconds is 300
|      Control connection is plain text
|      Data connections will be plain text
|      At session startup, client count was 4
|      vsFTPd 3.0.3 - secure, fast, stable
|_End of status
22/tcp   open  ssh     OpenSSH 7.6p1 Ubuntu 4 (Ubuntu Linux; protocol 2.0)
| ssh-hostkey: 
|   2048 55:4e:03:dc:c8:92:36:66:49:75:f3:2e:35:15:8e:57 (RSA)
|   256 1b:df:4c:ac:72:93:8f:77:92:05:98:ae:7c:c1:6a:ea (ECDSA)
|_  256 d8:3f:b9:21:e4:8c:34:3a:9b:c7:46:cc:c4:f5:6e:eb (ED25519)
8080/tcp open  http    Werkzeug httpd 1.0.1 (Python 3.6.9)
|_http-server-header: Werkzeug/1.0.1 Python/3.6.9
|_http-title: Blog
Service Info: OSs: Unix, Linux; CPE: cpe:/o:linux:linux_kernel
 
Service detection performed. Please report any incorrect results at https://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 13.76 seconds

The target system appears to be Ubuntu

UDP

┌──(kali㉿kali)-[~/PEN-200/PG_PRACTICE/reconstruction]
└─$ sudo nmap -sU -Pn -top-ports 1000 $IP
Starting Nmap 7.94SVN ( https://nmap.org ) at 2025-02-06 23:00 CET
Nmap scan report for 192.168.209.103
Host is up (0.018s latency).
Not shown: 997 closed udp ports (port-unreach)
PORT      STATE         SERVICE
959/udp   open|filtered unknown
1041/udp  open|filtered danf-ak2
25337/udp open|filtered unknown
 
Nmap done: 1 IP address (1 host up) scanned in 1156.87 seconds

Interactive Graph View

Backlinks