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
Threaded  |  Newest First  |  Oldest First
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.
How Attackers Could Use Azure Apps to Sneak into Microsoft 365
Kelly Sheridan, Staff Editor, Dark Reading,  3/24/2020
Malicious USB Drive Hides Behind Gift Card Lure
Dark Reading Staff 3/27/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
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
State of Cybersecurity Incident Response
State of Cybersecurity Incident Response
Data breaches and regulations have forced organizations to pay closer attention to the security incident response function. However, security leaders may be overestimating their ability to detect and respond to security incidents. 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-2020-10940
PUBLISHED: 2020-03-27
Local Privilege Escalation can occur in PHOENIX CONTACT PORTICO SERVER through 3.0.7 when installed to run as a service.
CVE-2020-10939
PUBLISHED: 2020-03-27
Insecure, default path permissions in PHOENIX CONTACT PC WORX SRT through 1.14 allow for local privilege escalation.
CVE-2020-6095
PUBLISHED: 2020-03-27
An exploitable denial of service vulnerability exists in the GstRTSPAuth functionality of GStreamer/gst-rtsp-server 1.14.5. A specially crafted RTSP setup request can cause a null pointer deference resulting in denial-of-service. An attacker can send a malicious packet to trigger this vulnerability.
CVE-2020-10817
PUBLISHED: 2020-03-27
The custom-searchable-data-entry-system (aka Custom Searchable Data Entry System) plugin through 1.7.1 for WordPress allows SQL Injection. NOTE: this product is discontinued.
CVE-2020-10952
PUBLISHED: 2020-03-27
GitLab EE/CE 8.11 through 12.9.1 allows blocked users to pull/push docker images.