RustSec logo

History ⋅ Edit ⋅ JSON (OSV)

RUSTSEC-2026-0591

Ineffective default DACL on Windows

Reported
Issued
Package
secmem-proc (crates.io)
Type
INFO Notice
Categories
References
Patched
  • >=0.3.9
Affected OSes
  • windows

Description

On Windows, affected versions of this crate do not provide the intended security-enhancement. In particular, any process running under the same user as the hardened process can reset our DACL, and thus bypass the protection the DACL should have provided. Usage of the crate however does not actively harm security.

On affected version, an explicit owner SID (taken from the process token) was used for the DACL. However, Windows implicitly grants extra access rights to the well-known "owner rights" SID, unless it occurs in the DACL, which it did not. This allows any process under the same user to reset the DACL of our process, making this defence effectively useless. The new code uses the well-known "owner rights" SID, preventing the attack.

The default hardening setup is fixed in version 0.3.9. Users creating a custom DACL with the API from the win_acl module need to manually update their code to get the security enhancement. They are strongly advised to use a well-known "owner rights" SID created using the new win_acl::SidRef::well_known (introduced in version 0.3.9) in their DACL instead of the owner SID returned by win_acl::TokenUser::sid.

Advisory available under CC0-1.0 license.