<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>NetScaler on Martin&#39;s Blog</title>
		<link>https://mac.sploit.dk/tags/netscaler/</link>
		<description>Recent content in NetScaler on Martin&#39;s Blog</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Mon, 07 Sep 2026 20:00:00 +0200</lastBuildDate>
		
			<atom:link href="https://mac.sploit.dk/tags/netscaler/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Inside a Network Appliance: Assessing NetScaler ADC 14.1</title>
				<link>https://mac.sploit.dk/blog/inside-a-netscaler-vpx-security-assessment/</link>
				<pubDate>Mon, 07 Sep 2026 20:00:00 +0200</pubDate>
				<guid>https://mac.sploit.dk/blog/inside-a-netscaler-vpx-security-assessment/</guid>
				<description>&lt;p&gt;Network appliances are often treated as sealed boxes. In reality, most modern&#xA;appliances, especially virtual appliances, are software distributions built from&#xA;a general-purpose operating system, open-source middleware, third-party&#xA;libraries, scripts, and proprietary services.&lt;/p&gt;&#xA;&lt;p&gt;That composition is not inherently unsafe. Apache, PHP, OpenSSH, OpenSSL,&#xA;Python, PostgreSQL, and FreeBSD can all be operated securely. The risk appears&#xA;when a vendor combines a large software inventory with weak privilege&#xA;separation, inconsistent authorization, incomplete exploit mitigations, opaque&#xA;updates, and limited forensic visibility.&lt;/p&gt;&#xA;&lt;p&gt;This post examines one such system: a NetScaler ADC VPX appliance running&#xA;&lt;strong&gt;NetScaler 14.1 build 73.30&lt;/strong&gt;. It is not a claim that every NetScaler version or&#xA;deployment behaves identically. It is a case study of one exact build, tested&#xA;inside an isolated and disposable lab.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
