Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix persistence module to use correct Windows path #4903

Merged
merged 1 commit into from Mar 12, 2015
Merged

Fix persistence module to use correct Windows path #4903

merged 1 commit into from Mar 12, 2015

Conversation

Jervelund
Copy link
Contributor

This fixes a bug in the write_script_to_target function, which alters the path that is returned and used for startup.
Currently an escaped path "C://Users//..." is being used instead of using windows standards "C:\Users...".

Issue introduced by #2395

… the write_script_to_target function, which screws up the path that is used for startup. Currently an escaped path "C://Users//..." is being used instead of using windows standards "C:\Users\...".
@todb-r7 todb-r7 changed the title Fixes bug in persistence module Fix persistence module to use correct Windows path Mar 10, 2015
@hdm
Copy link
Contributor

hdm commented Mar 12, 2015

Hello @Jervelund. I am not sure how this patch fixes the problem. The cleanup script needs to use unix-style paths to work with meterpreter, this change doesn't seem to modify what paths end up in the cleanup script (these would still be 'C://Users' and should probably be 'C:/Users' instead). Can you double check this?

@Jervelund
Copy link
Contributor Author

I haven't checked that the cleanup script is working, only verified that the path reference in HKLM...\run is now correct.

If I understand correctly, this commit only changes the return value of write_script_to_target, which is used for registry startup - the cleanup script should still be the same.

@hdm
Copy link
Contributor

hdm commented Mar 12, 2015

I understand now, thanks!

@hdm hdm merged commit c6cb1e8 into rapid7:master Mar 12, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants