Skip to main content
VulnerabilityPublished Updated

Secmem proc: Ineffective default DACL on Windows

Affects secmem-procSource GCVE Database

0
Severity
Medium

Rated Medium by Threat Radar's AI analysis

Patch
Available – fixed in 0.3.9

Data as of 22 Nov 2026, 10:39 UTC

What to do

Upgrade secmem-proc to 0.3.9.

Affected software

ProductAffectedFixed in
crates.iosecmem-procpkg:cargo/secmem-procOther threatsAffected
  • >=0.0.0-0 <0.3.9
Fixed in
  • 0.3.9

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

AI-suggested

Upgrade to secmem-proc version 0.3.9 or later, where the default hardening setup uses the well-known "owner rights" SID to enforce the DACL correctly. Users with custom DACLs using the win_acl module must update their code to use SidRef::well_known instead of the owner SID from TokenUser::sid to maintain the security enhancement.

Description

The secmem-proc crate for Windows had a security issue in versions before 0.3.9 where the default Discretionary Access Control List (DACL) did not provide the intended protection. Processes running under the same user could reset the DACL, bypassing the intended security enhancement. This was due to using an explicit owner SID instead of the well-known "owner rights" SID, which Windows treats differently. The issue is fixed in version 0.3.9 by using the correct SID. Users with custom DACLs must update their code accordingly.

References

Community reviews

Loading reviews…