Fundacja Rozwoju Regionu Gołdapedukacja techniczno informatyczna
Access:

» IPsec VPN discovery and fingerprinting

Related categories: VPN

Roy Hills
Viewed: 11736 | Article date: 2006-02-09 15:47:25

Many people believe that IPsec VPN systems are invisible and inherently secure. However, in reality most implementations can be easily detected and fingerprinted. Once this step is achieved, a successful attack is only a matter of time.

 

About the author

Roy Hills is the founder of NTA Monitor Ltd, a UK based security testing company. He wrote the ike-scan tool to investigate IPsec security, and has found several vulnerabilities using this tool in products from Checkpoint, Cisco, Nortel, and Juniper.

 

 

Many people believe that IPsec VPN systems are invisible and inherently secure. However, in reality most implementations can be easily detected and fingerprinted. Once this step is achieved, a successful attack is only a matter of time.

VPN security is often overlooked during a penetration test. There are several reasons for this: VPNs are often considered inherently secure because they employ strong cryptography, IPsec VPNs don't normally get picked up by a port scan, and many people are intimidated by the complexity of the protocol. However, given the correct tools and techniques, it is relatively straightforward to discover and fingerprint these systems.

We will show how it is possible to discover IPsec VPNs (see Inset Introduction to IPsec), and then determine what equipment is being used and find other useful information. We will see that the complexity of the IPsec protocol actually makes fingerprinting VPNs easier, because every manufacturer interprets the standards in a slightly different way.

 

 

What you will learn...

-how to discover IPsec VPN systems,

-how to use fingerprinting techniques to determine the type of VPN system.

What you should know...

-TCP/IP networking concepts,

-the basics of IPsec VPNs.

 

IPsec VPN detection

IPsec VPN servers generally will not be detected by a port scan. This is because they don't listen on any TCP ports, so a TCP port scan won't find them. What is more, they don't normally send ICMP unreachable messages, so a UDP port scan won't pick up IKE on port 500 (a standard port for such connections) and a raw IP scan won't pick up ESP or AH with IP protocols 50 and 51. In addition, the IPsec RFCs specify that incorrectly formatted packets should be ignored, so sending random garbage to UDP port 500 or IP protocols 50 and 51 will not normally elicit any response either.

 

Figure 1. Overview of the IPsec protocol framework

 

Page: 1 2 3
Buy article Buy subscription
Buy now add to cart
add to cart
Standard price: 2€/$3 Standard price: 25€/$30
Buy article for as little as (2€/$3) each allow access to individual articles. Buy a full access to our Hakin9 archive portal. You will be able to read the articles from all archive issues from year 2005 and 2006. For just 25€/$30 you get unrestricted access to the entire website for the whole year.
SDJhakin9

.SDJ Users:


.:Login
.:Password

[Register]
[Forgotten your password?]

...hakin9 StarterKit IT Practical Solutions for Newbies

...Shopping Cart

sum: 0 €
Choose currency:

...SUBSCRIBE TO
hakin9 Print Edition


...Advertisement



...Conferences

...Topics

...Advertisement

 

 

Subscribe | Contact Us | Newsletter | See all issues | About Hakin9
Copyright C 2006 by Software Developer's Journal. All rights reserved.