<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Network-Forensics on Blue Team Write-ups</title><link>https://zviarcyber.github.io/tags/network-forensics/</link><description>Recent content in Network-Forensics on Blue Team Write-ups</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 19 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://zviarcyber.github.io/tags/network-forensics/index.xml" rel="self" type="application/rss+xml"/><item><title>OpenWire — Investigating an Apache ActiveMQ RCE (CVE-2023-46604)</title><link>https://zviarcyber.github.io/posts/openwire-cyberdefenders/</link><pubDate>Fri, 19 Jun 2026 00:00:00 +0000</pubDate><guid>https://zviarcyber.github.io/posts/openwire-cyberdefenders/</guid><description>&lt;h2 id="abstract">Abstract&lt;/h2>
&lt;p>A network forensics walkthrough of the CyberDefenders &lt;strong>OpenWire&lt;/strong> challenge. Starting from a
single PCAP and a tier-1 escalation about a public-facing server beaconing to suspicious IPs, I
trace an Apache ActiveMQ compromise via &lt;strong>CVE-2023-46604&lt;/strong>: from the initial remote code
execution on the OpenWire port, through a malicious Spring XML payload that abuses
&lt;code>java.lang.ProcessBuilder&lt;/code>, down to a dropped reverse shell talking to two separate C2 servers.&lt;/p>
&lt;h2 id="scenario">Scenario&lt;/h2>
&lt;blockquote>
&lt;p>During your shift as a tier-2 SOC analyst, you receive an escalation from a tier-1 analyst about
a public-facing server. The server has been flagged for outbound connections to multiple
suspicious IPs. Following the incident response process, the host is isolated from the network
and a packet capture is pulled from the NSM sensor. Your task is to analyse the PCAP and assess
for signs of malicious activity.&lt;/p></description></item></channel></rss>