You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "potiuk (via GitHub)" <gi...@apache.org> on 2023/08/24 11:17:04 UTC
[GitHub] [airflow] potiuk opened a new pull request, #33691: Add back link to the ASF blog about severity to the policy
potiuk opened a new pull request, #33691:
URL: https://github.com/apache/airflow/pull/33691
The security policy should be the place where researchers are looking on how to assign severity to their reports. We had the link to the ASF blog post decribing how we assess the severity but it has been moved out in #32496 somewhat accidentally to the information about the security team. It can stay there (as a reference for the security team members/internal, but it would be great to keep it in our Policy targeted for the researchers.
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
<!--
Thank you for contributing! Please make sure that your code changes
are covered with tests. And in case of new features or big changes
remember to adjust the documentation.
Feel free to ping committers for the review!
In case of an existing issue, reference it using one of the following:
closes: #ISSUE
related: #ISSUE
How to write a good git commit message:
http://chris.beams.io/posts/git-commit/
-->
<!-- Please keep an empty line above the dashes. -->
---
**^ Add meaningful description above**
Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#pull-request-guidelines)** for more information.
In case of fundamental code changes, an Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals)) is needed.
In case of a new dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x).
In case of backwards incompatible changes please leave a note in a newsfragment file, named `{pr_number}.significant.rst` or `{issue_number}.significant.rst`, in [newsfragments](https://github.com/apache/airflow/tree/main/newsfragments).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] pankajkoti commented on a diff in pull request #33691: Add back link to the ASF blog about severity to the policy
Posted by "pankajkoti (via GitHub)" <gi...@apache.org>.
pankajkoti commented on code in PR #33691:
URL: https://github.com/apache/airflow/pull/33691#discussion_r1304187427
##########
.github/SECURITY.md:
##########
@@ -54,11 +54,16 @@ movie, HTML, or PDF attachment when you could as easily describe it with plain t
Before reporting vulnerabilities, please make sure to read and understand the
[security model](https://airflow.apache.org/docs/apache-airflow/stable/security/security_model.html) of Airflow, because
some of the potential security vulnerabilities that are valid for projects that are publicly accessible
-from the Internet, are not valid for Airflow. Airflow is not designed to be used by untrusted users, and some
-trusted users are trusted enough to do a variety of operations that could be considered as vulnerabilities
-in other products/circumstances. Therefore, some potential security vulnerabilities do not
-apply to Airflow, or have a different severity than some generic scoring systems (for example `CVSS`)
-calculation suggests.
+from the Internet, are not valid for Airflow.
+
+
+Airflow is not designed to be used by untrusted users, and some trusted users are trusted enough to do a
+variety of operations that could be considered as vulnerabilities in other products/circumstances.
+Therefore, some potential security vulnerabilities do not apply to Airflow, or have a different severity
+than some generic scoring systems (for example `CVSS`) calculation suggests. Severity of the issue is
+determined based on the criteria described in the
+[Severity Rating blog post](https://security.apache.org/blog/severityrating/) by the Apache Software
Review Comment:
```suggestion
[Severity Rating blog post](https://security.apache.org/blog/severityrating/) by the Apache Software
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk merged pull request #33691: Add back link to the ASF blog about severity to the policy
Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk merged PR #33691:
URL: https://github.com/apache/airflow/pull/33691
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org