|
6 | 6 | <p>
|
7 | 7 | Downloading executeables or other sensitive files over an unencrypted connection
|
8 | 8 | can leave a server open to man-in-the-middle attacks (MITM).
|
9 |
| - Such a man-in-the-middle attack can allow an attacker to insert arbitary content |
10 |
| - into the downloaded file, and in the worst case allow the attacker to execute |
11 |
| - arbitary code on the vulnerable system. |
| 9 | + Such an attack can allow an attacker to insert arbitrary content |
| 10 | + into the downloaded file, and in the worst case, allow the attacker to execute |
| 11 | + arbitrary code on the vulnerable system. |
12 | 12 | </p>
|
13 | 13 | </overview>
|
14 | 14 | <recommendation>
|
15 | 15 | <p>
|
16 |
| - Use an transfer protocol that includes encryption when downloading executeables or other sensitive files. |
| 16 | + Use a secure transfer protocol when downloading executables or other sensitive files. |
17 | 17 | </p>
|
18 | 18 | </recommendation>
|
19 | 19 | <example>
|
20 | 20 | <p>
|
21 |
| - In this example a server downloads a shell script from a remote URL using the <code>node-fetch</code> |
| 21 | + In this example, a server downloads a shell script from a remote URL using the <code>node-fetch</code> |
22 | 22 | library, and then executes this shell script.
|
23 | 23 | </p>
|
24 | 24 | <sample src="examples/insecure-download.js" />
|
25 | 25 | <p>
|
26 | 26 | The HTTP protocol is vulnerable to MITM, and thus an attacker could potentially replace the downloaded
|
27 |
| - shell script with arbitary code, which allows the attacker complete control over the attacked system. |
| 27 | + shell script with arbitrary code, which gives the attacker complete control over the system. |
28 | 28 | </p>
|
29 | 29 | <p>
|
30 |
| - The issue has been fixed in the below example by replacing the HTTP protocol with the HTTPS protocol. |
| 30 | + The issue has been fixed in the example below by replacing the HTTP protocol with the HTTPS protocol. |
31 | 31 | </p>
|
32 | 32 | <sample src="examples/insecure-download.js" />
|
33 | 33 | </example>
|
|
0 commit comments