IKEv1 aggresive mode

I know that IKEv2 is getting popular but still IKEv1 has a huge presence in production networks. There are many reasons but I’m not going to focus on them. I would rather focus on one issue I see from time to time: ikev1 and an aggressive mode. Just to remind you, there are two modes of ikev1: aggressive and main. The first one is much faster, only three messages are exchanged, but it isn’t secure as the main mode (with six messages). The main problem with the aggressive mode is the first two messages contain data which may help to perform attack on your VPN.

For this test I set up VPN on ASA with ‘aggressive mode’ enabled:

ciscoasa# sh run crypto
crypto ipsec ikev1 transform-set TS esp-3des esp-md5-hmac
crypto map MAPA 10 match address ACL
crypto map MAPA 10 set peer 192.168.111.128
crypto map MAPA 10 set ikev1 transform-set TS
crypto map MAPA interface inside
crypto ikev1 enable inside
crypto ikev1 policy 10
authentication pre-share
encryption 3des
hash md5
group 2
lifetime 86400
crypto ikev1 policy 65535
authentication pre-share
encryption 3des
hash sha
group 2
lifetime 86400
ciscoasa#
ciscoasa# sh run tunnel
tunnel-group 192.168.111.128 type ipsec-l2l
tunnel-group 192.168.111.128 ipsec-attributes
ikev1 pre-shared-key *****
ciscoasa#
To be 100% sure the aggressive mode is enabled:

ciscoasa(config)# no crypto ikev1 am-disable

There is one tool, quite old but still very useful: ike-scan

Let’s try to scan my ASA:

You can use the flag ‘-P’ to see hash of the PSK:

The flag ‘-P’ is valid only with the aggressive mode as the main mode doesn’t reply with hash in 2^nd message. You can also save the hash directly to the file (‘-Pfilename.txt), what is useful when you run a script:

As we can see the file contain the hash:

Then we can use another tool (psk-crack) to decode the hash. It took just 10 minutes to find the pre-share-key:

As you can see it didn’t take too much time to find out what is your PSK. I know my PSK was simple but you can use a dictionary attack on much powerful machine. One lesson from today’s lab: never use the aggressive mode and migrate to PKI if possible.

Comments

What should you know about HA 'override enabled' setting on Fortigate?

High availability is mandatory in most of today's network designs. Only very small companies or branches can run their business without redundancy. When you have Fortigate firewall in your network you have many options to increase network availability. You can use Fortigate Clustering Protocol ( FGCP ) or Virtual Router Redundancy Protocol ( VRRP ). FGCP has two modes: 'override' disabled (default) and 'override' enabled . I'm not going to explain how to set up HA as you can find many resources on Fortinet websites: https://cookbook.fortinet.com/high-availability-two-fortigates-56/ https://cookbook.fortinet.com/high-availability-with-fgcp-56/ Let's recap what is the main difference between them. The default HA setting is 'override' disabled and this is an order of selection an active unit: 1) number of monitored interfaces - when both units have the same number of working (up) interfaces check next parameter 2) HA uptime - an ...

FortiGate and GRE tunnel

Recently I worked on one project where a client requested to re-route web traffic to the GRE tunnel to perform traffic inspection. I would like to share with you what is required if you configure it on FortiGate. We need a new GRE interface and policy base routing (PBR) to change the route for specific source IPs. Of course you need firewall policies to permit the traffic. Let's start with GRE interface. Unfortunately you can't configure it using the GUI, only CLI is the option: config system gre-tunnel edit "gre1" set interface "port1" set local-gw 55.55.55.55 set remote-gw 44.44.44.44 next end When the end peer is Cisco router, you need to set the IP for the GRE interface: config system interface edit gre1 set ip 192.168.10.10 255.255.255.255 set remote-ip192.168.10.20 end In next step we need to fix routing. We need the alternate path via GRE but to keep the route in the active routing table you need to set the same AD (adminis...

Inpection of asymmetric sessions on FortiGate

There is one feature available on FortiGate, and I think you should know it, as it modifies a bit what we know about stateful firewalls. In past every packet was treated individually and you had to create policies in both directions. With stateful firewalls we can track connections, and by checking couple of attributes, we can treat them as part of the same session. For example when you initiate connection from a host1 to host2, the returning connection from host2 to host1 will be treated as part of the same connection (session). They have to have the same source/destination and destination/source IPs, port numbers and interfaces.There is an exception from this rule and FortiGate in some specific cases can accept connections on port which was not used in the initial connection. Let me explain how it works on the below example: The host1 has a default gateway on R1 (10.0.1.2), but you may notice that it is not the optimal path to host2 subnet. When we analyze ...

myITmicroblog

Search This Blog