id
stringlengths 13
16
| published
stringlengths 19
19
| modified
timestamp[ns] | details
stringlengths 30
3.87k
| severity
listlengths 1
1
⌀ | repo_url
stringlengths 23
68
| cwes
sequencelengths 0
1
| commits
sequencelengths 1
4
|
|---|---|---|---|---|---|---|---|
CVE-2022-31733 | 2023-02-03T19:15:11 | 2025-02-19T02:37:56.668313 | Starting with diego-release 2.55.0 and up to 2.69.0, and starting with CF Deployment 17.1 and up to 23.2.0, apps are accessible via another port on diego cells, allowing application ingress without a client certificate. If mTLS route integrity is enabled AND unproxied ports are turned off, then an attacker could connect to an application that should be only reachable via mTLS, without presenting a client certificate. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N",
"type": "CVSS_V3"
}
] | https://github.com/cloudfoundry/cf-deployment | [] | [
"36c1ff1a3fc4175c910aed00d423ea2edf457603"
] |
CVE-2023-20882 | 2023-05-26T17:15:13 | 2025-02-19T03:29:05.609843 | In Cloud foundry routing release versions from 0.262.0 and prior to 0.266.0,a bug in the gorouter process can lead to a denial of service of applications hosted on Cloud Foundry. Under the right circumstances, when client connections are closed prematurely, gorouter marks the currently selected backend as failed and removes it from the routing pool. | [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cloudfoundry/cf-deployment | [] | [
"1ef1fcda375fca5d7dc0cbbb9ba3d5de31efa83d"
] |
CVE-2021-22001 | 2021-07-22T14:15:07 | 2025-02-19T03:15:22.895405 | In UAA versions prior to 75.3.0, sensitive information like relaying secret of the provider was revealed in response when deletion request of an identity provider( IdP) of type “oauth 1.0” was sent to UAA server. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/cloudfoundry/cf-deployment | [] | [
"11822083b7d80dea7c1ff40e89812787c6d4fbe3",
"1bf516e1fffd86002d92d1d8c016d541c9d7a95b"
] |
CVE-2021-22098 | 2021-08-11T21:15:08 | 2025-02-19T03:15:21.744192 | UAA server versions prior to 75.4.0 are vulnerable to an open redirect vulnerability. A malicious user can exploit the open redirect vulnerability by social engineering leading to take over of victims’ accounts in certain cases along with redirection of UAA users to a malicious sites. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
] | https://github.com/cloudfoundry/cf-deployment | [] | [
"11822083b7d80dea7c1ff40e89812787c6d4fbe3",
"1bf516e1fffd86002d92d1d8c016d541c9d7a95b"
] |
CVE-2019-3801 | 2019-04-25T21:29:00 | 2025-01-14T08:00:00.865658 | Cloud Foundry cf-deployment, versions prior to 7.9.0, contain java components that are using an insecure protocol to fetch dependencies when building. A remote unauthenticated malicious attacker could hijack the DNS entry for the dependency, and inject malicious code into the component. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cloudfoundry/cf-deployment | [] | [
"11822083b7d80dea7c1ff40e89812787c6d4fbe3",
"1bf516e1fffd86002d92d1d8c016d541c9d7a95b"
] |
CVE-2019-11290 | 2019-11-26T00:15:11 | 2025-02-19T02:44:28.247619 | Cloud Foundry UAA Release, versions prior to v74.8.0, logs all query parameters to tomcat’s access file. If the query parameters are used to provide authentication, ie. credentials, then they will be logged as well. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/cloudfoundry/cf-deployment | [] | [
"11822083b7d80dea7c1ff40e89812787c6d4fbe3",
"1bf516e1fffd86002d92d1d8c016d541c9d7a95b"
] |
CVE-2019-11289 | 2019-11-19T19:15:23 | 2025-01-14T07:43:52.318446 | Cloud Foundry Routing, all versions before 0.193.0, does not properly validate nonce input. A remote unauthenticated malicious user could forge an HTTP route service request using an invalid nonce that will cause the Gorouter to crash. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cloudfoundry/cf-deployment | [] | [
"11822083b7d80dea7c1ff40e89812787c6d4fbe3",
"1bf516e1fffd86002d92d1d8c016d541c9d7a95b"
] |
CVE-2019-11277 | 2019-09-23T18:15:11 | 2025-02-19T02:44:03.166706 | Cloud Foundry NFS Volume Service, 1.7.x versions prior to 1.7.11 and 2.x versions prior to 2.3.0, is vulnerable to LDAP injection. A remote authenticated malicious space developer can potentially inject LDAP filters via service instance creation, facilitating the malicious space developer to deny service or perform a dictionary attack. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cloudfoundry/cf-deployment | [] | [
"11822083b7d80dea7c1ff40e89812787c6d4fbe3",
"1bf516e1fffd86002d92d1d8c016d541c9d7a95b"
] |
CVE-2019-11282 | 2019-10-23T16:15:11 | 2025-01-14T07:44:06.822388 | Cloud Foundry UAA, versions prior to v74.3.0, contains an endpoint that is vulnerable to SCIM injection attack. A remote authenticated malicious user with scim.invite scope can craft a request with malicious content which can leak information about users of the UAA. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/cloudfoundry/cf-deployment | [] | [
"11822083b7d80dea7c1ff40e89812787c6d4fbe3",
"1bf516e1fffd86002d92d1d8c016d541c9d7a95b"
] |
CVE-2019-11283 | 2019-10-23T16:15:11 | 2025-01-14T07:43:46.812881 | Cloud Foundry SMB Volume, versions prior to v2.0.3, accidentally outputs sensitive information to the logs. A remote user with access to the SMB Volume logs can discover the username and password for volumes that have been recently created, allowing the user to take control of the SMB Volume. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cloudfoundry/cf-deployment | [] | [
"11822083b7d80dea7c1ff40e89812787c6d4fbe3",
"1bf516e1fffd86002d92d1d8c016d541c9d7a95b"
] |
CVE-2019-11294 | 2019-12-19T20:15:12 | 2025-01-14T07:43:48.543741 | Cloud Foundry Cloud Controller API (CAPI), version 1.88.0, allows space developers to list all global service brokers, including service broker URLs and GUIDs, which should only be accessible to admins. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/cloudfoundry/cf-deployment | [] | [
"11822083b7d80dea7c1ff40e89812787c6d4fbe3",
"1bf516e1fffd86002d92d1d8c016d541c9d7a95b"
] |
CVE-2019-11293 | 2019-12-06T20:15:09 | 2025-02-19T02:44:37.678465 | Cloud Foundry UAA Release, versions prior to v74.10.0, when set to logging level DEBUG, logs client_secret credentials when sent as a query parameter. A remote authenticated malicious user could gain access to user credentials via the uaa.log file if authentication is provided via query parameters. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/cloudfoundry/cf-deployment | [] | [
"11822083b7d80dea7c1ff40e89812787c6d4fbe3",
"1bf516e1fffd86002d92d1d8c016d541c9d7a95b"
] |
CVE-2018-1221 | 2018-03-19T18:29:00 | 2025-02-19T02:29:45.038975 | In cf-deployment before 1.14.0 and routing-release before 0.172.0, the Cloud Foundry Gorouter mishandles WebSocket requests for AWS Application Load Balancers (ALBs) and some other HTTP-aware Load Balancers. A user with developer privileges could use this vulnerability to steal data or cause denial of service. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cloudfoundry/cf-deployment | [] | [
"11822083b7d80dea7c1ff40e89812787c6d4fbe3"
] |
CVE-2018-1191 | 2018-03-29T20:29:00 | 2025-01-14T07:21:54.415557 | Cloud Foundry Garden-runC, versions prior to 1.11.0, contains an information exposure vulnerability. A user with access to Garden logs may be able to obtain leaked credentials and perform authenticated actions using those credentials. | [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cloudfoundry/cf-deployment | [] | [
"11822083b7d80dea7c1ff40e89812787c6d4fbe3"
] |
CVE-2018-1277 | 2018-04-30T20:29:00 | 2025-02-19T02:30:01.241794 | Cloud Foundry Garden-runC, versions prior to 1.13.0, does not correctly enforce disc quotas for Docker image layers. A remote authenticated user may push an app with a malicious Docker image that will consume more space on a Diego cell than allocated in their quota, potentially causing a DoS against the cell. | [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cloudfoundry/cf-deployment | [] | [
"11822083b7d80dea7c1ff40e89812787c6d4fbe3"
] |
CVE-2018-1265 | 2018-06-06T20:29:00 | 2025-02-19T02:30:08.691071 | Cloud Foundry Diego, release versions prior to 2.8.0, does not properly sanitize file paths in tar and zip files headers. A remote attacker with CF admin privileges can upload a malicious buildpack that will allow a complete takeover of a Diego Cell VM and access to all apps running on that Diego Cell. | [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cloudfoundry/cf-deployment | [] | [
"11822083b7d80dea7c1ff40e89812787c6d4fbe3",
"1bf516e1fffd86002d92d1d8c016d541c9d7a95b"
] |
CVE-2018-1262 | 2018-05-15T20:29:00 | 2025-02-19T02:34:00.620678 | Cloud Foundry Foundation UAA, versions 4.12.X and 4.13.X, introduced a feature which could allow privilege escalation across identity zones for clients performing offline validation. A zone administrator could configure their zone to issue tokens which impersonate another zone, granting up to admin privileges in the impersonated zone for clients performing offline token validation. | [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cloudfoundry/cf-deployment | [] | [
"1bf516e1fffd86002d92d1d8c016d541c9d7a95b"
] |
CVE-2018-1193 | 2018-05-23T15:29:00 | 2025-02-19T02:29:41.187445 | Cloud Foundry routing-release, versions prior to 0.175.0, lacks sanitization for user-provided X-Forwarded-Proto headers. A remote user can set the X-Forwarded-Proto header in a request to potentially bypass an application requirement to only respond over secure connections. | [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/cloudfoundry/cf-deployment | [] | [
"11822083b7d80dea7c1ff40e89812787c6d4fbe3"
] |
CVE-2020-5416 | 2020-08-21T22:15:12 | 2025-02-19T03:12:28.651733 | Cloud Foundry Routing (Gorouter), versions prior to 0.204.0, when used in a deployment with NGINX reverse proxies in front of the Gorouters, is potentially vulnerable to denial-of-service attacks in which an unauthenticated malicious attacker can send specially-crafted HTTP requests that may cause the Gorouters to be dropped from the NGINX backend pool. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cloudfoundry/cf-deployment | [] | [
"11822083b7d80dea7c1ff40e89812787c6d4fbe3",
"1bf516e1fffd86002d92d1d8c016d541c9d7a95b"
] |
CVE-2020-5420 | 2020-09-03T01:15:10 | 2025-02-19T03:12:23.583960 | Cloud Foundry Routing (Gorouter) versions prior to 0.206.0 allow a malicious developer with "cf push" access to cause denial-of-service to the CF cluster by pushing an app that returns specially crafted HTTP responses that crash the Gorouters. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cloudfoundry/cf-deployment | [] | [
"11822083b7d80dea7c1ff40e89812787c6d4fbe3",
"1bf516e1fffd86002d92d1d8c016d541c9d7a95b"
] |
CVE-2020-5402 | 2020-02-27T20:15:11 | 2025-02-19T03:12:32.673469 | In Cloud Foundry UAA, versions prior to 74.14.0, a CSRF vulnerability exists due to the OAuth2 state parameter not being checked in the callback function when authenticating with external identity providers. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cloudfoundry/cf-deployment | [] | [
"11822083b7d80dea7c1ff40e89812787c6d4fbe3",
"1bf516e1fffd86002d92d1d8c016d541c9d7a95b"
] |
CVE-2016-6655 | 2017-06-13T06:29:00 | 2025-01-14T06:44:31.171099 | An issue was discovered in Cloud Foundry Foundation Cloud Foundry release versions prior to v245 and cf-mysql-release versions prior to v31. A command injection vulnerability was discovered in a common script used by many Cloud Foundry components. A malicious user may exploit numerous vectors to execute arbitrary commands on servers running Cloud Foundry. | [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cloudfoundry/cf-mysql-release | [] | [
"4a7df1cbeb2083b19a1b1537bbfc755deb515434"
] |
CVE-2018-15755 | 2018-10-12T22:15:07 | 2025-01-14T07:23:57.916428 | Cloud Foundry CF Networking Release, versions 2.11.0 prior to 2.16.0, contain an internal api endpoint vulnerable to SQL injection between Diego cells and the policy server. A remote authenticated malicious user with mTLS certs can issue arbitrary SQL queries and gain access to the policy server. | [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cloudfoundry/cf-networking-release | [] | [
"97edbbcb0d60390918ce61c7378a9e77329666b8"
] |
CVE-2019-3781 | 2019-03-07T18:29:00 | 2025-02-19T02:58:50.556105 | Cloud Foundry CLI, versions prior to v6.43.0, improperly exposes passwords when verbose/trace/debugging is turned on. A local unauthenticated or remote authenticated malicious user with access to logs may gain part or all of a users password. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cloudfoundry/cli | [] | [
"4947847c552d8aa967d3ad9ed720d74d42f674d3"
] |
CVE-2018-11084 | 2018-09-18T21:29:02 | 2025-02-19T02:28:34.716849 | Cloud Foundry Garden-runC release, versions prior to 1.16.1, prevents deletion of some app environments based on file attributes. A remote authenticated malicious user may create and delete apps with crafted file attributes to cause a denial of service for new app instances or scaling up of existing apps. | [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N",
"type": "CVSS_V3"
}
] | https://github.com/cloudfoundry/garden-runc-release | [] | [
"0e9adf1d37cd22507afff99a38b10bb413c5dd9b"
] |
CVE-2017-14388 | 2017-11-13T17:29:00 | 2025-02-19T02:23:57.754119 | Cloud Foundry Foundation GrootFS release 0.3.x versions prior to 0.30.0 do not validate DiffIDs, allowing specially crafted images to poison the grootfs volume cache. For example, this could allow an attacker to provide an image layer that GrootFS would consider to be the Ubuntu base layer. | [
{
"score": "CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cloudfoundry/grootfs | [] | [
"00520d66bfb6a1546b372942f98695dbe9454d75"
] |
CVE-2018-1268 | 2018-06-06T20:29:00 | 2025-01-14T07:22:29.210854 | Cloud Foundry Loggregator, versions 89.x prior to 89.5 or 96.x prior to 96.1 or 99.x prior to 99.1 or 101.x prior to 101.9 or 102.x prior to 102.2, does not validate app GUID structure in requests. A remote authenticated malicious user knowing the GUID of an app may construct malicious requests to read from or write to the logs of that app. | [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N",
"type": "CVSS_V3"
}
] | https://github.com/cloudfoundry/loggregator-release | [] | [
"423b6711d2a99577faf67f8bc4b8f307845cef36"
] |
CVE-2018-1269 | 2018-06-06T20:29:00 | 2025-01-14T07:22:29.338126 | Cloud Foundry Loggregator, versions 89.x prior to 89.5 or 96.x prior to 96.1 or 99.x prior to 99.1 or 101.x prior to 101.9 or 102.x prior to 102.2, does not handle errors thrown while constructing certain http requests. A remote authenticated user may construct malicious requests to cause the traffic controller to leave dangling TCP connections, which could cause denial of service. | [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cloudfoundry/loggregator-release | [] | [
"423b6711d2a99577faf67f8bc4b8f307845cef36"
] |
CVE-2018-15797 | 2018-12-05T18:29:00 | 2025-01-14T07:24:01.519112 | Cloud Foundry NFS volume release, 1.2.x prior to 1.2.5, 1.5.x prior to 1.5.4, 1.7.x prior to 1.7.3, logs the cf admin username and password when running the nfsbrokerpush BOSH deploy errand. A remote authenticated user with access to BOSH can obtain the admin credentials for the Cloud Foundry Platform through the logs of the NFS volume deploy errand. | [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cloudfoundry/nfs-volume-release | [] | [
"dbbef2ef49432a1a66539e1aff2948ef8570d80c"
] |
CVE-2018-1267 | 2018-03-27T16:29:00 | 2025-01-14T07:22:28.937664 | Cloud Foundry Silk CNI plugin, versions prior to 0.2.0, contains an improper access control vulnerability. If the platform is configured with an application security group (ASG) that overlaps with the Silk overlay network, any applications can reach any other application on the network regardless of the configured routing policies. | [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cloudfoundry/silk-release | [] | [
"bba5414efb0880288815d63524738b00e2374bad"
] |
CVE-2022-40082 | 2022-09-28T14:15:10 | 2025-01-14T11:09:32.041866 | Hertz v0.3.0 ws discovered to contain a path traversal vulnerability via the normalizePath function. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/cloudwego/hertz | [] | [
"a83e52c84424955e27d70250924d0d2189e61fb0"
] |
CVE-2023-30622 | 2023-04-24T16:15:07 | 2025-02-19T03:31:43.219703 | Clusternet is a general-purpose system for controlling Kubernetes clusters across different environments. An issue in clusternet prior to version 0.15.2 can be leveraged to lead to a cluster-level privilege escalation. The clusternet has a deployment called `cluster-hub` inside the `clusternet-system` Kubernetes namespace, which runs on worker nodes randomly. The deployment has a service account called `clusternet-hub`, which has a cluster role called `clusternet:hub` via cluster role binding. The `clusternet:hub` cluster role has `"*" verbs of "*.*"` resources. Thus, if a malicious user can access the worker node which runs the clusternet, they can leverage the service account to do malicious actions to critical system resources. For example, the malicious user can leverage the service account to get ALL secrets in the entire cluster, resulting in cluster-level privilege escalation. Version 0.15.2 contains a fix for this issue. | [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/clusternet/clusternet | [] | [
"e156bf08264f425b0ff56b4047d6d0fc0db87c8a"
] |
CVE-2022-40494 | 2022-10-06T22:15:09 | 2025-02-19T03:29:47.804412 | NPS before v0.26.10 was discovered to contain an authentication bypass vulnerability via constantly generating and sending the Auth key and Timestamp parameters. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cnlh/nps | [] | [
"18c11f108b149527ef069b9833ff683aeb2b8f52"
] |
CVE-2019-15119 | 2019-08-16T15:15:11 | 2025-02-19T02:48:13.365222 | lib/install/install.go in cnlh nps through 0.23.2 uses 0777 permissions for /usr/local/bin/nps and/or /usr/bin/nps, leading to a file overwrite by a local user. | [
{
"score": "CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N",
"type": "CVSS_V3"
}
] | https://github.com/cnlh/nps | [] | [
"18c11f108b149527ef069b9833ff683aeb2b8f52"
] |
CVE-2024-47877 | 2024-10-11T17:15:04 | 2025-01-14T12:17:15.493293 | Extract is aA Go library to extract archives in zip, tar.gz or tar.bz2 formats. A maliciously crafted archive may allow an attacker to create a symlink outside the extraction target directory. This vulnerability is fixed in 4.0.0. If you're using the Extractor.FS interface, then upgrading to /v4 will require to implement the new methods that have been added. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
"type": "CVSS_V3"
}
] | https://github.com/codeclysm/extract | [] | [
"07d6c3396bb2b57ec93b00c210ef35474dc786f7"
] |
CVE-2022-36111 | 2022-11-23T18:15:11 | 2025-01-14T11:04:09.822591 | immudb is a database with built-in cryptographic proof and verification. In versions prior to 1.4.1, a malicious immudb server can provide a falsified proof that will be accepted by the client SDK signing a falsified transaction replacing the genuine one. This situation can not be triggered by a genuine immudb server and requires the client to perform a specific list of verified operations resulting in acceptance of an invalid state value. This vulnerability only affects immudb client SDKs, the immudb server itself is not affected by this vulnerability. This issue has been patched in version 1.4.1. | [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N",
"type": "CVSS_V3"
}
] | https://github.com/codenotary/immudb | [] | [
"e512022c8157e77ef85ebb7f5b51d3f3c87ae6a2"
] |
CVE-2022-39199 | 2022-11-22T20:15:11 | 2025-01-14T11:06:27.539841 | immudb is a database with built-in cryptographic proof and verification. immudb client SDKs use server's UUID to distinguish between different server instance so that the client can connect to different immudb instances and keep the state for multiple servers. SDK does not validate this uuid and can accept any value reported by the server. A malicious server can change the reported UUID tricking the client to treat it as a different server thus accepting a state completely irrelevant to the one previously retrieved from the server. This issue has been patched in version 1.4.1. As a workaround, when initializing an immudb client object a custom state handler can be used to store the state. Providing custom implementation that ignores the server UUID can be used to ensure that even if the server changes the UUID, client will still consider it to be the same server. | [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N",
"type": "CVSS_V3"
}
] | https://github.com/codenotary/immudb | [] | [
"e512022c8157e77ef85ebb7f5b51d3f3c87ae6a2"
] |
CVE-2024-27918 | 2024-03-21T02:52:20 | 2025-01-15T05:19:02.109892 | Coder allows oragnizations to provision remote development environments via Terraform. Prior to versions 2.6.1, 2.7.3, and 2.8.4, a vulnerability in Coder's OIDC authentication could allow an attacker to bypass the `CODER_OIDC_EMAIL_DOMAIN` verification and create an account with an email not in the allowlist. Deployments are only affected if the OIDC provider allows users to create accounts on the provider. During OIDC registration, the user's email was improperly validated against the allowed `CODER_OIDC_EMAIL_DOMAIN`s. This could allow a user with a domain that only partially matched an allowed domain to successfully login or register. An attacker could register a domain name that exploited this vulnerability and register on a Coder instance with a public OIDC provider.
Coder instances with OIDC enabled and protected by the `CODER_OIDC_EMAIL_DOMAIN` configuration are affected. Coder instances using a private OIDC provider are not affected, as arbitrary users cannot register through a private OIDC provider without first having an account on the provider. Public OIDC providers are impacted. GitHub authentication and external authentication are not impacted. This vulnerability is remedied in versions 2.8.4, 2.7.3, and 2.6.1 All versions prior to these patches are affected by the vulnerability.*It is recommended that customers upgrade their deployments as soon as possible if they are utilizing OIDC authentication with the `CODER_OIDC_EMAIL_DOMAIN` setting. | null | https://github.com/coder/coder | [] | [
"d6cdaae8b194829c0631908d15e4ac57ae887ef6"
] |
CVE-2023-34451 | 2023-07-03T17:15:09 | 2025-02-19T03:33:51.702158 | CometBFT is a Byzantine Fault Tolerant (BFT) middleware that takes a state transition machine and replicates it on many machines. The mempool maintains two data structures to keep track of outstanding transactions: a list and a map.
These two data structures are supposed to be in sync all the time in the sense that the map tracks the index (if any) of the transaction in the list. In `v0.37.0`, and `v0.37.1`, as well as in `v0.34.28`, and all previous releases of the CometBFT repo2, it is possible to have them out of sync. When this happens, the list may contain several copies of the same transaction. Because the map tracks a single index, it is then no longer possible to remove all the copies of the transaction from the list. This happens even if the duplicated transaction is later committed in a block. The only way to remove the transaction is by restarting the node.
The above problem can be repeated on and on until a sizable number of transactions are stuck in the mempool, in order to try to bring down the target node. The problem is fixed in releases `v0.34.29` and `v0.37.2`. Some workarounds are available. Increasing the value of `cache_size` in `config.toml` makes it very difficult to effectively attack a full node. Not exposing the transaction submission RPC's would mitigate the probability of a successful attack, as the attacker would then have to create a modified (byzantine) full node to be able to perform the attack via p2p. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cometbft/cometbft | [] | [
"45e98ef8001b7be722fb080a78910a272a129172"
] |
CVE-2023-34450 | 2023-07-03T17:15:09 | 2025-02-19T03:32:27.936023 | CometBFT is a Byzantine Fault Tolerant (BFT) middleware that takes a state transition machine and replicates it on many machines. An internal modification made in versions 0.34.28 and 0.37.1 to the way struct `PeerState` is serialized to JSON introduced a deadlock when new function MarshallJSON is called. This function can be called from two places. The first is via logs, setting the `consensus` logging module to "debug" level (should not happen in production), and setting the log output format to JSON. The second is via RPC `dump_consensus_state`.
Case 1, which should not be hit in production, will eventually hit the deadlock in most goroutines, effectively halting the node.
In case 2, only the data structures related to the first peer will be deadlocked, together with the thread(s) dealing with the RPC request(s). This means that only one of the channels of communication to the node's peers will be blocked. Eventually the peer will timeout and excluded from the list (typically after 2 minutes). The goroutines involved in the deadlock will not be garbage collected, but they will not interfere with the system after the peer is excluded.
The theoretical worst case for case 2, is a network with only two validator nodes. In this case, each of the nodes only has one `PeerState` struct. If `dump_consensus_state` is called in either node (or both), the chain will halt until the peer connections time out, after which the nodes will reconnect (with different `PeerState` structs) and the chain will progress again. Then, the same process can be repeated.
As the number of nodes in a network increases, and thus, the number of peer struct each node maintains, the possibility of reproducing the perturbation visible with two nodes decreases. Only the first `PeerState` struct will deadlock, and not the others (RPC `dump_consensus_state` accesses them in a for loop, so the deadlock at the first iteration causes the rest of the iterations of that "for" loop to never be reached).
This regression was fixed in versions 0.34.29 and 0.37.2. Some workarounds are available. For case 1 (hitting the deadlock via logs), either don't set the log output to "json", leave at "plain", or don't set the consensus logging module to "debug", leave it at "info" or higher. For case 2 (hitting the deadlock via RPC `dump_consensus_state`), do not expose `dump_consensus_state` RPC endpoint to the public internet (e.g., via rules in one's nginx setup). | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L",
"type": "CVSS_V3"
}
] | https://github.com/cometbft/cometbft | [] | [
"45e98ef8001b7be722fb080a78910a272a129172"
] |
CVE-2024-23688 | 2024-01-19T22:15:08 | 2025-01-14T12:11:36.557230 | Consensys Discovery versions less than 0.4.5 uses the same AES/GCM nonce for the entire session. which should ideally be unique for every message. The node's private key isn't compromised, only the session key generated for specific peer communication is exposed.
| [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/consensys/discovery | [] | [
"c4ffade2cbf9943ac0f2f1be6e94a207fbc98ba5"
] |
CVE-2024-45040 | 2024-09-06T13:15:04 | 2025-02-19T03:38:23.741614 | gnark is a fast zk-SNARK library that offers a high-level API to design circuits. Prior to version 0.11.0, commitments to private witnesses in Groth16 as implemented break the zero-knowledge property. The vulnerability affects only Groth16 proofs with commitments. Notably, PLONK proofs are not affected. The vulnerability affects the zero-knowledge property of the proofs - in case the witness (secret or internal) values are small, then the attacker may be able to enumerate all possible choices to deduce the actual value. If the possible choices for the variables to be committed is large or there are many values committed, then it would be computationally infeasible to enumerate all valid choices. It doesn't affect the completeness/soundness of the proofs. The vulnerability has been fixed in version 0.11.0. The patch to fix the issue is to add additional randomized value to the list of committed value at proving time to mask the rest of the values which were committed. As a workaround, the user can manually commit to a randomized value. | [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/consensys/gnark | [] | [
"f9dfb87201d5166b25f0e0d44606df54c4ad3036"
] |
CVE-2024-50354 | 2024-10-31T16:15:05 | 2024-11-01T22:27:08.771887 | gnark is a fast zk-SNARK library that offers a high-level API to design circuits. In gnark 0.11.0 and earlier, deserialization of Groth16 verification keys allocate excessive memory, consuming a lot of resources and triggering a crash with the error fatal error: runtime: out of memory. | null | https://github.com/consensys/gnark | [] | [
"f9dfb87201d5166b25f0e0d44606df54c4ad3036"
] |
CVE-2023-44378 | 2023-10-09T14:15:10 | 2025-01-15T04:58:49.809218 | gnark is a zk-SNARK library that offers a high-level API to design circuits. Prior to version 0.9.0, for some in-circuit values, it is possible to construct two valid decomposition to bits. In addition to the canonical decomposition of `a`, for small values there exists a second decomposition for `a+r` (where `r` is the modulus the values are being reduced by). The second decomposition was possible due to overflowing the field where the values are defined. Upgrading to version 0.9.0 should fix the issue without needing to change the calls to value comparison methods. | [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N",
"type": "CVSS_V3"
}
] | https://github.com/consensys/gnark | [] | [
"f9dfb87201d5166b25f0e0d44606df54c4ad3036"
] |
CVE-2024-45039 | 2024-09-06T13:15:04 | 2025-02-19T03:38:25.155831 | gnark is a fast zk-SNARK library that offers a high-level API to design circuits. Versions prior to 0.11.0 have a soundness issue - in case of multiple commitments used inside the circuit the prover is able to choose all but the last commitment. As gnark uses the commitments for optimized non-native multiplication, lookup checks etc. as random challenges, then it could impact the soundness of the whole circuit. However, using multiple commitments has been discouraged due to the additional cost to the verifier and it has not been supported in the recursive in-circuit Groth16 verifier and Solidity verifier. gnark's maintainers expect the impact of the issue be very small - only for the users who have implemented the native Groth16 verifier or are using it with multiple commitments. We do not have information of such users. The issue has been patched in version 0.11.0. As a workaround, users should follow gnark maintainers' recommendation to use only a single commitment and then derive in-circuit commitments as needed using the `std/multicommit` package. | [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
"type": "CVSS_V3"
}
] | https://github.com/consensys/gnark-crypto | [] | [
"f93a56c714c4e6266429cac111a004e9eec7daa0"
] |
CVE-2023-44273 | 2023-09-28T04:15:12 | 2025-02-19T03:34:25.473005 | Consensys gnark-crypto through 0.11.2 allows Signature Malleability. This occurs because deserialisation of EdDSA and ECDSA signatures does not ensure that the data is in a certain interval. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/consensys/gnark-crypto | [] | [
"f93a56c714c4e6266429cac111a004e9eec7daa0"
] |
CVE-2022-24778 | 2022-03-25T18:15:22 | 2025-01-15T02:16:58.838611 | The imgcrypt library provides API exensions for containerd to support encrypted container images and implements the ctd-decoder command line tool for use by containerd to decrypt encrypted container images. The imgcrypt function `CheckAuthorization` is supposed to check whether the current used is authorized to access an encrypted image and prevent the user from running an image that another user previously decrypted on the same system. In versions prior to 1.1.4, a failure occurs when an image with a ManifestList is used and the architecture of the local host is not the first one in the ManifestList. Only the first architecture in the list was tested, which may not have its layers available locally since it could not be run on the host architecture. Therefore, the verdict on unavailable layers was that the image could be run anticipating that image run failure would occur later due to the layers not being available. However, this verdict to allow the image to run enabled other architectures in the ManifestList to run an image without providing keys if that image had previously been decrypted. A patch has been applied to imgcrypt 1.1.4. Workarounds may include usage of different namespaces for each remote user. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/containerd/imgcrypt | [] | [
"65d749cef36547473d1c1b0b67ed8a4b9e3d13d4"
] |
CVE-2020-1702 | 2021-05-27T20:15:07 | 2025-01-14T08:34:13.020021 | A malicious container image can consume an unbounded amount of memory when being pulled to a container runtime host, such as Red Hat Enterprise Linux using podman, or OpenShift Container Platform. An attacker can use this flaw to trick a user, with privileges to pull container images, into crashing the process responsible for pulling the image. This flaw affects containers-image versions before 5.2.0. | [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L",
"type": "CVSS_V3"
}
] | https://github.com/containers/image | [] | [
"eaab4bee6eecfa8220e8a21a802b81919f3c94e1"
] |
CVE-2019-10152 | 2019-07-30T23:15:11 | 2025-01-14T07:42:56.582522 | A path traversal vulnerability has been discovered in podman before version 1.4.0 in the way it handles symlinks inside containers. An attacker who has compromised an existing container can cause arbitrary files on the host filesystem to be read/written when an administrator tries to copy a file from/to the container. | [
{
"score": "CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N",
"type": "CVSS_V3"
}
] | https://github.com/containers/libpod | [] | [
"1f2e2a25bf0fec4a1e023a35903627e0562c88a6"
] |
CVE-2019-18466 | 2019-10-28T13:15:11 | 2025-01-15T01:41:09.511847 | An issue was discovered in Podman in libpod before 1.6.0. It resolves a symlink in the host context during a copy operation from the container to the host, because an undesired glob operation occurs. An attacker could create a container image containing particular symlinks that, when copied by a victim user to the host filesystem, may overwrite existing files with others from the host. | [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N",
"type": "CVSS_V3"
}
] | https://github.com/containers/libpod | [] | [
"1f2e2a25bf0fec4a1e023a35903627e0562c88a6"
] |
CVE-2018-10856 | 2018-07-03T01:29:00 | 2025-01-15T01:31:51.910274 | It has been discovered that podman before version 0.6.1 does not drop capabilities when executing a container as a non-root user. This results in unnecessary privileges being granted to the container. | [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/containers/libpod | [] | [
"1f2e2a25bf0fec4a1e023a35903627e0562c88a6"
] |
CVE-2024-3056 | 2024-08-02T21:16:30 | 2025-01-14T12:13:49.120701 | A flaw was found in Podman. This issue may allow an attacker to create a specially crafted container that, when configured to share the same IPC with at least one other container, can create a large number of IPC resources in /dev/shm. The malicious container will continue to exhaust resources until it is out-of-memory (OOM) killed. While the malicious container's cgroup will be removed, the IPC resources it created are not. Those resources are tied to the IPC namespace that will not be removed until all containers using it are stopped, and one non-malicious container is holding the namespace open. The malicious container is restarted, either automatically or by attacker control, repeating the process and increasing the amount of memory consumed. With a container configured to restart always, such as `podman run --restart=always`, this can result in a memory-based denial of service of the system. | [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/containers/podman | [] | [
"b22d5c61eef93475413724f49fd6a32980d2c746"
] |
CVE-2022-25891 | 2022-07-15T20:15:08 | 2025-01-15T02:19:07.046951 | The package github.com/containrrr/shoutrrr/pkg/util before 0.6.0 are vulnerable to Denial of Service (DoS) via the util.PartitionMessage function. Exploiting this vulnerability is possible by sending exactly 2000, 4000, or 6000 characters messages. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/containrrr/shoutrrr | [] | [
"23170b836d31a2231011472b6e8a91bf98bf6b26"
] |
CVE-2023-37279 | 2023-09-20T22:15:13 | 2025-01-14T11:49:15.155509 | Faktory is a language-agnostic persistent background job server. Prior to version 1.8.0, the Faktory web dashboard can suffer from denial of service by a crafted malicious url query param `days`. The vulnerability is related to how the backend reads the `days` URL query parameter in the Faktory web dashboard. The value is used directly without any checks to create a string slice. If a very large value is provided, the backend server ends up using a significant amount of memory and causing it to crash. Version 1.8.0 fixes this issue. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/contribsys/faktory | [] | [
"afc27bfb107e2146f11d0eed119ad54b2d57ec4e"
] |
CVE-2023-40586 | 2023-08-25T21:15:09 | 2025-01-15T04:57:24.513792 | OWASP Coraza WAF is a golang modsecurity compatible web application firewall library. Due to the misuse of `log.Fatalf`, the application using coraza crashed after receiving crafted requests from attackers. The application will immediately crash after receiving a malicious request that triggers an error in `mime.ParseMediaType`. This issue was patched in version 3.0.1.
| [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/corazawaf/coraza | [] | [
"ad50864cfa00f5143fff7f6877847326fdc4b394"
] |
CVE-2021-31232 | 2021-04-30T13:15:07 | 2025-01-14T09:13:03.803314 | The Alertmanager in CNCF Cortex before 1.8.1 has a local file disclosure vulnerability when -experimental.alertmanager.enable-api is used. The HTTP basic auth password_file can be used as an attack vector to send any file content via a webhook. The alertmanager templates can be used as an attack vector to send any file content because the alertmanager can load any text file specified in the templates list. | [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/cortexproject/cortex | [] | [
"06bbda1ec0bd4d5fc0194d3d28ac8c9fce914707"
] |
CVE-2021-36157 | 2021-08-03T15:15:08 | 2025-01-14T09:20:54.666264 | An issue was discovered in Grafana Cortex through 1.9.0. The header value X-Scope-OrgID is used to construct file paths for rules files, and if crafted to conduct directory traversal such as ae ../../sensitive/path/in/deployment pathname, then Cortex will attempt to parse a rules file at that location and include some of the contents in the error message. (Other Cortex API requests can also be sent a malicious OrgID header, e.g., tricking the ingester into writing metrics to a different location, but the effect is nuisance rather than information disclosure.) | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/cortexproject/cortex | [] | [
"06bbda1ec0bd4d5fc0194d3d28ac8c9fce914707"
] |
CVE-2022-23536 | 2022-12-19T22:15:10 | 2025-02-19T03:24:52.391172 | Cortex provides multi-tenant, long term storage for Prometheus. A local file inclusion vulnerability exists in Cortex versions 1.13.0, 1.13.1 and 1.14.0, where a malicious actor could remotely read local files as a result of parsing maliciously crafted Alertmanager configurations when submitted to the Alertmanager Set Configuration API. Only users of the Alertmanager service where `-experimental.alertmanager.enable-api` or `enable_api: true` is configured are affected. Affected Cortex users are advised to upgrade to patched versions 1.13.2 or 1.14.1. However as a workaround, Cortex administrators may reject Alertmanager configurations containing the `api_key_file` setting in the `opsgenie_configs` section before sending to the Set Alertmanager Configuration API.
| [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/cortexproject/cortex | [] | [
"06bbda1ec0bd4d5fc0194d3d28ac8c9fce914707"
] |
CVE-2021-41135 | 2021-10-20T18:15:07 | 2025-01-15T02:04:45.464227 | The Cosmos-SDK is a framework for building blockchain applications in Golang. Affected versions of the SDK were vulnerable to a consensus halt due to non-deterministic behaviour in a ValidateBasic method in the x/authz module. The MsgGrant of the x/authz module contains a Grant field which includes a user-defined expiration time for when the authorization grant expires. In Grant.ValidateBasic(), that time is compared to the node’s local clock time. Any chain running an affected version of the SDK with the authz module enabled could be halted by anyone with the ability to send transactions on that chain. Recovery would require applying the patch and rolling back the latest block. Users are advised to update to version 0.44.2. | null | https://github.com/cosmos/cosmos-sdk | [] | [
"8a73b266f52e08f24738c93ef519b529cd35bbd8"
] |
CVE-2021-25835 | 2021-02-08T18:15:13 | 2025-01-14T09:00:52.187035 | Cosmos Network Ethermint <= v0.4.0 is affected by a cross-chain transaction replay vulnerability in the EVM module. Since ethermint uses the same chainIDEpoch and signature schemes with ethereum for compatibility, a verified signature in ethereum is still valid in ethermint with the same msg content and chainIDEpoch, which enables "cross-chain transaction replay" attack. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
"type": "CVSS_V3"
}
] | https://github.com/cosmos/ethermint | [] | [
"11e2f636787f453dac645b53e6b930d42bbb8711"
] |
CVE-2021-25837 | 2021-02-08T18:15:13 | 2025-01-14T09:00:47.740158 | Cosmos Network Ethermint <= v0.4.0 is affected by cache lifecycle inconsistency in the EVM module. Due to the inconsistency between the Storage caching cycle and the Tx processing cycle, Storage changes caused by a failed transaction are improperly reserved in memory. Although the bad storage cache data will be discarded at EndBlock, it is still valid in the current block, which enables many possible attacks such as an "arbitrary mint token". | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
"type": "CVSS_V3"
}
] | https://github.com/cosmos/ethermint | [] | [
"11e2f636787f453dac645b53e6b930d42bbb8711"
] |
CVE-2021-25836 | 2021-02-08T18:15:13 | 2025-01-14T09:00:47.529974 | Cosmos Network Ethermint <= v0.4.0 is affected by cache lifecycle inconsistency in the EVM module. The bytecode set in a FAILED transaction wrongfully remains in memory(stateObject.code) and is further written to persistent store at the Endblock stage, which may be utilized to build honeypot contracts. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
"type": "CVSS_V3"
}
] | https://github.com/cosmos/ethermint | [] | [
"11e2f636787f453dac645b53e6b930d42bbb8711"
] |
CVE-2021-25834 | 2021-02-08T18:15:13 | 2025-01-14T09:00:43.880846 | Cosmos Network Ethermint <= v0.4.0 is affected by a transaction replay vulnerability in the EVM module. If the victim sends a very large nonce transaction, the attacker can replay the transaction through the application. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
"type": "CVSS_V3"
}
] | https://github.com/cosmos/ethermint | [] | [
"11e2f636787f453dac645b53e6b930d42bbb8711"
] |
CVE-2023-28119 | 2023-03-22T20:15:12 | 2025-01-15T04:49:22.111196 | The crewjam/saml go library contains a partial implementation of the SAML standard in golang. Prior to version 0.4.13, the package's use of `flate.NewReader` does not limit the size of the input. The user can pass more than 1 MB of data in the HTTP request to the processing functions, which will be decompressed server-side using the Deflate algorithm. Therefore, after repeating the same request multiple times, it is possible to achieve a reliable crash since the operating system kills the process. This issue is patched in version 0.4.13.
| [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/crewjam/saml | [] | [
"a60693989d9efbca89bb06007e3269a7da3cc214"
] |
CVE-2023-45683 | 2023-10-16T19:15:11 | 2025-01-15T04:59:19.475782 | github.com/crewjam/saml is a saml library for the go language. In affected versions the package does not validate the ACS Location URI according to the SAML binding being parsed. If abused, this flaw allows attackers to register malicious Service Providers at the IdP and inject Javascript in the ACS endpoint definition, achieving Cross-Site-Scripting (XSS) in the IdP context during the redirection at the end of a SAML SSO Flow. Consequently, an attacker may perform any authenticated action as the victim once the victim’s browser loaded the SAML IdP initiated SSO link for the malicious service provider. Note: SP registration is commonly an unrestricted operation in IdPs, hence not requiring particular permissions or publicly accessible to ease the IdP interoperability. This issue is fixed in version 0.4.14. Users unable to upgrade may perform external validation of URLs provided in SAML metadata, or restrict the ability for end-users to upload arbitrary metadata. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
] | https://github.com/crewjam/saml | [] | [
"a60693989d9efbca89bb06007e3269a7da3cc214"
] |
CVE-2022-41912 | 2022-11-28T15:15:10 | 2025-01-15T03:04:53.380049 | The crewjam/saml go library prior to version 0.4.9 is vulnerable to an authentication bypass when processing SAML responses containing multiple Assertion elements. This issue has been corrected in version 0.4.9. There are no workarounds other than upgrading to a fixed version. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/crewjam/saml | [] | [
"a60693989d9efbca89bb06007e3269a7da3cc214"
] |
CVE-2020-27846 | 2020-12-21T16:15:13 | 2025-01-14T08:44:31.904466 | A signature verification vulnerability exists in crewjam/saml. This flaw allows an attacker to bypass SAML Authentication. The highest threat from this vulnerability is to confidentiality, integrity, as well as system availability. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/crewjam/saml | [] | [
"a60693989d9efbca89bb06007e3269a7da3cc214"
] |
CVE-2024-5154 | 2024-06-12T09:15:19 | 2025-02-19T03:42:09.483829 | A flaw was found in cri-o. A malicious container can create a symbolic link to arbitrary files on the host via directory traversal (“../“). This flaw allows the container to read and write to arbitrary files on the host system. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:N",
"type": "CVSS_V3"
}
] | https://github.com/cri-o/cri-o | [] | [
"a85ea609db33ce5da282a02873021a3fdfb6562f"
] |
CVE-2022-0811 | 2022-03-16T15:15:16 | 2025-02-19T03:25:21.952374 | A flaw was found in CRI-O in the way it set kernel options for a pod. This issue allows anyone with rights to deploy a pod on a Kubernetes cluster that uses the CRI-O runtime to achieve a container escape and arbitrary code execution as root on the cluster node, where the malicious pod was deployed. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cri-o/cri-o | [] | [
"91f84584bc4b49fdc8aad716fdc7ac2a165d9f63"
] |
CVE-2022-1708 | 2022-06-07T18:15:11 | 2025-02-19T03:25:54.299667 | A vulnerability was found in CRI-O that causes memory or disk space exhaustion on the node for anyone with access to the Kube API. The ExecSync request runs commands in a container and logs the output of the command. This output is then read by CRI-O after command execution, and it is read in a manner where the entire file corresponding to the output of the command is read in. Thus, if the output of the command is large it is possible to exhaust the memory or the disk space of the node when CRI-O reads the output of the command. The highest threat from this vulnerability is system availability. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cri-o/cri-o | [] | [
"a85ea609db33ce5da282a02873021a3fdfb6562f"
] |
CVE-2022-2995 | 2022-09-19T20:15:12 | 2025-02-19T03:27:08.649106 | Incorrect handling of the supplementary groups in the CRI-O container engine might lead to sensitive information disclosure or possible data modification if an attacker has direct access to the affected container where supplementary groups are used to set access permissions and is able to execute a binary code in that container. | [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N",
"type": "CVSS_V3"
}
] | https://github.com/cri-o/cri-o | [] | [
"a85ea609db33ce5da282a02873021a3fdfb6562f"
] |
CVE-2022-0532 | 2022-02-09T23:15:16 | 2025-02-19T03:24:48.052369 | An incorrect sysctls validation vulnerability was found in CRI-O 1.18 and earlier. The sysctls from the list of "safe" sysctls specified for the cluster will be applied to the host if an attacker is able to create a pod with a hostIPC and hostNetwork kernel namespace. | [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:L",
"type": "CVSS_V3"
}
] | https://github.com/cri-o/cri-o | [] | [
"a85ea609db33ce5da282a02873021a3fdfb6562f"
] |
CVE-2019-14891 | 2019-11-25T11:15:11 | 2025-02-19T02:48:20.798554 | A flaw was found in cri-o, as a result of all pod-related processes being placed in the same memory cgroup. This can result in container management (conmon) processes being killed if a workload process triggers an out-of-memory (OOM) condition for the cgroup. An attacker could abuse this flaw to get host network access on an cri-o host. | [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L",
"type": "CVSS_V3"
}
] | https://github.com/cri-o/cri-o | [] | [
"a85ea609db33ce5da282a02873021a3fdfb6562f"
] |
CVE-2018-1000400 | 2018-05-18T18:29:00 | 2025-01-14T07:20:14.998240 | Kubernetes CRI-O version prior to 1.9 contains a Privilege Context Switching Error (CWE-270) vulnerability in the handling of ambient capabilities that can result in containers running with elevated privileges, allowing users abilities they should not have. This attack appears to be exploitable via container execution. This vulnerability appears to have been fixed in 1.9. | [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cri-o/cri-o | [] | [
"a85ea609db33ce5da282a02873021a3fdfb6562f"
] |
CVE-2023-27484 | 2023-03-09T21:15:11 | 2025-01-14T11:36:31.778754 | crossplane-runtime is a set of go libraries used to build Kubernetes controllers in Crossplane and its related stacks. In affected versions an already highly privileged user able to create or update Compositions can specify an arbitrarily high index in a patch's `ToFieldPath`, which could lead to excessive memory usage once such Composition is selected for a Composite resource. Compositions allow users to specify patches inserting elements into arrays at an arbitrary index. When a Composition is selected for a Composite Resource, patches are evaluated and if a specified index is greater than the current size of the target slice, Crossplane will grow that slice up to the specified index, which could lead to an excessive amount of memory usage and therefore the Pod being OOM-Killed. The index is already capped to the maximum value for a uint32 (4294967295) when parsed, but that is still an unnecessarily large value. This issue has been addressed in versions 1.11.2, 1.10.3, and 1.9.2. Users are advised to upgrade. Users unable to upgrade can restrict write privileges on Compositions to only admin users as a workaround. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/crossplane/crossplane | [] | [
"6b674f868403e92fa40d49a8a0385352d8d32e39"
] |
CVE-2023-38495 | 2023-07-27T19:15:10 | 2025-02-19T03:31:17.901954 | Crossplane is a framework for building cloud native control planes without needing to write code. In versions prior to 1.11.5, 1.12.3, and 1.13.0, Crossplane's image backend does not validate the byte contents of Crossplane packages. As such, Crossplane does not detect if an attacker has tampered with a Package. The problem has been fixed in 1.11.5, 1.12.3 and 1.13.0. As a workaround, only use images from trusted sources and keep Package editing/creating privileges to administrators only. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/crossplane/crossplane | [] | [
"ad3af882d09231d80a6e066bd4f72b9b543c76b6"
] |
CVE-2023-37900 | 2023-07-27T16:15:10 | 2025-02-19T03:33:02.233685 | Crossplane is a framework for building cloud native control planes without needing to write code. In versions prior to 1.11.5, 1.12.3, and 1.13.0, a high-privileged user could create a Package referencing an arbitrarily large image containing that Crossplane would then parse, possibly resulting in exhausting all the available memory and therefore in the container being OOMKilled. The impact is limited due to the high privileges required to be able to create the Package and the eventually consistency nature of controller. This issue is fixed in versions 1.11.5, 1.12.3, and 1.13.0. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L",
"type": "CVSS_V3"
}
] | https://github.com/crossplane/crossplane | [] | [
"ad3af882d09231d80a6e066bd4f72b9b543c76b6"
] |
CVE-2023-27483 | 2023-03-09T21:15:11 | 2025-01-15T04:48:11.983112 | crossplane-runtime is a set of go libraries used to build Kubernetes controllers in Crossplane and its related stacks. An out of memory panic vulnerability has been discovered in affected versions. Applications that use the `Paved` type's `SetValue` method with user provided input without proper validation might use excessive amounts of memory and cause an out of memory panic. In the fieldpath package, the Paved.SetValue method sets a value on the Paved object according to the provided path, without any validation. This allows setting values in slices at any provided index, which grows the target array up to the requested index, the index is currently capped at max uint32 (4294967295) given how indexes are parsed, but that is still an unnecessarily large value. If callers are not validating paths' indexes on their own, which most probably are not going to do, given that the input is parsed directly in the SetValue method, this could allow users to consume arbitrary amounts of memory. Applications that do not use the `Paved` type's `SetValue` method are not affected. This issue has been addressed in versions 0.16.1 and 0.19.2. Users are advised to upgrade. Users unable to upgrade can parse and validate the path before passing it to the `SetValue` method of the `Paved` type, constraining the index size as deemed appropriate. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/crossplane/crossplane-runtime | [] | [
"1fc35a41fccae56fdc26f075e737f4a7dc4a7a58"
] |
CVE-2021-43839 | 2021-12-21T17:15:08 | 2025-01-15T02:08:26.386075 | Cronos is a commercial implementation of a blockchain. In Cronos nodes running versions before v0.6.5, it is possible to take transaction fees from Cosmos SDK's FeeCollector for the current block by sending a custom crafted MsgEthereumTx. This problem has been patched in Cronos v0.6.5. There are no tested workarounds. All validator node operators are recommended to upgrade to Cronos v0.6.5 at their earliest possible convenience. | null | https://github.com/crypto-org-chain/cronos | [] | [
"087d3cdb4b003c92f77db8fe530679806e6520d6"
] |
CVE-2022-43996 | 2022-12-13T22:15:10 | 2025-01-14T11:14:26.768958 | The csaf_provider package before 0.8.2 allows XSS via a crafted CSAF document uploaded as text/html. The endpoint upload allows valid CSAF advisories (JSON format) to be uploaded with Content-Type text/html and filenames ending in .html. When subsequently accessed via web browser, these advisories are served and interpreted as HTML pages. Such uploaded advisories can contain JavaScript code that will execute within the browser context of users inspecting the advisory. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
] | https://github.com/csaf-poc/csaf_distribution | [] | [
"f6fa366ee571061bbfd6a3f311cef0ba18b9548e"
] |
CVE-2023-46741 | 2024-01-03T17:15:10 | 2025-01-15T05:00:16.077272 | CubeFS is an open-source cloud-native file storage system. A vulnerability was found in CubeFS prior to version 3.3.1 that could allow users to read sensitive data from the logs which could allow them escalate privileges. CubeFS leaks configuration keys in plaintext format in the logs. These keys could allow anyone to carry out operations on blobs that they otherwise do not have permissions for. For example, an attacker that has succesfully retrieved a secret key from the logs can delete blogs from the blob store. The attacker can either be an internal user with limited privileges to read the log, or they can be an external user who has escalated privileges sufficiently to access the logs. The vulnerability has been patched in v3.3.1. There is no other mitigation than upgrading.
| [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cubefs/cubefs | [] | [
"00e7ae59d56508e1926862adf83ef4329819ae6a"
] |
CVE-2023-46740 | 2024-01-03T17:15:10 | 2025-01-15T05:00:18.200412 | CubeFS is an open-source cloud-native file storage system. Prior to version 3.3.1, CubeFS used an insecure random string generator to generate user-specific, sensitive keys used to authenticate users in a CubeFS deployment. This could allow an attacker to predict and/or guess the generated string and impersonate a user thereby obtaining higher privileges. When CubeFS creates new users, it creates a piece of sensitive information for the user called the “accessKey”. To create the "accesKey", CubeFS uses an insecure string generator which makes it easy to guess and thereby impersonate the created user. An attacker could leverage the predictable random string generator and guess a users access key and impersonate the user to obtain higher privileges. The issue has been fixed in v3.3.1. There is no other mitigation than to upgrade. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cubefs/cubefs | [] | [
"00e7ae59d56508e1926862adf83ef4329819ae6a"
] |
CVE-2023-46739 | 2024-01-03T17:15:10 | 2025-01-15T05:00:20.002937 | CubeFS is an open-source cloud-native file storage system. A vulnerability was found during in the CubeFS master component in versions prior to 3.3.1 that could allow an untrusted attacker to steal user passwords by carrying out a timing attack. The root case of the vulnerability was that CubeFS used raw string comparison of passwords. The vulnerable part of CubeFS was the UserService of the master component. The UserService gets instantiated when starting the server of the master component. The issue has been patched in v3.3.1. For impacted users, there is no other way to mitigate the issue besides upgrading. | [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/cubefs/cubefs | [] | [
"00e7ae59d56508e1926862adf83ef4329819ae6a"
] |
CVE-2023-46742 | 2024-01-03T17:15:11 | 2025-01-15T05:00:17.109948 | CubeFS is an open-source cloud-native file storage system. CubeFS prior to version 3.3.1 was found to leak users secret keys and access keys in the logs in multiple components. When CubeCS creates new users, it leaks the users secret key. This could allow a lower-privileged user with access to the logs to retrieve sensitive information and impersonate other users with higher privileges than themselves. The issue has been patched in v3.3.1. There is no other mitigation than upgrading CubeFS. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/cubefs/cubefs | [] | [
"00e7ae59d56508e1926862adf83ef4329819ae6a"
] |
CVE-2023-46738 | 2024-01-03T16:15:08 | 2025-01-15T05:00:23.536706 | CubeFS is an open-source cloud-native file storage system. A security vulnerability was found in CubeFS HandlerNode in versions prior to 3.3.1 that could allow authenticated users to send maliciously-crafted requests that would crash the ObjectNode and deny other users from using it. The root cause was improper handling of incoming HTTP requests that could allow an attacker to control the ammount of memory that the ObjectNode would allocate. A malicious request could make the ObjectNode allocate more memory that the machine had available, and the attacker could exhaust memory by way of a single malicious request. An attacker would need to be authenticated in order to invoke the vulnerable code with their malicious request and have permissions to delete objects. In addition, the attacker would need to know the names of existing buckets of the CubeFS deployment - otherwise the request would be rejected before it reached the vulnerable code. As such, the most likely attacker is an inside user or an attacker that has breached the account of an existing user in the cluster. The issue has been patched in v3.3.1. There is no other mitigation besides upgrading. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/cubefs/cubefs | [] | [
"00e7ae59d56508e1926862adf83ef4329819ae6a"
] |
CVE-2023-30512 | 2023-04-12T06:15:07 | 2025-02-07T22:47:40.246956 | CubeFS through 3.2.1 allows Kubernetes cluster-level privilege escalation. This occurs because DaemonSet has cfs-csi-cluster-role and can thus list all secrets, including the admin secret. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/cubefs/cubefs | [] | [
"00e7ae59d56508e1926862adf83ef4329819ae6a"
] |
CVE-2024-35223 | 2024-05-23T09:15:09 | 2025-01-15T05:14:09.830302 | Dapr is a portable, event-driven, runtime for building distributed applications across cloud and edge. Dapr sends the app token of the invoker app instead of the app token of the invoked app. This causes of a leak of the application token of the invoker app to the invoked app when using Dapr as a gRPC proxy for remote service invocation. This vulnerability impacts Dapr users who use Dapr as a gRPC proxy for remote service invocation as well as the Dapr App API token functionality. An attacker could exploit this vulnerability to gain access to the app token of the invoker app, potentially compromising security and authentication mechanisms. This vulnerability was patched in version 1.13.3.
| null | https://github.com/dapr/dapr | [] | [
"9dbd0ab8733185008ec69ac0fa8d6546320b7799"
] |
CVE-2023-37918 | 2023-07-21T21:15:11 | 2025-01-15T04:56:06.542729 | Dapr is a portable, event-driven, runtime for building distributed applications across cloud and edge. A vulnerability has been found in Dapr that allows bypassing API token authentication, which is used by the Dapr sidecar to authenticate calls coming from the application, with a well-crafted HTTP request. Users who leverage API token authentication are encouraged to upgrade Dapr to 1.10.9 or to 1.11.2. This vulnerability impacts Dapr users who have configured API token authentication. An attacker could craft a request that is always allowed by the Dapr sidecar over HTTP, even if the `dapr-api-token` in the request is invalid or missing. The issue has been fixed in Dapr 1.10.9 or to 1.11.2. There are no known workarounds for this vulnerability.
| [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/dapr/dapr | [] | [
"9dbd0ab8733185008ec69ac0fa8d6546320b7799"
] |
CVE-2022-38817 | 2022-10-03T13:15:11 | 2025-02-19T03:29:35.853847 | Dapr Dashboard v0.1.0 through v0.10.0 is vulnerable to Incorrect Access Control that allows attackers to obtain sensitive data. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/dapr/dashboard | [] | [
"febc4a7bca4cb992bc3fdd9799a0a87b5922f8f6"
] |
CVE-2023-27163 | 2023-03-31T20:15:07 | 2025-02-18T18:49:50.036741 | request-baskets up to v1.2.1 was discovered to contain a Server-Side Request Forgery (SSRF) via the component /api/baskets/{name}. This vulnerability allows attackers to access network resources and sensitive information via a crafted API request. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N",
"type": "CVSS_V3"
}
] | https://github.com/darklynx/request-baskets | [] | [
"a36e2ae402204050ce42a78d750785b4b10e7958"
] |
CVE-2020-26277 | 2020-12-21T22:15:13 | 2025-01-15T01:44:50.923094 | DBdeployer is a tool that deploys MySQL database servers easily. In DBdeployer before version 1.58.2, users unpacking a tarball may use a maliciously packaged tarball that contains symlinks to files external to the target. In such scenario, an attacker could induce dbdeployer to write into a system file, thus altering the computer defenses. For the attack to succeed, the following factors need to contribute: 1) The user is logged in as root. While dbdeployer is usable as root, it was designed to run as unprivileged user. 2) The user has taken a tarball from a non secure source, without testing the checksum. When the tarball is retrieved through dbdeployer, the checksum is compared before attempting to unpack. This has been fixed in version 1.58.2. | [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:N/I:H/A:N",
"type": "CVSS_V3"
}
] | https://github.com/datacharmer/dbdeployer | [] | [
"9fb4cd3dda124d20151cc69a7d64219386eb1ce9"
] |
CVE-2016-15036 | 2023-12-23T20:15:37 | 2025-01-15T01:06:58.958418 | ** UNSUPPORTED WHEN ASSIGNED ** A vulnerability was found in Deis Workflow Manager up to 2.3.2. It has been classified as problematic. This affects an unknown part. The manipulation leads to race condition. The complexity of an attack is rather high. The exploitability is told to be difficult. Upgrading to version 2.3.3 is able to address this issue. The patch is named 31fe3bccbdde134a185752e53380330d16053f7f. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-248847. NOTE: This vulnerability only affects products that are no longer supported by the maintainer. | [
{
"score": "CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/deis/workflow-manager | [] | [
"2582640c2c13c5f5f9b860d62d2b7c3bc7f4826b"
] |
CVE-2021-21272 | 2021-01-25T19:15:12 | 2025-01-15T01:47:07.931263 | ORAS is open source software which enables a way to push OCI Artifacts to OCI Conformant registries. ORAS is both a CLI for initial testing and a Go Module. In ORAS from version 0.4.0 and before version 0.9.0, there is a "zip-slip" vulnerability. The directory support feature allows the downloaded gzipped tarballs to be automatically extracted to the user-specified directory where the tarball can have symbolic links and hard links. A well-crafted tarball or tarballs allow malicious artifact providers linking, writing, or overwriting specific files on the host filesystem outside of the user-specified directory unexpectedly with the same permissions as the user who runs `oras pull`. Users of the affected versions are impacted if they are `oras` CLI users who runs `oras pull`, or if they are Go programs, which invoke `github.com/deislabs/oras/pkg/content.FileStore`. The problem has been fixed in version 0.9.0. For `oras` CLI users, there is no workarounds other than pulling from a trusted artifact provider. For `oras` package users, the workaround is to not use `github.com/deislabs/oras/pkg/content.FileStore`, and use other content stores instead, or pull from a trusted artifact provider. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N",
"type": "CVSS_V3"
}
] | https://github.com/deislabs/oras | [] | [
"237ac925cb6a308a5523cc048292bb53037f6975"
] |
CVE-2022-34375 | 2022-08-30T21:15:08 | 2025-01-14T11:01:49.194402 | Dell Container Storage Modules 1.2 contains a path traversal vulnerability in goiscsi and gobrick libraries. A remote authenticated malicious user with low privileges could exploit this vulnerability leading to unintentional access to path outside of restricted directory. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/dell/csm | [] | [
"5c433c6b1cf704be3adb28e72e34c9098dc0c12f"
] |
CVE-2022-34374 | 2022-08-30T21:15:08 | 2025-01-14T11:01:47.941587 | Dell Container Storage Modules 1.2 contains an OS command injection in goiscsi and gobrick libraries. A remote authenticated malicious user with low privileges could exploit this vulnerability leading to to execute arbitrary OS commands on the affected system. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/dell/csm | [] | [
"5c433c6b1cf704be3adb28e72e34c9098dc0c12f"
] |
CVE-2024-8005 | 2024-08-20T14:15:11 | 2024-10-08T04:25:25.581629 | A vulnerability was found in demozx gf_cms 1.0/1.0.1. It has been classified as critical. This affects the function init of the file internal/logic/auth/auth.go of the component JWT Authentication. The manipulation leads to hard-coded credentials. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 1.0.2 is able to address this issue. The patch is named be702ada7cb6fdabc02689d90b38139c827458a5. It is recommended to upgrade the affected component. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/demozx/gf_cms | [] | [
"9bdb687920e57adad6e3a716e35b96dd3f80e3fe"
] |
CVE-2020-26222 | 2020-11-13T16:15:18 | 2025-01-15T01:46:10.424417 | Dependabot is a set of packages for automated dependency management for Ruby, JavaScript, Python, PHP, Elixir, Rust, Java, .NET, Elm and Go. In Dependabot-Core from version 0.119.0.beta1 before version 0.125.1, there is a remote code execution vulnerability in dependabot-common and dependabot-go_modules when a source branch name contains malicious injectable bash code. For example, if Dependabot is configured to use the following source branch name: "/$({curl,127.0.0.1})", Dependabot will make a HTTP request to the following URL: 127.0.0.1 when cloning the source repository. The fix was applied to version 0.125.1. As a workaround, one can escape the branch name prior to passing it to the Dependabot::Source class. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/dependabot/dependabot-core | [] | [
"8dc6ce1966e1637db91f21aa89b331ee83e59ec6"
] |
CVE-2020-15391 | 2020-07-23T20:15:11 | 2025-02-19T03:08:43.680230 | The UI in DevSpace 4.13.0 allows web sites to execute actions on pods (on behalf of a victim) because of a lack of authentication for the WebSocket protocol. This leads to remote code execution. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/devspace-cloud/devspace | [] | [
"c29f25a287002e41d2208301763268089551ec95"
] |
CVE-2024-23656 | 2024-01-25T20:15:41 | 2025-01-15T05:08:05.090261 | Dex is an identity service that uses OpenID Connect to drive authentication for other apps. Dex 2.37.0 serves HTTPS with insecure TLS 1.0 and TLS 1.1. `cmd/dex/serve.go` line 425 seemingly sets TLS 1.2 as minimum version, but the whole `tlsConfig` is ignored after `TLS cert reloader` was introduced in v2.37.0. Configured cipher suites are not respected either. This issue is fixed in Dex 2.38.0. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/dexidp/dex | [] | [
"71bbbee0752781a65d7f9dde198d58f97ddec097"
] |
CVE-2020-27847 | 2021-05-28T11:15:07 | 2025-02-19T03:09:48.000373 | A vulnerability exists in the SAML connector of the github.com/dexidp/dex library used to process SAML Signature Validation. This flaw allows an attacker to bypass SAML authentication. The highest threat from this vulnerability is to confidentiality, integrity, as well as system availability. This flaw affects dex versions before 2.27.0. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/dexidp/dex | [] | [
"71bbbee0752781a65d7f9dde198d58f97ddec097"
] |
Subsets and Splits