HP 635n Practical IPsec Deployment for Printing and Imaging Devices - Page 22

Too Easy: MITM Data Injection

Page 22 highlights

Device-1 Cache B:2 IP Address: A Ethernet Address: 1 Device-2 Cache A:1 IP Address: B Ethernet Address: 2 NEW MAC ADDRESS!!! IP B has Ethernet Address 3 Device-3 Pretends to be Device-1 announcing a new Ethernet Address to Device-2 Also pretends to be Device-2 announcing a new MAC address to Device-1 NEW MAC ADDRESS!!! IP A has Ethernet Address 3 IP Address: C Ethernet Address: 3 Device-1 Cache B:3 IP Address: A Ethernet Address: 1 Device-2 Cache A:3 IP Address: B Ethernet Address: 2 Device-3 IP Address: C Ethernet Address: 3 Device-1 Cache B:3 IP Address: A Ethernet Address: 1 Device-2 Cache A:3 IP Address: B Ethernet Address: 2 Device-3 Copies all information before forwarding the packet on. IP Address: C Ethernet Address: 3 Figure 20 - MITM In Figure 20 we can see how Device-3 modifies the cache by pretending to be both Device-1 and Device-2. Once the cache has been modified, Device-1 sends packets to Device-3's Ethernet Address when the destination IP address is actually for Device-2. Device-2 sends packets to Device-3's Ethernet address when the destination IP address is actually for Device-1. It should be clear that our attacker Jane's laptop is Device-3. When it receives a packet to or from the MFP, it can capture the data and then send the packet back on its proper way. Ettercap has facilities to automate this process making it extremely easy to do. Once done, Wireshark can be used to capture the information. Too Easy: MITM Data Injection As if what we discussed so far isn't enough, there is yet another attack Jane can use to capture data leveraging off of our previous MITM attack. Once Jane is in possession of a packet, let's say a packet from the MFP containing the destination email addresses that the secret document is going to be delivered to, Jane simply adds her email address to the existing email addresses in the protocol 22

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193

22
Device-1
Cache
B:2
IP Address: A
Ethernet Address: 1
Device-2
Cache
A:1
IP Address: B
Device-3
Pretends to be Device-1
announcing a new Ethernet
Address to Device-2
Also pretends to be Device-2
announcing a new MAC address
to Device-1
Ethernet Address: 2
NEW MAC ADDRESS!!!
IP A has Ethernet Address 3
NEW MAC ADDRESS!!!
IP B has Ethernet Address 3
Device-1
Cache
B:3
IP Address: A
Ethernet Address: 1
Device-2
Cache
A:3
IP Address: B
Device-3
Ethernet Address: 2
IP Address: C
Ethernet Address: 3
IP Address: C
Ethernet Address: 3
Device-1
Cache
B:3
IP Address: A
Ethernet Address: 1
Device-2
Cache
A:3
IP Address: B
Device-3
Copies all information before
forwarding the packet on.
Ethernet Address: 2
IP Address: C
Ethernet Address: 3
Figure 20 - MITM
In Figure 20 we can see how Device-3 modifies the cache by pretending to be both Device-1 and
Device-2.
Once the cache has been modified, Device-1 sends packets to Device-3’s Ethernet Address
when the destination IP address is actually for Device-2.
Device-2 sends packets to Device-3’s
Ethernet address when the destination IP address is actually for Device-1.
It should be clear that our attacker Jane’s laptop is Device-3.
When it receives a packet to or from the
MFP, it can capture the data and then send the packet back on its proper way.
Ettercap has facilities
to automate this process making it extremely easy to do.
Once done, Wireshark can be used to
capture the information.
Too Easy: MITM Data Injection
As if what we discussed so far isn’t enough, there is yet another attack Jane can use to capture data
leveraging off of our previous MITM attack.
Once Jane is in possession of a packet, let’s say a
packet from the MFP containing the destination email addresses that the secret document is going to
be delivered to, Jane simply adds
her email address to the existing email addresses in the protocol