CVE-2025-46718: CWE-497: Exposure of Sensitive System Information to an Unauthorized Control Sphere in trifectatechfoundation sudo-rs
sudo-rs is a memory safe implementation of sudo and su written in Rust. Prior to version 0.2.6, users with limited sudo privileges (e.g. execution of a single command) can list sudo privileges of other users using the `-U` flag. This vulnerability allows users with limited sudo privileges to enumerate the sudoers file, revealing sensitive information about other users' permissions. Attackers can collect information that can be used to more targeted attacks. Systems where users either do not have sudo privileges or have the ability to run all commands as root through sudo (the default configuration on most systems) are not affected by this advisory. Version 0.2.6 fixes the vulnerability.
AI Analysis
Technical Summary
CVE-2025-46718 is a vulnerability identified in sudo-rs, a Rust-based, memory-safe reimplementation of the traditional sudo and su utilities. The flaw exists in versions prior to 0.2.6 and allows users with limited sudo privileges—specifically those permitted to execute only a single command—to enumerate the sudo privileges of other users by leveraging the `-U` flag. This enumeration exposes sensitive system information, namely the sudoers file contents, which detail user permissions and command execution rights. The vulnerability is classified under CWE-497, which pertains to the exposure of sensitive system information to unauthorized control spheres. The issue arises because the sudo-rs implementation did not sufficiently restrict access to the privilege listing functionality, thereby allowing limited-privilege users to gain insight into the sudo configuration beyond their authorized scope. Notably, systems where users either lack sudo privileges entirely or have unrestricted sudo access (the default on many systems) are not affected. The vulnerability has a CVSS v3.1 base score of 3.3, indicating a low severity level, with an attack vector of local access, low complexity, requiring privileges but no user interaction, and impacts confidentiality only without affecting integrity or availability. No known exploits are reported in the wild, and the issue is resolved in version 0.2.6 of sudo-rs.
Potential Impact
For European organizations, the primary impact of this vulnerability lies in the potential exposure of sudo privilege configurations, which could aid attackers in crafting more targeted privilege escalation or lateral movement attacks. While the vulnerability does not directly allow privilege escalation or system compromise, the disclosure of sudoers file information can facilitate reconnaissance efforts by malicious insiders or compromised low-privilege accounts. This could lead to more effective exploitation of other vulnerabilities or misconfigurations. Organizations with strict role-based access controls and limited sudo privileges per user are more likely to be affected, as the vulnerability specifically targets scenarios where users have restricted sudo command execution rights. However, organizations that rely on traditional sudo implementations or grant broad sudo access may not be impacted. Given the low CVSS score and absence of known exploits, the immediate risk is limited, but the exposure of sensitive permission data could contribute to a broader attack chain if combined with other vulnerabilities or social engineering tactics.
Mitigation Recommendations
European organizations using sudo-rs should upgrade to version 0.2.6 or later to remediate this vulnerability. Beyond patching, administrators should audit sudo configurations to ensure that users have the minimum necessary privileges and that privilege assignments are tightly controlled. Implementing strict monitoring and logging of sudo command usage can help detect anomalous privilege enumeration attempts. Additionally, organizations should consider restricting access to systems running sudo-rs to trusted users only and employ multi-factor authentication to reduce the risk of compromised accounts being leveraged to exploit this vulnerability. Since the vulnerability requires local access with limited sudo privileges, enforcing strong endpoint security controls and user behavior analytics can further mitigate risk. Finally, educating users about the risks of privilege enumeration and encouraging prompt reporting of suspicious activities can enhance overall security posture.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Norway, Denmark
CVE-2025-46718: CWE-497: Exposure of Sensitive System Information to an Unauthorized Control Sphere in trifectatechfoundation sudo-rs
Description
sudo-rs is a memory safe implementation of sudo and su written in Rust. Prior to version 0.2.6, users with limited sudo privileges (e.g. execution of a single command) can list sudo privileges of other users using the `-U` flag. This vulnerability allows users with limited sudo privileges to enumerate the sudoers file, revealing sensitive information about other users' permissions. Attackers can collect information that can be used to more targeted attacks. Systems where users either do not have sudo privileges or have the ability to run all commands as root through sudo (the default configuration on most systems) are not affected by this advisory. Version 0.2.6 fixes the vulnerability.
AI-Powered Analysis
Technical Analysis
CVE-2025-46718 is a vulnerability identified in sudo-rs, a Rust-based, memory-safe reimplementation of the traditional sudo and su utilities. The flaw exists in versions prior to 0.2.6 and allows users with limited sudo privileges—specifically those permitted to execute only a single command—to enumerate the sudo privileges of other users by leveraging the `-U` flag. This enumeration exposes sensitive system information, namely the sudoers file contents, which detail user permissions and command execution rights. The vulnerability is classified under CWE-497, which pertains to the exposure of sensitive system information to unauthorized control spheres. The issue arises because the sudo-rs implementation did not sufficiently restrict access to the privilege listing functionality, thereby allowing limited-privilege users to gain insight into the sudo configuration beyond their authorized scope. Notably, systems where users either lack sudo privileges entirely or have unrestricted sudo access (the default on many systems) are not affected. The vulnerability has a CVSS v3.1 base score of 3.3, indicating a low severity level, with an attack vector of local access, low complexity, requiring privileges but no user interaction, and impacts confidentiality only without affecting integrity or availability. No known exploits are reported in the wild, and the issue is resolved in version 0.2.6 of sudo-rs.
Potential Impact
For European organizations, the primary impact of this vulnerability lies in the potential exposure of sudo privilege configurations, which could aid attackers in crafting more targeted privilege escalation or lateral movement attacks. While the vulnerability does not directly allow privilege escalation or system compromise, the disclosure of sudoers file information can facilitate reconnaissance efforts by malicious insiders or compromised low-privilege accounts. This could lead to more effective exploitation of other vulnerabilities or misconfigurations. Organizations with strict role-based access controls and limited sudo privileges per user are more likely to be affected, as the vulnerability specifically targets scenarios where users have restricted sudo command execution rights. However, organizations that rely on traditional sudo implementations or grant broad sudo access may not be impacted. Given the low CVSS score and absence of known exploits, the immediate risk is limited, but the exposure of sensitive permission data could contribute to a broader attack chain if combined with other vulnerabilities or social engineering tactics.
Mitigation Recommendations
European organizations using sudo-rs should upgrade to version 0.2.6 or later to remediate this vulnerability. Beyond patching, administrators should audit sudo configurations to ensure that users have the minimum necessary privileges and that privilege assignments are tightly controlled. Implementing strict monitoring and logging of sudo command usage can help detect anomalous privilege enumeration attempts. Additionally, organizations should consider restricting access to systems running sudo-rs to trusted users only and employ multi-factor authentication to reduce the risk of compromised accounts being leveraged to exploit this vulnerability. Since the vulnerability requires local access with limited sudo privileges, enforcing strong endpoint security controls and user behavior analytics can further mitigate risk. Finally, educating users about the risks of privilege enumeration and encouraging prompt reporting of suspicious activities can enhance overall security posture.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2025-04-28T20:56:09.083Z
- Cisa Enriched
- true
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 682d9816c4522896dcbd6819
Added to database: 5/21/2025, 9:08:38 AM
Last enriched: 7/12/2025, 2:47:05 AM
Last updated: 8/1/2025, 6:28:41 AM
Views: 21
Related Threats
CVE-2025-43735: CWE-79 Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') in Liferay Portal
MediumCVE-2025-40770: CWE-300: Channel Accessible by Non-Endpoint in Siemens SINEC Traffic Analyzer
HighCVE-2025-40769: CWE-1164: Irrelevant Code in Siemens SINEC Traffic Analyzer
HighCVE-2025-40768: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in Siemens SINEC Traffic Analyzer
HighCVE-2025-40767: CWE-250: Execution with Unnecessary Privileges in Siemens SINEC Traffic Analyzer
HighActions
Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.