I think there might be a buffer overflow in how you instanciate the structre FILE_RENAME_INFO.

In the file mod.rs in windows directory, you do this :

`fn rename(placeholder: &[u8; 9], handle: HANDLE) -> Result<(), HoudiniError> {
let filename = placeholder.map(|b| b as u16);
let length = size_of::<[u16; 9]>();

let mut file_rename_info: FILE_RENAME_INFO = FILE_RENAME_INFO {
    Anonymous: FILE_RENAME_INFO_0 {
        ReplaceIfExists: BOOLEAN(0),
    },
    RootDirectory: HANDLE::default(),
    FileNameLength: length as u32,
    FileName: [0],
};

unsafe {
    copy(
        filename.as_ptr(),
        file_rename_info.FileName.as_mut_ptr(),
        length,
    )
};`

But here, you are instanciating FILE_RENAME_INFO as any other variables. So I think (tell me if I'm wrong) the memory allocation will only allocate an array of length 1 for the FileName member of the struct whereas you start copying your string at this location. So I think you copy your string here in non allocated memory.

The correct way to instanciate this string is on the heap, where you allocate as much memory as you need for your string + the size of the FILE_RENAME_INFO and reinterpret cast the given memory address as pointer to a FILE_RENAME_INFO struct.

In C, it would look like this :

FILE_RENAME_INFO *file_rename_info = malloc(sizeof(FILE_RENAME_INFO) + n * sizeof(wchar_t));

with n being your string size.

Maybe I'm all wrong about this as I'm not an expert on how Rust allocates memory and everything, but it might be worth looking into it.

Hello!

Does Houdini still work? Tested on Windows 11 and executable is not deleted.

regards