Securing third-party code and components
As with all software, mobile applications heavily use third-party libraries and wrappers to perform a function such as making HTTP requests or encrypting objects. These libraries can also introduce weaknesses into an application and expose confidential information or affect the integrity of the application itself. With this in mind, third-party code should be reviewed for vulnerabilities, updated, and tested where applicable. This is especially true for hybrid applications that depend on third-party hybrid frameworks and libraries to send, receive, and save data. This recipe will discuss methods to ensure third-party code does not introduce vulnerabilities into IoT applications.
How to do it...
In Chapter 8,Firmware Security Best Practices, methods to scan JavaScript libraries with NSP as well as Retire.js were discussed, these can still be applied to mobile applications. To ensure third-party code does not introduce security holes into mobile applications...