<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>project on Asa&#39;s Website</title><link>https://ahessmat.netlify.com/tags/project/</link><description>Recent content in project on Asa&#39;s Website</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Sun, 25 Jul 2021 04:04:38 +0000</lastBuildDate><atom:link href="https://ahessmat.netlify.com/tags/project/index.xml" rel="self" type="application/rss+xml"/><item><title>SUIDcheck</title><link>https://ahessmat.netlify.com/post/2021-07-suidcheck/</link><pubDate>Sun, 25 Jul 2021 04:04:38 +0000</pubDate><guid>https://ahessmat.netlify.com/post/2021-07-suidcheck/</guid><description>One thing you have to keep in mind when securing your UNIX-based systems is the presence of binaries that have inappropriate permissions.
I recently released a working proof-of-concept (POC) code for identifying vulnerable UNIX binaries that have their SUID bit set.
A little background:
The Set owner user ID (SUID) bit denotes which user ID a given binary should be run as. Generally, a UNIX program inherits permissions from the user that runs it (i.</description></item></channel></rss>