Monthly Archives: October 2014

DDoS Attacks Can Take Down Your Online Services Part 3: Defending Against DDoS Attacks

Various defense strategies can be invoked to defend against DDoS attacks. Many of these depend upon the intensity of the attack. We discuss some of these in this article. Mitigation Strategies Some protection from DDoS attacks can be provided by firewalls and intrusion-prevention systems (systems that monitor for malicious activity). When a DDoS attack begins, it is important to determine the method or methods that the attacker is using. The web site’s front-end networking devices and the server’s processing flow may be able to be reconfigured to stop the attack. UDP Attacks UDP (User Datagram Protocol) attacks send a mass of UDP requests to a victim system, which must respond to each request. One example is a ping attack. It is an enormous influx of ping requests from an attacker that requires the victim server to respond with ping responses. Another example of a UDP attack is when the Internet Control Message Protocol (ICMP) must be used by the server to return error messages. The messages may indicate that a requested service is unavailable or that a host or router cannot be reached. An attacker may send UDP messages to random ports on the victim server, and the server must respond with a “port unreachable” ICMP message. Mitigation Strategy In the case of a UDP attack, the firewall could be configured to reject all UDP messages. True, this would prevent legitimate use of UDP messages, such as pings sent by monitoring services to measure the uptimes and response times of the web site. However, to be shown as failed by a monitoring service is much better than actually being down. SYN Attacks In a SYN attack, a mass of connection requests are sent to the victim server via SYN messages. Typically, the victim server will assign connection resources and will respond with SYN ACK messages. The server expects the requesting client to complete the connections with ACK messages. However, the attacker never completes the connections; and the server soon runs out of resources to handle further connection requests. Mitigation Strategy In this case, the server connection facility could be reconfigured so that it did not assign connection resources until it received the ACK from the client. This would slightly extend the time required to establish a connection but would protect the server from being overwhelmed by this sort of an attack. DNS Reflection Attack A DNS reflection attack allows an attacker to send a massive amount of malicious traffic to a victim server by generating a relatively small amount of traffic. DNS requests with a spoofed victim address are sent to multiple DNS systems to resolve a URL. The DNS servers respond to the victim system with DNS responses. What makes this sort of attack so efficient is that the DNS response is about 100 times as large as the DNS request. Therefore, the attacker only needs to generate 1% of the traffic that will be sent to the victim system. DNS reflection attacks depend upon DNS open resolvers that will accept requests from anywhere on the Internet. DNS open resolvers were supposed to have been removed from the Internet, but 27 million still remain. Mitigation Strategy A defense against DNS reflection attacks is to allow only DNS responses from the domain of the victim server to be passed to the server. Mitigation Services Given a sufficiently large DDoSattack, even the steps mentioned here may not protect a system. If nothing else, the attack can overwhelm the bandwidth of the victim’s connection to the Internet. In such cases, the next step is to use the services of a DDoS mitigation company with large data centers that can spread the attack volume over multiple data centers and can scrub the traffic to separate bad traffic from legitimate traffic. Prolexic, Tata Communications, AT&T, Verisign, CloudFare, and others are examples of DDoS mitigation providers. These services will also monitor the nature of the attack and will adjust their defenses to be effective in the face of an attacker that modifies its strategies as the attack progresses. Legality DDoS attacks are specifically outlawed by many countries. Violators in the U.K. can serve up to ten years in prison. The U.S. has similar penalties, as do most major countries. However, there are many countries from which DDoS attacks can be launched without penalty. With respect to the Spamhaus attack described in Part 1, the CEO of CyberBunker, a Dutch company, was arrested in Spain and was returned to the Netherlands for prosecution. Summary Companies must prepare for the likelihood of losing their public-facing web services and must make plans for how they will continue in operation if these services are taken down. This should be a major topic in their Business Continuity Plans. For instance, in the case of the bank attacks described in Part 1, many banks made plans to significantly increase their call center capabilities to handle customer services should their web sites be taken down by a DDoS attack. DDoS attacks are here to stay. They are motivated by too many factors – retaliation, political statements, aggressive competitors, ransom – and are fairly easy to launch. Botnets can be rented inexpensively. There are even sophisticated tools available on the darknet to launch significant attacks. The defenses against DDoS attacks are at best limited. The ultimate defense is to subscribe to a DDoS mitigation service that can be called upon when needed. Source: http://www.techproessentials.com/ddos-attacks-can-take-down-your-online-services-part-3-defending-against-ddos-attacks/

