500/udp - Pentesting IPsec/IKE VPN
Basic Information
IPsec is the most commonly used technology for both gateway-to-gateway (LAN-to-LAN) and host to gateway (remote access) enterprise VPN solutions.
IKE is a type of ISAKMP (Internet Security Association Key Management Protocol) implementation, which is a framework for authentication and key exchange. IKE establishes the security association (SA) between two endpoints through a three-phase process:
Phase 1: Establish a secure channel between 2 endpoints using a Pre-Shared Key (PSK) or certificates. It can use main mode (3 pairs of messages) or aggresive mode.
Phase1.5: This is optional, is called Extended Authentication Phase and authenticates the user that is trying to connect (user+password).
Phase2: Negotiates the parameter for the data security using ESP and AH. It can use a different algorithm than the one used in phase 1 (Perfect Forward Secrecy (PFS)).
Default port: 500/udp
Discover the service using nmap
Finding a valid transformation
The IPSec configuration can be prepared only to accept one or a few transformations. A transformation is a combination of values. Each transform contains a number of attributes like DES or 3DES as the encryption algorithm, SHA or MD5 as the integrity algorithm, a pre-shared key as the authentication type, Diffie-Hellman 1 or 2 as the key distribution algorithm and 28800 seconds as the lifetime.
Then, the first thing that you have to do is find a valid transformation, so the server will talk to you. To do so, you can use the tool ike-scan. By default, Ike-scan works in main mode, and sends a packet to the gateway with an ISAKMP header and a single proposal with eight transforms inside it.
Depending on the response you can obtain some information about the endpoint:
As you can see in the previous response, there is a field called AUTH with the value PSK. This means that the vpn is configured using a preshared key (and this is really good for a pentester). The value of the last line is also very important:
0 returned handshake; 0 returned notify: This means the target is not an IPsec gateway.
1 returned handshake; 0 returned notify: This means the target is configured for IPsec and is willing to perform IKE negotiation, and either one or more of the transforms you proposed are acceptable (a valid transform will be shown in the output)
0 returned handshake; 1 returned notify: VPN gateways respond with a notify message when none of the transforms are acceptable (though some gateways do not, in which case further analysis and a revised proposal should be tried).
Then, in this case we already have a valid transformation but if you are in the 3rd case, then you need to brute-force a little bit to find a valid transformation:
First of all you need to create all the possible transformations:
And then brute-force each one using ike-scan (this can take several minutes):
If the brute-force didn't work, maybe the server is responding without handshakes even to valid transforms. Then, you could try the same brute-force but using aggressive mode:
In DH Group also: 14 = 2048-bit MODP and 15 = 3072-bit 2 = HMAC-SHA = SHA1 (in this case). The --trans format is $Enc,$Hash,$Auth,$DH
Cisco recommends avoidance of DH groups 1 and 2 in particular. The paper’s authors describe how it is likely that nation states can decrypt IPsec sessions negotiated using weak groups via discrete log precomputation. The hundreds of millions of dollars spent performing precomputation are amortised through the real-time decryption of any session using a weak group (1,024-bit or smaller).
Server fingerprinting
Then, you can use ike-scan to try to discover the vendor of the device. The tool send an initial proposal and stops replaying. Then, it will analyze the time difference between the received messages from the server and the matching response pattern, the pe tester can successfully fingerprint the VPN gateway vendor. More over, some VPN servers will use the optional Vendor ID (VID) payload with IKE.
Specify the valid transformation if needed (using --trans)
If IKE discover which is the vendor it will print it:
This can be also achieve with nmap script ike-version
Finding the correct ID (group name)
For being allowed to capture the hash you need a valid transformation supporting Aggressive mode and the correct ID (group name). _**_You probably won't know the valid group name, so you will have to brute-force it. To do so, I would recommend you 2 methods:
Bruteforcing ID with ike-scan
First of all try to make a request with a fake ID trying to gather the hash ("-P"):
If no hash is returned, then probably this method of brute forcing will work. If some hash is returned, this means that a fake hash is going to be sent back for a fake ID, so this method won't be reliable to brute-force the ID. For example, a fake hash could be returned (this happens in modern versions):
But if as I have said, no hash is returned, then you should try to brute-force common group names using ike-scan.
This script will try to brute-force possible IDs and will return the IDs where a valid handshake is returned (this will be a valid group name).
If you have discovered an specific transformation add it in the ike-scan command. And if you have discovered several transformations feel free to add a new loop to try them all (you should try them all until one of them is working properly).
Or use this dict (is a combination of the other 2 dicts without repetitions):
Bruteforcing ID with Iker
Bruteforcing ID with ikeforce
By default ikeforce will send at the beginning some random ids to check the behaviour of the server and determinate the tactic to use.
The first method is to brute-force the group names by searching for the information Dead Peer Detection DPD of Cisco systems (this info is only replayed by the server if the group name is correct).
The second method available is to checks the number of responses sent to each try because sometimes more packets are sent when the correct id is used.
The third method consist on searching for "INVALID-ID-INFORMATION" in response to incorrect ID.
Finally, if the server does not replay anything to the checks, ikeforce will try to brute force the server and check if when the correct id is sent the server replay with some packet. Obviously, the goal of brute forcing the id is to get the PSK when you have a valid id. Then, with the id and PSK you will have to bruteforce the XAUTH (if it is enabled).
If you have discovered an specific transformation add it in the ikeforce command. And if you have discovered several transformations feel free to add a new loop to try them all (you should try them all until one of them is working properly).
Sniffing ID
It is also possible to obtain valid usernames by sniffing the connection between the VPN client and server, as the first aggressive mode packet containing the client ID is sent in the clear (from the book Network Security Assessment: Know Your Network)
Capturing & cracking the hash
Finally, If you have find a valid transformation and the group name and the aggressive mode is allowed, then you can very easily grab the crackable hash:
The hash will be saved inside hash.txt
You can use psk-crack to crack the password
XAuth
Most implementations use aggressive mode IKE with a PSK to perform group authentication, and XAUTH to provide additional user authentication (via Microsoft Active Directory, RADIUS, or similar). Within IKEv2, EAP replaces XAUTH to authenticate users.
Local network MitM to capture credentials
Also, using IPSec try to make a MitM attack and block all traffic to port 500, if the IPSec tunnel cannot be established maybe the traffic will be sent in clear.
Brute-forcing XAUTH username ad password with ikeforce
To brute force the XAUTH (when you know a valid group name id and the psk) you can use a username or list of usernames and a list o passwords:
This way, ikeforce will try to connect using each combination of username:password.
If you found one or several valid transforms just use them like in the previous steps.
Authentication with an IPSEC VPN
In Kali VPNC is used to establish IPsec tunnels. The profiles have to be located in /etc/vpnc/ **and you can use the tool _vpnc_ to call them. Example taken from book Network Security Assessment 3rd Edition**.
Reference Material
Shodan
port:500 IKE
Last updated
