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

Path Traversal vulnerability #97

Closed
aegisduck opened this issue Nov 13, 2019 · 4 comments
Closed

Path Traversal vulnerability #97

aegisduck opened this issue Nov 13, 2019 · 4 comments

Comments

@aegisduck
Copy link

Describe the bug

Suggested description of the vulnerability

: A path traversal vulnerability in the web application component of piSignage 2.6 allows a remote attacker authenticated as a low privilege user to download arbitrary files from the Raspberry Pi.

Attack vector(s)

66
 1. Click the Log Download button at the bottom of the 'piSignage' administration page.

67
 2. HTTP Packet is sent when the button is pressed.

68
 3. Change the value of 'file' parameter to ../../../../../../../../../../etc/passwd.

69
 4. You can see that the /etc/passwd file is read.

Affected URL/API(s)

URL: /api/settings/log
Parameter: file

Environment

  • Raspberry Pi Hardware Version: Model 3B+ Revision: 1.3 Ram: 1 GB Sony UK
  • piSignage Version: pisignage_2.6.1.img
@colloqi
Copy link
Owner

colloqi commented Nov 13, 2019

Thanks, will sandbox the content, since it happens after login there is one level of check if you secure the webUI or disable altogether as of now

@aegisduck
Copy link
Author

Thanks, will sandbox the content, since it happens after login there is one level of check if you secure the webUI or disable altogether as of now

Thank you for your answer. Are you saying it's not a vulnerability? Does this not apply to the next patch?

@colloqi
Copy link
Owner

colloqi commented Nov 13, 2019

Yes and no, if the password is known, piShell is more dangerous place :) best way is to either block the webUI in such cases using server settings or change the password. However we will fix this vulnerability (it is) in the next release

@colloqi
Copy link
Owner

colloqi commented Jan 5, 2020

Fixed in 2.6.4

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

2 participants