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

As an alternative to Java, Kotlin has gained rapid popularity since itsintroduction and has become the default choice for developing Android apps.However, due to its interoperability with Java, Kotlin programs may containalmost the same security vulnerabilities as their Java counterparts. Hence, wequestion: to what extent can one use an existing Java static taint analysis onKotlin code? In this paper, we investigate the challenges in implementing ataint analysis for Kotlin compared to Java. To answer this question, weperformed an exploratory study where each Kotlin construct was examined andcompared to its Java equivalent. We identified 18 engineering challenges thatstatic-analysis writers need to handle differently due to Kotlin's uniqueconstructs or the differences in the generated bytecode between the Kotlin andJava compilers. For eight of them, we provide a conceptual solution, while sixof those we implemented as part of SecuCheck-Kotlin, an extension to theexisting Java taint analysis SecuCheck.

To what extent can we analyze Kotlin programs using existing Java taint analysis tools? (Extended Version)