Static Analysis of Context Leaks in Android Applications
•
0 likes•198 views
The document discusses static analysis of context memory leaks in Android applications. It outlines how the Android lifecycle works and how objects like activities have a lifecycle controlled by Android. Context memory leaks can occur through static fields, threads, and managers that hold context references. The analysis detects these leaks by simulating the lifecycle, building a control flow graph, and using abstract interpretation. It identifies fields that point to contexts or context containers and uses backward analysis to determine if the field will leak based on what initialized it. The approach was evaluated on 8 open source apps and compared to the Lint analyzer.
Report
Share
Report
Share
Recommended
Angular testing
Angular Unit Testing, Mid Way Testing and E2E Testing workshop by Mathieu Chauvinc, CTO of Red Ape Solutions Malaysia
Javascript unit tests with angular 1.x
This document discusses using Jasmine for unit testing JavaScript and Angular 1.x applications. It covers setting up a test framework with Jasmine and Karma, writing testable code, and testing Angular services, controllers, directives, and common patterns. Real-world examples are provided for testing Angular services using spies and dependency injection. The document emphasizes writing tests with a Given-When-Then structure, using matchers like toBe() and toEqual(), and spies for method stubs. Links are included for code samples, exercises, and the author's blog for further information on testing Angular applications with Jasmine.
Introduction to Object Oriented Javascript
This document provides an introduction to object oriented JavaScript. It covers functions, objects, prototypes, inheritance, callbacks, closures, asynchronous programming and some exercises. Functions are first class citizens that can be treated like variables. Objects can be created using constructors, literals or built-in methods. Prototypes allow objects to inherit properties from other objects in a prototypical inheritance chain. Callbacks and closures help deal with JavaScript's asynchronous nature. Asynchronous flow control with promises avoids "callback hell". Examples are provided for key concepts.
Spring AOP Introduction
The document provides an introduction and overview of Spring AOP (Aspect Oriented Programming). It discusses key AOP concepts like aspects, join points, pointcuts, and advices. It provides examples of adding aspects in Spring using XML and annotations. It also covers best practices like keeping pointcuts linear and targeting specific cross-cutting concerns with individual aspects. Potential weaknesses discussed include excessive AOP use complicating code and performance overhead from proxying.
Memory Leaks in Android Applications
This presentation aims to demonstrate the importance of certain practices in Android Application Development to avoid annoying memory leaks which lead to fatal crash .
Xamarin.android memory management gotchas
Xamarin.Android applications can leak memory when framework objects like Activities are not properly cleaned up. StrictMode and the Android Debug Bridge (ADB) are useful tools for detecting memory leaks caused by lingering Activity references. Demonstrations showed an obvious leak from a static Activity reference and a less obvious leak from an anonymous delegate closure. Proper cleanup involves disposing of framework peers when no longer needed to allow garbage collection.
A healthy diet for your Java application Devoxx France.pdf
Have you ever faced OutOfMemoryError? Was it in your CI or during the local run? Maybe you faced it as a user while playing your favorite video game or using online banking to pay your bills.
That’s annoying, isn’t it? Every time we give the application more and more memory, it seems never enough…
In Sonar we know how important it is to use memory efficiently. As our tools are often a part of your ci jobs, we care how much you spend on the infrastructure and try to minimize the cost.
So in this session, I will try to share some tips for investigating, fixing, and preventing potential memory leaks and reducing the memory footprint. In simple words, I will show how you can help your applications eat memory « healthier ».
LeakPair: Proactive Repairing of Leaks in Single Page Web Applications
Modern web applications often resort to application development frameworks such as React, Vue.js, and Angular. While the frameworks facilitate the development of web applications with several useful components, they are inevitably vulnerable to unmanaged memory consumption since the frameworks often produce Single Page Applications (SPAs). Web applications can be alive for hours and days with behavior loops, in such cases, even a single memory leak in a SPA app can cause performance degradation on the client side. However, recent debugging techniques for web applications still focus on memory leak detection, which requires manual tasks and produces imprecise results.
We propose LeakPair, a technique to repair memory leaks in single page applications. Given the insight that memory leaks are mostly non-functional bugs and fixing them might not change the behavior of an application, the technique is designed to proactively generate patches to fix memory leaks, without leak detection, which is often heavy and tedious. To generate effective patches, LeakPair follows the idea of pattern-based program repair since the automated repair strategy shows successful results in many recent studies. We evaluate the technique on more than 20 open-source projects without using explicit leak detection. The patches generated by our technique are also submitted to the projects as pull requests. The results show that LeakPair can generate effective patches to reduce memory consumption that are acceptable to developers. In addition, we execute the test suites given by the projects after applying the patches, and it turns out that the patches do not cause any functionality breakage; this might imply that LeakPair can generate non-intrusive patches for memory leaks.
Recommended
Angular testing
Angular Unit Testing, Mid Way Testing and E2E Testing workshop by Mathieu Chauvinc, CTO of Red Ape Solutions Malaysia
Javascript unit tests with angular 1.x
This document discusses using Jasmine for unit testing JavaScript and Angular 1.x applications. It covers setting up a test framework with Jasmine and Karma, writing testable code, and testing Angular services, controllers, directives, and common patterns. Real-world examples are provided for testing Angular services using spies and dependency injection. The document emphasizes writing tests with a Given-When-Then structure, using matchers like toBe() and toEqual(), and spies for method stubs. Links are included for code samples, exercises, and the author's blog for further information on testing Angular applications with Jasmine.
Introduction to Object Oriented Javascript
This document provides an introduction to object oriented JavaScript. It covers functions, objects, prototypes, inheritance, callbacks, closures, asynchronous programming and some exercises. Functions are first class citizens that can be treated like variables. Objects can be created using constructors, literals or built-in methods. Prototypes allow objects to inherit properties from other objects in a prototypical inheritance chain. Callbacks and closures help deal with JavaScript's asynchronous nature. Asynchronous flow control with promises avoids "callback hell". Examples are provided for key concepts.
Spring AOP Introduction
The document provides an introduction and overview of Spring AOP (Aspect Oriented Programming). It discusses key AOP concepts like aspects, join points, pointcuts, and advices. It provides examples of adding aspects in Spring using XML and annotations. It also covers best practices like keeping pointcuts linear and targeting specific cross-cutting concerns with individual aspects. Potential weaknesses discussed include excessive AOP use complicating code and performance overhead from proxying.
Memory Leaks in Android Applications
This presentation aims to demonstrate the importance of certain practices in Android Application Development to avoid annoying memory leaks which lead to fatal crash .
Xamarin.android memory management gotchas
Xamarin.Android applications can leak memory when framework objects like Activities are not properly cleaned up. StrictMode and the Android Debug Bridge (ADB) are useful tools for detecting memory leaks caused by lingering Activity references. Demonstrations showed an obvious leak from a static Activity reference and a less obvious leak from an anonymous delegate closure. Proper cleanup involves disposing of framework peers when no longer needed to allow garbage collection.
A healthy diet for your Java application Devoxx France.pdf
Have you ever faced OutOfMemoryError? Was it in your CI or during the local run? Maybe you faced it as a user while playing your favorite video game or using online banking to pay your bills.
That’s annoying, isn’t it? Every time we give the application more and more memory, it seems never enough…
In Sonar we know how important it is to use memory efficiently. As our tools are often a part of your ci jobs, we care how much you spend on the infrastructure and try to minimize the cost.
So in this session, I will try to share some tips for investigating, fixing, and preventing potential memory leaks and reducing the memory footprint. In simple words, I will show how you can help your applications eat memory « healthier ».
LeakPair: Proactive Repairing of Leaks in Single Page Web Applications
Modern web applications often resort to application development frameworks such as React, Vue.js, and Angular. While the frameworks facilitate the development of web applications with several useful components, they are inevitably vulnerable to unmanaged memory consumption since the frameworks often produce Single Page Applications (SPAs). Web applications can be alive for hours and days with behavior loops, in such cases, even a single memory leak in a SPA app can cause performance degradation on the client side. However, recent debugging techniques for web applications still focus on memory leak detection, which requires manual tasks and produces imprecise results.
We propose LeakPair, a technique to repair memory leaks in single page applications. Given the insight that memory leaks are mostly non-functional bugs and fixing them might not change the behavior of an application, the technique is designed to proactively generate patches to fix memory leaks, without leak detection, which is often heavy and tedious. To generate effective patches, LeakPair follows the idea of pattern-based program repair since the automated repair strategy shows successful results in many recent studies. We evaluate the technique on more than 20 open-source projects without using explicit leak detection. The patches generated by our technique are also submitted to the projects as pull requests. The results show that LeakPair can generate effective patches to reduce memory consumption that are acceptable to developers. In addition, we execute the test suites given by the projects after applying the patches, and it turns out that the patches do not cause any functionality breakage; this might imply that LeakPair can generate non-intrusive patches for memory leaks.
Exploring Kotlin language basics for Android App development
Kotlin is a new programming language that targets JVM, Android and JavaScript. It is 100% interoperable with Java and avoids NullPointerExceptions. Some key features include lambda expressions, immutable val properties, smart casting, and named arguments. Kotlin code can use existing Java frameworks and libraries. Data classes, sealed classes, and when expressions make the code cleaner. Best practices include using apply() for object initialization and named arguments instead of method chaining.
Advanced android app development
Indonesian Android Kejar (IAK) Discussion group
Advance Class Day 1 & 2
Covering :
- Memory Leak
- Job Scheduler
- Architecture Component
Framework engineering JCO 2011
Framework design involves balancing many considerations, such as:
- Managing dependencies between components to allow for flexibility and evolution over time. Techniques like dependency injection and layering help achieve this.
- Designing APIs by first writing code samples for key scenarios and defining object models to support these samples to ensure usability.
- Treating simplicity as a feature by removing unnecessary requirements and reusing existing concepts where possible.
Understanding memory management in xamarin forms
Lecture delivered in BASTA 2018, regarding Xamarin Forms memory structure and specifics when dealing with custom renderers, effects and external plugins
Common mistakes in android development
Slide sharing common mistakes when develop Android application.
Including LiveData and Kotlin Coroutine knowledge.
Inside the Android application framework - Google I/O 2009
- Android applications are composed of components that can span multiple processes and tasks. Components have managed lifecycles as they transition between states like active, paused, and stopped.
- Inter-process communication (IPC) allows components in different processes to share data. The Android Binder system provides efficient IPC using parcelables and bundles to pass data across processes.
- Activities represent screens or views within an application. Tasks group related activities that maintain a back stack. By default each application runs in its own process but additional processes can be used to isolate components from one another.
Ase02.ppt
The document summarizes work on Caffeine, a tool for dynamic analysis of Java programs. It discusses:
1) The motivation for dynamic analysis to understand program behavior at runtime.
2) Models used in Caffeine including a trace model to record execution events and an execution model using Prolog predicates.
3) An example analysis counting the number of backtracks in a n-queens algorithm to illustrate using Caffeine.
Android App Architecture with modern libs in practice. Our way in R.I.D., Ser...
The document discusses the architecture and testing approach used in an Android application called R.I.D. It describes the Dagger dependency injection structure including AppComponent, BaseActivityComponent, and ActivityComponent. It provides code samples for modules, subcomponents, and annotations. It also discusses the use of UI tests with Espresso and custom rules to mock dependencies, as well as unit testing with mocked presenters and custom RxJava schedulers. Finally, it covers test coverage, continuous integration, hiring needs, and future plans.
Garbage collection
The document discusses Java garbage collection. It explains that Java's garbage collector automatically manages memory by freeing unreferenced objects. The garbage collector runs when memory is low to find and delete objects that cannot be reached. While garbage collection provides convenience, it has overhead as the system must pause current execution to run it which can influence user experience. The document also describes how objects are identified as garbage using tracing and reference counting collectors as well as how to explicitly make objects available for collection and finalize objects before deletion.
Meetup - Singleton & DI/IoC
The document discusses design patterns including the Singleton pattern and Dependency Injection (DI) / Inversion of Control (IoC). It provides examples of different ways to implement the Singleton pattern in Java and compares their thread safety. It also shows an implementation of DI/IoC without a third party library by using annotations to mark classes and fields for injection. The implementation finds annotated classes, instantiates them, and resolves their dependencies by setting injected fields.
OpenWebBeans and DeltaSpike at ApacheCon
This document provides an overview of CDI (Contexts and Dependency Injection) and some portable CDI extensions, including Apache DeltaSpike. It discusses key CDI concepts like dependency injection, interceptors, events, and scopes. It introduces Apache OpenWebBeans as a fast and stable CDI container implementation. It then demonstrates how DeltaSpike extends CDI with additional features like transaction management, qualifiers, specialized configuration, and alternatives. The document encourages involvement to help shape the future of Apache DeltaSpike.
Singleton Object Management
This is from my series of presentations on C++ and Design Pattern. This was first presented at Interra in 2005.
Kandroid for nhn_deview_20131013_v5_final
The document provides information about high performance Android app development. It begins with a history of Android performance features from early versions through Jellybean and Project Butter. It then compares the three Android programming models (SDK, NDK, RenderScript) in terms of workflow, execution model, and performance. A case study on the performance features of the Google Chrome browser for Android is presented, covering its multi-process architecture, hardware acceleration, networking, and VSync scheduling. The document concludes with a questionnaire on topics like multi-core vs GPU, Android vs Chrome, and developments beyond Android.
Design patterns in javascript
The document provides an introduction to design patterns developed by the Gang of Four (GoF). It discusses several common design patterns in JavaScript like the constructor pattern, module pattern, singleton pattern, observer pattern, mediator pattern, prototype pattern, command pattern, facade pattern, and mixin pattern. For each pattern, it explains the problem it addresses, provides an example implementation, and notes advantages and disadvantages of the pattern. The overall document serves as a high-level overview of fundamental design patterns and their usage in JavaScript applications.
performance optimization: Memory
Memory management best practices in Android include using the sparse array family for collections below 1,000 items, avoiding unnecessary object creation, using StringBuilder for string concatenation, properly closing streams to prevent memory leaks, and using patterns like object pools and flyweights to reduce memory usage. The onTrimMemory callback and memory monitoring tools like Memory Monitor and Heap Viewer can help detect memory issues and leaks in an Android application.
Prospector Osq 2004 Final
The document discusses an approach called "jungloid mining" to help programmers more easily perform common tasks by automatically finding concise code snippets (called "jungloids") to transform objects of one type to another. It observes that many programming problems can be described as searching for a jungloid to transform a single input object to a single output object type. It presents an algorithm and tool called Prospector that mines codebases for valid jungloids and represents them as paths in a graph, often finding the optimal jungloid via the shortest path. Future work aims to improve Prospector's understanding of semantics, types, and other graph-theoretic considerations.
Five android architecture
Introduction to the modification of the Clean Architecture that we use at Five Agency during our Android development
Finding Concurrency Errors in Event-Driven Applications - Strangeloop'14
We present a new open-source analysis system called EventRacer (www.eventracer.org) developed at the Software Reliability Lab at ETH Zurich, that finds harmful concurrency errors in event-driven applications such as web pages and Android applications. We illustrate how these concurrency errors can occur in real-world applications as well as the key analysis mechanisms behind EventRacer.
Os Haase
This document provides an overview of the Swing Application Framework and Beans Binding frameworks being developed as part of JSR 296 and JSR 295. It discusses the motivations for creating standard frameworks to simplify Swing development, outlines the key goals and components of the Swing Application Framework, and briefly introduces Beans Binding for keeping object properties in sync. The frameworks are aimed at addressing common issues for typical Swing applications and are intended for the Java SE 7 platform.
Droid con 2013 workshop unit testing in android [robolectirc]
This document discusses unit testing Android applications. It introduces Robolectric, an emulation framework that runs unit tests for Android apps on a Java Virtual Machine instead of an emulator or device. This allows tests to run much faster. Robolectric emulates the Android SDK and resources using shadow objects and view/resource loading. It is easy to extend and has good community support. While useful for unit testing, it cannot replace integrated tests that run on actual devices.
SGXMonitor Presentation - ACSAC 2022
- SgxMonitor is a provenance analysis tool for SGX enclaves that provides attack-resistant tracing without introducing new attack surfaces.
- It models SGX enclaves as finite state machines including global states, extracted using symbolic execution and static analysis.
- Evaluation shows it identifies attacks in tested malware with no false positives, and incurs limited overhead in benchmarks.
SnakeGX (full version)
SnakeGX is a framework that implants a persistent backdoor in SGX enclaves without being detected by the host OS. It works by exploiting SGX isolation to avoid memory inspection, leaving minimal traces. The key aspects are: (1) analyzing enclave memory to find a trusted thread for payload installation, (2) installing ROP chains and a fake ocall context trigger, (3) designing the backdoor with split payload chains that interact inside and outside the enclave via context switching. An evaluation on StealthDB shows the trigger is much smaller than the payload, making it harder to detect through memory forensics.
More Related Content
Similar to Static Analysis of Context Leaks in Android Applications
Exploring Kotlin language basics for Android App development
Kotlin is a new programming language that targets JVM, Android and JavaScript. It is 100% interoperable with Java and avoids NullPointerExceptions. Some key features include lambda expressions, immutable val properties, smart casting, and named arguments. Kotlin code can use existing Java frameworks and libraries. Data classes, sealed classes, and when expressions make the code cleaner. Best practices include using apply() for object initialization and named arguments instead of method chaining.
Advanced android app development
Indonesian Android Kejar (IAK) Discussion group
Advance Class Day 1 & 2
Covering :
- Memory Leak
- Job Scheduler
- Architecture Component
Framework engineering JCO 2011
Framework design involves balancing many considerations, such as:
- Managing dependencies between components to allow for flexibility and evolution over time. Techniques like dependency injection and layering help achieve this.
- Designing APIs by first writing code samples for key scenarios and defining object models to support these samples to ensure usability.
- Treating simplicity as a feature by removing unnecessary requirements and reusing existing concepts where possible.
Understanding memory management in xamarin forms
Lecture delivered in BASTA 2018, regarding Xamarin Forms memory structure and specifics when dealing with custom renderers, effects and external plugins
Common mistakes in android development
Slide sharing common mistakes when develop Android application.
Including LiveData and Kotlin Coroutine knowledge.
Inside the Android application framework - Google I/O 2009
- Android applications are composed of components that can span multiple processes and tasks. Components have managed lifecycles as they transition between states like active, paused, and stopped.
- Inter-process communication (IPC) allows components in different processes to share data. The Android Binder system provides efficient IPC using parcelables and bundles to pass data across processes.
- Activities represent screens or views within an application. Tasks group related activities that maintain a back stack. By default each application runs in its own process but additional processes can be used to isolate components from one another.
Ase02.ppt
The document summarizes work on Caffeine, a tool for dynamic analysis of Java programs. It discusses:
1) The motivation for dynamic analysis to understand program behavior at runtime.
2) Models used in Caffeine including a trace model to record execution events and an execution model using Prolog predicates.
3) An example analysis counting the number of backtracks in a n-queens algorithm to illustrate using Caffeine.
Android App Architecture with modern libs in practice. Our way in R.I.D., Ser...
The document discusses the architecture and testing approach used in an Android application called R.I.D. It describes the Dagger dependency injection structure including AppComponent, BaseActivityComponent, and ActivityComponent. It provides code samples for modules, subcomponents, and annotations. It also discusses the use of UI tests with Espresso and custom rules to mock dependencies, as well as unit testing with mocked presenters and custom RxJava schedulers. Finally, it covers test coverage, continuous integration, hiring needs, and future plans.
Garbage collection
The document discusses Java garbage collection. It explains that Java's garbage collector automatically manages memory by freeing unreferenced objects. The garbage collector runs when memory is low to find and delete objects that cannot be reached. While garbage collection provides convenience, it has overhead as the system must pause current execution to run it which can influence user experience. The document also describes how objects are identified as garbage using tracing and reference counting collectors as well as how to explicitly make objects available for collection and finalize objects before deletion.
Meetup - Singleton & DI/IoC
The document discusses design patterns including the Singleton pattern and Dependency Injection (DI) / Inversion of Control (IoC). It provides examples of different ways to implement the Singleton pattern in Java and compares their thread safety. It also shows an implementation of DI/IoC without a third party library by using annotations to mark classes and fields for injection. The implementation finds annotated classes, instantiates them, and resolves their dependencies by setting injected fields.
OpenWebBeans and DeltaSpike at ApacheCon
This document provides an overview of CDI (Contexts and Dependency Injection) and some portable CDI extensions, including Apache DeltaSpike. It discusses key CDI concepts like dependency injection, interceptors, events, and scopes. It introduces Apache OpenWebBeans as a fast and stable CDI container implementation. It then demonstrates how DeltaSpike extends CDI with additional features like transaction management, qualifiers, specialized configuration, and alternatives. The document encourages involvement to help shape the future of Apache DeltaSpike.
Singleton Object Management
This is from my series of presentations on C++ and Design Pattern. This was first presented at Interra in 2005.
Kandroid for nhn_deview_20131013_v5_final
The document provides information about high performance Android app development. It begins with a history of Android performance features from early versions through Jellybean and Project Butter. It then compares the three Android programming models (SDK, NDK, RenderScript) in terms of workflow, execution model, and performance. A case study on the performance features of the Google Chrome browser for Android is presented, covering its multi-process architecture, hardware acceleration, networking, and VSync scheduling. The document concludes with a questionnaire on topics like multi-core vs GPU, Android vs Chrome, and developments beyond Android.
Design patterns in javascript
The document provides an introduction to design patterns developed by the Gang of Four (GoF). It discusses several common design patterns in JavaScript like the constructor pattern, module pattern, singleton pattern, observer pattern, mediator pattern, prototype pattern, command pattern, facade pattern, and mixin pattern. For each pattern, it explains the problem it addresses, provides an example implementation, and notes advantages and disadvantages of the pattern. The overall document serves as a high-level overview of fundamental design patterns and their usage in JavaScript applications.
performance optimization: Memory
Memory management best practices in Android include using the sparse array family for collections below 1,000 items, avoiding unnecessary object creation, using StringBuilder for string concatenation, properly closing streams to prevent memory leaks, and using patterns like object pools and flyweights to reduce memory usage. The onTrimMemory callback and memory monitoring tools like Memory Monitor and Heap Viewer can help detect memory issues and leaks in an Android application.
Prospector Osq 2004 Final
The document discusses an approach called "jungloid mining" to help programmers more easily perform common tasks by automatically finding concise code snippets (called "jungloids") to transform objects of one type to another. It observes that many programming problems can be described as searching for a jungloid to transform a single input object to a single output object type. It presents an algorithm and tool called Prospector that mines codebases for valid jungloids and represents them as paths in a graph, often finding the optimal jungloid via the shortest path. Future work aims to improve Prospector's understanding of semantics, types, and other graph-theoretic considerations.
Five android architecture
Introduction to the modification of the Clean Architecture that we use at Five Agency during our Android development
Finding Concurrency Errors in Event-Driven Applications - Strangeloop'14
We present a new open-source analysis system called EventRacer (www.eventracer.org) developed at the Software Reliability Lab at ETH Zurich, that finds harmful concurrency errors in event-driven applications such as web pages and Android applications. We illustrate how these concurrency errors can occur in real-world applications as well as the key analysis mechanisms behind EventRacer.
Os Haase
This document provides an overview of the Swing Application Framework and Beans Binding frameworks being developed as part of JSR 296 and JSR 295. It discusses the motivations for creating standard frameworks to simplify Swing development, outlines the key goals and components of the Swing Application Framework, and briefly introduces Beans Binding for keeping object properties in sync. The frameworks are aimed at addressing common issues for typical Swing applications and are intended for the Java SE 7 platform.
Droid con 2013 workshop unit testing in android [robolectirc]
This document discusses unit testing Android applications. It introduces Robolectric, an emulation framework that runs unit tests for Android apps on a Java Virtual Machine instead of an emulator or device. This allows tests to run much faster. Robolectric emulates the Android SDK and resources using shadow objects and view/resource loading. It is easy to extend and has good community support. While useful for unit testing, it cannot replace integrated tests that run on actual devices.
Similar to Static Analysis of Context Leaks in Android Applications (20)
Exploring Kotlin language basics for Android App development
Exploring Kotlin language basics for Android App development
Inside the Android application framework - Google I/O 2009
Inside the Android application framework - Google I/O 2009
Android App Architecture with modern libs in practice. Our way in R.I.D., Ser...
Android App Architecture with modern libs in practice. Our way in R.I.D., Ser...
Finding Concurrency Errors in Event-Driven Applications - Strangeloop'14
Finding Concurrency Errors in Event-Driven Applications - Strangeloop'14
Droid con 2013 workshop unit testing in android [robolectirc]
Droid con 2013 workshop unit testing in android [robolectirc]
More from Flavio Toffalini
SGXMonitor Presentation - ACSAC 2022
- SgxMonitor is a provenance analysis tool for SGX enclaves that provides attack-resistant tracing without introducing new attack surfaces.
- It models SGX enclaves as finite state machines including global states, extracted using symbolic execution and static analysis.
- Evaluation shows it identifies attacks in tested malware with no false positives, and incurs limited overhead in benchmarks.
SnakeGX (full version)
SnakeGX is a framework that implants a persistent backdoor in SGX enclaves without being detected by the host OS. It works by exploiting SGX isolation to avoid memory inspection, leaving minimal traces. The key aspects are: (1) analyzing enclave memory to find a trusted thread for payload installation, (2) installing ROP chains and a fake ocall context trigger, (3) designing the backdoor with split payload chains that interact inside and outside the enclave via context switching. An evaluation on StealthDB shows the trigger is much smaller than the payload, making it harder to detect through memory forensics.
SnakeGX (short version)
- SnakeGX is a framework that implants a persistent backdoor in SGX enclaves using code-reuse techniques, allowing an attacker to interact with the enclave without detection by the host OS. It exploits SGX isolation to avoid memory inspection and leaves minimal traces.
- The backdoor remains inside the enclave after installation and can invoke syscalls. It is more stealthy than prior attacks as it does not require crashing the enclave repeatedly or introducing unexpected enclaves.
- An evaluation shows the backdoor payload is over 4KB in size but the trigger is only 56B, making it much harder to detect through memory forensic analysis than state-of-the-art attacks.
ScaRR
ScaRR is a system that provides scalable runtime remote attestation to verify dynamic properties of complex systems. It uses offline analysis to generate measurements of expected execution paths that are verified online. ScaRR models programs as graphs of execution checkpoints and actions to handle complex control flows. It provides efficient verification by checking consistency between reported execution paths and pre-computed expected paths stored in a hashmap. An evaluation shows ScaRR can verify programs faster and with lower network overhead than previous work, while providing security against various attacks.
Careful Packing
Careful-Packing is an anti-tampering software protection technique that uses trusted computing to protect critical sections of code. It works by encrypting critical sections when not in use and only decrypting them in a trusted region when execution is needed. This prevents attackers from tampering with the code offline or online. The approach addresses challenges regarding denial of service attacks, concurrency, installation, and booting by techniques like heartbeat proofs, reference counting threads, sealed key installation, and encrypted key booting. An evaluation of a proof of concept keystroke monitoring implementation showed around 5% overhead for a single instance and linear scaling for multiple parallel instances.
Google Dorks: Analysis, Creation, and new Defenses
1) The document analyzes Google dorks, which are search queries used by attackers to find vulnerable systems. It presents a taxonomy of existing dorks and motivates the need for new defenses.
2) The authors introduce a new type of "word-based" dork that uses common words left by content management systems to target websites built with those systems. An algorithm is developed to automatically generate effective word-based dorks.
3) Defenses against word-based dorks are proposed, such as inserting invisible Unicode characters into common words to prevent search engines from indexing them. The document concludes by motivating the need for continued research into new dork types and defenses.
More from Flavio Toffalini (6)
Google Dorks: Analysis, Creation, and new Defenses
Google Dorks: Analysis, Creation, and new Defenses
Recently uploaded
AI 101: An Introduction to the Basics and Impact of Artificial Intelligence
Imagine a world where machines not only perform tasks but also learn, adapt, and make decisions. This is the promise of Artificial Intelligence (AI), a technology that's not just enhancing our lives but revolutionizing entire industries.
UiPath Test Automation using UiPath Test Suite series, part 6
Welcome to UiPath Test Automation using UiPath Test Suite series part 6. In this session, we will cover Test Automation with generative AI and Open AI.
UiPath Test Automation with generative AI and Open AI webinar offers an in-depth exploration of leveraging cutting-edge technologies for test automation within the UiPath platform. Attendees will delve into the integration of generative AI, a test automation solution, with Open AI advanced natural language processing capabilities.
Throughout the session, participants will discover how this synergy empowers testers to automate repetitive tasks, enhance testing accuracy, and expedite the software testing life cycle. Topics covered include the seamless integration process, practical use cases, and the benefits of harnessing AI-driven automation for UiPath testing initiatives. By attending this webinar, testers, and automation professionals can gain valuable insights into harnessing the power of AI to optimize their test automation workflows within the UiPath ecosystem, ultimately driving efficiency and quality in software development processes.
What will you get from this session?
1. Insights into integrating generative AI.
2. Understanding how this integration enhances test automation within the UiPath platform
3. Practical demonstrations
4. Exploration of real-world use cases illustrating the benefits of AI-driven test automation for UiPath
Topics covered:
What is generative AI
Test Automation with generative AI and Open AI.
UiPath integration with generative AI
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
June Patch Tuesday
Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
Choosing The Best AWS Service For Your Website + API.pptx
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
GraphRAG for Life Science to increase LLM accuracy
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
ここ3000字までしか入らないけどタイトルの方がたくさん文字入ると思います。
20240609 QFM020 Irresponsible AI Reading List May 2024
Everything I found interesting about the irresponsible use of machine intelligence in May 2024
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...Edge AI and Vision Alliance
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/building-and-scaling-ai-applications-with-the-nx-ai-manager-a-presentation-from-network-optix/
Robin van Emden, Senior Director of Data Science at Network Optix, presents the “Building and Scaling AI Applications with the Nx AI Manager,” tutorial at the May 2024 Embedded Vision Summit.
In this presentation, van Emden covers the basics of scaling edge AI solutions using the Nx tool kit. He emphasizes the process of developing AI models and deploying them globally. He also showcases the conversion of AI models and the creation of effective edge AI pipelines, with a focus on pre-processing, model conversion, selecting the appropriate inference engine for the target hardware and post-processing.
van Emden shows how Nx can simplify the developer’s life and facilitate a rapid transition from concept to production-ready applications.He provides valuable insights into developing scalable and efficient edge AI solutions, with a strong focus on practical implementation.Webinar: Designing a schema for a Data Warehouse
Are you new to data warehouses (DWH)? Do you need to check whether your data warehouse follows the best practices for a good design? In both cases, this webinar is for you.
A data warehouse is a central relational database that contains all measurements about a business or an organisation. This data comes from a variety of heterogeneous data sources, which includes databases of any type that back the applications used by the company, data files exported by some applications, or APIs provided by internal or external services.
But designing a data warehouse correctly is a hard task, which requires gathering information about the business processes that need to be analysed in the first place. These processes must be translated into so-called star schemas, which means, denormalised databases where each table represents a dimension or facts.
We will discuss these topics:
- How to gather information about a business;
- Understanding dictionaries and how to identify business entities;
- Dimensions and facts;
- Setting a table granularity;
- Types of facts;
- Types of dimensions;
- Snowflakes and how to avoid them;
- Expanding existing dimensions and facts.
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
Digital Marketing Trends in 2024 | Guide for Staying Ahead
https://www.wask.co/ebooks/digital-marketing-trends-in-2024
Feeling lost in the digital marketing whirlwind of 2024? Technology is changing, consumer habits are evolving, and staying ahead of the curve feels like a never-ending pursuit. This e-book is your compass. Dive into actionable insights to handle the complexities of modern marketing. From hyper-personalization to the power of user-generated content, learn how to build long-term relationships with your audience and unlock the secrets to success in the ever-shifting digital landscape.
HCL Notes and Domino License Cost Reduction in the World of DLAU
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?
ABSTRACT: A prima vista, un mattoncino Lego e la backdoor XZ potrebbero avere in comune il fatto di essere entrambi blocchi di costruzione, o dipendenze di progetti creativi e software. La realtà è che un mattoncino Lego e il caso della backdoor XZ hanno molto di più di tutto ciò in comune.
Partecipate alla presentazione per immergervi in una storia di interoperabilità, standard e formati aperti, per poi discutere del ruolo importante che i contributori hanno in una comunità open source sostenibile.
BIO: Sostenitrice del software libero e dei formati standard e aperti. È stata un membro attivo dei progetti Fedora e openSUSE e ha co-fondato l'Associazione LibreItalia dove è stata coinvolta in diversi eventi, migrazioni e formazione relativi a LibreOffice. In precedenza ha lavorato a migrazioni e corsi di formazione su LibreOffice per diverse amministrazioni pubbliche e privati. Da gennaio 2020 lavora in SUSE come Software Release Engineer per Uyuni e SUSE Manager e quando non segue la sua passione per i computer e per Geeko coltiva la sua curiosità per l'astronomia (da cui deriva il suo nickname deneb_alpha).
5th LF Energy Power Grid Model Meet-up Slides
5th Power Grid Model Meet-up
It is with great pleasure that we extend to you an invitation to the 5th Power Grid Model Meet-up, scheduled for 6th June 2024. This event will adopt a hybrid format, allowing participants to join us either through an online Mircosoft Teams session or in person at TU/e located at Den Dolech 2, Eindhoven, Netherlands. The meet-up will be hosted by Eindhoven University of Technology (TU/e), a research university specializing in engineering science & technology.
Power Grid Model
The global energy transition is placing new and unprecedented demands on Distribution System Operators (DSOs). Alongside upgrades to grid capacity, processes such as digitization, capacity optimization, and congestion management are becoming vital for delivering reliable services.
Power Grid Model is an open source project from Linux Foundation Energy and provides a calculation engine that is increasingly essential for DSOs. It offers a standards-based foundation enabling real-time power systems analysis, simulations of electrical power grids, and sophisticated what-if analysis. In addition, it enables in-depth studies and analysis of the electrical power grid’s behavior and performance. This comprehensive model incorporates essential factors such as power generation capacity, electrical losses, voltage levels, power flows, and system stability.
Power Grid Model is currently being applied in a wide variety of use cases, including grid planning, expansion, reliability, and congestion studies. It can also help in analyzing the impact of renewable energy integration, assessing the effects of disturbances or faults, and developing strategies for grid control and optimization.
What to expect
For the upcoming meetup we are organizing, we have an exciting lineup of activities planned:
-Insightful presentations covering two practical applications of the Power Grid Model.
-An update on the latest advancements in Power Grid -Model technology during the first and second quarters of 2024.
-An interactive brainstorming session to discuss and propose new feature requests.
-An opportunity to connect with fellow Power Grid Model enthusiasts and users.
Recently uploaded (20)
AI 101: An Introduction to the Basics and Impact of Artificial Intelligence
AI 101: An Introduction to the Basics and Impact of Artificial Intelligence
UiPath Test Automation using UiPath Test Suite series, part 6
UiPath Test Automation using UiPath Test Suite series, part 6
Deep Dive: AI-Powered Marketing to Get More Leads and Customers with HyperGro...
Deep Dive: AI-Powered Marketing to Get More Leads and Customers with HyperGro...
Choosing The Best AWS Service For Your Website + API.pptx
Choosing The Best AWS Service For Your Website + API.pptx
GraphRAG for Life Science to increase LLM accuracy
GraphRAG for Life Science to increase LLM accuracy
Nordic Marketo Engage User Group_June 13_ 2024.pptx
Nordic Marketo Engage User Group_June 13_ 2024.pptx
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
20240609 QFM020 Irresponsible AI Reading List May 2024
20240609 QFM020 Irresponsible AI Reading List May 2024
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Digital Marketing Trends in 2024 | Guide for Staying Ahead
Digital Marketing Trends in 2024 | Guide for Staying Ahead
HCL Notes and Domino License Cost Reduction in the World of DLAU
HCL Notes and Domino License Cost Reduction in the World of DLAU
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?
Static Analysis of Context Leaks in Android Applications
- 1. Static Analysis of Context Leaks in Android Applications Flavio Toffalini, Sun Jun, and Martín Ochoa Singapore University of Technology and Design
- 2. Outline • Goal • Android Life-cycle • Context Memory Leaks • Our Analysis • Experiments
- 3. Detect Context memory leaks in Android applications
- 4. Android employs a garbage collector Developers cannot trigger memory deallocation Automatic garbage collection is not perfect Some objects are not deallocated Android life-cycle
- 5. Android life-cycle Some objects follow a life-cycle (e.g., Activities) Only Android can change the state of an object The developer can only drive objects status by implementing callback functions It is impossible to avoid an object destruction BUT it is possible to intercept events and close it gracefully Life-cycle objects are “subclasses” of Context classes
- 6. Context Memory Leaks Static-fields Thread-like objects Manager (interfaces)
- 7. Context Memory Leaks – Static Fields // things for handling a GUI static Activity a; void method1() {} int setA() {} void getA() {} Class CActivity A (subclass of Context) Created Running… Running… Running… Destroyed This field does not allow the GC to deallocate A’s memory
- 8. Context Memory Leaks – Thread-like objects // things for handling a GUI void run() { // I’m doing my long // long process! } Thread T (inner class) Activity A (subclass of Context) Created Running… Thread running… Running… Destroyed This is a synthetic field that does not allow the GC to deallocate A’s memory till the thread T is running
- 9. Context Memory Leaks – Managers // things for handling a GUI void onCallbackFuntion() { // I do my callback duties } void a() { setManager(this); } Activity A implement Callback (subclass of Context) Created Running… Callback assignment Running… Destroyed This assignment does not allow the GC to deallocate A’s memory
- 10. Our Analysis – overview APK Warnings Julia analyzer
- 11. Our Analysis – overview APK Warnings Julia analyzer What Julia does: - Simulate android life-cycle - Create a full CFG (besides reflection) - Implement abstract interpretation (e.g., for backward analysis)
- 12. Our Analysis - intuition Not all Context are bad guys.. Context Activity Service ApplicationContextBroadcastReceiver This is a safe Context It is valid as long as the application is running
- 13. Our Analysis - intuition Application Context is returned by getApplicationContext() Activity a = …; Context c = (Context)a; Context c = getApplicationContext(); Bad Context Good Context!
- 14. Our Analysis How can a field reach a Context? - It points to a Context subclass - It points to a Context-container That’s trivial That’s not trivial at all
- 15. Our Analysis – Context-container static Class2 c2 // GUI stuffs Class1 Class2 Activity Class3 c3 Class4 c4 Class3 Context-containers
- 16. Our Analysis 1. List all fields that point to a Context subclass or to a context-container 2. Backward analysis to identify the nature of the fields: 1. If all producers are ApplicationContext or Null, the field does not leak 2. Else, the field will leak
- 17. Evaluation We selected 8 open source applications Compared to another memory leak analyzers: Lint
- 18. Evaluation
- 19. Thanks! Q&A