@@ -7,7 +7,7 @@ platform that contains modules to back up, restore, archive, replicate, and sear
7
7
8
8
According to public documentation, the data is protected by installing agent software on the
9
9
physical or virtual hosts, which use the OS or application native APIs to protect data in a
10
- consistent state. Production data is processed by the agent on client computers and backuped
10
+ consistent state. Production data is processed by the agent on client computers and backed
11
11
up through a data manager (the MediaAgent) to disk, tape, or cloud storage. All data
12
12
management activity in the environment is tracked by a centralized server (called CommServe),
13
13
and can be managed by administrators through a central user interface. End users can access
@@ -72,7 +72,7 @@ BOOL WINAPI CreateProcess(
72
72
```
73
73
74
74
Since ``` CreateProcess() ``` is meant to replace ``` WinExec() ``` according to Microsoft, we can create a
75
- break point there fist in our debugger (WinDBG), and we hit it:
75
+ breakpoint there first in our debugger (WinDBG), and we hit it:
76
76
77
77
```
78
78
0:044> g
@@ -153,7 +153,7 @@ If we take a closer look at the ```execCmd``` function, we can tell the purpose
153
153
.text:000000018015A0D2 jz loc_18015A220
154
154
```
155
155
156
- However, if you don't call one of these processes, the ``` exeCmd ``` will assume you want to run your
156
+ However, if you don't call one of these processes, the ``` execCmd ``` will assume you want to run your
157
157
custom process, and pass it to ``` CreateProcess ``` anyway:
158
158
159
159
```
@@ -190,8 +190,8 @@ custom process, and pass it to ```CreateProcess``` anyway:
190
190
```
191
191
192
192
It is unclear whether allowing an arbitrary custom process is intentional or not, it is unsafe
193
- anyway considering the cvd process binds to 0.0.0.0, so anybody can access to it under the context
194
- of SYSTEM.
193
+ anyway considering the cvd process binds to 0.0.0.0, so anybody can gain access to it under the
194
+ context of SYSTEM.
195
195
196
196
## Using the Metasploit Module
197
197
0 commit comments