You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Require further research in terms of type of payload can be used for vuln verification, should achieve detection effectiveness while minimizing state changing actions on the target system.
Please read the rules of engagement first at #409.
The text was updated successfully, but these errors were encountered:
We are not completely sure on whether we would like to continue with that product or CVE. To help us make a decision, would you be willing to contribute to fingerprints for Craft CMS? If so, please open a new issue and I will be sure to accept it right away.
Thank you, ~tooryx
#406
I sent PR on March 22. Didn't recieve any updates until September. I don't have currently environment to test this PR.
@OccamsXor Thank you for updating the fingerprint. I have updated the status for #511. You can start working on this issue and please complete the following tasks:
I analyzed the details of this CVE. It seems that the RCE attack scenario assumes the attacker can create a user with a specific username like /etc/cron.d. However, the terminal access to the server is required to be able to create any user in chuanhuchatgpt. Therefore, the arbitrary file upload bug cannot be leveraged into RCE in a real world scenario.
This CVE also contains 2 other bugs which won't be interesting from Tsunami Scanner's perspective.
Reference: https://sightline.protectai.com/vulnerabilities/2cbac1ac-2561-4f8e-8854-7022973f7422/assess
Require further research in terms of type of payload can be used for vuln verification, should achieve detection effectiveness while minimizing state changing actions on the target system.
Please read the rules of engagement first at #409.
The text was updated successfully, but these errors were encountered: