ABRT-ACTION-ANALYZ(1)

✨ NAME ✨

okay bestie, welcome to ABRT-ACTION-ANALYZ(1) from the ABRT Manual 💅 this page is all about abrt-action-analyze-vulnerability, which gives you the tea on how exploitable a crash might be 🔥

🧚 SYNOPSIS 🧚

abrt-action-analyze-vulnerability

💖 DESCRIPTION 💖

okay so this tool expects a file called coredump to be sitting in the current directory 📂 then it runs the abrt-gdb-exploitable gdb plugin on that file 🔍 the results get saved in a file called exploitable in the current directory, with info about the likely crash reason and an exploitable rating (check the EXPLOITABLE RATING section below, it's giving main character energy ✨). if the rating lands between <0-3>, no output gets generated and the tool silently exits with 0 exit code 🤫

this tool needs both gdb and eu-readelf executables placed in PATH 🛣️ if either one is missing, the tool silently exits with 0 exit code too, so no drama, just vibes 🫠

🦋 EXPLOITABLE RATING 🦋

bestie, the exploitable rating is a score on a scale of 0-9 📊 it's given to a coredump based on the likely reason the program crashed and whether it could've been caused by a potentially exploitable security issue 🕵️‍♀️

the lower numbers, 0-3, are reserved for reasons that are highly unlikely to be security issues 🌸 the higher numbers, 4-9, are reserved for potentially dangerous crashes 🚨

ngl, higher scores don't automatically mean security problems 💀 but they can totally help with debugging and figuring out how severe the issue is 🎀

👑 AUTHORS 👑

• ABRT team 🫶

---

that's the whole page, bestie 💜 it's from abrt 2.17.9, dated 08/03/2026, and it's the ABRT-ACTION-ANALYZ(1) manual page, so you're officially up to date 🌈✨