The post analyses the exploit of CVE-2023-4069, a vulnerability arising due to certain optimizations in maglev JIT compiler of chromium. All the primitives are explained in detail that allow us to execute arbitray code.

A leading dash in git_url turned a safe-looking exec call into remote code execution on the Semaphore server. CVSS 9.9, GHSA-xp7j-h7jc-4w8p.

In this post I try to explain the exploitation process of CVE-2024-5830. I explain all the primitives and the v8 specific concepts necessary for exploiting an OOB read.

This post shows how we can set up chromium source code in the elixir project that makes code auditing very convinient.

This post shows how I discovered 2 CVEs in fluent-bit using network fuzzer called boofuzz. Different mangled HTTP packets are sent to differnt input endpoints of fluent-bit to find vulnerabilities.

This post contains my attempt to rediscover CVE-2021-3156 using fuzzing with AFL++. This post also shows how much good input corpus is necessary for vulnerability finding as without the 2 inputs given, this bug would not have been found by the fuzzer.

In this post I try to rediscover CVE-2024-35524 with AFL++. This post teaches us how crucial code coverage is in fuzzing campaigns. This vulnerability was triggered in a few seconds and the hard part was to cover the code that had the vulnerability.

This post contains detailed steps on how I found CVE-2024-22857 in zlog logging library with fuzzing using AFL++.

This post contains root cause analysis and PoC for CVE-2024-22857.