ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

Protecting Against Common Firewall Attacks

Updated on November 11, 2015

According to McClure, Scambray, and Kurtz (2005), firewall discovery comprises a routine of port scanning and banner grabbing to determine the specific type of firewall and the possible vulnerabilities. Two types of firewall attacks may be launched by the hacker. The first type includes attacks against the firewall itself for the purpose of taking control of the firewall’s functionality or launching a Denial of Service (DOS) attack. The second type of firewall attack includes attacks on the inside or Local Area Network (LAN) side of the firewall.

Attacks against firewalls aimed toward the inside or LAN side of firewalls attempt to circumvent the firewall’s rules or policy to gain access to the protected devices. One useful discovery tool that hackers use to find those inside targets is firewalking.

Firewalking is a technique that uses traceroute-like tools to probe firewalls and screening routers for ports, services, and protocols that are used by the target network. Firewalking can also be used to map hosts behind the firewalls and packet filtering devices” (Peake, 2003, p. 12).

Firewalking methods are not aimed at the target hosts themselves but rather at the firewall that protects them. The method is based on the Time to Live (TTL) property of TCP/IP packets directed at the virtual host located one hop beyond the firewall. The theory states, according to Goldsmith and Schiffman (1998), that a firewall will drop packet directed at a port that the firewall blocks but forward those packets directed toward open ports. The firewalk tool can then assume that all responses forwarded back from the firewall that contain the ICMP message TTL expired are responses to probe packets directed at open ports on the firewall. The hacker can then craft more specific port scans directed at the network using those open ports.

The best way to defend against firewalking a stated by McClure et al. (2005), is block TTL expired messages from passing from the inside interface of the firewall to the outside interface. This act may have detrimental consequences, however, because legitimate traffic will be blocked. A better method nay be to null route packets that arrive on the outside interface with a TTL less than or equal to 1 but I do not know if today’s firewalls permit such granular testing of packets.

What do you think?

Your comments are always welcome.

References

Goldsmith, D., Schiffman, M. (1998). Firewalking: A traceroute-like analysis of IP packet responses to determine gateway accesscontrol lists.

McClure, S., Scambray, J., and Kurtz, G. (2005). Chapter 9: Firewalls. HackingExposed Network Security Secrets & Solutions (5th Ed.). Emeryville, CA: Mcgraw-Hill / Osborne.

Peake, C. (2003). Red teaming: The art of ethical hacking. GIAC Security Essentials

Certification (GSEC) SANS Practical assignment Version 1.4b – Option 1. Retrieved May 7, 2008 from https://www2.sans.org/reading_room/whitepapers/auditing/1272.php.

Comments

    0 of 8192 characters used
    Post Comment

    No comments yet.

    working

    This website uses cookies

    As a user in the EEA, your approval is needed on a few things. To provide a better website experience, hubpages.com uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

    For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at: https://hubpages.com/privacy-policy#gdpr

    Show Details
    Necessary
    HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
    LoginThis is necessary to sign in to the HubPages Service.
    Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
    AkismetThis is used to detect comment spam. (Privacy Policy)
    HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
    HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
    Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
    CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
    Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the googleapis.com or gstatic.com domains, for performance and efficiency reasons. (Privacy Policy)
    Features
    Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
    Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
    Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
    Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
    Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
    VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
    PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
    Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
    MavenThis supports the Maven widget and search functionality. (Privacy Policy)
    Marketing
    Google AdSenseThis is an ad network. (Privacy Policy)
    Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
    Index ExchangeThis is an ad network. (Privacy Policy)
    SovrnThis is an ad network. (Privacy Policy)
    Facebook AdsThis is an ad network. (Privacy Policy)
    Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
    AppNexusThis is an ad network. (Privacy Policy)
    OpenxThis is an ad network. (Privacy Policy)
    Rubicon ProjectThis is an ad network. (Privacy Policy)
    TripleLiftThis is an ad network. (Privacy Policy)
    Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
    Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
    Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
    Statistics
    Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
    ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
    Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)