Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Operations

7/16/2018
03:00 PM

10 Ways to Protect Protocols That Aren't DNS

Here's how to safeguard three other network foundation protocols so they don't become weapons or critical vulnerabilities.
2 of 11

BGP: Protect the Speaker
BGP is a way for routers to let other routers know where they are and for the routers, as a group, to establish the best way to send packets from one address to another. Part of the process is establishing that a router is still on the Internet: This is done via the speaker, which sends a TCP message on port 179 every 60 seconds to keep the connection to its neighbor alive. If the speaker is taken down, it not only disrupts the router's presence on the Internet, it also opens the door for a substitute, illegitimate router to be inserted in its place.
Obviously, a critical network link that communicates regularly on a known port is vulnerable, so network owners need to take special precautions to protect it. As a first step, the IETF recommends an access control list (ACL) that rejects traffic from any router not explicitly a neighbor.
Next, the network admin should instigate rate limiting on both the control and data planes so that a packet flood can't take the speaker off the network. Rate limiting should be put in place to protect against both attacks and an excessive volume of legitimate traffic that could take the network off the Internet.
(Image: Eaum M VIA SHUTTERSTOCK)

BGP: Protect the Speaker

BGP is a way for routers to let other routers know where they are and for the routers, as a group, to establish the best way to send packets from one address to another. Part of the process is establishing that a router is still on the Internet: This is done via the speaker, which sends a TCP message on port 179 every 60 seconds to keep the connection to its neighbor alive. If the speaker is taken down, it not only disrupts the router's presence on the Internet, it also opens the door for a substitute, illegitimate router to be inserted in its place.

Obviously, a critical network link that communicates regularly on a known port is vulnerable, so network owners need to take special precautions to protect it. As a first step, the IETF recommends an access control list (ACL) that rejects traffic from any router not explicitly a neighbor.

Next, the network admin should instigate rate limiting on both the control and data planes so that a packet flood can't take the speaker off the network. Rate limiting should be put in place to protect against both attacks and an excessive volume of legitimate traffic that could take the network off the Internet.

(Image: Eaum M VIA SHUTTERSTOCK)

2 of 11
Comment  | 
Print  | 
Comments
Newest First  |  Oldest First  |  Threaded View
Jon M. Kelley
100%
0%
Jon M. Kelley,
User Rank: Moderator
7/19/2018 | 12:01:23 PM
Too many tabs, too little info
THis is the first time this year that I've gone through one of DRs multitab "specials".  To be honest this post subject still explains why I skip them:  too many slow loading tabs, with almost no relevant text per tab. Tabs with less than 100 words - get real.  Maybe I'll try again near Christmas.
Firms Improve Threat Detection but Face Increasingly Disruptive Attacks
Robert Lemos, Contributing Writer,  2/20/2020
Ransomware Damage Hit $11.5B in 2019
Dark Reading Staff 2/20/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
6 Emerging Cyber Threats That Enterprises Face in 2020
This Tech Digest gives an in-depth look at six emerging cyber threats that enterprises could face in 2020. Download your copy today!
Flash Poll
How Enterprises Are Developing and Maintaining Secure Applications
How Enterprises Are Developing and Maintaining Secure Applications
The concept of application security is well known, but application security testing and remediation processes remain unbalanced. Most organizations are confident in their approach to AppSec, although others seem to have no approach at all. Read this report to find out more.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-19668
PUBLISHED: 2020-02-27
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2018-17963. Reason: This candidate is a reservation duplicate of CVE-2018-17963. Notes: All CVE users should reference CVE-2018-17963 instead of this candidate. All references and descriptions in this candidate have been removed to preve...
CVE-2019-12882
PUBLISHED: 2020-02-27
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none.
CVE-2017-6363
PUBLISHED: 2020-02-27
** DISPUTED ** In the GD Graphics Library (aka LibGD) through 2.2.5, there is a heap-based buffer over-read in tiffWriter in gd_tiff.c. NOTE: the vendor says "In my opinion this issue should not have a CVE, since the GD and GD2 formats are documented to be 'obsolete, and should only be used for...
CVE-2017-6371
PUBLISHED: 2020-02-27
Synchronet BBS 3.16c for Windows allows remote attackers to cause a denial of service (service crash) via a long string in the HTTP Referer header.
CVE-2017-5861
PUBLISHED: 2020-02-27
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2017-1000020. Reason: This candidate is a reservation duplicate of CVE-2017-1000020. Notes: All CVE users should reference CVE-2017-1000020 instead of this candidate. All references and descriptions in this candidate have been removed to...