{"id":605,"date":"2026-02-05T14:36:03","date_gmt":"2026-02-05T14:36:03","guid":{"rendered":"https:\/\/thecyberstaff.com\/?p=605"},"modified":"2026-02-05T14:36:04","modified_gmt":"2026-02-05T14:36:04","slug":"traverxec-hackthebox","status":"publish","type":"post","link":"https:\/\/thecyberstaff.com\/?p=605","title":{"rendered":"Traverxec- Hackthebox"},"content":{"rendered":"\n

I began with an Nmap scan<\/strong> to identify open TCP ports, detect service versions, and run the default NSE scripts. The scan revealed two open ports: 22 (SSH) and 80 (HTTP)<\/strong>. Port 80 was hosting a web server identified as Nostromo version 1.9.6<\/strong>. This immediately caught my attention, as Nostromo is not commonly seen in modern environments. I proceeded to research known vulnerabilities associated with this specific version to determine if it could be leveraged for initial access.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

execution (RCE)<\/strong> flaw. I reviewed the corresponding Exploit Database<\/strong> entry to better understand how the vulnerability worked and to verify that it applied to this specific version of the service. After confirming its relevance, I downloaded the exploit and prepared to test it against the target.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

After running the exploit against the target, I was able to execute the id<\/code> command successfully. The output confirmed that the exploit was working and that remote command execution was possible on the system. This verified that the vulnerability could be leveraged to run arbitrary commands, providing an initial foothold on the target machine.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Next, I leveraged the command execution vulnerability to invoke Netcat<\/strong> and establish a reverse shell back to my attacker machine over port 443<\/strong>. I set up a listener on my local system and executed the payload through the exploit. Shortly after, the connection was received successfully, granting me an interactive shell on the target and confirming remote access.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Shell as www-data user<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

While enumerating the local filesystem, I searched for sensitive files such as configuration files, credential stores, and user-related data. During this process, I discovered a password hash belonging to the user david<\/strong>. This suggested the possibility of credential reuse or offline hash cracking, which could potentially allow lateral movement or privilege escalation on the system.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

I extracted the discovered hash and used John<\/strong> to attempt offline password cracking. After running the tool against the hash, the password was successfully recovered. With valid credentials for the david<\/strong> user now available, I tried to switch users but the discovered credential was not working.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Continuing my enumeration of the filesystem, I discovered an archive named backup-ssh-identity-files.tgz<\/code><\/strong>. The filename immediately stood out, as it suggested the archive might contain SSH keys or other authentication material. Access to such files could potentially allow lateral movement or direct login as another user, so I proceeded to extract and inspect its contents.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

To analyze the archive, I used Netcat<\/strong> to transfer the file from the target machine to my attacker system. Once the file was successfully copied over, I extracted it locally to inspect its contents.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n

With the archive now on my local attacker machine, I extracted its contents and found an SSH private key. Since the key was protected with a passphrase, I used ssh2john<\/code><\/strong> to convert the private key into a hash format compatible with John the Ripper<\/strong>. After generating the hash, I ran John<\/strong> again to brute-force the passphrase. The attack was successful, and I recovered the private key\u2019s password, allowing me to use the key for SSH authentication.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

After gaining SSH access as david<\/strong>, I began enumerating the system for potential privilege escalation vectors. During this process, I discovered a script in David\u2019s home directory that executed a sudo<\/code><\/strong> command running journalctl<\/code>. Since journalctl<\/code> can sometimes be abused to spawn a pager or shell under elevated privileges, this immediately looked promising. I began researching possible techniques to leverage this behavior for privilege escalation.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

While researching journalctl<\/code> on GTFOBins<\/strong>, I discovered that journalctl<\/code> uses less<\/code><\/strong> as its default pager. Because less<\/code> allows shell escapes when running with elevated privileges, this behavior can potentially be abused to execute arbitrary commands as root<\/strong>. This confirmed that the journalctl<\/code> sudo permission could be leveraged as a viable privilege escalation vector.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n

After executing the command in the script, I used the technique documented on GTFOBins to exploit the pager spawned by journalctl<\/code>. By escaping from the less<\/code> pager, I was able to execute a shell with elevated privileges. This successfully dropped me into a root shell<\/strong>, completing the privilege escalation and giving me full control over the system.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

This box demonstrated the importance of thorough enumeration and careful analysis of exposed services. By identifying a vulnerable Nostromo 1.9.6<\/strong> web server, I was able to gain initial access through a remote command execution vulnerability. From there, credential discovery and password cracking allowed lateral movement to the david<\/strong> user. Finally, misconfigured sudo<\/code> permissions involving journalctl<\/code> provided a straightforward path to privilege escalation via pager escape, resulting in full root access.<\/p>\n","protected":false},"excerpt":{"rendered":"

I began with an Nmap scan to identify open TCP ports, detect service versions, and run the default NSE scripts. The scan revealed two open ports: 22 (SSH) and 80 (HTTP). Port 80 was hosting a web server identified as Nostromo version 1.9.6. This immediately caught my attention, as Nostromo […]<\/p>\n","protected":false},"author":1,"featured_media":622,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3,4],"tags":[],"class_list":["post-605","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cybersecurity","category-pentesting"],"brizy_media":[],"_links":{"self":[{"href":"https:\/\/thecyberstaff.com\/index.php?rest_route=\/wp\/v2\/posts\/605","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/thecyberstaff.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/thecyberstaff.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/thecyberstaff.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/thecyberstaff.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=605"}],"version-history":[{"count":2,"href":"https:\/\/thecyberstaff.com\/index.php?rest_route=\/wp\/v2\/posts\/605\/revisions"}],"predecessor-version":[{"id":623,"href":"https:\/\/thecyberstaff.com\/index.php?rest_route=\/wp\/v2\/posts\/605\/revisions\/623"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/thecyberstaff.com\/index.php?rest_route=\/wp\/v2\/media\/622"}],"wp:attachment":[{"href":"https:\/\/thecyberstaff.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=605"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/thecyberstaff.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=605"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/thecyberstaff.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=605"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}