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

There is a deserialization vulnerability #32

Open
w0s1np opened this issue Oct 31, 2022 · 0 comments
Open

There is a deserialization vulnerability #32

w0s1np opened this issue Oct 31, 2022 · 0 comments

Comments

@w0s1np
Copy link

w0s1np commented Oct 31, 2022

In http://material-admin/material-manage/src/main/java/cn/enilu/material/admin/config/web/ShiroConfig.java we can find a fixed key and uses this key to encrypt the rememberMe parameter in the cookie. It will cause deserialization vulnerability

I set up a a local environment for attacks.

I found that the source code contains commons-collections-3.2.2.jar and commons-beanutils-1.9.4.jar dependency, which is actually a dependency included in shiro.
Using this dependency, it is possible to generate a deserialized payload and then encrypt the payload using the key obtained by blasting. write this payload after the rememberMe field and attack it. Successful RCE.

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

No branches or pull requests

1 participant