Patching a binary file
Generally discussed herein are systems, apparatuses, and methods for patching a binary file using a nested executable. In one or more embodiments, a system can include a memory including a nested binary file stored thereon, the nested binary file including a child executable and a parent executable, the child executable configured as a payload of the parent executable, the parent executable including instructions that, when executed by an intermediate device, cause the intermediate device to identify a value of a variable of the child executable, determine a memory location on the target device corresponding to the variable, write the value of the variable to the child executable, and throw the child executable to the target device after writing the value of the variable to the determined memory location, and communications circuitry configured to provide the nested binary file to the intermediate device.
1. A device comprising: a memory including a nested binary file stored thereon, the nested binary file including a child executable and a parent executable, the child executable configured as a payload of the parent executable, the parent executable including instructions that, when executed by an intermediate device, cause the intermediate device to identify a value of a variable of the child executable, determine a memory location on a target device corresponding to the variable, write the value of the variable to the child executable, and throw the child executable to the target device after writing the value of the variable to the determined memory location, and communications circuitry configured to provide the nested binary file to the intermediate device.
2. The device of claim 1 , wherein the variable is an internet protocol (IP) address of the target device or a port number over which to communicate with the target device.
3. The device of claim 1 , wherein the parent executable includes further instructions that, when executed by the intermediate device, further cause the intermediate device to save a file, install an application, or alter a configuration of the intermediate device so that the intermediate device can execute the child executable.
4. The device of claim 1 , wherein the parent executable includes further instructions that, when executed by the intermediate device, further cause the intermediate device to only throw the child executable to the target device after determining a specified trigger event has occurred.
5. The device of claim 1 , wherein the parent executable includes further instructions that, when executed by the intermediate device, further cause the intermediate device to issue a communication to the device indicating whether the child executable was successfully thrown to the target device.
6. The device of claim 1 , wherein identifying the value of the variable of the child executable includes issuing a communication to the target device to determine a value of the variable.
7. The device of claim 6 , wherein writing the value of the variable to the determined memory location includes issuing an object mapping command to determine the memory location of the value of the variable.
8. A method comprising: generating, by a program builder, a nested binary file including a child executable and a parent executable, the child executable configured as a payload of the parent executable, the parent executable including instructions that, when executed by an intermediate device, cause the intermediate device to identify a value of a variable of the child executable, determine a memory location on the intermediate device corresponding to the variable, write the value of the variable to the child executable, and throw the child executable to a target device after writing the value of the variable to the determined memory location; and providing the nested binary file to the intermediate device.
9. The method of claim 8 , wherein the variable is an internet protocol (IP) address of the target device or a port number over which to communicate with the target device.
10. The method of claim 8 , wherein the parent executable includes further instructions that, when executed by the intermediate device, further cause the intermediate device to save a file, install an application, or alter a configuration of the intermediate device so that the intermediate device can execute the child executable.
11. The method of claim 8 , wherein the parent executable includes further instructions that, when executed by the intermediate device, further cause the intermediate device to only throw the child executable to the target device after determining a specified trigger event has occurred.
12. The method of claim 8 , wherein the parent executable includes further instructions that, when executed by the intermediate device, further cause the intermediate device to issue a communication to the device indicating whether the child executable was successfully thrown to the target device.
13. The device of claim 8 , wherein identifying the value of the variable of the child executable includes issuing a communication to the target device to determine a value of the variable.
14. The device of claim 13 , wherein writing the value of the variable to the determined memory location includes issuing an object mapping command to determine the memory location of the value of the variable.
15. A non-transitory machine-readable medium including instructions that, when executed by a machine, cause the machine to perform operations comprising: generating, by a program builder, a nested binary file including a child executable and a parent executable, the child executable configured as a payload of the parent executable, the parent executable including instructions that, when executed by an intermediate device, cause the intermediate device to identify a value of a variable of the child executable, determine a memory location on the intermediate device corresponding to the variable, write the value of the variable to the child executable, and throw the child executable to a target device after writing the value of the variable to the determined memory location; and providing the nested binary file to the intermediate device.
16. The non-transitory machine-readable medium of claim 15 , wherein the variable is an internet protocol (IP) address of the target device or a port number over which to communicate with the target device.
17. The non-transitory machine-readable medium of claim 15 , wherein the parent executable includes further instructions that, when executed by the intermediate device, further cause the intermediate device to save a file, install an application, or alter a configuration of the intermediate device so that the intermediate device can execute the child executable.
18. The non-transitory machine-readable medium of claim 15 , wherein the parent executable includes further instructions that, when executed by the intermediate device, further cause the intermediate device to only throw the child executable to the target device after determining a specified trigger event has occurred.
19. The non-transitory machine-readable medium of claim 15 , wherein the parent executable includes further instructions that, when executed by the intermediate device, further cause the intermediate device to issue a communication to the device indicating whether the child executable was successfully thrown to the target device.
20. The non-transitory machine-readable medium of claim 15 , wherein identifying the value of the variable of the child executable includes issuing a communication to the target device to determine a value of the variable and wherein writing the value of the variable to the determined memory location includes issuing an object mapping command to determine the memory location of the value of the variable.