Report Security Issues for sugarnailart.com
If you’ve found a security vulnerability on sugarnailart.com, we encourage you to message us immediately. We will review all legitimate vulnerability reports and will do our utmost to quickly resolve the matter. Before you report, please review this document, including fundamentals, bounty program, reward guidelines, and what should not be reported.
Fundamentals
If you adhere to the rules below when reporting a security issue to sugarnailart.com, we will not initiate a lawsuit or enforcement investigation against you in response to your report.
We ask that you:
Give us reasonable time to review and fix a problem you report before making public any information about the report or sharing such information with others.
Do not interact with a personal account (which includes modifying or accessing data from the account) if the account owner has not consented to such actions.
Make a good faith effort to avoid privacy violations and disruptions to others, including (but not limited to) destruction of data and interruption or degradation of our services.
Do not exploit a security issue you discover for any reason. (This includes demonstrating additional risk, such as attempted compromise of sensitive company data or trying to find additional issues.)
Do not violate any other applicable laws or regulations.
BOUNTY PROGRAM
We recognize and reward security researchers who help us keep people safe by reporting vulnerabilities in our services. Monetary bounties for such reports are entirely at sugarnailart.com’s discretion, based on risk, impact, and other factors. To potentially qualify for a bounty, you must meet the subsequent requirements:
Adhere to our fundamentals (see above).
Report a security bug: that is, identify a vulnerability in our services or infrastructure which creates a security or privacy risk. (Note that sugarnailart.com ultimately determines the risk of a problem, and many bugs are not security issues.)
Submit your report via our security center. Please do not contact employees directly.
If you inadvertently cause a privacy violation or disruption (such as accessing account data, service configurations, or other confidential information) while investigating a problem, please fully disclose this in your report.
We investigate and respond to all valid reports. Due to the volume of reports we receive, though, we prioritize evaluations based on risk and other factors, and it may take some time before you receive a reply.
We reserve the right to publish reports.
REWARDS
Our rewards are based on the impact of a vulnerability. We will update the program over time based on feedback, so please give us feedback on any area of the program you think we can improve on.
Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the problem, the issue will not be eligible for bounty.
When duplicates occur, we award the first report that we can completely reproduce.
Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.
We determine bounty reward based on a variety of factors, including (but not limited to) impact, ease of exploitation, and quality of the report. We specifically note the bounty rewards, which are listed below.
Amounts below are the maximum we will pay per level. We aim to be fair; all reward amounts are at our discretion.
Critical severity Vulnerabilities ($200): Vulnerabilities that cause a privilege escalation (unprivileged to admin), allow remote code execution, financial theft, etc. (E.g., Remote Code/Shell Execution, Vertical Authentication bypass, SQL Injection that leaks targeted data, Full access to accounts)
High severity Vulnerabilities ($100): Vulnerabilities that affect the security of the platform, including the processes it supports. (E.g., Lateral authentication bypass, Disclosure of significant company information, Stored XSS for another user, Local file inclusion, Insecure handling of authentication cookies)
Medium severity Vulnerabilities ($50): Vulnerabilities that affect multiple users and require little or no user interaction to trigger. (E.g., Common logic design flaws and business process defects, Insecure direct object references)
Low severity Vulnerabilities: Issues that affect singular users and require interaction or significant prerequisites (MITM) to trigger. (E.g., Open redirect, Reflected XSS, Low sensitivity Information leaks)
Customer Contact 24/7
Shop Name: SugarNail
Address: 1500 N GRANT ST STE N DENVER CO 80203 US
Email: support@sugarnaiart.com
Phone: +1 (209) 266-7591