Attacking 3G and 4G Mobile Tele-Communications Networks

Document Title:
===============
Attacking 3G and 4G Mobile Tele-Communications Networks


References:
===========
Document: https://www.vulnerability-lab.com/resources/documents/320.pdf
Speaker: https://conference.hitb.org/hitbsecconf2011kul/?page_id=1782

Original Mirror:
https://www.c0decafe.de/publications.html

Conference Mirror:
https://conference.hitb.org/hitbsecconf2011kul/materials/D2%20LABS%20-%20Daniel%20Mende%20and%20Jim%20Geovedi%20-%20Practical%203G-4G%20Attacks.pdf



Release Date:
=============
2011-11-10


Vulnerability Laboratory ID (VL-ID):
====================================
320


Discovery Status:
=================
Published


Exploitation Technique:
=======================
Report


Severity Level:
===============
High


Technical Details & Description:
================================
In 2010 a number of practical high-profile attacks against GSM has been discussed and demonstrated. Still it should 
be noted that GSM ( 2G ) has been standardized in the early 90s, followed by the 3G family of standards in 2000 
which in turn is currently superseded (better: complemented) by yet another generation (4G). What about their security 
aspects? In this talk we ll outline 3G and 4G architectures and associated attack paths, enriched by anecdotes from 
the field and - potentially more interesting ;-) - results from some 3G/4G security testing performed in the wild.

Overview:
=======
-Overview 3G / 4G
-Backhaul Networks
- Backend Protocols in depth
- The Lab
- The Tools
- Exercises
- Conclusions


Credits & Authors:
==================
ERNW GmbH - Daniel Mende


Disclaimer & Information:
=========================
The information provided in this advisory is provided as it is without any warranty. Vulnerability-Lab disclaims all warranties, 
either expressed or implied, including the warranties of merchantability and capability for a particular purpose. Vulnerability-
Lab or its suppliers are not liable in any case of damage, including direct, indirect, incidental, consequential loss of business 
profits or special damages, even if Vulnerability-Lab or its suppliers have been advised of the possibility of such damages. Some 
states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation 
may not apply. We do not approve or encourage anybody to break any vendor licenses, policies, deface websites, hack into databases 
or trade with fraud/stolen material.

Domains:    www.vulnerability-lab.com   	- www.vuln-lab.com			       - www.vulnerability-lab.com/register
Contact:    [email protected] 	- [email protected] 	       - [email protected]
Section:    video.vulnerability-lab.com 	- forum.vulnerability-lab.com 		       - news.vulnerability-lab.com
Social:	    twitter.com/#!/vuln_lab 		- facebook.com/VulnerabilityLab 	       - youtube.com/user/vulnerability0lab
Feeds:	    vulnerability-lab.com/rss/rss.php	- vulnerability-lab.com/rss/rss_upcoming.php   - vulnerability-lab.com/rss/rss_news.php

Any modified copy or reproduction, including partially usages, of this file requires authorization from Vulnerability Laboratory. 
Permission to electronically redistribute this alert in its unmodified form is granted. All other rights, including the use of other 
media, are reserved by Vulnerability-Lab Research Team or its suppliers. All pictures, texts, advisories, sourcecode, videos and 
other information on this website is trademark of vulnerability-lab team & the specific authors or managers. To record, list (feed), 
modify, use or edit our material contact ([email protected] or [email protected]) to get a permission.

    				   	Copyright © 2012 | Vulnerability Laboratory