<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>P1 Labs &#187; Diameter</title>
	<atom:link href="http://labs.p1sec.com/tag/diameter/feed/" rel="self" type="application/rss+xml" />
	<link>http://labs.p1sec.com</link>
	<description>P1 Security Labs</description>
	<lastBuildDate>Wed, 31 Dec 2014 00:24:12 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=4.1</generator>
	<item>
		<title>[Hackito Ergo Sum 2014] Hacking Telco Equipment: The HLR/HSS</title>
		<link>http://labs.p1sec.com/2014/05/07/hackito-ergo-sum-2014-hacking-telco-equipment-the-hlrhss/</link>
		<comments>http://labs.p1sec.com/2014/05/07/hackito-ergo-sum-2014-hacking-telco-equipment-the-hlrhss/#comments</comments>
		<pubDate>Wed, 07 May 2014 18:11:57 +0000</pubDate>
		<dc:creator><![CDATA[Laurent Ghigonis]]></dc:creator>
				<category><![CDATA[Conferences]]></category>
		<category><![CDATA[Network & Protocols]]></category>
		<category><![CDATA[News]]></category>
		<category><![CDATA[Reverse engineering]]></category>
		<category><![CDATA[Diameter]]></category>
		<category><![CDATA[fuzzing]]></category>
		<category><![CDATA[hlr]]></category>
		<category><![CDATA[hss]]></category>
		<category><![CDATA[reverse]]></category>
		<category><![CDATA[ss7]]></category>
		<category><![CDATA[system]]></category>
		<category><![CDATA[virtualization]]></category>

		<guid isPermaLink="false">http://labs.p1sec.com/?p=529</guid>
		<description><![CDATA[P1 Security presented at the Hackito Ergo Sum 2014 conference in Paris (http://2014.hackitoergosum.org/) the weaknesses of Telecom Infrastructure systems, and particularly HLR/HSS equipment. Hacking Telco equipment: The HLR/HSS, by Laurent Ghigonis from P1Security Download slides here. Abstract: HLR...]]></description>
				<content:encoded><![CDATA[<p style="color: #b30f25;"><span style="color: #505050;">P1 Security presented at the Hackito Ergo Sum 2014 conference in Paris (</span><a style="color: #ea6315;" href="http://2014.hackitoergosum.org/">http://2014.hackitoergosum.org/</a><span style="color: #505050;">) the weaknesses of Telecom Infrastructure systems, and particularly HLR/HSS equipment.</span></p>
<p><iframe style="border: 1px solid #CCC; border-width: 1px 1px 0; margin-bottom: 5px; max-width: 100%;" src="http://www.slideshare.net/slideshow/embed_code/34291135" width="597" height="486" frameborder="0" marginwidth="0" marginheight="0" scrolling="no" allowfullscreen="allowfullscreen"> </iframe></p>
<div style="margin-bottom: 5px;"><strong> <a title="Hacking Telco equipment: The HLR/HSS, by Laurent Ghigonis" href="https://www.slideshare.net/p1sec/day1-hacking-telcoequipmentthehlrhsslaurentghigonisp1sec" target="_blank">Hacking Telco equipment: The HLR/HSS, by Laurent Ghigonis</a> </strong> from <strong><a href="http://www.slideshare.net/p1sec" target="_blank">P1Security</a></strong></div>
<p>Download slides <a href="http://2014.hackitoergosum.org/slides/day1_Hacking-telco-equipment-The-HLR-HSS-Laurent-Ghigonis-p1sec.pdf">here</a>.</p>
<p>Abstract:</p>
<p>HLR and HSS are the most important Telecom Equipment in an Operator Core Network.<br />
We are going to see that this so-called “Critical Infrastructure” is not as robust as you could think, by exploring the some weaknesses of the HLR/HSS equipment.</p>
<p>Plan:<br />
* Virtualization of HLR/HSS, for instrumentation purposes<br />
* HLR/HSS system analysis<br />
* SS7/Diameter network fuzzing<br />
* HLR/HSS binaries reverse</p>
<p>We also did another presentation on <a style="color: #ea6315;" href="http://labs.p1sec.com/2014/05/02/hackito-ergo-sum-2014-worldwide-attacks-on-ss7sigtran-network/">Worldwide attacks on SS7/SIGTRAN network</a> at HES.</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://labs.p1sec.com/2014/05/07/hackito-ergo-sum-2014-hacking-telco-equipment-the-hlrhss/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Diameter vs SS7 from a security perspective</title>
		<link>http://labs.p1sec.com/2013/07/28/346/</link>
		<comments>http://labs.p1sec.com/2013/07/28/346/#comments</comments>
		<pubDate>Sun, 28 Jul 2013 22:34:42 +0000</pubDate>
		<dc:creator><![CDATA[Philippe Langlois]]></dc:creator>
				<category><![CDATA[Network & Protocols]]></category>
		<category><![CDATA[News]]></category>
		<category><![CDATA[Diameter]]></category>
		<category><![CDATA[pcap]]></category>
		<category><![CDATA[telecom]]></category>
		<category><![CDATA[wireshark]]></category>

		<guid isPermaLink="false">http://labs.p1sec.com/?p=346</guid>
		<description><![CDATA[On a dedicated forum to Diameter, one person asked about the main difference between SS7 and Diameter. While some expert answered on the telecom and protocol aspect, we answered on the security side: From a security standpoint SS7 (and SIGTRAN, its transport over IP) is a legacy protocol (but still ...]]></description>
				<content:encoded><![CDATA[<p>On a dedicated forum to Diameter, one person asked about the main difference between SS7 and Diameter. While some expert answered on the telecom and protocol aspect, we answered on the security side:</p>
<div style="width: 266px" class="wp-caption alignleft"><img class=" " alt="" src="http://wiki.jss7.googlecode.com/git/images/MobicentsjSS7Layers.jpg" width="256" height="192" /><p class="wp-caption-text">Source: Mobicents</p></div>
<p>From a security standpoint SS7 (and SIGTRAN, its transport over IP) is a legacy protocol (but still the most used protocol for roaming), with protocol stacks which are sometime not very robust, even fragile, and have been released with only reliability to load in mind, not with reliability in front of malformed traffic. Hence the quite high number of crashes we witness in telecom and mobile core networks.</p>
<p>The reason for this is also the former lack of deep testing tools (fuzzers, scanners, etc..): for example, most of the fuzzers target at best M3UA (one of the encapsulation layer of SS7 over IP which is part of SIGTRAN) and do not cross neither its state machine nor the encoding. Fuzzing is mostly affecting the decoding of these message (ASN1), not the applications (MAP, INAP, CAP, &#8230;).</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<div style="width: 247px" class="wp-caption alignright"><img alt="" src="http://www.diametriq.com/wp-content/uploads/2013/04/Diameter-Edge-Appliance.jpg" width="237" height="189" /><p class="wp-caption-text">Source: Diametriq</p></div>
<p>Diameter is much more inspired by IETF / Internet philosophy and practices. IP protocols being more exposed to attacks, the protocols are a little bit more security-minded in term of resilience in front of hostile activities. Using Diameter also means that more attacker will know how to attack these protocols, hence more threat pressure.<br />
Diameter is an evolution of Radius (hint: Diameter = Radius * 2).<br />
Some very questionable protocol design decision involve for example the removal of Radius shared secret. Another questionable design decision is to consider that Diameter must either be transported with TLS _or_ with IPsec. This is very damageable as the Diameter protocol has no way to verify that IPsec is really used underneath. Therefore, some deployment are done in Diameter mode &#8220;as&#8221; IPsec but without IPsec being deployed, therefore without spoofing or interception protection.</p>
<p>Another factor is the &#8220;reach&#8221; of signaling messages. Deep reach vs. Shallow reach.<br />
For example, SS7 has deep reach, can go from deep into Roaming network and deep toward Home network. For Diameter, it depends on the application being used (CCA, &#8230;).</p>
<p>Lastly, SS7 is being used for roaming and interworking of thousands of operators in the world whereas Diameter is being used only for maybe 10 to 20 operators for LTE roaming. SS7 and Diameter are both just &#8220;tubes&#8221; for transporting messages. Their respective strength is overrated, specifically with the myth or belief that SS7 and IPX network being closed, secure networks. They are not, they are as secure as the least secure operator having access to these. We will see the real impact and usage of Diameter as a worldwide transport mechanism in the future, but already one can see that it&#8217;s not a magic bullet regarding security from the audits we&#8217;ve done.</p>
<p>Some things P1 Security does with SS7, SIGTRAN and Diameter is:<br />
* Scanning with PTA<br />
* Fuzzing with PTF<br />
* Intrusion/Misuse detection with PTM<br />
and professional services, audits.</p>
<p>A few links about Diameter security at P1:<br />
<a href="http://www.linkedin.com/redirect?url=http%3A%2F%2Fwww%2Ep1sec%2Ecom%2Fcorp%2Fconsulting%2Flte-and-diameter-audit%2F&amp;urlhash=bMte&amp;_t=tracking_disc" target="_blank">http://www.p1sec.com/corp/consulting/lte-and-diameter-audit/</a><br />
<a href="http://www.linkedin.com/redirect?url=http%3A%2F%2Fwww%2Ep1sec%2Ecom%2Fcorp%2F2013%2F05%2F01%2Fp1-security-newsletter-the-6-best-ways-to-secure-your-telecom-network%2F&amp;urlhash=jA91&amp;_t=tracking_disc" target="_blank">http://www.p1sec.com/corp/2013/05/01/p1-security-newsletter-the-6-best-ways-to-secure-your-telecom-network/</a></p>
<p>Regarding the <a href="http://www.p1sec.com/corp/products/vulnerability-knowledge-base-vkb/">VKB</a>, we have seen so far fewer vulnerabilities on Diameter than on SS7:</p>
<p>Total <a href="https://saas.p1sec.com/vulns?search%5Border%5D=&amp;search%5Bfull_search_like%5D=PROTO_DIAMETER+&amp;commit=Search">Diameter vulnerabilities</a>: 10<br />
<a href="https://saas.p1sec.com/vulns?search%5Border%5D=&amp;search%5Bfull_search_like%5D=PROTO_SCCP&amp;commit=Search">SCCP vulnerabilities</a>: 18<br />
<a href="https://saas.p1sec.com/vulns?search%5Border%5D=&amp;search%5Bfull_search_like%5D=PROTO_MAP&amp;commit=Search">MAP vulnerabilities</a>: 46<br />
<a href="https://saas.p1sec.com/vulns?search%5Border%5D=&amp;search%5Bfull_search_like%5D=PROTO_INAP&amp;commit=Search">INAP vulnerabilities</a>: 4<br />
<a href="https://saas.p1sec.com/vulns?search%5Border%5D=&amp;search%5Bfull_search_like%5D=PROTO_TCAP&amp;commit=Search">TCAP vulnerabilities</a>: 4<br />
<span style="font-size: 13px; line-height: 19px;"><a href="https://saas.p1sec.com/vulns?search%5Border%5D=&amp;search%5Bfull_search_like%5D=PROTO_SCCP&amp;commit=Search">SCCP vulnerabilities</a>: 18<br />
</span>Total <a href="https://saas.p1sec.com/vulns?search%5Border%5D=&amp;search%5Bfull_search_like%5D=PROTO_SS7+&amp;commit=Search">SS7 vulnerabilities</a>: 90 (69 including overlaps vulnerabilities touching more than one SS7 protocol)</p>
<p>But this is also an exposure bias: we have seen much more mature/production deployment of SS7 than in Diameter so it&#8217;s only natural that the old protocol&#8217;s vulnerabilities are more known than the ones of recent protocols.</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://labs.p1sec.com/2013/07/28/346/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
