2

If a 3rd party who is malicious manages to get a hold of a SSL private key for domain (ex: xyz.com), but does not have access to the domain registrar or DNS for the domain, how can the 3rd party utilize the SSL private key? Would they be able to man in middle? What are potential attack vectors?

Justin
  • 1,157
  • 3
  • 14
  • 20

1 Answers1

3

The attacker can use the private key to either mount an active man in the middle attack or decrypt passively sniffed traffic if RSA key exchange was used. The exact possibilities of an active man in the middle attack depends on the abilities and location of the attacker in the network. Some examples:

  • If the attacker is inside the local network of the victim he might try to use ARP spoofing or DHCP spoofing to either incorporate the router or the DNS server used by the victim.
  • At the ISP level the attacker could reroute DNS requests to a DNS server under his own control and this way direct the victim to its own fake system which uses the stolen certificate and key.
  • Similar attacks could be done if the attacker is near the original server or near the authoritative name server for the domain with the compromised certificate.
  • An attacker at a different ISP could also bring itself in the path to the original server or the authoritative DNS server by rerouting traffic using BGP spoofing.

For more information see the related questions What can an attacker do with a stolen SSL private key? What should the web admin do? and Can an attacker reuse stolen SSL private key to recreate that domain on his server.

Steffen Ullrich
  • 190,458
  • 29
  • 381
  • 434
  • Thank you. All your examples assume the attacker is able to access the local network. Let's assume they cannot. – Justin Sep 24 '17 at 07:08
  • 1
    @Justin: *"All your examples assume the attacker is able to access the local network."* - they don't. Only the first example assumes that the attacker is in the local network of the victim. The second example is at the WAN (ISP and similar) and the third assumes an attacker near the original server or near the servers authoritative name server. – Steffen Ullrich Sep 24 '17 at 07:11
  • Thanks. But assume the attacker as I stated in my question cannot control the domain or DNS. The origin server is hosted at a physically secure location such as AWS or Google Cloud as well. – Justin Sep 24 '17 at 07:13
  • 1
    @Justin: In your question you are only assuming that the attacker *"does not have access to the domain registrar or DNS for the domain"*. You did not exclude that the attacker is somewhere in the path to the authoritative DNS server for the domain nor did you exclude that the attacker is somewhere in the path to the DNS server used by the victim (i.e. often the DNS server provided by the ISP). But being in the path is enough to spoof DNS, no direct access to the DNS server or registrar is needed. – Steffen Ullrich Sep 24 '17 at 07:21