PPhying中文
Curated security research, vulnerabilities, advisories and tools for practitioners.

Navigating the Perils of Race Conditions in iOS App Development

hackerone.com | blog | #code-review | #mobile-security | #ios | #race-conditions | #concurrency | #swift | #dispatchqueue | #thread-safety | #mobile-development
📄 Raw .md⬇️ Download .md🔗 Original ↗

Summary

Reviews race conditions in iOS development: use serial DispatchQueue to synchronize shared resource access and ensure UI updates run on the main thread to avoid data corruption and crashes.
Published
Collected

Related coverage

blog · bishopfox.com
Unified Code, Unified Risks: Uncovering Vulnerabilities in .NET MAUI Applications
Bishop Fox shows how to bypass .NET MAUI's platform packaging to extract readable C# assemblies from Android and iOS apps, then use that shared-assembly insight to uncover critical vulnerability patterns in common business logic.
research · calif.io
Learning to Jailbreak an iPhone with Claude (Part 1)
Claude helped me take apart an iOS Safari exploit, and retune it for my Mac. It even wrote its own variant.
vulnerability · calif.io
[CVE-2025-31207] Taking Apart iOS Apps: Anti-Debugging and Anti-Tampering in the Wild
# Taking Apart iOS Apps: Anti-Debugging and Anti-Tampering in the Wild Five apps, and what each of them does to stop you attaching a debugger. Huy Nguyen March 17, 2026 applereversing Contents 1....
blog · hackerone.com
Rust Safety: Writing Secure Concurrency without Fear
How Rust's ownership, borrowing, and lifetimes make concurrent code secure by construction: data races are rejected at compile time rather than found at runtime, without garbage collection overhead.
blog · hackerone.com
Leveraging Async/Await in ASP.NET for Enhanced Performance
Covers effective async/await usage in ASP.NET: reserve it for I/O-bound work, avoid .Result and .Wait() deadlocks with ConfigureAwait(false), and skip async for CPU-bound paths.
blog · hackerone.com
Avoiding the Hazards of Dependencies - Part 2
Mobile developer Chris Griffith shares practices for mitigating third-party dependency risks, including abstraction layers that ease library removal, with Swift examples applicable across platforms.
Back