submit bug report:https://nem.io
Rewards
The following is high level description of how some examples of vulnerability/error types might map to the various scopes:
Critical
key generation and persistence
key usage and signing of transactions
protocol level issues that could corrupt or break the state of the blockchain given a valid signed transaction
High
Holes or compromises to software components themselves that would allow attacker to gain access to the computer/host that the software is running on
Gain access to secure key/password/etc information from outside the application or service from the host machine
Medium
Errant input issues that include corrupt/wrong data but able to send a valid transaction. Something like a invalid input that would transfer 10x the funds while user thinks they are transfering 1x
Low
These would be mostly user experience level issues that render a end user to be stuck or applications to be useless. Typically this could be something like a user submitting to a form that breaks and user gets locked into a certain workflow until killing/quitting an application
Last updated on March 25, 2020.
View changes
Policy
The Symbol project looks forward to working with the security community to find vulnerabilities in order to further our projects technology development and keep our community of active users safe.
Response Targets
We will make a best effort to meet the following SLAs for hackers participating in our program:
Type of Response SLA in business days
First Response 2 days
Time to Triage 5 days
Time to Bounty 10 days
Time to Resolution depends on severity and complexity
We’ll keep you informed about our progress throughout the process and contact should any engineers need more details or have issues with reproduction of disclosures.
Disclosure Policy
As this is a private program, please do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.
Program Rules
Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue will not be eligible for a reward.
Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).
Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.
Social engineering (e.g. phishing, vishing, smishing) is prohibited.
Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder.
Test Plan
Currently we are rolling out the scoped items that are stand alone libraries, their perspective usage and testing are self contained in their github repositories.
As we open up the larger range of scoped items we will provide any specific test plans.
Out of scope vulnerabilities
When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:
Clickjacking on pages with no sensitive actions
Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
Attacks requiring MITM or physical access to a user's device.
Previously known vulnerable libraries without a working Proof of Concept.
Comma Separated Values (CSV) injection without demonstrating a vulnerability.
Missing best practices in SSL/TLS configuration.
Any activity that could lead to the disruption of our service (DoS).
Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
Rate limiting or bruteforce issues on non-authentication endpoints
Missing best practices in Content Security Policy.
Missing HttpOnly or Secure flags on cookies
Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]
Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).
Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis.
Tabnabbing
Open redirect - unless an additional security impact can be demonstrated
Issues that require unlikely user interaction
Safe Harbor
Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.
Thank you for helping keep our project and community of users safe!
