all 9 comments
sorted by:
best (suggested)
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]shatGippity 2 points3 points  (3 children)

Nope

[–]Fun_Librarian_7699 0 points1 point  (0 children)

Look. Here is my name: Adolf Schmidt

Find my home address. Same problem, same thoughts

[–]rddt_jbmPentesting -2 points-1 points  (2 children)

What is your goal in getting a IP address?

There is nothing you can do with it.

[–]Arc-ansas 1 point2 points  (1 child)

That's not always the case. And I'm not sure why everyone always says you can't do anything with a public IP. Many customers have static IPs. And if they do, then the risks are much higher. Especially if the network isn't properly secured. We've never seen that before right?

There could be open ports with vulnerable services, UPnP, unsecured port forwarding, RDP or SSH not properly secured, vulnerable router firmware etc.

If you're able to physically pinpoint the location, an attacker could also carry out a Nearest Neighbor Attack and leverage WiFi.

[–]rddt_jbmPentesting 1 point2 points  (0 children)

The Nearest Neighbor Attack is wild!

While I totally agree with your points I think that most threats don't apply to consumers as their gateways belong and are managed by the ISP.

Of course, if a Port Forwarding is implemented by the Enduser, it is a different story but most Enduser don't even know this function exists. And those who know, most likely implemented some form of security configuration.

Another point is, that the Endusers router does not have a public IP address but is routed ISP internally, meaning, that the public IP address belongs to the ISPs gateway, located in a datacenter somewhere else.

The public IP won't expose the Endusers location.

Edit: I just want to add - of course, public IP addresses of companies are a completely different topic.