Add CVE-2021-32747 for GHSA-2xv9-886q-p7xx

This commit is contained in:
Shelby J. Cunningham 2021-07-12 18:46:18 -04:00
parent a9d4447ae2
commit 13f5791a25
No known key found for this signature in database
GPG Key ID: 0781D7D998EB82AA

View File

@ -1,18 +1,98 @@
{
"data_type": "CVE",
"data_format": "MITRE",
"data_version": "4.0",
"CVE_data_meta": {
"ASSIGNER": "security-advisories@github.com",
"ID": "CVE-2021-32747",
"ASSIGNER": "cve@mitre.org",
"STATE": "RESERVED"
"STATE": "PUBLIC",
"TITLE": "Custom variable protection and blacklists can be circumvented"
},
"affects": {
"vendor": {
"vendor_data": [
{
"product": {
"product_data": [
{
"product_name": "icingaweb2",
"version": {
"version_data": [
{
"version_value": ">= 2.0.0, <= 2.8.2"
}
]
}
}
]
},
"vendor_name": "Icinga"
}
]
}
},
"data_format": "MITRE",
"data_type": "CVE",
"data_version": "4.0",
"description": {
"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": "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."
}
]
},
"impact": {
"cvss": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.3,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "HIGH",
"integrityImpact": "NONE",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N",
"version": "3.1"
}
},
"problemtype": {
"problemtype_data": [
{
"description": [
{
"lang": "eng",
"value": "CWE-200: Exposure of Sensitive Information to an Unauthorized Actor"
}
]
}
]
},
"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",
"url": "https://github.com/Icinga/icingaweb2/releases/tag/v2.7.5"
},
{
"name": "https://github.com/Icinga/icingaweb2/releases/tag/v2.8.3",
"refsource": "MISC",
"url": "https://github.com/Icinga/icingaweb2/releases/tag/v2.8.3"
},
{
"name": "https://github.com/Icinga/icingaweb2/releases/tag/v2.9.0",
"refsource": "MISC",
"url": "https://github.com/Icinga/icingaweb2/releases/tag/v2.9.0"
}
]
},
"source": {
"advisory": "GHSA-2xv9-886q-p7xx",
"discovery": "UNKNOWN"
}
}