Chapter3_2 Flashcards

1
Q

We are now in the network layer ( IP, BGP, RIP); WE are looking at the vulnerabilities

A

TRue

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

IP Function

A

IP is used for routing :
 IP host knows location of router (gateway)
 IP gateway must know route to other networks

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Vulnerability in IP

A

No source IP authentication imples it is easy to override using raw sockets
 Libnet: a library for formatting raw packets with arbitrary IP headers

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Attack usng IP

A

: Anyone who owns their machine can send
packets with arbitrary source IP (IP spoofing)
 … response will be sent back to forged source IP

This can lead to anonymous DOS attacks

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What happens in IP fragmentation

A

Routers divide an IP datagram into several smaller fragments based on Maximum Transmission Unit

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Fragment uses same header format as

A

datagram

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Each fragment is routed

A

independently

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

All the IP fragments of a datagram will be

assembled

A

before the datagram is delivered to the

layers above

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Where IP fragments are assembled

A

destination.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Why IP reassembly uses a timer

A

IP reassembly uses a timer. If timer expires and there are still missing fragments, all the fragments will be discarded.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

IP Fragmentation Vulnerabilities

A

 IP of source is not authenticated
 Nothing in the IP header is checked for authenticity
 Only checking done on checksum

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Vulnerability: IP Fragmentation Attack: “Ping of death”

A

someone discovered that many operating systems,
routers, etc. can be crashed/rebooted by sending a single
malformed packet
 It turns out that sending an IP packet larger than
65,535 bytes would crash the system

It allows sending packet bigger than what IP allows, which
blows up most fixed buffer size implementations (buffer
overflow attack)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

“Ping of death” Defense:

A

patch the implementations

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

IP Fragmentation Attacks Denial of Service Attack

A

1st fragment: offset = 0
 2nd fragment: offset = 64800
 Result: The target machine will allocate 64 kilobytes
of memory, which is typically held for 15 to 255
seconds. Windows 2000, XP, and almost all versions
of Unix are vulnerable.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

IP Fragmentation Attacks TearDrop

A
Send a packet with:
 offset = 0
 payload size N
 More Fragments bit on
 Second packet:
 More Fragments bit off
 offset + payload size < N
 i.e., the 2nd fragment fits entirely inside the first one.
 When OS tries to put these two fragments
together, it crashes.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

IP Fragmentation Attacks Overlapping Attacks Against Firewalls

A

If the fragment size is made small enough to force some of a TCP
packet’s TCP header fields into the second fragment, filter rules that
specify patterns for those fields will not match.
 If the filtering implementation does not enforce a minimum fragment size,
a disallowed packet might be passed because it didn’t hit a match in the
filter

17
Q

IP Spoofing Attack

A

Any host can send packets pretending to be from any IP

address

18
Q

Egress (outgoing) Filtering

A

Remove packets that couldn’t be coming from your network;

however it doesn’t benefit you directly, so few people do it.

19
Q

 Ingress (incoming) Filtering:

A

remove packets from

invalid (e.g. local) addresses.

20
Q

IP Spoofing

A
Victim attempts to reply to the spoofed address
through the router
 Since attacker is on
same LAN, he can
see the response
and reply again
 This needs to be
done faster than
the router returning
“ICMP Unreachable
21
Q

ICMP: Internet Control Message Protocol

A

ICMP is a special-purpose protocol:
 Defines error or control messages that can be sent
to/by routers or hosts
• Unreachable host, network, protocol, etc.
• Time-to-live counter expiry

22
Q

ICMP: Vulnerabilities

The Internet Control Message Protocol is a supporting protocol in the Internet protocol suite. It is used to send error messages and operational information

A

 Mapping Network Topology
 Smurf Attack
 Ping of Death
 ICMP Redirect Attack

23
Q

ICMP: Mapping Network Topology

A

 Sending ICMP echo requests to network in order to discover target network.

24
Q

ICMP: Smurf Attack

A

 Ping a broadcast address, with the (spoofed) IP of a
victim as source address
 All hosts on the network respond to the victim
 The victim is overwhelmed

25
Q

ICMP Redirect Attack

A

 Ask a host to send their packet to the target “router”.
 Useful for man-in-the-middle attacks
 Winfreeze attack: essentially causes a susceptible host to attack itself
 ICMP Redirect using Router spoofed IP: YOU are the quickest
link to host Z
 Host changes its routing table for Z to itself
 Host sends packets to itself in an infinite loop

26
Q

e

A

e

27
Q

IP Routing: Vulnerabilities

A

 Common attack: Routing manipulation
 Advertise false routes (can propagate everywhere)
 Causes traffic to go through compromised hosts
 E.g., attacking BGP routing tables: attacker can cause entire
Internet to send traffic for a victim IP to attacker’s address
 Implications:
 Path manipulation
 Denial of service (link cutting attack)
 Connection hijacking
 Defense:
 Authenticate data, but this causes a problem: inefficiency
(complexity, overhead, etc.)

28
Q

Routing Attacks

 Source routing

A

 Source of the packet specifies a particular route: It is an IP
option which allows the originator of a packet to specify what path
that packet will take, and what path return packets sent back to
the originator will take.
• For example, because the automatic route is dead
 Attacker can spoof source IP address and use source routing to
direct response through a compromised host
 Use source routing to access non-routable IP via gateway
 Solution: reject packets with source routing!
• More heavy-duty: allow source route only via trusted gateways
 Routing Information Protocol (RIP)
 Use bogus routing updates to intercept traffic
• RIP implicitly assumes that routers are trusted
 “Black hole” attacks and many others

29
Q

BGP Issues

A
BGP Issues
 BGP convergence problems
 Protocol allows policy flexibility
 Some legal policies prevent convergence
 Even shortest-path policy converges slowly
 Incentive for dishonesty
 ISP pays for some routes, others free
 Security problems
 Potential for disruptive attacks
30
Q

Wormhole Attack on BGP

A

 Multiple colluding malicious BGP routers exchange BGP
update messages over a tunneled connection
 Routers can claim better paths than actually exist

31
Q

BGP Attacks Blackholing:

A

ccurs when a prefix is unreachable from a
large portion of the Internet.
 false route advertisements that aim to attract traffic to a
particular router and then drop it.
 Redirection occurs when traffic owing to a particular
network is forced to take a different path and to
reach an incorrect, potentially also compromised,
destination

32
Q

BGP Attacks Subversion

A

Subversion is a special case of redirection
 Attacker forces the traffic to pass through a certain link with
the objective of eavesdropping or modifying the data.
 Traffic is still forwarded to the correct destination, making
the attack more difficult to detect.

33
Q

Protecting BGP

A

Simple authentication of packet sources and packet integrity is not enough