English (United Kingdom)

https://curated-unify.zendy.io/wp-json/zendy-region/v1/featured_content/oa?rat=en

https://curated-unify.zendy.io/wp-json/zendy-region/v1/highlighted_journal/

Global: Zendy Plus annual

Presents the access of premium content as premium feature

Premium Content

Presents the keyphrase highlighting as premium feature

Keyphrase Highlighting

Presents the summarisation as premium feature

Summarisation

Insights

Presents the pdf analysis as premium feature

PDF Analysis

Presents the zaia usage as premium feature

ZAIA

Global: Zendy Plus monthly

Global: Zendy Tools annual

Global: Zendy Tools monthly

Global: Zendy Free Plan

Vetting security impacts introduced by third-party libraries in iOS appsrequires a reliable library detection technique. Especially when a newvulnerability (or a privacy-invasive behavior) was discovered in a third-partylibrary, there is a practical need to precisely identify the existence oflibraries and their versions for iOS apps. However, few studies have beenproposed to tackle this problem, and they all suffer from the code duplicationproblem in different libraries. In this paper, we focus on third-party librarydetection in iOS apps. Given an app, we aim to identify the integratedlibraries and pinpoint their versions (or the version range).To this end, wefirst conduct an in-depth study on iOS third-party libraries to demystify thecode duplication challenge. By doing so, we have two key observations: 1) eventhough two libraries can share classes, the shared classes cannot be integratedinto an app simultaneously without causing a class name conflict; and 2) codeduplication between multiple versions of two libraries can vary. Based on thesefindings, we propose a novel profile-based similarity comparison approach toperform the detection. Specifically, we build a library database consists oforiginal library binaries with distinct versions. After extracting profiles foreach library version and the target app, we conduct a similarity comparison tofind the best matches. We implemented this approach in iLibScope. We built abenchmark consists of 5,807 apps with 10,495 library integrations and appliedour tool to it. Our evaluation shows that iLibScope achieves a recall exceeds99% and a precision exceeds 97% for library detection. We also appliediLibScope to detect the presence of well-known vulnerable third-party librariesin real-world iOS mobile apps to show the promising usage of our tool. Itsuccessfully identified 405 vulnerable library usage from 4,249 apps.

iLibScope: Reliable Third-Party Library Detection for iOS Mobile Apps