Updated Bug Bounty Example #8338
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fredrik0x
requested review from
corwintines,
jmcook1186,
minimalsm,
pettinarip,
samajammin and
wackerow
as code owners
minimalsm
approved these changes
Oct 24, 2022
Contributor
minimalsm
left a comment
minimalsm
left a comment
There was a problem hiding this comment.
Thanks @fredriksvantes
|
Congrats, your important contribution to this open-source project has earned you a GitPOAP! GitPOAP: 2022 Ethereum.org Contributor: Head to gitpoap.io & connect your GitHub account to mint! Learn more about GitPOAPs here. |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
As stated in the bug bounty program, the EF Bug Bounty Program bases its impact on the effect a vulnerability has on the Network: "The severity is calculated according to the OWASP risk rating model based on Impact on the Ethereum Network and Likelihood. View OWASP method"
Below the above line, there is an example of what could be described as a "High" vulnerability which states "There is a consensus bug between two clients, but it is difficult or impractical for the attacker to trigger the event." - This could indeed be accurate from a network perspective - if the issue was in a client being used by a large part of the network (say 45%), while if the consensus bug was in a client being used by 0.1% of the network it would most likely not have as big of an impact on the network itself.
This PR tries to make the example more clear.