Pylon Eco Token

<p>Today, we would like to discuss the bug bounty program that was implemented by the PETN executive team. To those, who do not know, the bug bounty program is a process in which a company engages third-party cybersecurity specialists (in the industry we call them “white hat hackers” or “research workers”) to test their software for vulnerabilities for monetary rewards. For each vulnerability (bug) found, the developer receives a reward (bounty).</p>
<p>Pylon Eco Token project that is administered by the responsible and conscientious people managed to elaborate our own bug bounty program. We do offer financial rewards to those individuals and teams who will discover vulnerabilities on the PETN website. The Pylon Eco Token executive team publicly announced the scope of work, the level of compensation for vulnerabilities, and anyone can register and take part in the bug bounty program. But, it is important to note that the Pylon Eco Token management council will reward people for locating certain bugs, not all vulnerable issues are subject to a reward.</p>
<h2 id="header-0"></h2>
<h2 id="header-1">We do remunerate IT, specialists, for identifying the following problems in our system:</h2>
<ul>
 <li>Cross-Site Request Forgery (CSRF)</li>
 <li>Cross-Site Scripting (XSS)</li>
 <li>Code Executions</li>
 <li>SQL injections</li>
 <li>Server-Side Request Forgery (SSRF)</li>
 <li>Privilege Escalations</li>
 <li>Authentication Bypasses</li>
 <li>File inclusions (Local &amp; Remote)</li>
 <li>Protection Mechanism bypasses (CSRF bypass, etc.)</li>
 <li>Leakage of sensitive data</li>
 <li>Directory Traversal</li>
 <li>Payment manipulation</li>
 <li>Administration portals without an authentication mechanism</li>
</ul>
<h2 id="header-2"></h2>
<p><strong>Please, also note that reporting of the following vulnerabilities will not be recompensed:</strong></p>
<ul>
 <li>Lack of rate-limiting mechanisms</li>
 <li>Captcha related concerns</li>
 <li>Open redirects without a severe impact</li>
 <li>Application stack traces (path disclosures, etc.)</li>
 <li>Self-type Cross-Site Scripting / Self-XSS</li>
 <li>Vulnerabilities that require Man in the Middle (MiTM) attacks</li>
 <li>Denial of Service attacks</li>
 <li>CSRF issues on actions with minimal impact</li>
 <li>Cache Poisoning</li>
 <li>Clickjacking</li>
 <li>Missing SPF records</li>
 <li>Brute force attacks</li>
 <li>Security practices (banner revealing a software version, missing security headers, etc.)</li>
 <li>Vulnerabilities on sites hosted by third parties unless they lead to a vulnerability on the main website.</li>
 <li>Vulnerabilities are contingent on physical attack, social engineering, spamming, DDOS attack, etc.</li>
 <li>Vulnerabilities affecting outdated or unpatched browsers / Operating Systems.</li>
 <li>Bugs that have not been responsibly investigated and reported.</li>
 <li>Bugs in products or websites related to acquisition for a period of 180 days following any public announcement.</li>
 <li>Bugs are already known to us, or already reported by someone else (reward goes to the first reporter).</li>
 <li>Issues that aren’t reproducible.</li>
 <li>Issues that we can’t reasonably be expected to do anything about.</li>
 <li>Before participating in our bug bounty program, please see below our rules and procedures.</li>
 <li>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.</li>
 <li>Submit one vulnerability per the report, unless you need to chain vulnerabilities to provide impact.</li>
 <li>When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).</li>
 <li>Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.</li>
 <li>Social engineering (e.g. phishing, vishing) is prohibited.</li>
 <li>Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service.</li>
</ul>
<p>Please, also take into consideration that when you decide to report about the vulnerabilities that were discovered by you or your team, it should include a detailed, step-by-step proof of concept to enable us to reproduce and evaluate the problem.</p>
<p>You could send your bug report or any inquiries regarding the Pylon Eco Token (PETN) bug bounty program to this email address: bug@pylontoken.com</p>
<p>More detailed information about our bug bounty program you can find on our website:</p>
<h2 id="header-3"><a href="https://www.pylontoken.com/bug-bounty" rel="noopener noreferrer nofollow">www.pylontoken.com</a></h2>

Pylon Eco Token (PETN) bug bounty program

Table of Contents

PylonEcosystem

Other articles published on Jul 19, 2022

AUCTION FEATURE IS NOW AVAILABLE

WEEKLY PVP SUMMARY

What is Binance Smart Chain (BSC)?

Everything you need to know about 8.Finance

$MOWA & NFT OF MONIWAR ARE OFFICIALLY AVAILABLE IN TOKEN POCKET

How does the 8.Finance tokenomics work?

Join our free newsletter for daily crypto updates!