S-284: Border Gateway Protocol Vulnerabilities


 
Thread Tools Search this Thread
Special Forums Cybersecurity Security Advisories (RSS) S-284: Border Gateway Protocol Vulnerabilities
# 1  
Old 05-07-2008
S-284: Border Gateway Protocol Vulnerabilities

Boorder Gateway Protocol (BGP) implementations from multiple vendors including Juniper may not properly handle specially crafted BGP UPDATE messages. These vulnerabilities could allow an unauthenticated, remote attacker to cause a denial of service. Disrupting BGP communication could lead to routing instability. The risk is LOW. A remote attacker could cause a denial of servcie by injecting a specially crafted BGP UPDATE message into a legitimate BGP session. An attacker with a configured BGP session could attack targets several BGP hops away, or an attacker could spoof TCP traffic.


More...
Login or Register to Ask a Question

Previous Thread | Next Thread

6 More Discussions You Might Find Interesting

1. UNIX for Beginners Questions & Answers

Inconsistency between RedHat 6.5 global gateway and single gateway leads to loss of default gateway

Dear friends I use RedHat 6.5, which sets the gateway in the configuration file / etc / sysconfig / network as GATEWAY = 192.168.1.26, and the gateway in the configuration file / etc / sysconfig / network-scripts / ifcfg-eth11 as GATEWAY = 192.168.1.256. The two gateways are different.... (6 Replies)
Discussion started by: tanpeng
6 Replies

2. IP Networking

Regarding Protocol certiifcation

Hello Forum Members, I am siva ranganath from Hyderabad-India. I have an work experince of 4.5 years as application developer and support member in open source systems.i am good basic network programing ie applications developing in TCP/IP and i have an experince of 1 year in this N/W... (0 Replies)
Discussion started by: workforsiva
0 Replies

3. Linux

GNUGK-How to setup static gateway to gateway routing

Dear Sir I am a newbie in the world of IP telephony. I have been working with Asterisk PBX (SIP) and Cisco Call Manager (MGCP) but now I am learning on how to work GNUGK for H.323 Gatekeeper. I am having a problem, configuring static call routing on GNUGK in the section ... (0 Replies)
Discussion started by: mfondoum
0 Replies

4. Infrastructure Monitoring

SNMP protocol

dear friends , how can I use the SNMP protocol to monitor the network and send notification alerts to the clients which have windows machines. I found the utility snmp_trapsend at the directory /usr/sbin ,how can I use this command ?? my server is SUN SOLARIS. please help !!!:confused: (1 Reply)
Discussion started by: Ahmed waheed
1 Replies

5. IP Networking

protocol

iam doing a research on WAN so pliz any body can give me or tell me where i would find communication protocol map..thats all 7 layers..OIS MODEL (1 Reply)
Discussion started by: ravineelkumar
1 Replies

6. IP Networking

Protocol Numbers

I'm planning on putting together a chart of basic information (port number, protocol number, transport layer protocol, etc) on different protocols (FTP, ICMP, DNS, IP, etc) I found: http://www.phys-iasi.ro/Library/RFCs/rfc1700.htm and that tells me a little bit of information but I'm looking... (3 Replies)
Discussion started by: thmnetwork
3 Replies
Login or Register to Ask a Question
ECACCESS-ASSOCIATION-DELETE(1p) 			User Contributed Perl Documentation			   ECACCESS-ASSOCIATION-DELETE(1p)

NAME
ecaccess-association-delete - Delete Association SYNOPSIS
ecaccess-association-delete -version|-help|-manual ecaccess-association-delete [-debug] [-gateway name] association-name DESCRIPTION
Allow deleting an ECtrans Association. Once deleted the Association can not be retrieved. The History associated with this Association will also be removed from the ECaccess Gateway Database. ARGUMENTS
association-name The name of the Association to delete. OPTIONS
-gateway name This is the name of the ECaccess Gateway where the Association is installed. It is by default the Gateway you are connected to. In order to get the name of your current Gateway you can use the ecaccess-gateway-name command. When using the commands at ECMWF the default Gateway is always "ecaccess.ecmwf.int". -version Display version number and exits. -help Print a brief help message and exits. -manual Prints the manual page and exits. -debug Display the SOAP messages exchanged. EXAMPLES
ecaccess-association-delete -gateway ecaccess.ecmwf.int test Remove the test Association on the ecaccess.ecmwf.int Gateway. ecaccess-association-delete test2 Remove the test2 Association on the default Gateway. SEE ALSO
ecaccess-association-get, ecaccess-association-list, ecaccess-association-protocol, ecaccess-association-put and ecaccess. perl v5.14.2 2012-04-16 ECACCESS-ASSOCIATION-DELETE(1p)