An investigation into the compromise of dev-jumpbox, an Alpine Linux 3.24.3 host, through SSHole (CVE-2026-123158), an OpenSSH password authentication bypass affecting musl-based systems without PAM. This writeup follows the attack from the exposed service account to the activity that followed: a port sweep of the local subnet, a remotely fetched script, and the exfiltration and shredding of forensic evidence
So whilst travelling back home, I had time on my hands since I arrived at the airport 5 HOURS early because I thought the traffic would be bad *turns out it was ok.
Welcome to a comprehensive guide through five interesting cryptographic and steganographic challenges! Each one teaches a different technique for hiding or protecting information. Whether you’re new to CTFs or looking to expand your toolkit, these challenges showcase common patterns you’ll encounter in cybersecurity competitions.
In today’s digital landscape, network security is a critical concern for organizations and individuals. Cyberattacks are becoming increasingly sophisticated, making it essential to detect and mitigate potential threats in real time. Traditional intrusion detection systems (IDS) often struggle with high false-positive rates or fail to adapt to evolving attack patterns (Cisco, 2023).
Scenario
In this very easy Sherlock, you will familiarize yourself with Unix auth.log and wtmp logs. We’ll explore a scenario where a Confluence server was brute-forced via its SSH service. After gaining access to the server, the attacker performed additional activities, which we can track using auth.log. Although auth.log is primarily used for brute-force analysis, we will delve into the full potential of this artifact in our investigation, including aspects of privilege escalation, persistence, and even some visibility into command execution.
Sherlock Scenario
The IDS device alerted us to a possible rogue device in the internal Active Directory network. The Intrusion Detection System also indicated signs of LLMNR traffic, which is unusual. It is suspected that an LLMNR poisoning attack occurred. The LLMNR traffic was directed towards Forela-WKstn002, which has the IP address 172.17.79.136. A limited packet capture from the surrounding time is provided to you, our Network Forensics expert. Since this occurred in the Active Directory VLAN, it is suggested that we perform network threat hunting with the Active Directory attack vector in mind, specifically focusing on LLMNR poisoning.
Challenge Description
The program provided allows you to write to a file and read what you wrote from it. Try playing around with it and see if you can break it!