<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>sudo on Rich Mirch</title>
    <link>https://blog.mirch.io/tags/sudo/</link>
    <description>Recent content in sudo on Rich Mirch</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 30 Jun 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://blog.mirch.io/tags/sudo/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>CVE-2025-32462, CVE-2025-32463 Sudo chroot, host Option Elevation of Privilege Vulnerabilities</title>
      <link>https://blog.mirch.io/sudo-elevation-of-privilege-vulnerabilities/</link>
      <pubDate>Mon, 30 Jun 2025 00:00:00 +0000</pubDate>
      <guid>https://blog.mirch.io/sudo-elevation-of-privilege-vulnerabilities/</guid>
      <description>&lt;p&gt;I discovered two vulnerabilities in &lt;a href=&#34;https://www.sudo.ws&#34;&gt;Sudo&lt;/a&gt;. Upgrade to Sudo 1.9.17p1 or later.&lt;/p&gt;
&lt;h3 id=&#34;cve-2025-32462---sudo-host-option-elevation-of-privilege-vulnerability&#34;&gt;CVE-2025-32462 - Sudo Host Option Elevation of Privilege Vulnerability&lt;/h3&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;a href=&#34;https://www.cve.org/CVERecord?id=CVE-2025-32462&#34;&gt;CVE-2025-32462&lt;/a&gt; has remained unnoticed for over 12 years, despite being present in the code all along. It relies on a specific yet common configuration where Sudo rules are restricted to certain hostnames or hostname patterns. If these conditions are met, privilege escalation to root requires no exploit.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;ul&gt;
&lt;li&gt;Write-up: &lt;a href=&#34;https://www.stratascale.com/resource/cve-2025-32462-sudo-host-option-vulnerability/&#34;&gt;Sudo Host Option Elevation of Privilege&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Advisories
&lt;ul&gt;
&lt;li&gt;Sudo: &lt;a href=&#34;https://www.sudo.ws/security/advisories/host_any/&#34;&gt;https://www.sudo.ws/security/advisories/host_any/&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;RedHat: &lt;a href=&#34;https://access.redhat.com/security/cve/cve-2025-32462&#34;&gt;https://access.redhat.com/security/cve/cve-2025-32462&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Ubuntu: &lt;a href=&#34;https://ubuntu.com/security/notices/USN-7604-1&#34;&gt;https://ubuntu.com/security/notices/USN-7604-1&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Debian: &lt;a href=&#34;https://lists.debian.org/debian-security-announce/2025/msg00118.html&#34;&gt;https://lists.debian.org/debian-security-announce/2025/msg00118.html&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Amazon: &lt;a href=&#34;https://explore.alas.aws.amazon.com/CVE-2025-32462.html&#34;&gt;https://explore.alas.aws.amazon.com/CVE-2025-32462.html&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Gentoo: &lt;a href=&#34;https://bugs.gentoo.org/show_bug.cgi?id=CVE-2025-32462&#34;&gt;https://bugs.gentoo.org/show_bug.cgi?id=CVE-2025-32462&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;cve-2025-32463---sudo-chroot-elevation-of-privilege-vulnerability&#34;&gt;CVE-2025-32463 - Sudo chroot Elevation of Privilege Vulnerability&lt;/h3&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;a href=&#34;https://www.cve.org/CVERecord?id=CVE-2025-32463&#34;&gt;CVE-2025-32463&lt;/a&gt; The default Sudo configuration is vulnerable. Although the vulnerability involves the Sudo chroot feature, it does not require any Sudo rules to be defined for the user. As a result, any local unprivileged user could potentially escalate privileges to root if a vulnerable version is installed.&lt;/p&gt;
&lt;/blockquote&gt;</description>
    </item>
    <item>
      <title>sudoedit symlink fix for CVE-2021-23240 introduced new vulnerability</title>
      <link>https://blog.mirch.io/2021/01/25/sudoedit-lpe/</link>
      <pubDate>Tue, 26 Jan 2021 02:43:51 +0000</pubDate>
      <guid>https://blog.mirch.io/2021/01/25/sudoedit-lpe/</guid>
      <description>&lt;p&gt;I noticed the following changelog entry in sudo &lt;a href=&#34;https://www.sudo.ws/stable.html#1.9.5p1&#34;&gt;1.9.5p1.&lt;/a&gt; This caught my attention so I decided to look further. I was unable to find an advisory, PoC, or CVE for this vulnerability. Using the details from the changelog message and fix, I decided to write an exploit for it.&lt;/p&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://blog.mirch.io/images/2021/01/image.png?w=1024&#34;&gt;&lt;/p&gt;
