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

Does not seem to work #6

Open
CaledoniaProject opened this issue Oct 9, 2017 · 3 comments
Open

Does not seem to work #6

CaledoniaProject opened this issue Oct 9, 2017 · 3 comments
Labels

Comments

@CaledoniaProject
Copy link

I just did a simple test with JDK 1.8

Since all java applications depends on the jli.dll,

screen 2017-10-09 at 20 01 01

rattler should easily find this DLL hijack point, but it didn't ...

screen 2017-10-09 at 20 02 35

Am I using this tool incorrectly?

@brompwnie
Copy link
Contributor

hi there,
It appears that Rattler did not identify any DLL's to enumerate(first green line of text) so that's why it was not able to detect the vulnerable DLL's. This could be due to multiple reasons, what permissions did you run Rattler with and secondly, did you use the 32 or 64 bit version?

@CaledoniaProject
Copy link
Author

Hmm, I'm on Windows 7 x86, using 32 bit JDK with 32 bit rattler (downloaded from https://github.com/sensepost/rattler/releases)

Running CMD as elevated administrator

@brompwnie brompwnie added the bug label Oct 11, 2017
@brompwnie
Copy link
Contributor

Thanks for the info, ill try replicate the issue. In the meantime I',m going to mark this as a bug

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

No branches or pull requests

2 participants