<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dominik Czarnota on The Trail of Bits Blog</title><link>https://blog.trailofbits.com/authors/dominik-czarnota/</link><description>Recent content in Dominik Czarnota on The Trail of Bits Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 16 Dec 2025 00:00:00 -0500</lastBuildDate><atom:link href="https://blog.trailofbits.com/authors/dominik-czarnota/index.xml" rel="self" type="application/rss+xml"/><item><title>Use GWP-ASan to detect exploits in production environments</title><link>https://blog.trailofbits.com/2025/12/16/use-gwp-asan-to-detect-exploits-in-production-environments/</link><pubDate>Tue, 16 Dec 2025 07:00:00 -0500</pubDate><guid>https://blog.trailofbits.com/2025/12/16/use-gwp-asan-to-detect-exploits-in-production-environments/</guid><description>GWP-ASan is a sampling-based memory error detection tool that catches critical bugs like use-after-free and buffer overflows in production environments with near-zero performance overhead, unlike AddressSanitizer which is too resource-intensive for deployment.</description></item><item><title>Sanitize your C++ containers: ASan annotations step-by-step</title><link>https://blog.trailofbits.com/2024/09/10/sanitize-your-c-containers-asan-annotations-step-by-step/</link><pubDate>Tue, 10 Sep 2024 09:00:42 -0400</pubDate><guid>https://blog.trailofbits.com/2024/09/10/sanitize-your-c-containers-asan-annotations-step-by-step/</guid><description>AddressSanitizer (ASan) is a compiler plugin that helps detect memory errors like buffer overflows or use-after-frees. In this post, we explain how to equip your C++ code with ASan annotations to find more bugs. We also show our work on ASan in GCC and LLVM. In LLVM, Trail of […]</description></item><item><title>Understanding AddressSanitizer: Better memory safety for your code</title><link>https://blog.trailofbits.com/2024/05/16/understanding-addresssanitizer-better-memory-safety-for-your-code/</link><pubDate>Thu, 16 May 2024 09:00:57 -0400</pubDate><guid>https://blog.trailofbits.com/2024/05/16/understanding-addresssanitizer-better-memory-safety-for-your-code/</guid><description>This post will guide you through using AddressSanitizer (ASan), a compiler plugin that helps developers detect memory issues in code that can lead to remote code execution attacks (such as WannaCry or this WebP implementation bug). ASan inserts checks around memory accesses during compile time, and crashes the program […]</description></item><item><title>Out of the kernel, into the tokens</title><link>https://blog.trailofbits.com/2024/03/08/out-of-the-kernel-into-the-tokens/</link><pubDate>Fri, 08 Mar 2024 09:00:48 -0500</pubDate><guid>https://blog.trailofbits.com/2024/03/08/out-of-the-kernel-into-the-tokens/</guid><description>We’re digging up the archives of vulnerabilities that Trail of Bits has reported over the years. This post shares the story of two such issues: a denial-of-service (DoS) vulnerability hidden in JSON Web Tokens (JWTs), and an oversight in the Linux kernel that could enable circumvention of critical kernel […]</description></item><item><title>Typos that omit security features and how to test for them</title><link>https://blog.trailofbits.com/2023/04/20/typos-that-omit-security-features-and-how-to-test-for-them/</link><pubDate>Thu, 20 Apr 2023 07:00:08 -0400</pubDate><guid>https://blog.trailofbits.com/2023/04/20/typos-that-omit-security-features-and-how-to-test-for-them/</guid><description>During a security audit, I discovered an easy-to-miss typo that unintentionally failed to enable _FORTIFY_SOURCE, which helps detect memory corruption bugs in incorrectly used C functions. We searched, found, and fixed twenty C and C++ bugs on GitHub with this same pattern. Here is a list of some of them related […]</description></item><item><title>How to check if a mutex is locked in Go</title><link>https://blog.trailofbits.com/2020/06/09/how-to-check-if-a-mutex-is-locked-in-go/</link><pubDate>Tue, 09 Jun 2020 07:50:53 -0400</pubDate><guid>https://blog.trailofbits.com/2020/06/09/how-to-check-if-a-mutex-is-locked-in-go/</guid><description>TL;DR: Can we check if a mutex is locked in Go? Yes, but not with a mutex API. Here’s a solution for use in debug builds. Although you can Lock() or Unlock() a mutex, you can’t check whether it’s locked. While it is a reasonable omission (e.g., due to possible race conditions; see also Why […]</description></item><item><title>Understanding Docker container escapes</title><link>https://blog.trailofbits.com/2019/07/19/understanding-docker-container-escapes/</link><pubDate>Fri, 19 Jul 2019 21:01:09 -0400</pubDate><guid>https://blog.trailofbits.com/2019/07/19/understanding-docker-container-escapes/</guid><description>Trail of Bits recently completed a security assessment of Kubernetes, including its interaction with Docker. Felix Wilhelm’s recent tweet of a Proof of Concept (PoC) “container escape” sparked our interest, since we performed similar research and were curious how this PoC could impact Kubernetes. Quick and dirty way to get out of a privileged k8s […]</description></item></channel></rss>