Read the article:
DDoS Attacks Can Take Down Your Online Services Part 3: Defending Against DDoS Attacks

Monster banking Trojan botnet claims 500,000 victims

This ain’t your father’s ZeuS Security researchers have uncovered the infrastructure behind one of largest and most voracious banking Trojan networks uncovered to date.…

See more here:
Monster banking Trojan botnet claims 500,000 victims

Yahoo! servers! SHELLSHOCKED! by! Bash! bug! bad! boys!

Hash bang wallop Updated   Yahoo ! has confirmed “a handful” of its systems fell to hackers exploiting the Shellshock vulnerability in Bash. The miscreants used the hole to take control of the web servers and build a botnet out of them.…

More:
Yahoo! servers! SHELLSHOCKED! by! Bash! bug! bad! boys!

Hackers using Shellshock to spread Kaiten Mac OS DDoS malware

Hackers are exploiting the Shellshock bug to infect numerous systems, including Apple Mac OS X, with a distributed denial-of-service (DDoS) malware known as Kaiten. Security researchers from Trend Micro reported uncovering the campaign in a blog post, warning that it has the potential to inflict devastating DDoS attacks. “We found that one of the payloads of Bash vulnerabilities, which we detect as TROJ_BASHKAI.SM, downloaded the source code of Kaiten malware, which is used to carry out denial-of-service attacks,” read the post. “Kaiten is old IRC-controlled DDoS malware and, as such, there is a possibility that the attackers employed Shellshock to revive its old activities like DDoS attacks to target organisations.” Discovered earlier in September, Shellshock is a critical vulnerability in the Bash code used by Unix and Unix-like systems. Trend Micro listed the new attack’s ability to infect Mac OS systems as being particularly troubling, highlighting it as evidence that hackers are using Shellshock to expand the victim-base of their campaigns. “Typically, systems infected with Shellshock payloads become a part of their botnet, and therefore can be used to launch DDoS attacks. In addition, the emergence of a downloaded file that targets Mac OS clearly shows that attackers are broadening their target platform,” the security firm said. Trend Micro added that the threat is doubly dangerous as Apple had mistakenly told its users that most should be safe by default. “Users who configured to enable the Advanced Unix Services are still affected by this vulnerability,” read the post. “The Advanced Unix services enables remote access via Secure Shell which offers ease of access to system or network administrators in managing their servers. This service is most likely enabled for machines used as servers such as web servers, which are the common targets Shellshock attacks.” Apple released security patches to plug Shellshock for its OS X Maverick, Lion and Mountain Lion operating systems in September. The Trend Micro researchers added that IT managers should be on guard for the attack as it has advanced detection dodging powers. “When it connects to http://www[dot]computer-services[dot]name/b[dot]c, it downloads the Kaiten source code, which is then compiled using the common gcc compiler. This means that once connected to the URL, it won’t immediately download an executable file,” explained the researchers. “This routine could also be viewed as an evasion technique as some network security systems filter out non-executable files from scanning, due to network performance concerns. Systems configured this way may skip the scanning of the source code because it’s basically a text file.” The Kaiten attack is one of many recently discovered campaigns using Shellshock. Researchers from FireEye caught hackers exploiting the Shellshock Bash vulnerability to infect enterprise Network Attached Storage systems with malware at the end of September. Source: http://www.v3.co.uk/v3-uk/news/2374038/hackers-using-shellshock-to-spread-kaiten-mac-os-ddos-malware

More here:
Hackers using Shellshock to spread Kaiten Mac OS DDoS malware

Apple updates XProtect to kill iWorm botnet threat

Apple has released an update for its XProtect anti-malware system which makes it detect three different version of the iWorm OS backdoor malware discovered last week by AV specialists from Dr. Web. …

Follow this link:
Apple updates XProtect to kill iWorm botnet threat

Apple tries to kill iWorm: Zombie botnet feasting on Mac brains

Updates XProtect Apple has updated its XProtect anti-malware system to squash several variants of the iWorm before the malware causes any further damage.…

View article:
Apple tries to kill iWorm: Zombie botnet feasting on Mac brains

Will we ever can the spam monster?

An unending battle against email-borne nasties and botnets Spam may be the best known security threat in the world. Anyone with email or a Facebook account has experienced it, despite providers’ best efforts to block it from their inboxes.…

