Detection of malicious invocation of application program interface calls
View Patent ↗Particular embodiments described herein provide for an electronic device that includes a binder kernel driver. The binder kernel driver can be configured to receive an application program interface (API) call, extract metadata from the API call, determine that the API call should be hooked based on the extracted metadata, and hook the API call.
1. At least one non-transitory computer-readable medium comprising one or more instructions that when executed by at least one processor, cause the processor to:
receive, by a kernel driver executed by the at least one processor, an application program interface (API) call, wherein the kernel driver is included within a kernel space;
extract, with the kernel driver, metadata from the API call;
determine, with the kernel driver, that the API call should be hooked based on the extracted metadata;
hook, with the kernel driver, the API call;
communicate the API call and the extracted metadata to a security module, wherein the security module determines if the API call should be allowed or denied; and
allow the API call if a response from the security module is not received after a predetermined amount of time has passed from when the API call and the extracted metadata was communicated to the security module.
2. The at least one nom-transitory computer-readable medium of claim 1 , wherein the kernel driver is a binder kernel driver.
3. The at least one non-transitory computer-readable medium of claim 2 , wherein an interceptor in the kernel driver intercepts the API call.
4. The at least one non-transitory computer-readable medium of claim 2 , wherein a policy manager inside the kernel driver determines that the API call should be hooked based on the extracted metadata.
5. The at least one non-transitory computer-readable medium of claim 2 , wherein the extracted metadata is compared to a security policy to determine that the API call should be hooked.
6. The at least one nom-transitory computer-readable medium of claim 5 , wherein the security policy is located in the kernel driver.
7. An apparatus comprising:
a hardware processor configured to execute a kernel driver, wherein the kernel driver is configured to:
receive an application program interface (API) call, wherein the kernel driver is included within a kernel space;
extract metadata from the API call;
determine that the API call should be hooked based on the extracted metadata;
hook the API call;
communicate the API call and the extracted metadata to a security module, wherein the security module determines if the API call should be allowed or denied; and
allow the API call if a response from the security module is not received after a predetermined amount of time has passed from when the API call and the extracted metadata was communicated to the security module.
8. The apparatus of claim 7 , wherein the kernel driver is a binder kernel driver.
9. The apparatus of claim 8 , wherein an interceptor in the kernel driver intercepts the API call.
10. The apparatus of claim 8 , wherein a policy manager inside the kernel driver determines that the API call should be hooked based on the extracted metadata.
11. The apparatus of claim 8 , wherein the extracted metadata is compared to a security policy to determine that the API call should be hooked.
12. The apparatus of claim 11 , wherein the security policy is located in the kernel driver.
13. A method comprising:
receiving an application program interface (API) call at a kernel driver, wherein the kernel driver is included within a kernel space;
extracting metadata from the API call with the kernel driver;
determining, with the kernel driver, that the API call should be hooked based on the extracted metadata;
hooking, with the kernel driver, the API call;
communicate the API call and the extracted metadata to a security module, wherein the security module determines if the API call should be allowed or denied; and
allow the API call if a response from the security module is not received after a predetermined amount of time has passed from when the API call and the extracted metadata was communicated to the security module.
14. The method of claim 13 , wherein the kernel driver is a binder kernel driver.
15. The method of claim 14 , wherein an interceptor in the kernel driver intercepts the API call.
16. The method of claim 14 , wherein a policy manager inside the kernel driver determines that the API call should be hooked based on the extracted metadata.
17. The method of claim 14 , wherein the extracted metadata is compared to a security policy in the kernel driver to determine that the API call should be hooked.
18. A system for detecting and mitigating malicious invocation of sensitive code, the system comprising:
a hardware processor configured to execute a binder kernel driver, wherein the binder kernel driver is configured to:
receive an application program interface (API) call, wherein the binder kernel driver is included within a kernel space;
extract metadata from the API call;
determine that the API call should be hooked based on the extracted metadata;
hook the API call;
communicate the API call and the extracted metadata to a security module, wherein the security module determines if the API call should be allowed or denied; and
allow the API call if a response from the security module is not received after a predetermined amount of time has passed from when the API call and the extracted metadata was communicated to the security module.
19. The system of claim 18 , wherein a policy manager inside the binder kernel driver compares the extracted metadata to a security policy in the binder kernel driver and determines that the API call should be hooked based on the extracted metadata.