&lt;p&gt;Using an Ubuntu 20.04.1 VM, I created a low privileged user named &amp;ldquo;lowpriv&amp;rdquo; and added a sudoedit rule for a root owned file /etc/test.txt. I also downloaded the &lt;a href=&#34;https://github.com/sudo-project/sudo/archive/SUDO_1_9_5.tar.gz&#34;&gt;source&lt;/a&gt; for sudo 1.9.5, compiled it, and installed it to /opt/sudo.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Metasploit module developed for CVE-2018-18556 VyOS Privilege Escalation</title>
      <link>https://blog.mirch.io/2020/09/25/metasploit-module-developed-for-cve-2018-18556-vyos-privilege-escalation/</link>
      <pubDate>Fri, 25 Sep 2020 20:52:25 +0000</pubDate>
      <guid>https://blog.mirch.io/2020/09/25/metasploit-module-developed-for-cve-2018-18556-vyos-privilege-escalation/</guid>
      <description>&lt;p&gt;Today, a Metasploit module was merged for a vulnerability I found in 2018 with &lt;a href=&#34;https://www.vyos.io/&#34;&gt;VyOS&lt;/a&gt;. This vulnerability was my first public InfoSec blog post. I appreciate &lt;a href=&#34;https://github.com/bcoles&#34;&gt;bcoles&lt;/a&gt; for developing the &lt;a href=&#34;https://github.com/rapid7/metasploit-framework/pull/14123&#34;&gt;exploit/linux/ssh/vyos_restricted_shell_privesc&lt;/a&gt; module. Read the &lt;a href=&#34;https://www.rapid7.com/blog/post/2020/09/25/metasploit-wrap-up-80/&#34;&gt;Metasploit Wrapup for 9/25/2020&lt;/a&gt;. The full write-up can be found on this blog at &lt;a href=&#34;https://blog.mirch.io/2018/11/05/cve-2018-18556-vyos-privilege-escalation-via-sudo-pppd-for-operator-users/&#34;&gt;CVE-2018-18556 – VyOS Privilege escalation via sudo pppd for operator users&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>CVE-2018-18556 - VyOS Privilege escalation via sudo pppd for operator users</title>
      <link>https://blog.mirch.io/2018/11/05/cve-2018-18556-vyos-privilege-escalation-via-sudo-pppd-for-operator-users/</link>
      <pubDate>Tue, 06 Nov 2018 04:39:42 +0000</pubDate>
      <guid>https://blog.mirch.io/2018/11/05/cve-2018-18556-vyos-privilege-escalation-via-sudo-pppd-for-operator-users/</guid>
      <description>&lt;p&gt;Recently I found several ways to escape the restricted shell for an operator user in &lt;a href=&#34;https://wiki.vyos.net/wiki/User_Guide&#34;&gt;VyOS&lt;/a&gt; 1.1.8. VyOS is a Linux-based network operating system that provides software-based network routing, firewall, and VPN functionality. I plan to post information on the restricted shell escapes in the near future; For now read the &lt;a href=&#34;http://blog.vyos.net/the-operator-level-is-proved-insecure-and-will-be-removed-in-the-next-releases&#34;&gt;blog&lt;/a&gt; by &lt;a href=&#34;https://x.com/dmbaturin&#34;&gt;@dmbaturin&lt;/a&gt; detailing some of the methods.&lt;/p&gt;
&lt;p&gt;This post will focus on how root access was obtained using sudo after the restricted shell was escaped. One of my first post exploitation steps on Linux after a low privileged shell is obtained is to check if the user has sudo rules configured. Sudo is designed to limit privileges but often it can be leveraged to elevate access.&lt;/p&gt;
</description>
    </item>
  </channel>
</rss>
