A Quick and Dirty Guide to BGP attacks

1. A Quick and Dirty Guide to BGP attacks Or “How to 0wn the Backbone in your Spare Time”

2. Outline • How BGP works • What can be attacked? • How is it attacked? • Who might be attacking? • Common approaches to fixing BGP • References

3. How BGP works • An autonomous system (AS) has border routers that “speak” BGP with “BGP peers” at border routers in neighboring AS’s. • AS’s that send traffic directly to each other have a “BGP session” using TCP to communicate information in “BGP updates”

4. How BGP works Creating Global Reachability: • An autonomous system will “originate” whatever network blocks it is currently allowed by ICANN to use. • AS’s can choose to “advertise” reachability to BGP peers for network blocks it knows its neighbors can reach.

5. How BGP works BGP Update Format Withdrawn Routes Path Attributes (Origin, AS-Path, etc) NLRI (prefixes)

6. How BGP works • Receive update message • Apply in-bound filters for peer • Update RIB • Run BGP decision process (if not new best route, exit) • Update FIB • For each peer, apply outbound filters and send new update message.

7. How BGP Works Business Relationships define Export Filters. • “Prov -> Cust” all known best routes • “Cust -> Prov” only originated routes or routes from their customers. • “Peer -> Peer” originated or customer routes (but with no export).

8. How BGP works Providers provide connectivity for their customers. Top-level “tier-1” providers peer with each-other to provide global reachability.

9. What can be attacked? • Availability • Reachability • Degrade link quality • Overwhelm communication capacity • Data Confidentiality • Data Integrity • Authentication (impersonation)

10. How To Attack? (ie: what needs to be secured?) • Peer-Peer Attacks (attack exchange of data between two BGP speakers) • Protocol Content Attacks (falsify or modify use of BGP Update messages) • Traffic Attraction • Traffic Direction • Instability Attacks (attempts to destabilize routing)

11. Peer-Peer Attacks Uses: • Create unavailability by tearing down BGP session and causing path withdrawals. • Inject information into BGP session to perform traffic-attractor or traffic-director attacks. Note: Assumes no possession of a BGP speaking router

12. Peer-Peer Attacks BGP sessions have no required protections. • Attackers my DoS the link bandwidth • TCP injection attacks may insert data into the session, or reset the connection. • Authenticating Peers • Eaves-dropping on session (who cares?) • Attack on CPU resources

13. Peer-Peer Solutions • Integrity: TCP MD5 Option (requires pre-configured secret) • Integrity, Confidentiality, Authentication: IPSec (negotiates shared secret) • CPU protections (drop packets that use CPU time) • TTL Hack (filters non single-hop packets)

14. Protocol Content Attacks What we normally think about when considering BGP attacks These attacks can be the result of malicious behavior or misconfiguration.

15. Traffic Attractor Attacks Uses: • Drop, degrade traffic. • Inspect traffic, communication analysis • Modify Traffic • Impersonation Attacks • Man-in-the-Middle Attacks • Send from un-owned prefix.

16. Traffic Attractor:MOAS – Multiple Origin AS Occurs when multiple AS’s originate (ie: are the first AS to advertise) a particular prefix. Also referred to as a prefix-hijack. • This may be legitimate, e.g., multi-homing with a private ASN. • Roughly speaking, a simple MOAS can trick “half” of the Internet

17. Traffic Attractor:De-aggregation An AS illegitimately originates the “sub-prefix” of another AS’s address space. • More powerful than MOAS, as it does not conflict with a legitimate prefix, but is preferred routing decision. Can trick the entire Internet. • Prefixes larger than 24 bits often filtered by large ISPs.

18. Traffic Attractor:AS-Path Shortening Instead of claiming to originate a prefix, an adversary can keep the correct originator, but shorten the remainder of the path to make it look more attractive. • This attack is more stealthy than simple origination. • Unlikely to occur as misconfig.

19. Traffic Direction Attacks Uses: • Send larger amounts of traffic to a particular AS, potentially overwhelming them. • Force use of alternate paths, which may be more expensive, or vulnerable to snooping, physical attack.

20. Traffic Direction: • False AS-Path Padding (make path look unattractive) • Dropping an announcement • Creating a “fake withdrawal” • Placing another AS’s number in the path, so that it’s loop detection will drop the announcement. Note: These are weakly labeled “attacks”, as they could simply result from legitimate policy decisions.

21. Instability Attacks: Uses: • Cause temporary unavailability for certain regions of the Internet. • Create “cascading failures” across many routing domains. Such attacks often target the limited resources on a router.

22. Instability Attacks How? • Intentional Route-flapping • Route leaks (advertise many /24’s, overwhelm RIB, FIB memory) • BGP connection resets (CPU exhaustion, congestion, etc).

23. Data Plane attacks • Can also compromise availability, confidentiality, integrity and authentication. • Strictly weaker than control plane attacks (local impact) • Not handled by s-BGP, so-BGP. • Very difficult to detect!

24. Who might be attacking? • Network operator has a typo or other misconfiguration. • Malicious party gains control of a BGP speaking router on the black-market • Spammers with shady or clue-less upstream hijack address space • Terrorists pay-off ISP insider or own and operate a portion of the infrastructure

25. Fixing BGP: Origin Authentication Who is allowed to originate a particular prefix? • Needed to detect illegitimate MOAS • Seems to require a complete registry of address space allocations, and an associated PKI (complicated!)

26. Fixing BGP: Path Attestation Roughly attempts to verify that the AS-Path included in an update is a valid AS-level path to the destination. • Different approaches to solving this problem: s-BGP uses signed attestations, so-BGP has a data-base of signed “links” • “Worm-hole” attacks still possible.

27. Fixing BGP: Needs Both! Origin Authentication (OA) AND Path Attestation (PA) are required to provide security benefits. • OA without PA would allow any malicious AS to claim to be directly connected to the originating AS. • PA without OA would allow any AS to originate a prefix, as long as the path to the malicious AS was correct.

28. References • Beware of BGP Attacks (Nordstrom, et. al.) • BGP Security Vulnerabilities Analysis (draft-ietf-idr-bgp-vuln-01.txt, Murphy) • BGP Security Requirements (draft-ietf-rpsec-bgpsecrec-05.txt, Christian) • A Survey of BGP Security (Butler, et. al.)