Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add rules for known vulnerabilites #3

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

svenseeberg
Copy link
Member

No description provided.

@svenseeberg svenseeberg force-pushed the feature/known-vulnerabilities branch from fb56b48 to 0f111d9 Compare September 26, 2023 07:39
@@ -34,6 +37,8 @@ it reports one of the following problems:
- Publicly accessible version strings of used software.
- Security vulnerablities that can only be used within the scope of the
used account.
- The vulnerability exists in a third party software and is already
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That would exclude about everything. What about something along the lines of:

  • The vulnerability is known and has a CVSS score less than 7
  • Deviations from best practices or common configuration that do not have a direct security impact


For used open source software, we recommend to file bug reports and/or
pull requests against the upstream repositories. This includes hardening
instructions in the installation documentation.

If you are reporting a known vulnerability, please include a reference
to the original vulnerability report.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

... and/or a CVE number.

Please stick to the methods defined out in the Common Vulnerability Scoring System (CVSS) for defining the criticality of a vulnerability.


For used open source software, we recommend to file bug reports and/or
pull requests against the upstream repositories. This includes hardening
instructions in the installation documentation.

If you are reporting a known vulnerability, please include a reference
to the original vulnerability report.

5. Bug Bounties / Vulnerability Rewards

The amount of the reward payed depends on the severity of the found
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Only responsible disclosures and reports adhering to this policy are eligible for a reward.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants