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

Android apps include third-party native libraries to increase performance andto reuse functionality. Native code is directly executed from apps through theJava Native Interface or the Android Native Development Kit. Android developersadd precompiled native libraries to their projects, enabling their use.Unfortunately, developers often struggle or simply neglect to update theselibraries in a timely manner. This results in the continuous use of outdatednative libraries with unpatched security vulnerabilities years after patchesbecame available.  To further understand such phenomena, we study the security updates in nativelibraries in the most popular 200 free apps on Google Play from Sept. 2013 toMay 2020. A core difficulty we face in this study is the identification oflibraries and their versions. Developers often rename or modify libraries,making their identification challenging. We create an approach called LibRARIAN(LibRAry veRsion IdentificAtioN) that accurately identifies native librariesand their versions as found in Android apps based on our novel similaritymetric bin2sim. LibRARIAN leverages different features extracted from librariesbased on their metadata and identifying strings in read-only sections.  We discovered 53/200 popular apps (26.5%) with vulnerable versions with knownCVEs between Sept. 2013 and May 2020, with 14 of those apps remainingvulnerable. We find that app developers took, on average, 528.71 days to applysecurity patches, while library developers release a security patch after 54.59days - a 10 times slower rate of update.

Too Quiet in the Library: An Empirical Study of Security Updates in Android Apps' Native Code