mirror of
https://github.com/netbirdio/advisory-database.git
synced 2026-05-22 18:04:22 -07:00
Publish Advisories
GHSA-6362-gv4m-53ww GHSA-j9hf-98c3-wrm8 GHSA-pxv8-qhrh-jc7v GHSA-2qmw-pvf7-4mw6 GHSA-5248-h45p-9pgw GHSA-8mm6-wmpp-mmm3 GHSA-3wfj-3x8q-hrpg
This commit is contained in:
advisory-database[bot]
@@ -1,7 +1,7 @@
|
||||
{
|
||||
"schema_version": "1.4.0",
|
||||
"id": "GHSA-6362-gv4m-53ww",
|
||||
"modified": "2024-07-08T21:06:23Z",
|
||||
"modified": "2024-09-06T21:39:28Z",
|
||||
"published": "2024-04-30T00:30:34Z",
|
||||
"aliases": [
|
||||
"CVE-2024-33522"
|
||||
@@ -75,6 +75,10 @@
|
||||
"type": "WEB",
|
||||
"url": "https://github.com/projectcalico/calico/pull/8517"
|
||||
},
|
||||
{
|
||||
"type": "ADVISORY",
|
||||
"url": "https://github.com/advisories/GHSA-6362-gv4m-53ww"
|
||||
},
|
||||
{
|
||||
"type": "PACKAGE",
|
||||
"url": "https://github.com/projectcalico/calico"
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
{
|
||||
"schema_version": "1.4.0",
|
||||
"id": "GHSA-j9hf-98c3-wrm8",
|
||||
"modified": "2024-07-17T06:30:47Z",
|
||||
"modified": "2024-09-06T21:39:25Z",
|
||||
"published": "2024-06-04T18:12:31Z",
|
||||
"aliases": [
|
||||
"CVE-2024-5154"
|
||||
@@ -25,16 +25,13 @@
|
||||
"type": "ECOSYSTEM",
|
||||
"events": [
|
||||
{
|
||||
"introduced": "1.30.0"
|
||||
"introduced": "1.28.6"
|
||||
},
|
||||
{
|
||||
"fixed": "1.30.1"
|
||||
"fixed": "1.28.7"
|
||||
}
|
||||
]
|
||||
}
|
||||
],
|
||||
"versions": [
|
||||
"1.30.0"
|
||||
]
|
||||
},
|
||||
{
|
||||
@@ -54,9 +51,6 @@
|
||||
}
|
||||
]
|
||||
}
|
||||
],
|
||||
"versions": [
|
||||
"1.29.4"
|
||||
]
|
||||
},
|
||||
{
|
||||
@@ -69,16 +63,13 @@
|
||||
"type": "ECOSYSTEM",
|
||||
"events": [
|
||||
{
|
||||
"introduced": "1.28.6"
|
||||
"introduced": "1.30.0"
|
||||
},
|
||||
{
|
||||
"fixed": "1.28.7"
|
||||
"fixed": "1.30.1"
|
||||
}
|
||||
]
|
||||
}
|
||||
],
|
||||
"versions": [
|
||||
"1.28.6"
|
||||
]
|
||||
}
|
||||
],
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
{
|
||||
"schema_version": "1.4.0",
|
||||
"id": "GHSA-pxv8-qhrh-jc7v",
|
||||
"modified": "2024-08-12T16:03:48Z",
|
||||
"modified": "2024-09-06T21:40:06Z",
|
||||
"published": "2024-06-06T18:21:05Z",
|
||||
"aliases": [
|
||||
"CVE-2024-32873"
|
||||
|
||||
@@ -1,13 +1,13 @@
|
||||
{
|
||||
"schema_version": "1.4.0",
|
||||
"id": "GHSA-2qmw-pvf7-4mw6",
|
||||
"modified": "2024-07-16T17:33:39Z",
|
||||
"modified": "2024-09-06T21:38:47Z",
|
||||
"published": "2024-07-11T21:31:13Z",
|
||||
"aliases": [
|
||||
"CVE-2024-6468"
|
||||
],
|
||||
"summary": "Hashicorp Vault vulnerable to Improper Check or Handling of Exceptional Conditions ",
|
||||
"details": "Vault and Vault Enterprise did not properly handle requests originating from unauthorized IP addresses when the TCP listener option, proxy_protocol_behavior, was set to deny_unauthorized. When receiving a request from a source IP address that was not listed in proxy_protocol_authorized_addrs, the Vault API server would shut down and no longer respond to any HTTP requests, potentially resulting in denial of service.\n\nWhile this bug also affected versions of Vault up to 1.17.1 and 1.16.5, a separate regression in those release series did not allow Vault operators to configure the deny_unauthorized option, thus not allowing the conditions for the denial of service to occur.\n\nFixed in Vault and Vault Enterprise 1.17.2, 1.16.6, and 1.15.12.",
|
||||
"details": "Vault and Vault Enterprise did not properly handle requests originating from unauthorized IP addresses when the TCP listener option, proxy_protocol_behavior, was set to deny_unauthorized. When receiving a request from a source IP address that was not listed in proxy_protocol_authorized_addrs, the Vault API server would shut down and no longer respond to any HTTP requests, potentially resulting in denial of service.\n\nWhile this bug also affected versions of Vault up to 1.17.1 and 1.16.5, a separate regression in those release series did not allow Vault operators to configure the deny_unauthorized option, thus not allowing the conditions for the denial of service to occur.\n\nFixed in Vault and Vault Enterprise 1.17.2, 1.16.6, and 1.15.12",
|
||||
"severity": [
|
||||
{
|
||||
"type": "CVSS_V3",
|
||||
|
||||
@@ -1,13 +1,13 @@
|
||||
{
|
||||
"schema_version": "1.4.0",
|
||||
"id": "GHSA-5248-h45p-9pgw",
|
||||
"modified": "2024-07-12T19:16:46Z",
|
||||
"modified": "2024-09-06T21:38:40Z",
|
||||
"published": "2024-07-12T13:56:42Z",
|
||||
"aliases": [
|
||||
"CVE-2024-39909"
|
||||
],
|
||||
"summary": "SQL Injection in the KubeClarity REST API",
|
||||
"details": "### Summary\nA time/boolean SQL Injection is present in the following resource `/api/applicationResources` via the following parameter `packageID`\n\n### Details\nAs it can be seen [here](https://github.com/openclarity/kubeclarity/blob/main/backend/pkg/database/id_view.go#L79), while building the SQL Query the `fmt.Sprintf` function is used to build the query string without the input having first been subjected to any validation.\n\n### PoC\nThe following command should be able to trigger a basic version of the behavior:\n`curl -i -s -k -X $'GET' \\\n -H $'Host: kubeclarity.test' \\\n $'https://kubeclarity.test/api/applicationResources?page=1&pageSize=50&sortKey=vulnerabilities&sortDir=DESC&packageID=c89973a6-4e7f-50b5-afe2-6bf6f4d3da0a\\'HTTP/2'`\n\n### Impact\nWhile using the Helm chart, the impact of this vulnerability is limited since it allows read access only to the kuberclarity database, to which access is already given as far as I understand to regular users anyway.\nOn the other hand, if Kuberclarity is deployed in a less secure way, this might allow access to more data then allowed or expected (beyond the limits of the KuberClarity database)\n\nThe vulnerable line was introduced as part of the initial commit of Kubeclarity, so all versions up until the latest (2.23.1) are assumed vulnerable.",
|
||||
"details": "### Summary\nA time/boolean SQL Injection is present in the following resource `/api/applicationResources` via the following parameter `packageID`\n\n### Details\nAs it can be seen [here](https://github.com/openclarity/kubeclarity/blob/main/backend/pkg/database/id_view.go#L79), while building the SQL Query the `fmt.Sprintf` function is used to build the query string without the input having first been subjected to any validation.\n\n### PoC\nThe following command should be able to trigger a basic version of the behavior:\n`curl -i -s -k -X $'GET' \\\n -H $'Host: kubeclarity.test' \\\n $'https://kubeclarity.test/api/applicationResources?page=1&pageSize=50&sortKey=vulnerabilities&sortDir=DESC&packageID=c89973a6-4e7f-50b5-afe2-6bf6f4d3da0a\\'HTTP/2'`\n\n### Impact\nWhile using the Helm chart, the impact of this vulnerability is limited since it allows read access only to the kuberclarity database, to which access is already given as far as I understand to regular users anyway.\nOn the other hand, if Kuberclarity is deployed in a less secure way, this might allow access to more data then allowed or expected (beyond the limits of the KuberClarity database). The vulnerable line was introduced as part of the initial commit of Kubeclarity, so all versions up until the latest (2.23.1) are assumed vulnerable.",
|
||||
"severity": [
|
||||
{
|
||||
"type": "CVSS_V3",
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
{
|
||||
"schema_version": "1.4.0",
|
||||
"id": "GHSA-8mm6-wmpp-mmm3",
|
||||
"modified": "2024-07-12T19:20:32Z",
|
||||
"modified": "2024-09-06T21:38:52Z",
|
||||
"published": "2024-07-04T18:31:11Z",
|
||||
"aliases": [
|
||||
"CVE-2024-39933"
|
||||
@@ -44,6 +44,10 @@
|
||||
"type": "ADVISORY",
|
||||
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-39933"
|
||||
},
|
||||
{
|
||||
"type": "ADVISORY",
|
||||
"url": "https://github.com/advisories/GHSA-8mm6-wmpp-mmm3"
|
||||
},
|
||||
{
|
||||
"type": "PACKAGE",
|
||||
"url": "https://github.com/gogs/gogs"
|
||||
|
||||
@@ -1,13 +1,13 @@
|
||||
{
|
||||
"schema_version": "1.4.0",
|
||||
"id": "GHSA-3wfj-3x8q-hrpg",
|
||||
"modified": "2024-08-07T15:16:53Z",
|
||||
"modified": "2024-09-06T21:38:20Z",
|
||||
"published": "2024-08-05T16:07:50Z",
|
||||
"aliases": [
|
||||
"CVE-2024-41820"
|
||||
],
|
||||
"summary": "Kubean vulnerable to cluster-level privilege escalation",
|
||||
"details": "### Impact\nThis ClusterRole has `*` verbs of `*` resources. If a malicious user can access the worker node which has kubean's deployment, he/she can abuse these excessive permissions to do whatever he/she likes to the whole cluster, resulting in a cluster-level privilege escalation.\n\n### Patches\n`>=v0.18.0`\n\n### References\nReporting by @younaman(Nanzi Yang)\nhttps://github.com/kubean-io/kubean/issues/1326",
|
||||
"details": "### Impact\nThis ClusterRole has `*` verbs of `*` resources. If a malicious user can access the worker node which has kubean's deployment, he/she can abuse these excessive permissions to do whatever he/she likes to the whole cluster, resulting in a cluster-level privilege escalation.\n\n### Patches\n>=v0.18.0\n\n### References\nReporting by @younaman(Nanzi Yang)\nhttps://github.com/kubean-io/kubean/issues/1326",
|
||||
"severity": [
|
||||
{
|
||||
"type": "CVSS_V3",
|
||||
|
||||
Reference in New Issue
Block a user