summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAndrew Kampjes <a.kampjes@gmail.com>2015-01-13 07:38:52 +1300
committerBen Pfaff <blp@nicira.com>2015-01-13 13:45:56 -0800
commitb13bfc3c11d7c20d6a7cc85104e015adc7f78892 (patch)
tree3dd59797e96f024295becc2c82faa2243a73e0d4
parenta445a8d8811a565c5a86f326744b3489921c844f (diff)
downloadopenvswitch-b13bfc3c11d7c20d6a7cc85104e015adc7f78892.tar.gz
SECURITY.md: Update.
Add bit about reporting vulns with GPG. Add generalised rules for vulnerabilties. Signed-off-by: Andrew Kampjes <a.kampjes@gmail.com> [blp@nicira.com edited and removed text about not using public lists] Signed-off-by: Ben Pfaff <blp@nicira.com>
-rw-r--r--AUTHORS1
-rw-r--r--SECURITY.md31
2 files changed, 22 insertions, 10 deletions
diff --git a/AUTHORS b/AUTHORS
index 7d343532a..74e50a359 100644
--- a/AUTHORS
+++ b/AUTHORS
@@ -10,6 +10,7 @@ Alfredo Finelli alf@computationes.de
Alin Serdean aserdean@cloudbasesolutions.com
Amit Bose bose@noironetworks.com
Andrew Evans aevans@nicira.com
+Andrew Kampjes a.kampjes@gmail.com
Andrew Lambeth wal@nicira.com
Andy Hill hillad@gmail.com
Andy Southgate andy.southgate@citrix.com
diff --git a/SECURITY.md b/SECURITY.md
index d558d44ff..08a6ed8b4 100644
--- a/SECURITY.md
+++ b/SECURITY.md
@@ -23,25 +23,33 @@ What is a vulnerability?
------------------------
All vulnerabilities are bugs, but not every bug is a vulnerability.
+Vulnerabilities compromise one or more of:
+
+ * Confidentiality (personal or corporate confidential data).
+ * Integrity (trustworthiness and correctness).
+ * Availability (uptime and service).
+
Here are some examples of vulnerabilities to which one would expect to
apply this process:
- * A crafted packet that causes a kernel or userspace crash.
+ * A crafted packet that causes a kernel or userspace crash
+ (Availability).
* A flow translation bug that misforwards traffic in a way likely
- to hop over security boundaries.
+ to hop over security boundaries (Integrity).
* An OpenFlow protocol bug that allows a controller to read
- arbitrary files from the file system.
+ arbitrary files from the file system (Confidentiality).
* Misuse of the OpenSSL library that allows bypassing certificate
- checks.
+ checks (Integrity).
* A bug (memory corruption, overflow, ...) that allows one to
modify the behaviour of OVS through external configuration
- interfaces such as OVSDB.
+ interfaces such as OVSDB (Integrity).
- * Privileged information is exposed to unprivileged users.
+ * Privileged information is exposed to unprivileged users
+ (Confidentiality).
If in doubt, please do use the vulnerability management process. At
worst, the response will be to report the bug through the usual
@@ -59,6 +67,9 @@ the report has been received.
Please consider reporting the information mentioned in
REPORTING-BUGS.md, where relevant.
+Reporters may ask for a GPG key while initiating contact with the
+security team to deliver more sensitive reports.
+
The Linux kernel has its own vulnerability management process:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/SecurityBugs
Handling of vulnerabilities that affect both the Open vSwitch tree and
@@ -132,11 +143,11 @@ vSwitch user who is interested and can be considered trustworthy
enough could be included. To become a downstream stakeholder, email
the ovs-security mailing list.
-If the vulnerability is public, skip this step.
+If the vulnerability is already public, skip this step.
-Step 5: Full Disclosure
------------------------
+Step 5: Public Disclosure
+-------------------------
When the embargo expires, push the (reviewed) patches to appropriate
branches, post the patches to the ovs-dev mailing list (noting that
@@ -151,7 +162,7 @@ The security advisory should be GPG-signed by a security team member
with a key that is in a public web of trust.
-Contact
+Contact
=======
Report security vulnerabilities to the ovs-security mailing list: