From 64ef528fe2a87503575f6903209d0c543e9e3c2d Mon Sep 17 00:00:00 2001
From: CVE Team <cve-request@mitre.org>
Date: Wed, 10 Apr 2019 14:00:41 +0000
Subject: [PATCH] "-Synchronized-Data."

---
 2018/20xxx/CVE-2018-20321.json | 53 ++++++++++++++++++++++++++++++++--
 1 file changed, 51 insertions(+), 2 deletions(-)

diff --git a/2018/20xxx/CVE-2018-20321.json b/2018/20xxx/CVE-2018-20321.json
index b9dc6c04f86..c4be867710b 100644
--- a/2018/20xxx/CVE-2018-20321.json
+++ b/2018/20xxx/CVE-2018-20321.json
@@ -2,7 +2,30 @@
     "CVE_data_meta": {
         "ASSIGNER": "cve@mitre.org",
         "ID": "CVE-2018-20321",
-        "STATE": "RESERVED"
+        "STATE": "PUBLIC"
+    },
+    "affects": {
+        "vendor": {
+            "vendor_data": [
+                {
+                    "product": {
+                        "product_data": [
+                            {
+                                "product_name": "n/a",
+                                "version": {
+                                    "version_data": [
+                                        {
+                                            "version_value": "n/a"
+                                        }
+                                    ]
+                                }
+                            }
+                        ]
+                    },
+                    "vendor_name": "n/a"
+                }
+            ]
+        }
     },
     "data_format": "MITRE",
     "data_type": "CVE",
@@ -11,7 +34,33 @@
         "description_data": [
             {
                 "lang": "eng",
-                "value": "** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided."
+                "value": "An issue was discovered in Rancher 2 through 2.1.5. Any project member with access to the default namespace can mount the netes-default service account in a pod, and then use that pod to execute administrative privileged commands against the k8s cluster. This could be mitigated by isolating the default namespace in a separate project, where only cluster admins can be given permissions to access. As of 2018-12-20, this bug affected ALL clusters created or imported by Rancher."
+            }
+        ]
+    },
+    "problemtype": {
+        "problemtype_data": [
+            {
+                "description": [
+                    {
+                        "lang": "eng",
+                        "value": "n/a"
+                    }
+                ]
+            }
+        ]
+    },
+    "references": {
+        "reference_data": [
+            {
+                "refsource": "CONFIRM",
+                "name": "https://rancher.com/blog/2019/2019-01-29-explaining-security-vulnerabilities-addressed-in-rancher-v2-1-6-and-v2-0-11/",
+                "url": "https://rancher.com/blog/2019/2019-01-29-explaining-security-vulnerabilities-addressed-in-rancher-v2-1-6-and-v2-0-11/"
+            },
+            {
+                "refsource": "CONFIRM",
+                "name": "https://forums.rancher.com/c/announcements",
+                "url": "https://forums.rancher.com/c/announcements"
             }
         ]
     }