mirror of
https://github.com/HaschekSolutions/pictshare.git
synced 2026-04-25 23:15:51 +03:00
[GH-ISSUE #133] Possible XSS vulnerability #106
Labels
No labels
Feature request
Feature request
bug
cant reproduce
enhancement
help wanted
pull-request
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/pictshare#106
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @enferas on GitHub (Nov 11, 2021).
Original GitHub issue: https://github.com/HaschekSolutions/pictshare/issues/133
Hello,
I would like to report for XSS vulnerability.
in api/info.php
function getInfoAboutHash
line 15
exit function will terminate the script and print the message which has $_REQUEST['hash'].
Then there is XSS vulnerability.
@geek-at commented on GitHub (Nov 11, 2021):
Cannot confirm because the script will return
{"status":"err","reason":"File not found"}if the hash is invalid see here because of line 17But I did find another small bug that if you leave the hash variable out, it was telling you the size of the data folder
Thanks!
@enferas commented on GitHub (Dec 2, 2021):
Thank you for the confirmation.
CVE-2021-43683 is assigned to this discovery.
pictshare v1.5 is affected by is affected by a Cross Site Scripting (XSS) vulnerability in api/info.php. The exit function will terminate the script and print the message which has $_REQUEST['hash'].
@geek-at commented on GitHub (Dec 2, 2021):
Do you have a PoC because I can't reproduce as it will just say "file not found" if an invalid hash is supplied
@enferas commented on GitHub (Dec 9, 2021):
Thank you for your response.
Specific values can pass the json_encode.
This example give an alert with me.
@geek-at commented on GitHub (Dec 10, 2021):
You do realize that the bug was fixed 3 years before you opened the CVE, right? Pictshare 1.5 was released in 2018
@vitalijalbu commented on GitHub (Dec 10, 2021):
@geek-at would be better if you add releases on this repo, so people can easily ask questions and open issues.
@geek-at commented on GitHub (Dec 10, 2021):
I'm open to pull requests if you want to automate it on every push. At the moment the "releases" are basically what's on docker hub.
Rolling updates I find more suitable for a project of this scope because it's easier to manage and faster to update with a git pull if you don't want to use the docker image