Report Security Issues

If you’ve found a security vulnerability on annanhardware.com, we encourage you to message us immediately. We’ll 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 shouldn’t be reported.

Fundamentals

If you follow the principles below when reporting a security issue to annanhardware.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 repair an issue you report before making public any information about the report or sharing such information with others.

You do not interact with a private account, including modifying or accessing data from the account, if the account owner has not consented to such actions.

You make an honest 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.

You 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.

You do not violate any 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 Annan Hardware’s discretion, based on risk, impact, and other factors. To potentially qualify for a bounty, you must first meet the following requirements:

Adhere to our fundamentals listed above.

Report a security bug, meaning identify a vulnerability in our services or infrastructure that creates a security or privacy risk. Please note that Annan Hardware ultimately determines the severity of an issue, and that many bugs are not security issues.

Submit your report through our security contact process. 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 an issue, inform us and disclose this in your report.

We investigate and respond to all valid reports. Because of the number of reports we may receive, 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 share any suggestions on how we can improve it.

Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, it will not be eligible for a bounty.

When duplicates occur, we award the first report that we can fully reproduce.

Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.

We determine bounty rewards based on a selection of factors, including but not limited to impact, ease of exploitation, and quality of the report. We specifically note the bounty reward levels below.

Amounts below are the maximum we will pay per level. All reward amounts are at our discretion.

Critical Severity Vulnerabilities (£200)

Vulnerabilities that cause privilege escalation on the platform from unprivileged to admin, allow remote code execution, financial theft, or similar critical compromise.

Examples:

Remote Code Execution

Remote Shell or Command Execution

Vertical Authentication Bypass

SQL Injection that leaks targeted data

Full account access

High Severity Vulnerabilities (£100)

Vulnerabilities that affect the security of the platform, including the processes it supports.

Examples:

Lateral authentication bypass

Disclosure of important internal company information

Stored XSS affecting 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.

Examples:

Common logic design flaws

Insecure Direct Object References

Low Severity Vulnerabilities

Issues that affect single users and require interaction or significant prerequisites to trigger.

Examples:

Open redirect

Reflected XSS

Low-sensitivity information leaks

If you would like to report a security issue, please contact us at:

Annan Hardware
Downie's Wynd, Annan DG12 6DW, United Kingdom

Email: support@annanhardware.com
Website: https://annanhardware.com/

Telephone: +44 14 60712 132