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.

Sign up for GitHub

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

Jump to bottom

Privilege escalation using sourcefilename #46

Closed
myyxl opened this issue Jan 30, 2021 · 1 comment · Fixed by #47
Closed

Privilege escalation using sourcefilename #46

myyxl opened this issue Jan 30, 2021 · 1 comment · Fixed by #47

Comments

@myyxl
Copy link
Contributor

myyxl commented Jan 30, 2021

Hi Richard,
I have found another privilege escalation but this time using the sourcefilename. When adding "../../" before the actual file name you can store the file in another directory. If you store the file into the web directory you can execute php code by doing a request to the website. After this you can patch runguard and gain root.
Here is the affected line in the source code: Link

Sincerely,
Marlon
trampgeek added a commit that referenced this issue Jan 30, 2021
@trampgeek
Prevent privilege escalation attacks via sourcefilename [issue #46](#46…
694da50 
…). Thanks Marlon.
@trampgeek
Copy link
Owner

Thanks again Marlon. Hopefully fixed now (version 1.6.5).

@myyxl myyxl mentioned this issue Jan 31, 2021
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fixed check if sourcefilename is valid
2 participants
@trampgeek @myyxl