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.
DevSecOps: The Answer to the Cloud Security Skills Gap
Lamont Orange, Chief Information Security Officer at Netskope,  11/15/2019
Attackers' Costs Increasing as Businesses Focus on Security
Robert Lemos, Contributing Writer,  11/15/2019
Human Nature vs. AI: A False Dichotomy?
John McClurg, Sr. VP & CISO, BlackBerry,  11/18/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: -when I told you that our cyber-defense was from another age
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2011-3350
PUBLISHED: 2019-11-19
masqmail 0.2.21 through 0.2.30 improperly calls seteuid() in src/log.c and src/masqmail.c that results in improper privilege dropping.
CVE-2011-3352
PUBLISHED: 2019-11-19
Zikula 1.3.0 build #3168 and probably prior has XSS flaw due to improper sanitization of the 'themename' parameter by setting default, modifying and deleting themes. A remote attacker with Zikula administrator privilege could use this flaw to execute arbitrary HTML or web script code in the context ...
CVE-2011-3349
PUBLISHED: 2019-11-19
lightdm before 0.9.6 writes in .dmrc and Xauthority files using root permissions while the files are in user controlled folders. A local user can overwrite root-owned files via a symlink, which can allow possible privilege escalation.
CVE-2019-10080
PUBLISHED: 2019-11-19
The XMLFileLookupService in NiFi versions 1.3.0 to 1.9.2 allowed trusted users to inadvertently configure a potentially malicious XML file. The XML file has the ability to make external calls to services (via XXE) and reveal information such as the versions of Java, Jersey, and Apache that the NiFI ...
CVE-2019-10083
PUBLISHED: 2019-11-19
When updating a Process Group via the API in NiFi versions 1.3.0 to 1.9.2, the response to the request includes all of its contents (at the top most level, not recursively). The response included details about processors and controller services which the user may not have had read access to.