Continue Reading:
Will we ever can the spam monster?

Secondhand DDoS: Why hosting providers need to take action

Unfortunately, the sheer size and scale of hosting or datacenter operator network infrastructures and their massive customer base presents an incredibly attractive attack surface due to the multiple entry points and significant aggregate bandwidth that acts as a conduit for a damaging and disruptive DDoS attack. As enterprises increasingly rely on hosted critical infrastructure or services, they are placing themselves at even greater risk from these devastating cyber threats – even as an indirect target. What is secondhand DDoS? The multi-tenant nature of cloud-based data centres and shared, hosted environments can be less than forgiving for unsuspecting tenants. A DDoS attack, volumetric in nature against one tenant, can lead to disastrous repercussions for others; a domino effect of latency issues, service degradation and potentially damaging and long lasting service outages. The excessive amount of malicious traffic bombarding a single tenant during a volumetric DDoS attack can have adverse effects on other tenants as well as the overall data centre or hosting providers operation. In fact, it is becoming more common that attacks on a single tenant or service can completely choke up the shared infrastructure and bandwidth resources, resulting in the entire data centre can be taken offline or severely slowed – AKA, secondhand DDoS. Black-holing or black-hole routing is a common, crude defense against DDoS attacks, which is intended to mitigate secondhand DDoS. With this approach, the cloud or hosting provider blocks all packets destined for a domain by advertising a null route for the IP address (es) under attack. There are a number of problems with utilising this approach for defending against DDoS attacks: Most notably is the situation where multiple tenants share a public IP address range. In this case, all customers associated with the address range under attack will lose all service, regardless of whether they were a specific target of the attack. In effect, the data centre or hosting operator has finished the attacker’s job by completely DoS’ing their own customers. Furthermore, injection of null-routes is a manual process, which requires human analysts, workflow processes and approvals; increasing the time to respond to the attack, leaving all tenants of the shared environment suffering the consequences for extended periods of time, potentially hours. The growing dependence on the Internet makes the impact of successful DDoS attacks-financial and otherwise-increasingly painful for service providers, enterprises, and government agencies. And newer, more powerful DDoS tools promise to unleash even more destructive attacks in the months and years to come. Enterprises which rely on hosted infrastructure or services need to start asking the tough questions of their hosting or datacentre providers, as to how they will be properly protected when a DDoS attack strikes. As we’ve seen on numerous occasions, hosted customers are simply relying on their provider to ‘take care of the attacks’ when they occur, without fully understanding the ramifications of turning a blind eye to this type of malicious behavior. What to do to mitigate an attack and protect the infrastructure Here are three key steps for providers to consider to better protect their own infrastructure, and that of their customers. Eliminate the delays incurred between the time traditional monitoring devices detects a threat, generates an alert and an operator is able to respond; reducing initial attack impact from hours to seconds by deploying appliances that both monitor and mitigate DDoS threats automatically. The mitigation solution should allow for real-time reporting alert and event integration with back-end OSS infrastructure for fast reaction times, and the clear visibility needed to understand the threat condition and proactively improve DDoS defenses. Deploy the DDoS mitigation inline. If you have out-of-band devices in place to scrub traffic, deploy inline threat detection equipment quickly that can inspect, analyse and respond to DDoS threats in real-time. Invest in a DDoS mitigation solution that is architected to never drop good traffic. Providers should avoid the risk of allowing the security equipment to become a bottleneck in delivering hosted services—always allowing legitimate traffic to pass un-interrupted, a do no harm approach to successful DDoS defense. Enterprises rely on their providers to ensure availability and ultimately protection against DDoS attacks cyber threats. With a comprehensive first line of defense against DDoS attacks deployed, date centre and hosting providers are protecting its customers from damaging volumetric threats directed at or originating from or within its networks. Source: http://www.information-age.com/technology/security/123458517/secondhand-ddos-why-hosting-providers-need-take-action

Link:
Secondhand DDoS: Why hosting providers need to take action

MAC BOTNET uses REDDIT comments for directions

17,000 Macs compromised by malicious miscreants A zombie network that feasts on the computer brains of infected Macs has press-ganged 17,000 compromised machines into its ranks, Russian anti-virus firm Dr Web warns.…

Visit site:
MAC BOTNET uses REDDIT comments for directions