Remove 2000 Remove DNS Remove Internet Remove Risk
article thumbnail

Microsoft Buys Corp.com So Bad Guys Can’t

Krebs on Security

From February’s piece: At issue is a problem known as “ namespace collision ,” a situation where domain names intended to be used exclusively on an internal company network end up overlapping with domains that can resolve normally on the open Internet. Further reading: Mitigating the Risk of DNS Namespace Collisions (PDF).

DNS 328
article thumbnail

Linux Ghost Vulnerability: A GHOST in the….Linux….Wires

NopSec

Applications have access to the DNS resolver primarily through the gethostbyname*() set of functions. The risk associated with this vulnerability is that an attacker who exploits this issue can gain complete control of the compromised system. released on November 10, 2000. and glibc-2.18).

DNS 52
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Dangerous Domain Corp.com Goes Up for Sale

Krebs on Security

At issue is a problem known as “ namespace collision ,” a situation where domain names intended to be used exclusively on an internal company network end up overlapping with domains that can resolve normally on the open Internet. INSTANT CORPORATE BOTNET, ANYONE? Department of Homeland Security. Control corp.com.”

DNS 338
article thumbnail

Cyber CEO: The History Of Cybercrime, From 1834 To Present

Herjavec Group

1988 — The Morris Worm — Robert Morris creates what would be known as the first worm on the Internet. 2000 — Lou Cipher — Barry Schlossberg, aka Lou Cipher, successfully extorts $1.4 2002 – Internet Attack — By targeting the thirteen Domain Name System (DNS) root servers, a DDoS attack assaults the entire Internet for an hour.