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

Exploitation of Windows Services vulnerabilities #28

Closed
wants to merge 3 commits into from

Conversation

emanuelb
Copy link

@emanuelb emanuelb commented Nov 1, 2015

Implementation of detection & exploitation of insecure registry permissions that associated with a service.
more information can be found at the following paper in section 2.2:

https://labs.mwrinfosecurity.com/system/assets/760/original/Windows_Services_-_All_roads_lead_to_SYSTEM.pdf

emanuelb added 3 commits November 1, 2015 06:28
…Permissions

Implementation of detection & exploitation of insecure registry
permissions that associated with a service.
more information can be found at the following paper in section 2.2:

https://labs.mwrinfosecurity.com/system/assets/760/original/Windows_Services_-_All_roads_lead_to_SYSTEM.pdf
@emanuelb emanuelb changed the title Exploitation of Windows Services vulnerabilities - Insecure Registry Permissions Exploitation of Windows Services vulnerabilities Nov 16, 2015
@Lexus89
Copy link

Lexus89 commented Oct 15, 2018

Bump - Is this ever going to be merged?

@samratashok
Copy link
Owner

I am not sure. Never ended up testing this.

@Lexus89
Copy link

Lexus89 commented Oct 15, 2018

Shame, such priv-esc scripts could be a great addition to the toolkit

@samratashok
Copy link
Owner

Feel free to test the code and then I can merge it.

@Lexus89
Copy link

Lexus89 commented Oct 15, 2018

I've taken a quick look but seems it could use an upgrade before merge to maintain code quality of nishang:

  • hardcoded path (D:..)
  • use of third party tool (accesschk.exe)
  • no additional parameters (e.g. output is really big no filter to display vuln only)

@samratashok
Copy link
Owner

Use of accesschk.exe is a bummer :/
Don't remember at all that could be the reason why I never merged it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants