From 4c06bea79f33949430e5c29a7947df649f4adcb8 Mon Sep 17 00:00:00 2001 From: CVE Team Date: Mon, 12 Jul 2021 23:01:13 +0000 Subject: [PATCH] "-Synchronized-Data." --- 2021/20xxx/CVE-2021-20267.json | 5 ----- 2021/30xxx/CVE-2021-30639.json | 10 ++++++++++ 2021/32xxx/CVE-2021-32747.json | 12 ++++++------ 3 files changed, 16 insertions(+), 11 deletions(-) diff --git a/2021/20xxx/CVE-2021-20267.json b/2021/20xxx/CVE-2021-20267.json index 0c6bdb7b347..4d626643c42 100644 --- a/2021/20xxx/CVE-2021-20267.json +++ b/2021/20xxx/CVE-2021-20267.json @@ -53,11 +53,6 @@ "refsource": "CONFIRM", "name": "https://security.openstack.org/ossa/OSSA-2021-001.html", "url": "https://security.openstack.org/ossa/OSSA-2021-001.html" - }, - { - "refsource": "MLIST", - "name": "[oss-security] 20210712 [OSSA-2021-001] Neutron: Anti-spoofing bypass for Open vSwitch networks (CVE-2021-20267)", - "url": "http://www.openwall.com/lists/oss-security/2021/07/12/2" } ] }, diff --git a/2021/30xxx/CVE-2021-30639.json b/2021/30xxx/CVE-2021-30639.json index 9f0ef00cde3..19bc3d155b6 100644 --- a/2021/30xxx/CVE-2021-30639.json +++ b/2021/30xxx/CVE-2021-30639.json @@ -75,6 +75,16 @@ "refsource": "MISC", "url": "https://lists.apache.org/thread.html/rd84fae1f474597bdf358f5bdc0a5c453c507bd527b83e8be6b5ea3f4%40%3Cannounce.tomcat.apache.org%3E", "name": "https://lists.apache.org/thread.html/rd84fae1f474597bdf358f5bdc0a5c453c507bd527b83e8be6b5ea3f4%40%3Cannounce.tomcat.apache.org%3E" + }, + { + "refsource": "MLIST", + "name": "[tomcat-users] 20210712 RE: [SECURITY] CVE-2021-30639 Apache Tomcat DoS", + "url": "https://lists.apache.org/thread.html/r79a7c019712b39aedf7cf4da9276d80610f04441b2a4f6506cb2daaf@%3Cusers.tomcat.apache.org%3E" + }, + { + "refsource": "MLIST", + "name": "[tomcat-dev] 20210712 RE: [SECURITY] CVE-2021-30639 Apache Tomcat DoS", + "url": "https://lists.apache.org/thread.html/r79a7c019712b39aedf7cf4da9276d80610f04441b2a4f6506cb2daaf@%3Cdev.tomcat.apache.org%3E" } ] }, diff --git a/2021/32xxx/CVE-2021-32747.json b/2021/32xxx/CVE-2021-32747.json index df0939ac635..fa2c41c9c82 100644 --- a/2021/32xxx/CVE-2021-32747.json +++ b/2021/32xxx/CVE-2021-32747.json @@ -35,7 +35,7 @@ "description_data": [ { "lang": "eng", - "value": "Icinga Web 2 is an open source monitoring web interface, framework, and command-line interface. A vulnerability in which custom variables are exposed to unauthorized users exists between versions 2.0.0 and 2.8.2. Custom variables are user-defined keys and values on configuration objects in Icinga 2. These are commonly used to reference secrets in other configurations such as check commands to be able to authenticate with a service being checked.\n\nIcinga Web 2 displays these custom variables to logged in users with access to said hosts or services. In order to protect the secrets from being visible to anyone, it's possible to setup protection rules and blacklists in a user's role. Protection rules result in `***` being shown instead of the original value, the key will remain. Backlists will hide a custom variable entirely from the user. Besides using the UI, custom variables can also be accessed differently by using an undocumented URL parameter. By adding a parameter to the affected routes, Icinga Web 2 will show these columns additionally in the respective list. This parameter is also respected when exporting to JSON or CSV. Protection rules and blacklists however have no effect in this case. Custom variables are shown as-is in the result.\n\nThe issue has been fixed in the 2.9.0, 2.8.3, and 2.7.5 releases. As a workaround, one may set up a restriction to hide hosts and services with the custom variable in question." + "value": "Icinga Web 2 is an open source monitoring web interface, framework, and command-line interface. A vulnerability in which custom variables are exposed to unauthorized users exists between versions 2.0.0 and 2.8.2. Custom variables are user-defined keys and values on configuration objects in Icinga 2. These are commonly used to reference secrets in other configurations such as check commands to be able to authenticate with a service being checked. Icinga Web 2 displays these custom variables to logged in users with access to said hosts or services. In order to protect the secrets from being visible to anyone, it's possible to setup protection rules and blacklists in a user's role. Protection rules result in `***` being shown instead of the original value, the key will remain. Backlists will hide a custom variable entirely from the user. Besides using the UI, custom variables can also be accessed differently by using an undocumented URL parameter. By adding a parameter to the affected routes, Icinga Web 2 will show these columns additionally in the respective list. This parameter is also respected when exporting to JSON or CSV. Protection rules and blacklists however have no effect in this case. Custom variables are shown as-is in the result. The issue has been fixed in the 2.9.0, 2.8.3, and 2.7.5 releases. As a workaround, one may set up a restriction to hide hosts and services with the custom variable in question." } ] }, @@ -69,11 +69,6 @@ }, "references": { "reference_data": [ - { - "name": "https://github.com/Icinga/icingaweb2/security/advisories/GHSA-2xv9-886q-p7xx", - "refsource": "CONFIRM", - "url": "https://github.com/Icinga/icingaweb2/security/advisories/GHSA-2xv9-886q-p7xx" - }, { "name": "https://github.com/Icinga/icingaweb2/releases/tag/v2.7.5", "refsource": "MISC", @@ -88,6 +83,11 @@ "name": "https://github.com/Icinga/icingaweb2/releases/tag/v2.9.0", "refsource": "MISC", "url": "https://github.com/Icinga/icingaweb2/releases/tag/v2.9.0" + }, + { + "name": "https://github.com/Icinga/icingaweb2/security/advisories/GHSA-2xv9-886q-p7xx", + "refsource": "CONFIRM", + "url": "https://github.com/Icinga/icingaweb2/security/advisories/GHSA-2xv9-886q-p7xx" } ] },