VulnerabilityPublished 12 Nov 2025Updated 14 Nov 2025

CVE-2025-64170: trifectatechfoundation sudo-rs · Missing Password Field Masking

Affects trifectatechfoundation sudo-rsSource CVE Database V5

Not known to be exploited · CVSS 3.8 Low : upgrade to 0.2.10 when convenient.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

3.8Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 0.2.10

CVSS:3.1/AV:P/AC:H/PR:H/UI:R/S:U/C:H/I:N/A:N

Attack Vector: Physical
Attack Complexity: High
Privileges Required: High
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Physical: The attack requires the attacker to physically touch or manipulate the vulnerable component. Physical interaction may be brief or persistent.
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade github/trifectatechfoundation/sudo-rs to 0.2.10.

Affected software

Product	Affected	Fixed in
crates.iogithub/trifectatechfoundation/sudo-rs`pkg:cargo/github/trifectatechfoundation/sudo-rs`Other threats	Affected <0.2.10 >=0.2.7	Fixed in 0.2.10

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should upgrade all sudo-rs deployments to version 0.2.10 or later to eliminate this vulnerability. Until upgrades are applied, users should be trained to avoid delaying password entry and to ensure they press return promptly to prevent timeout-triggered echoing. Terminal sessions should be secured to prevent unauthorized observation, including use of privacy screens and restricting physical access. Organizations should audit shell history configurations to ensure that password inputs or terminal outputs are not inadvertently logged or saved. Implementing session timeout policies and terminal locking can reduce the risk of pass-by attacks. Monitoring for unusual terminal activity or user reports of unexpected password echoes can help detect exploitation attempts. Finally, organizations should consider whether sudo-rs is appropriate for their environment or if traditional sudo implementations with mature security controls are preferable.

Description

sudo-rs is a memory safe implementation of sudo and su written in Rust. Starting in version 0.2.7 and prior to version 0.2.10, if a user begins entering a password but does not press return for an extended period, a password timeout may occur. When this happens, the keystrokes that were entered are echoed back to the console. This could reveal partial password information, possibly exposing history files when not carefully handled by the user and on screen, usable for Social Engineering or Pass-By attacks. Version 0.2.10 fixes the issue.

Impact

For European organizations, the impact of this vulnerability is generally low but non-negligible in environments where sudo-rs is deployed and used interactively by privileged users. Exposure of partial password input could lead to credential compromise if attackers have physical or remote access to terminals or if users inadvertently save terminal output or history files containing echoed passwords. This risk is heightened in shared or public workspaces, or in organizations with lax terminal security policies. While the vulnerability does not allow direct privilege escalation or system compromise, it undermines password confidentiality and could facilitate targeted social engineering or pass-by attacks. Organizations with high-security requirements or those handling sensitive data should consider the risk more seriously. The lack of known exploits and the requirement for local user interaction reduce the immediacy of the threat, but the vulnerability should be remediated promptly to maintain best security practices.

Summary

The vulnerability identified as CVE-2025-64170 affects sudo-rs, a memory-safe Rust implementation of the traditional sudo and su commands used for privilege escalation on Unix-like systems. Specifically, in versions 0.2.7 through 0.2.9, if a user starts typing their password but does not press the return key promptly, a password timeout mechanism triggers. Instead of masking the password input as is standard practice, the partially typed password characters are echoed back to the console. This behavior violates the principle of password field masking (CWE-549), potentially exposing sensitive password fragments to anyone observing the terminal or through residual data in shell history files if the user inadvertently saves such input. The exposure is limited to partial passwords and requires the user to delay input, but it nonetheless increases the risk of credential leakage through shoulder surfing, social engineering, or physical pass-by attacks. The vulnerability does not affect the confidentiality of the entire password if the user completes input normally and presses return promptly. The issue was addressed and fixed in sudo-rs version 0.2.10. The CVSS v3.1 score of 3.8 reflects a low severity due to the requirement for local privileges, user interaction, and the limited scope of impact (confidentiality only, no integrity or availability impact). No public exploits have been reported to date.

CWE-549Missing Password Field Masking (opens in a new tab)
Base weakness
The product does not mask passwords during entry, increasing the potential for attackers to observe and capture passwords.
Implementation · Requirements
Recommendations include requiring all password fields in your web application be masked to prevent other users from seeing this information.
OWASP ASVS 4.0.3
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
V9.2.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 19 Nov 2025, 21:14 UTC

WeaknessesCWE-549

Technical details

References

Community reviews

Related threats