React on Chain (formerly BOS Web Engine) offers component-level sandboxing to minimize the risk of using third-party components in your frontend. Developers can freely compose components they find in the ecosystem into a new interface without the burden of auditing each component’s source code for malicious behavior.
This bounty covers vulnerabilities that violate the sandboxing mechanisms of the engine. The primary suspected attack vector is publishing of components that seem useful and are therefore chosen to be embedded by other components, but contain malicious behavior.
Links
Sandbox: [http://roc-sandbox.near.dev/]
Gateway: [http://roc.near.dev/]
Docs: [http://roc-docs.near.dev/]
In Scope
| Target | Type | Reward |
|---|---|---|
http://roc-sandbox.near.dev/ |
Web3 | Bounty |
In-Scope Vulnerabilities
The list is not limited to the following submissions but it gives an overview of what issues we care about:
Cross-component
- Sandboxed components can affect the rendering of parents or siblings by modifying their styles or altering behavior
- Does not apply to reasonable expectations of scoped CSS, or clickjacking by positioning elements over parent
- Does not apply to affecting Children prop passed by parent
- Does not apply to parents affecting rendering of any downtree components
- Component can impersonate render requests for other containers
Outer Window Application
- Component can interact with global variables, browser APIs, or browser storage of root window
- Component can execute arbitrary JS in the root window frame
- Component can bypass DOM sanitization performed by engine
Out-of-Scope Vulnerabilities
- Modifying content passed down from parent i.e. via Children prop
- Attacks which operate within the confines of CSS modules
- e.g. simple clickjacking by positioning an element over an ancestor element
- Components affecting rendering of any downtree component. Isolation is only upwards and lateral
- Affecting another component within the same trust boundary
- Accessing information about other containers
- Reading messages from other containers
- Denail of service attacks
- JavaScript code execution via element attributes
- Make every effort not to damage or restrict the availability of products, services, or infrastructure
- Avoid compromising any personal data, interruption, or degradation of any service
- Don’t access or modify other user data, localize all tests to your accounts
- Perform testing only within the scope
- Don’t exploit any DoS/DDoS vulnerabilities, social engineering attacks, or spam
- In case you find chain vulnerabilities we’ll pay only for vulnerability with the highest severity.
- Don’t break any law and stay in the defined scope
- Any details of found vulnerabilities must not be communicated to anyone who is not a HackenProof Team or an authorized employee of this Company without appropriate permission
- Please note: Near company is entitled to make the payment in their native NEAR token
- In case that your finding is valid you might be asked for extra KYC verification to proceed with payments
- Perform testing on a private testnet wherever possible
For more information, check: https://docs.near.org/
- Do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization
- No vulnerability disclosure, including partial is allowed for the moment.
- Please do NOT publish/discuss bugs
We are happy to thank everyone who submits valid reports which help us improve the security. However, only those that meet the following eligibility requirements may receive a monetary reward:
- You must be the first reporter of a vulnerability.
- The vulnerability must be a qualifying vulnerability
- Any vulnerability found must be reported no later than 24 hours after discovery and exclusively through hackenproof.com
- You must send a clear textual description of the report along with steps to reproduce the issue, include attachments such as screenshots or proof of concept code as necessary.
- ONLY USE YOUR HackenProof ADDRESS (in case of violation, no bounty can be awarded)
- Provide detailed but to-the point reproduction steps
- Employees, spouses, partners, or families of employees, and former employees of Pagoda, Near, and the Near Foundation, and any subsidiaries, are not eligible to participate in the Bug Bounty program.