Datasets:
ASSERT-KTH
/
go_vulnerabilities_2019_2024

Dataset card Data Studio Files Community
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-24797
2022-03-31T23:15:08
2025-01-15T02:17:55.836491
Pomerium is an identity-aware access proxy. In distributed service mode, Pomerium's Authenticate service exposes pprof debug and prometheus metrics handlers to untrusted traffic. This can leak potentially sensitive environmental information or lead to limited denial of service conditions. This issue is patched in version v0.17.1 Workarounds: Block access to `/debug` and `/metrics` paths on the authenticate service. This can be done with any L7 proxy, including Pomerium's own proxy service.
[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H", "type": "CVSS_V3" } ]
https://github.com/pomerium/pomerium
[]
[ "7692b2ac4966f2606e1cea376dd33a14c984d9c9" ]
CVE-2020-24130
2021-08-20T20:15:06
2025-02-19T03:10:45.342561
A cross site request forgery (CSRF) vulnerability in the configure.html component of Ponzu 0.11.0 allows attackers to change user and administrator credentials, and add or delete administrator accounts.
[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H", "type": "CVSS_V3" } ]
https://github.com/ponzu-cms/ponzu
[]
[ "f0472b990d7022e2022538d54286bd11ecfaa912" ]
CVE-2020-27519
2021-04-30T14:15:08
2025-01-15T01:45:21.547824
Pritunl Client v1.2.2550.20 contains a local privilege escalation vulnerability in the pritunl-service component. The attack vector is: malicious openvpn config. A local attacker could leverage the log and log-append along with log injection to create or append to privileged script files and execute code as root/SYSTEM.
[ { "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]
https://github.com/pritunl/pritunl-client-electron
[]
[ "4ec6a7c7fca16c30d3fb21f2c01a4969673b2b02" ]
CVE-2022-25372
2022-02-20T20:15:18
2025-01-15T02:19:10.402030
Pritunl Client through 1.2.3019.52 on Windows allows local privilege escalation, related to an ACL entry for CREATOR OWNER in platform_windows.go.
[ { "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]
https://github.com/pritunl/pritunl-client-electron
[]
[ "4ec6a7c7fca16c30d3fb21f2c01a4969673b2b02" ]
CVE-2020-25989
2020-11-19T21:15:12
2025-01-15T01:44:48.086489
Privilege escalation via arbitrary file write in pritunl electron client 1.0.1116.6 through v1.2.2550.20. Successful exploitation of the issue may allow an attacker to execute code on the effected system with root privileges.
[ { "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]
https://github.com/pritunl/pritunl-client-electron
[]
[ "4ec6a7c7fca16c30d3fb21f2c01a4969673b2b02" ]
CVE-2016-7064
2020-07-21T17:15:11
2025-01-14T06:46:59.371014
A flaw was found in pritunl-client before version 1.0.1116.6. A lack of signature verification leads to sensitive information leakage
[ { "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/pritunl/pritunl-client-electron
[]
[ "4ec6a7c7fca16c30d3fb21f2c01a4969673b2b02" ]
CVE-2016-7063
2020-07-21T17:15:11
2025-01-14T06:47:00.535897
A flaw was found in pritunl-client before version 1.0.1116.6. Arbitrary write to user specified path may lead to privilege escalation.
[ { "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/pritunl/pritunl-client-electron
[]
[ "4ec6a7c7fca16c30d3fb21f2c01a4969673b2b02" ]
CVE-2024-39897
2024-07-09T19:15:12
2025-01-15T05:15:11.156527
zot is an OCI image registry. Prior to 2.1.0, the cache driver `GetBlob()` allows read access to any blob without access control check. If a Zot `accessControl` policy allows users read access to some repositories but restricts read access to other repositories and `dedupe` is enabled (it is enabled by default), then an attacker who knows the name of an image and the digest of a blob (that they do not have read access to), they may maliciously read it via a second repository they do have read access to. This attack is possible because [`ImageStore.CheckBlob()` calls `checkCacheBlob()`](https://github.com/project-zot/zot/blob/v2.1.0-rc2/pkg/storage/imagestore/imagestore.go#L1158-L1159) to find the blob a global cache by searching for the digest. If it is found, it is copied to the user requested repository with `copyBlob()`. The attack may be mitigated by configuring "dedupe": false in the "storage" settings. The vulnerability is fixed in 2.1.0.
null
https://github.com/project-zot/zot
[]
[ "a4b6892a9c276de41e4858e89774c07032410993" ]
CVE-2025-23208
2025-01-17T23:15:13
2025-01-28T15:41:48.395996
zot is a production-ready vendor-neutral OCI image registry. The group data stored for users in the boltdb database (meta.db) is an append-list so group revocations/removals are ignored in the API. SetUserGroups is alled on login, but instead of replacing the group memberships, they are appended. This may be due to some conflict with the group definitions in the config file, but that wasn't obvious to me if it were the case. Any Zot configuration that relies on group-based authorization will not respect group remove/revocation by an IdP. This issue has been addressed in version 2.1.2. All users are advised to upgrade. There are no known workarounds for this vulnerability.
null
https://github.com/project-zot/zot
[]
[ "a4b6892a9c276de41e4858e89774c07032410993" ]
CVE-2024-39690
2024-08-20T15:15:21
2024-10-08T04:17:42.801619
Capsule is a multi-tenancy and policy-based framework for Kubernetes. In Capsule v0.7.0 and earlier, the tenant-owner can patch any arbitrary namespace that has not been taken over by a tenant (i.e., namespaces without the ownerReference field), thereby gaining control of that namespace.
[ { "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/projectcapsule/capsule
[]
[ "206ce71ec69b81332568e0488e055690c93ce48a" ]
CVE-2021-32783
2021-07-23T22:15:08
2025-01-15T01:54:39.929587
Contour is a Kubernetes ingress controller using Envoy proxy. In Contour before version 1.17.1 a specially crafted ExternalName type Service may be used to access Envoy's admin interface, which Contour normally prevents from access outside the Envoy container. This can be used to shut down Envoy remotely (a denial of service), or to expose the existence of any Secret that Envoy is using for its configuration, including most notably TLS Keypairs. However, it *cannot* be used to get the *content* of those secrets. Since this attack allows access to the administration interface, a variety of administration options are available, such as shutting down the Envoy or draining traffic. In general, the Envoy admin interface cannot easily be used for making changes to the cluster, in-flight requests, or backend services, but it could be used to shut down or drain Envoy, change traffic routing, or to retrieve secret metadata, as mentioned above. The issue will be addressed in Contour v1.18.0 and a cherry-picked patch release, v1.17.1, has been released to cover users who cannot upgrade at this time. For more details refer to the linked GitHub Security Advisory.
[ { "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:H", "type": "CVSS_V3" } ]
https://github.com/projectcontour/contour
[]
[ "b40292b056a715f8b6e96546779985df5c35ec51" ]
CVE-2020-15127
2020-08-05T21:15:12
2025-01-14T08:42:22.928863
In Contour ( Ingress controller for Kubernetes) before version 1.7.0, a bad actor can shut down all instances of Envoy, essentially killing the entire ingress data plane. GET requests to /shutdown on port 8090 of the Envoy pod initiate Envoy's shutdown procedure. The shutdown procedure includes flipping the readiness endpoint to false, which removes Envoy from the routing pool. When running Envoy (For example on the host network, pod spec hostNetwork=true), the shutdown manager's endpoint is accessible to anyone on the network that can reach the Kubernetes node that's running Envoy. There is no authentication in place that prevents a rogue actor on the network from shutting down Envoy via the shutdown manager endpoint. Successful exploitation of this issue will lead to bad actors shutting down all instances of Envoy, essentially killing the entire ingress data plane. This is fixed in version 1.7.0.
[ { "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/projectcontour/contour
[]
[ "b40292b056a715f8b6e96546779985df5c35ec51" ]
CVE-2024-5262
2024-06-05T04:15:11
2025-01-14T12:17:22.693737
Files or Directories Accessible to External Parties vulnerability in smb server in ProjectDiscovery Interactsh allows remote attackers to read/write any files in the directory and subdirectories of where the victim runs interactsh-server via anonymous login.
[ { "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/projectdiscovery/interactsh
[]
[ "c7a1b32a1a3b11aa131dd3438d85c4f4c3386cee" ]
CVE-2023-36474
2023-06-28T22:15:09
2025-01-14T11:48:13.689885
Interactsh is an open-source tool for detecting out-of-band interactions. Domains configured with interactsh server prior to version 1.0.0 were vulnerable to subdomain takeover for a specific subdomain, i.e `app.` Interactsh server used to create cname entries for `app` pointing to `projectdiscovery.github.io` as default, which intended to used for hosting interactsh web client using GitHub pages. This is a security issue with a self-hosted interactsh server in which the user may not have configured a web client but still have a CNAME entry pointing to GitHub pages, making them vulnerable to subdomain takeover. This allows a threat actor to host / run arbitrary client side code (cross-site scripting) in a user's browser when browsing the vulnerable subdomain. Version 1.0.0 fixes this issue by making CNAME optional, rather than default.
[ { "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/projectdiscovery/interactsh
[]
[ "c7a1b32a1a3b11aa131dd3438d85c4f4c3386cee" ]
CVE-2024-43405
2024-09-04T16:15:06
2025-02-05T08:49:42.654427
Nuclei is a vulnerability scanner powered by YAML based templates. Starting in version 3.0.0 and prior to version 3.3.2, a vulnerability in Nuclei's template signature verification system could allow an attacker to bypass the signature check and possibly execute malicious code via custom code template. The vulnerability is present in the template signature verification process, specifically in the `signer` package. The vulnerability stems from a discrepancy between how the signature verification process and the YAML parser handle newline characters, combined with the way multiple signatures are processed. This allows an attacker to inject malicious content into a template while maintaining a valid signature for the benign part of the template. CLI users are affected if they execute custom code templates from unverified sources. This includes templates authored by third parties or obtained from unverified repositories. SDK Users are affected if they are developers integrating Nuclei into their platforms, particularly if they permit the execution of custom code templates by end-users. The vulnerability is addressed in Nuclei v3.3.2. Users are strongly recommended to update to this version to mitigate the security risk. As an interim measure, users should refrain from using custom templates if unable to upgrade immediately. Only trusted, verified templates should be executed. Those who are unable to upgrade Nuclei should disable running custom code templates as a workaround.
[ { "score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]
https://github.com/projectdiscovery/nuclei
[]
[ "bb98eced070f4ae137b8cd2a7f887611bc1b9c93" ]
CVE-2023-37896
2023-08-04T16:15:09
2025-01-14T11:49:45.570230
Nuclei is a vulnerability scanner. Prior to version 2.9.9, a security issue in the Nuclei project affected users utilizing Nuclei as Go code (SDK) running custom templates. This issue did not affect CLI users. The problem was related to sanitization issues with payload loading in sandbox mode. There was a potential risk with payloads loading in sandbox mode. The issue occurred due to relative paths not being converted to absolute paths before doing the check for `sandbox` flag allowing arbitrary files to be read on the filesystem in certain cases when using Nuclei from `Go` SDK implementation. This issue has been fixed in version 2.9.9. The maintainers have also enabled sandbox by default for filesystem loading. This can be optionally disabled if required. The `-sandbox` option has been deprecated and is now divided into two new options: `-lfa` (allow local file access) which is enabled by default and `-lna` (restrict local network access) which can be enabled by users optionally. The `-lfa` allows file (payload) access anywhere on the system (disabling sandbox effectively), and `-lna` blocks connections to the local/private network.
[ { "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/projectdiscovery/nuclei
[]
[ "bb98eced070f4ae137b8cd2a7f887611bc1b9c93" ]
CVE-2021-29622
2021-05-19T20:15:07
2025-02-19T03:18:32.480565
Prometheus is an open-source monitoring system and time series database. In 2.23.0, Prometheus changed its default UI to the New ui. To ensure a seamless transition, the URL's prefixed by /new redirect to /. Due to a bug in the code, it is possible for an attacker to craft an URL that can redirect to any other URL, in the /new endpoint. If a user visits a prometheus server with a specially crafted address, they can be redirected to an arbitrary URL. The issue was patched in the 2.26.1 and 2.27.1 releases. In 2.28.0, the /new endpoint will be removed completely. The workaround is to disable access to /new via a reverse proxy in front of Prometheus.
[ { "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/prometheus/prometheus
[]
[ "3cafc58827d1ebd1a67749f88be4218f0bab3d8d" ]
CVE-2024-27102
2024-03-13T21:15:59
2025-01-23T23:51:20.318769
Wings is the server control plane for Pterodactyl Panel. This vulnerability impacts anyone running the affected versions of Wings. The vulnerability can potentially be used to access files and directories on the host system. The full scope of impact is exactly unknown, but reading files outside of a server's base directory (sandbox root) is possible. In order to use this exploit, an attacker must have an existing "server" allocated and controlled by Wings. Details on the exploitation of this vulnerability are embargoed until March 27th, 2024 at 18:00 UTC. In order to mitigate this vulnerability, a full rewrite of the entire server filesystem was necessary. Because of this, the size of the patch is massive, however effort was made to reduce the amount of breaking changes. Users are advised to update to version 1.11.9. There are no known workarounds for this vulnerability.
[ { "score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H", "type": "CVSS_V3" } ]
https://github.com/pterodactyl/wings
[]
[ "c0063d2c6125f52e566bc7e7546d4533a47db7a3" ]
CVE-2024-34066
2024-05-03T18:15:09
2025-01-15T05:13:40.831940
Pterodactyl wings is the server control plane for Pterodactyl Panel. If the Wings token is leaked either by viewing the node configuration or posting it accidentally somewhere, an attacker can use it to gain arbitrary file write and read access on the node the token is associated to. This issue has been addressed in version 1.11.12 and users are advised to upgrade. Users unable to upgrade may enable the `ignore_panel_config_updates` option as a workaround.
null
https://github.com/pterodactyl/wings
[]
[ "c0063d2c6125f52e566bc7e7546d4533a47db7a3" ]
CVE-2024-34068
2024-05-03T18:15:09
2025-01-15T05:13:41.698949
Pterodactyl wings is the server control plane for Pterodactyl Panel. An authenticated user who has access to a game server is able to bypass the previously implemented access control (GHSA-6rg3-8h8x-5xfv) that prevents accessing internal endpoints of the node hosting Wings in the pull endpoint. This would allow malicious users to potentially access resources on local networks that would otherwise be inaccessible. This issue has been addressed in version 1.11.2 and users are advised to upgrade. Users unable to upgrade may enable the `api.disable_remote_download` option as a workaround.
null
https://github.com/pterodactyl/wings
[]
[ "c0063d2c6125f52e566bc7e7546d4533a47db7a3" ]
CVE-2023-25152
2023-02-08T19:15:11
2025-01-15T04:44:31.945606
Wings is Pterodactyl's server control plane. Affected versions are subject to a vulnerability which can be used to create new files and directory structures on the host system that previously did not exist, potentially allowing attackers to change their resource allocations, promote their containers to privileged mode, or potentially add ssh authorized keys to allow the attacker access to a remote shell on the target machine. In order to use this exploit, an attacker must have an existing "server" allocated and controlled by the Wings Daemon. This vulnerability has been resolved in version `v1.11.3` of the Wings Daemon, and has been back-ported to the 1.7 release series in `v1.7.3`. Anyone running `v1.11.x` should upgrade to `v1.11.3` and anyone running `v1.7.x` should upgrade to `v1.7.3`. There are no known workarounds for this vulnerability. ### Workarounds None at this time.
[ { "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/pterodactyl/wings
[]
[ "c0063d2c6125f52e566bc7e7546d4533a47db7a3" ]
CVE-2023-25168
2023-02-09T00:16:36
2025-01-15T04:44:34.461576
Wings is Pterodactyl's server control plane. This vulnerability can be used to delete files and directories recursively on the host system. This vulnerability can be combined with `GHSA-p8r3-83r8-jwj5` to overwrite files on the host system. In order to use this exploit, an attacker must have an existing "server" allocated and controlled by Wings. This vulnerability has been resolved in version `v1.11.4` of Wings, and has been back-ported to the 1.7 release series in `v1.7.4`. Anyone running `v1.11.x` should upgrade to `v1.11.4` and anyone running `v1.7.x` should upgrade to `v1.7.4`. There are no known workarounds for this issue.
[ { "score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:H/A:H", "type": "CVSS_V3" } ]
https://github.com/pterodactyl/wings
[]
[ "c0063d2c6125f52e566bc7e7546d4533a47db7a3" ]
CVE-2023-32080
2023-05-10T21:15:08
2025-01-14T11:43:01.982999
Wings is the server control plane for Pterodactyl Panel. A vulnerability affecting versions prior to 1.7.5 and versions 1.11.0 prior to 1.11.6 impacts anyone running the affected versions of Wings. This vulnerability can be used to gain access to the host system running Wings if a user is able to modify an server's install script or the install script executes code supplied by the user (either through environment variables, or commands that execute commands based off of user data). This vulnerability has been resolved in version `v1.11.6` of Wings, and has been back-ported to the 1.7 release series in `v1.7.5`. Anyone running `v1.11.x` should upgrade to `v1.11.6` and anyone running `v1.7.x` should upgrade to `v1.7.5`. There are no workarounds aside from upgrading. Running Wings with a rootless container runtime may mitigate the severity of any attacks, however the majority of users are using container runtimes that run as root as per the Wings documentation. SELinux may prevent attackers from performing certain operations against the host system, however privileged containers have a lot of freedom even on systems with SELinux enabled. It should be noted that this was a known attack vector, for attackers to easily exploit this attack it would require compromising an administrator account on a Panel. However, certain eggs (the data structure that holds the install scripts that get passed to Wings) have an issue where they are unknowingly executing shell commands with escalated privileges provided by untrusted user data.
[ { "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/pterodactyl/wings
[]
[ "c0063d2c6125f52e566bc7e7546d4533a47db7a3" ]
CVE-2021-32699
2021-06-22T20:15:08
2025-01-15T01:54:26.813831
Wings is the control plane software for the open source Pterodactyl game management system. All versions of Pterodactyl Wings prior to `1.4.4` are vulnerable to system resource exhaustion due to improper container process limits being defined. A malicious user can consume more resources than intended and cause downstream impacts to other clients on the same hardware, eventually causing the physical server to stop responding. Users should upgrade to `1.4.4` to mitigate the issue. There is no non-code based workaround for impacted versions of the software. Users running customized versions of this software can manually set a PID limit for containers created.
[ { "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H", "type": "CVSS_V3" } ]
https://github.com/pterodactyl/wings
[]
[ "c0063d2c6125f52e566bc7e7546d4533a47db7a3" ]
CVE-2023-27583
2023-03-13T21:15:14
2025-01-15T04:48:36.650777
PanIndex is a network disk directory index. In Panindex prior to version 3.1.3, a hard-coded JWT key `PanIndex` is used. An attacker can use the hard-coded JWT key to sign JWT token and perform any actions as a user with admin privileges. Version 3.1.3 has a patch for the issue. As a workaround, one may change the JWT key in the source code before compiling the project.
[ { "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/px-org/panindex
[]
[ "f9ba0aa405203c49ab3ba801bcca6914669940bc" ]
CVE-2023-32751
2023-06-08T21:15:17
2025-01-14T11:45:14.115021
Pydio Cells through 4.1.2 allows XSS. Pydio Cells implements the download of files using presigned URLs which are generated using the Amazon AWS SDK for JavaScript [1]. The secrets used to sign these URLs are hardcoded and exposed through the JavaScript files of the web application. Therefore, it is possible to generate valid signatures for arbitrary download URLs. By uploading an HTML file and modifying the download URL to serve the file inline instead of as an attachment, any included JavaScript code is executed when the URL is opened in a browser, leading to a cross-site scripting vulnerability.
[ { "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/pydio/cells
[]
[ "b9f2b173c5e8008041837d8320a847b9277bc390" ]
CVE-2023-32749
2023-06-08T20:15:09
2025-01-14T11:45:23.648503
Pydio Cells allows users by default to create so-called external users in order to share files with them. By modifying the HTTP request sent when creating such an external user, it is possible to assign the new user arbitrary roles. By assigning all roles to a newly created user, access to all cells and non-personal workspaces is granted.
[ { "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/pydio/cells
[]
[ "b9f2b173c5e8008041837d8320a847b9277bc390" ]
CVE-2023-32750
2023-06-08T21:15:17
2025-01-14T11:45:24.770585
Pydio Cells through 4.1.2 allows SSRF. For longer running processes, Pydio Cells allows for the creation of jobs, which are run in the background. The job "remote-download" can be used to cause the backend to send a HTTP GET request to a specified URL and save the response to a new file. The response file is then available in a user-specified folder in Pydio Cells.
[ { "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/pydio/cells
[]
[ "b9f2b173c5e8008041837d8320a847b9277bc390" ]
CVE-2021-41323
2021-09-30T19:15:07
2025-01-14T09:55:54.538725
Directory traversal in the Compress feature in Pydio Cells 2.2.9 allows remote authenticated users to overwrite personal files, or Cells files belonging to any user, via the format parameter.
[ { "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N", "type": "CVSS_V3" } ]
https://github.com/pydio/cells
[]
[ "a99933a3b75568ec6721e61053377ee8e88d438b" ]
CVE-2021-41325
2021-09-30T19:15:07
2025-01-14T09:55:50.849255
Broken access control for user creation in Pydio Cells 2.2.9 allows remote anonymous users to create standard users via the profile parameter. (In addition, such users can be granted several admin permissions via the Roles parameter.)
[ { "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N", "type": "CVSS_V3" } ]
https://github.com/pydio/cells
[]
[ "a99933a3b75568ec6721e61053377ee8e88d438b" ]
CVE-2021-41324
2021-09-30T21:15:08
2025-01-14T09:55:57.631747
Directory traversal in the Copy, Move, and Delete features in Pydio Cells 2.2.9 allows remote authenticated users to enumerate personal files (or Cells files belonging to any user) via the nodes parameter (for Copy and Move) or via the Path parameter (for Delete).
[ { "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/pydio/cells
[]
[ "a99933a3b75568ec6721e61053377ee8e88d438b" ]
CVE-2019-12901
2019-06-20T00:15:10
2025-01-14T07:41:18.224250
Pydio Cells before 1.5.0 fails to neutralize '../' elements, allowing an attacker with minimum privilege to Upload files to, and Delete files/folders from, an unprivileged directory, leading to Privilege escalation.
[ { "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/pydio/cells
[]
[ "a99933a3b75568ec6721e61053377ee8e88d438b" ]
CVE-2019-12903
2019-06-20T00:15:10
2025-01-14T07:41:14.353172
Pydio Cells before 1.5.0, when supplied with a Name field in an unexpected Unicode format, fails to handle this and includes the database column/table name as pert of the error message, exposing sensitive information.
[ { "score": "CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N", "type": "CVSS_V3" } ]
https://github.com/pydio/cells
[]
[ "a99933a3b75568ec6721e61053377ee8e88d438b" ]
CVE-2019-12902
2019-06-20T00:15:10
2025-01-14T07:41:14.669093
Pydio Cells before 1.5.0 does incomplete cleanup of a user's data upon deletion. This allows a new user, holding the same User ID as a deleted user, to restore the deleted user's data.
[ { "score": "CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N", "type": "CVSS_V3" } ]
https://github.com/pydio/cells
[]
[ "a99933a3b75568ec6721e61053377ee8e88d438b" ]
CVE-2020-12848
2020-06-05T13:15:10
2025-01-14T08:18:08.133949
In Pydio Cells 2.0.4, once an authenticated user shares a file selecting the create a public link option, a hidden shared user account is created in the backend with a random username. An anonymous user that obtains a valid public link can get the associated hidden account username and password and proceed to login to the web application. Once logged into the web application with the hidden user account, some actions that were not available with the public share link can now be performed.
[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N", "type": "CVSS_V3" } ]
https://github.com/pydio/cells
[]
[ "a99933a3b75568ec6721e61053377ee8e88d438b" ]
CVE-2020-12849
2020-06-05T13:15:10
2025-01-14T08:18:07.492174
Pydio Cells 2.0.4 allows any user to upload a profile image to the web application, including standard and shared user roles. These profile pictures can later be accessed directly with the generated URL by any unauthenticated or authenticated user.
[ { "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/pydio/cells
[]
[ "a99933a3b75568ec6721e61053377ee8e88d438b" ]
CVE-2020-12852
2020-06-04T20:15:11
2025-01-14T08:18:08.081094
The update feature for Pydio Cells 2.0.4 allows an administrator user to set a custom update URL and the public RSA key used to validate the downloaded update package. The update process involves downloading the updated binary file from a URL indicated in the update server response, validating its checksum and signature with the provided public key and finally replacing the current application binary. To complete the update process, the application’s service or appliance needs to be restarted. An attacker with administrator access can leverage the software update feature to force the application to download a custom binary that will replace current Pydio Cells binary. When the server or service is eventually restarted the attacker will be able to execute code under the privileges of the user running the application. In the Pydio Cells enterprise appliance this is with the privileges of the user named “pydio”.
[ { "score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]
https://github.com/pydio/cells
[]
[ "a99933a3b75568ec6721e61053377ee8e88d438b" ]
CVE-2020-12853
2020-06-04T20:15:11
2025-01-14T08:18:09.126484
Pydio Cells 2.0.4 allows XSS. A malicious user can either upload or create a new file that contains potentially malicious HTML and JavaScript code to personal folders or accessible cells.
[ { "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/pydio/cells
[]
[ "a99933a3b75568ec6721e61053377ee8e88d438b" ]
CVE-2020-12850
2020-06-11T02:15:10
2025-01-14T08:18:07.419117
The following vulnerability applies only to the Pydio Cells Enterprise OVF version 2.0.4. Prior versions of the Pydio Cells Enterprise OVF (such as version 2.0.3) have a looser policy restriction allowing the “pydio” user to execute any privileged command using sudo. In version 2.0.4 of the appliance, the user pydio is responsible for running all the services and binaries that are contained in the Pydio Cells web application package, such as mysqld, cells, among others. This user has privileges restricted to run those services and nothing more.
[ { "score": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]
https://github.com/pydio/cells
[]
[ "a99933a3b75568ec6721e61053377ee8e88d438b" ]
CVE-2020-12851
2020-06-04T20:15:11
2025-01-14T08:18:09.025954
Pydio Cells 2.0.4 allows an authenticated user to write or overwrite existing files in another user’s personal and cells folders (repositories) by uploading a custom generated ZIP file and leveraging the file extraction feature present in the web application. The extracted files will be placed in the targeted user folders.
[ { "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N", "type": "CVSS_V3" } ]
https://github.com/pydio/cells
[]
[ "a99933a3b75568ec6721e61053377ee8e88d438b" ]
CVE-2020-12847
2020-06-04T20:15:11
2025-01-14T08:18:08.184028
Pydio Cells 2.0.4 web application offers an administrative console named “Cells Console” that is available to users with an administrator role. This console provides an administrator user with the possibility of changing several settings, including the application’s mailer configuration. It is possible to configure a few engines to be used by the mailer application to send emails. If the user selects the “sendmail” option as the default one, the web application offers to edit the full path where the sendmail binary is hosted. Since there is no restriction in place while editing this value, an attacker authenticated as an administrator user could force the web application into executing any arbitrary binary.
[ { "score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]
https://github.com/pydio/cells
[]
[ "a99933a3b75568ec6721e61053377ee8e88d438b" ]
CVE-2022-21947
2022-04-01T07:15:07
2025-01-14T10:45:34.959021
A Exposure of Resource to Wrong Sphere vulnerability in Rancher Desktop of SUSE allows attackers in the local network to connect to the Dashboard API (steve) to carry out arbitrary actions. This issue affects: SUSE Rancher Desktop versions prior to V.
[ { "score": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]
https://github.com/rancher-sandbox/rancher-desktop
[]
[ "0b3eb2b1c53191c8f32007c310201f08441790e9" ]
CVE-2023-22649
2024-10-16T08:15:04
2025-02-19T03:31:11.399711
A vulnerability has been identified which may lead to sensitive data being leaked into Rancher's audit logs. [Rancher Audit Logging](https://ranchermanager.docs.rancher.com/how-to-guides/advanced-user-guides/enable-api-audit-log) is an opt-in feature, only deployments that have it enabled and have [AUDIT_LEVEL](https://ranchermanager.docs.rancher.com/how-to-guides/advanced-user-guides/enable-api-audit-log#audit-log-levels) set to `1 or above` are impacted by this issue.
[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N", "type": "CVSS_V3" } ]
https://github.com/rancher/rancher
[]
[ "f650ce839db0e2fb755dfff1ce28b005a5f1c0e3" ]
CVE-2022-43760
2023-06-01T13:15:10
2025-02-19T03:28:36.462448
An Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in SUSE Rancher allows users in some higher-privileged groups to to inject code that is executed within another user's browser, allowing the attacker to steal sensitive information, manipulate web content, or perform other malicious activities on behalf of the victims. This could result in a user with write access to the affected areas being able to act on behalf of an administrator, once an administrator opens the affected web page. This issue affects Rancher: from >= 2.6.0 before < 2.6.13, from >= 2.7.0 before < 2.7.4.
[ { "score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H", "type": "CVSS_V3" } ]
https://github.com/rancher/rancher
[]
[ "f650ce839db0e2fb755dfff1ce28b005a5f1c0e3" ]
CVE-2023-22648
2023-06-01T13:15:10
2025-02-19T03:31:11.188198
A Improper Privilege Management vulnerability in SUSE Rancher causes permission changes in Azure AD not to be reflected to users while they are logged in the Rancher UI. This would cause the users to retain their previous permissions in Rancher, even if they change groups on Azure AD, for example, to a lower privileged group, or are removed from a group, thus retaining their access to Rancher instead of losing it. This issue affects Rancher: from >= 2.6.7 before < 2.6.13, from >= 2.7.0 before < 2.7.4.
[ { "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/rancher/rancher
[]
[ "f650ce839db0e2fb755dfff1ce28b005a5f1c0e3" ]
CVE-2023-22647
2023-06-01T13:15:10
2025-02-19T03:31:12.089139
An Improper Privilege Management vulnerability in SUSE Rancher allowed standard users to leverage their existing permissions to manipulate Kubernetes secrets in the local cluster, resulting in the secret being deleted, but their read-level permissions to the secret being preserved. When this operation was followed-up by other specially crafted commands, it could result in the user gaining access to tokens belonging to service accounts in the local cluster. This issue affects Rancher: from >= 2.6.0 before < 2.6.13, from >= 2.7.0 before < 2.7.4.
[ { "score": "CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]
https://github.com/rancher/rancher
[]
[ "f650ce839db0e2fb755dfff1ce28b005a5f1c0e3" ]
CVE-2022-43759
2023-02-07T13:15:09
2025-02-19T03:28:34.609416
A Improper Privilege Management vulnerability in SUSE Rancher, allows users with access to the escalate verb on PRTBs to escalate permissions for any -promoted resource in any cluster. This issue affects: SUSE Rancher Rancher versions prior to 2.5.17; Rancher versions prior to 2.6.10.
[ { "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/rancher/rancher
[]
[ "1582f61de3e995870ace4de9d78f456376ce0e2c" ]
CVE-2022-21953
2023-02-07T13:15:09
2025-02-19T03:23:42.709904
A Missing Authorization vulnerability in of SUSE Rancher allows authenticated user to create an unauthorized shell pod and kubectl access in the local cluster This issue affects: SUSE Rancher Rancher versions prior to 2.5.17; Rancher versions prior to 2.6.10; Rancher versions prior to 2.7.1.
[ { "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/rancher/rancher
[]
[ "1582f61de3e995870ace4de9d78f456376ce0e2c" ]
CVE-2022-43757
2023-02-07T13:15:09
2025-02-19T03:28:37.120755
A Cleartext Storage of Sensitive Information vulnerability in SUSE Rancher allows users on managed clusters to gain access to credentials. The impact depends on the credentials exposed This issue affects: SUSE Rancher Rancher versions prior to 2.5.17; Rancher versions prior to 2.6.10; Rancher versions prior to 2.7.1.
[ { "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/rancher/rancher
[]
[ "1582f61de3e995870ace4de9d78f456376ce0e2c" ]
CVE-2022-43755
2023-02-07T13:15:09
2025-02-19T03:28:37.724795
A Insufficient Entropy vulnerability in SUSE Rancher allows attackers that gained knowledge of the cattle-token to continue abusing this even after the token was renewed. This issue affects: SUSE Rancher Rancher versions prior to 2.6.10; Rancher versions prior to 2.7.1.
[ { "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/rancher/rancher
[]
[ "f650ce839db0e2fb755dfff1ce28b005a5f1c0e3" ]
CVE-2022-43758
2023-02-07T13:15:09
2025-02-19T03:28:44.999743
A Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability in SUSE Rancher allows code execution for user with the ability to add an untrusted Helm catalog or modifying the URL configuration used to download KDM (only admin users by default) This issue affects: SUSE Rancher Rancher versions prior to 2.5.17; Rancher versions prior to 2.6.10; Rancher versions prior to 2.7.1.
[ { "score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]
https://github.com/rancher/rancher
[]
[ "1582f61de3e995870ace4de9d78f456376ce0e2c" ]
CVE-2023-22651
2023-05-04T08:15:22
2025-01-29T19:50:48.514463
Improper Privilege Management vulnerability in SUSE Rancher allows Privilege Escalation. A failure in the update logic of Rancher's admission Webhook may lead to the misconfiguration of the Webhook. This component enforces validation rules and security checks before resources are admitted into the Kubernetes cluster. The issue only affects users that upgrade from 2.6.x or 2.7.x to 2.7.2. Users that did a fresh install of 2.7.2 (and did not follow an upgrade path) are not affected.
[ { "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H", "type": "CVSS_V3" } ]
https://github.com/rancher/rancher
[]
[ "f650ce839db0e2fb755dfff1ce28b005a5f1c0e3" ]
CVE-2020-10676
2023-12-12T17:15:07
2025-02-19T03:01:50.947460
In Rancher 2.x before 2.6.13 and 2.7.x before 2.7.4, an incorrectly applied authorization check allows users who have certain access to a namespace to move that namespace to a different project.
[ { "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/rancher/rancher
[]
[ "32e12d5e1a418f917dc9b170e3354bf4e28c803b", "f650ce839db0e2fb755dfff1ce28b005a5f1c0e3" ]
CVE-2021-25313
2021-03-05T09:15:13
2025-01-14T09:00:50.209394
A Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Rancher allows remote attackers to execute JavaScript via malicious links. This issue affects: SUSE Rancher Rancher versions prior to 2.5.6.
[ { "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/rancher/rancher
[]
[ "32e12d5e1a418f917dc9b170e3354bf4e28c803b" ]
CVE-2021-31999
2021-07-15T09:15:08
2025-02-19T03:18:30.511889
A Reliance on Untrusted Inputs in a Security Decision vulnerability in Rancher allows users in the cluster to act as others users in the cluster by forging the "Impersonate-User" or "Impersonate-Group" headers. This issue affects: Rancher versions prior to 2.5.9. Rancher versions prior to 2.4.16.
[ { "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/rancher/rancher
[]
[ "32e12d5e1a418f917dc9b170e3354bf4e28c803b" ]
CVE-2021-25318
2021-07-15T09:15:07
2025-02-19T03:17:27.082561
A Incorrect Permission Assignment for Critical Resource vulnerability in Rancher allows users in the cluster to modify resources they should not have access to. This issue affects: Rancher versions prior to 2.5.9 ; Rancher versions prior to 2.4.16.
[ { "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/rancher/rancher
[]
[ "32e12d5e1a418f917dc9b170e3354bf4e28c803b" ]
CVE-2021-25320
2021-07-15T09:15:08
2025-02-19T03:17:26.586925
A Improper Access Control vulnerability in Rancher, allows users in the cluster to make request to cloud providers by creating requests with the cloud-credential ID. Rancher in this case would attach the requested credentials without further checks This issue affects: Rancher versions prior to 2.5.9; Rancher versions prior to 2.4.16.
[ { "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H", "type": "CVSS_V3" } ]
https://github.com/rancher/rancher
[]
[ "32e12d5e1a418f917dc9b170e3354bf4e28c803b" ]
CVE-2021-36776
2022-04-04T13:15:07
2025-02-19T03:19:41.077184
A Improper Access Control vulnerability in SUSE Rancher allows remote attackers impersonate arbitrary users. This issue affects: SUSE Rancher Rancher versions prior to 2.5.10.
[ { "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/rancher/rancher
[]
[ "32e12d5e1a418f917dc9b170e3354bf4e28c803b" ]
CVE-2021-36775
2022-04-04T13:15:07
2025-02-19T03:19:33.522270
a Improper Access Control vulnerability in SUSE Rancher allows users to keep privileges that should have been revoked. This issue affects: SUSE Rancher Rancher versions prior to 2.4.18; Rancher versions prior to 2.5.12; Rancher versions prior to 2.6.3.
[ { "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/rancher/rancher
[]
[ "32e12d5e1a418f917dc9b170e3354bf4e28c803b" ]
CVE-2022-31247
2022-09-07T09:15:08
2025-02-19T03:27:42.898440
An Improper Authorization vulnerability in SUSE Rancher, allows any user who has permissions to create/edit cluster role template bindings or project role template bindings (such as cluster-owner, manage cluster members, project-owner and manage project members) to gain owner permission in another project in the same cluster or in another project on a different downstream cluster. This issue affects: SUSE Rancher Rancher versions prior to 2.6.7; Rancher versions prior to 2.5.16.
[ { "score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H", "type": "CVSS_V3" } ]
https://github.com/rancher/rancher
[]
[ "1582f61de3e995870ace4de9d78f456376ce0e2c" ]
CVE-2021-36782
2022-09-07T09:15:08
2025-02-19T03:19:40.528949
A Cleartext Storage of Sensitive Information vulnerability in SUSE Rancher allows authenticated Cluster Owners, Cluster Members, Project Owners, Project Members and User Base to use the Kubernetes API to retrieve plaintext version of sensitive data. This issue affects: SUSE Rancher Rancher versions prior to 2.5.16; Rancher versions prior to 2.6.7.
[ { "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H", "type": "CVSS_V3" } ]
https://github.com/rancher/rancher
[]
[ "1582f61de3e995870ace4de9d78f456376ce0e2c" ]
CVE-2021-36783
2022-09-07T09:15:08
2025-02-19T03:20:31.701198
A Insufficiently Protected Credentials vulnerability in SUSE Rancher allows authenticated Cluster Owners, Cluster Members, Project Owners and Project Members to read credentials, passwords and API tokens that have been stored in cleartext and exposed via API endpoints. This issue affects: SUSE Rancher Rancher versions prior to 2.6.4; Rancher versions prior to 2.5.13.
[ { "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H", "type": "CVSS_V3" } ]
https://github.com/rancher/rancher
[]
[ "1582f61de3e995870ace4de9d78f456376ce0e2c" ]
CVE-2021-36784
2022-05-02T12:16:26
2025-02-19T03:20:33.591193
A Improper Privilege Management vulnerability in SUSE Rancher allows users with the restricted-admin role to escalate to full admin. This issue affects: SUSE Rancher Rancher versions prior to 2.5.13; Rancher versions prior to 2.6.4.
[ { "score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]
https://github.com/rancher/rancher
[]
[ "1582f61de3e995870ace4de9d78f456376ce0e2c", "32e12d5e1a418f917dc9b170e3354bf4e28c803b" ]
CVE-2021-36778
2022-05-02T12:16:25
2025-02-19T03:19:39.029831
A Incorrect Authorization vulnerability in SUSE Rancher allows administrators of third-party repositories to gather credentials that are sent to their servers. This issue affects: SUSE Rancher Rancher versions prior to 2.5.12; Rancher versions prior to 2.6.3.
[ { "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/rancher/rancher
[]
[ "32e12d5e1a418f917dc9b170e3354bf4e28c803b" ]
CVE-2021-4200
2022-05-02T12:16:26
2025-02-19T03:23:15.925622
A Improper Privilege Management vulnerability in SUSE Rancher allows write access to the Catalog for any user when restricted-admin role is enabled. This issue affects: SUSE Rancher Rancher versions prior to 2.5.13; Rancher versions prior to 2.6.4.
[ { "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L", "type": "CVSS_V3" } ]
https://github.com/rancher/rancher
[]
[ "1582f61de3e995870ace4de9d78f456376ce0e2c", "32e12d5e1a418f917dc9b170e3354bf4e28c803b" ]
CVE-2022-21951
2022-05-25T09:15:08
2025-02-19T03:23:40.170367
A Cleartext Transmission of Sensitive Information vulnerability in SUSE Rancher, Rancher allows attackers on the network to read and change network data due to missing encryption of data transmitted via the network when a cluster is created from an RKE template with the CNI value overridden This issue affects: SUSE Rancher Rancher versions prior to 2.5.14; Rancher versions prior to 2.6.5.
[ { "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/rancher/rancher
[]
[ "1582f61de3e995870ace4de9d78f456376ce0e2c" ]
CVE-2018-20321
2019-04-10T14:29:00
2025-01-14T07:28:16.486056
An issue was discovered in Rancher 2 through 2.1.5. Any project member with access to the default namespace can mount the netes-default service account in a pod, and then use that pod to execute administrative privileged commands against the k8s cluster. This could be mitigated by isolating the default namespace in a separate project, where only cluster admins can be given permissions to access. As of 2018-12-20, this bug affected ALL clusters created or imported by Rancher.
[ { "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/rancher/rancher
[]
[ "32e12d5e1a418f917dc9b170e3354bf4e28c803b" ]
CVE-2019-6287
2019-04-10T15:29:00
2025-01-14T08:04:52.800440
In Rancher 2.0.0 through 2.1.5, project members have continued access to create, update, read, and delete namespaces in a project after they have been removed from it.
[ { "score": "CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N", "type": "CVSS_V3" } ]
https://github.com/rancher/rancher
[]
[ "32e12d5e1a418f917dc9b170e3354bf4e28c803b" ]
CVE-2019-11202
2019-07-30T17:15:12
2025-02-19T02:43:33.236146
An issue was discovered that affects the following versions of Rancher: v2.0.0 through v2.0.13, v2.1.0 through v2.1.8, and v2.2.0 through 2.2.1. When Rancher starts for the first time, it creates a default admin user with a well-known password. After initial setup, the Rancher administrator may choose to delete this default admin user. If Rancher is restarted, the default admin user will be recreated with the well-known default password. An attacker could exploit this by logging in with the default admin credentials. This can be mitigated by deactivating the default admin user rather than completing deleting them.
[ { "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/rancher/rancher
[]
[ "32e12d5e1a418f917dc9b170e3354bf4e28c803b" ]
CVE-2019-12303
2019-06-06T16:29:01
2025-01-14T07:29:15.492120
In Rancher 2 through 2.2.3, Project owners can inject additional fluentd configuration to read files or execute arbitrary commands inside the fluentd 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/rancher/rancher
[]
[ "32e12d5e1a418f917dc9b170e3354bf4e28c803b" ]
CVE-2019-12274
2019-06-06T16:29:01
2025-02-19T02:41:53.627963
In Rancher 1 and 2 through 2.2.3, unprivileged users (if allowed to deploy nodes) can gain admin access to the Rancher management plane because node driver options intentionally allow posting certain data to the cloud. The problem is that a user could choose to post a sensitive file such as /root/.kube/config or /var/lib/rancher/management-state/cred/kubeconfig-system.yaml.
[ { "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/rancher/rancher
[]
[ "32e12d5e1a418f917dc9b170e3354bf4e28c803b" ]
CVE-2019-11881
2019-06-10T20:29:01
2025-01-15T01:37:37.810796
A vulnerability exists in Rancher before 2.2.4 in the login component, where the errorMsg parameter can be tampered to display arbitrary content, filtering tags but not special characters or symbols. There's no other limitation of the message, allowing malicious users to lure legitimate users to visit phishing sites with scare tactics, e.g., displaying a "This version of Rancher is outdated, please visit https://malicious.rancher.site/upgrading" message.
[ { "score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:N", "type": "CVSS_V3" } ]
https://github.com/rancher/rancher
[]
[ "32e12d5e1a418f917dc9b170e3354bf4e28c803b" ]
CVE-2019-13209
2019-09-04T14:15:11
2025-01-14T07:40:07.913319
Rancher 2 through 2.2.4 is vulnerable to a Cross-Site Websocket Hijacking attack that allows an exploiter to gain access to clusters managed by Rancher. The attack requires a victim to be logged into a Rancher server, and then to access a third-party site hosted by the exploiter. Once that is accomplished, the exploiter is able to execute commands against the cluster's Kubernetes API with the permissions and identity of the victim.
[ { "score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N", "type": "CVSS_V3" } ]
https://github.com/rancher/rancher
[]
[ "32e12d5e1a418f917dc9b170e3354bf4e28c803b" ]
CVE-2017-7297
2017-03-29T00:59:00
2025-01-14T07:15:22.221235
Rancher Labs rancher server 1.2.0+ is vulnerable to authenticated users disabling access control via an API call. This is fixed in versions rancher/server:v1.2.4, rancher/server:v1.3.5, rancher/server:v1.4.3, and rancher/server:v1.5.3.
[ { "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/rancher/rancher
[]
[ "2abfaedae070e3c81a8b17bffd7180362da8fe7c" ]
CVE-2022-31249
2023-02-07T13:15:09
2025-01-14T10:59:03.219316
A Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability in wrangler of SUSE Rancher allows remote attackers to inject commands in the underlying host via crafted commands passed to Wrangler. This issue affects: SUSE Rancher wrangler version 0.7.3 and prior versions; wrangler version 0.8.4 and prior versions; wrangler version 1.0.0 and prior versions.
[ { "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/rancher/wrangler
[]
[ "c4a56314a1b7d4daf867936178eb3b8afe6c97c5" ]
CVE-2022-43756
2023-02-07T13:15:09
2025-01-14T11:14:03.875228
A Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') vulnerability in SUSE Rancher allows remote attackers to cause denial of service by supplying specially crafted git credentials. This issue affects: SUSE Rancher wrangler version 0.7.3 and prior versions; wrangler version 0.8.4 and prior versions; wrangler version 1.0.0 and prior versions.
[ { "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/rancher/wrangler
[]
[ "c4a56314a1b7d4daf867936178eb3b8afe6c97c5" ]
CVE-2018-12907
2018-06-27T13:29:00
2025-02-19T02:30:53.948261
In Rclone 1.42, use of "rclone sync" to migrate data between two Google Cloud Storage buckets might allow attackers to trigger the transmission of any URL's content to Google, because there is no validation of a URL field received from the Google Cloud Storage API server, aka a "RESTLESS" issue.
[ { "score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N", "type": "CVSS_V3" } ]
https://github.com/rclone/rclone
[]
[ "a9adb4389628c086c0183c8daa1c8a59004f08b6" ]
CVE-2023-30450
2023-04-08T23:15:06
2025-02-12T19:50:11.533050
rpk in Redpanda before 23.1.2 mishandles the redpanda.rpc_server_tls field, leading to (for example) situations in which there is a data type mismatch that cannot be automatically fixed by rpk, and instead a user must reconfigure (while a cluster is turned off) in order to have TLS on broker RPC ports. NOTE: the fix was also backported to the 22.2 and 22.3 branches.
[ { "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N", "type": "CVSS_V3" } ]
https://github.com/redpanda-data/redpanda
[]
[ "f2d73b1151ccf1ce4186fadd0121fbc34b9b7f4c" ]
CVE-2023-24619
2023-02-13T19:15:11
2025-02-19T03:31:25.415469
Redpanda before 22.3.12 discloses cleartext AWS credentials. The import functionality in the rpk binary logs an AWS Access Key ID and Secret in cleartext to standard output, allowing a local user to view the key in the console, or in Kubernetes logs if stdout output is collected. The fixed versions are 22.3.12, 22.2.10, and 22.1.12.
[ { "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/redpanda-data/redpanda
[]
[ "f2d73b1151ccf1ce4186fadd0121fbc34b9b7f4c" ]
CVE-2023-50976
2023-12-18T00:15:11
2025-02-19T03:35:13.617418
Redpanda before 23.1.21 and 23.2.x before 23.2.18 has missing authorization checks in the Transactions API.
[ { "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/redpanda-data/redpanda
[]
[ "f2d73b1151ccf1ce4186fadd0121fbc34b9b7f4c" ]
CVE-2024-45298
2024-09-18T17:15:18
2024-10-08T04:12:21.788070
Wiki.js is an open source wiki app built on Node.js. A disabled user can still gain access to a wiki by abusing the password reset function. While setting up SMTP e-mail's on my server, I tested said e-mails by performing a password reset with my test user. To my shock, not only did it let me reset my password, but after resetting my password I can get into the wiki I was locked out of. The ramifications of this bug is a user can **bypass an account disabling by requesting their password be reset**. All users of wiki.js version `2.5.303` who use any account restrictions and have disabled user are affected. This issue has been addressed in version 2.5.304 and all users are advised to upgrade. There are no known workarounds for this vulnerability.
null
https://github.com/requarks/wiki
[]
[ "b2931471c0796dc8989d1b5779bce7c17887dadd" ]
CVE-2024-34710
2024-05-20T22:15:08
2025-01-15T05:14:00.656861
Wiki.js is al wiki app built on Node.js. Client side template injection was discovered, that could allow an attacker to inject malicious JavaScript into the content section of pages that would execute once a victim loads the page that contains the payload. This was possible through the injection of a invalid HTML tag with a template injection payload on the next line. This vulnerability is fixed in 2.5.303.
null
https://github.com/requarks/wiki
[]
[ "b2931471c0796dc8989d1b5779bce7c17887dadd" ]
CVE-2021-21383
2021-03-18T17:15:13
2025-01-15T01:47:31.399217
Wiki.js an open-source wiki app built on Node.js. Wiki.js before version 2.5.191 is vulnerable to stored cross-site scripting through mustache expressions in code blocks. This vulnerability exists due to mustache expressions being parsed by Vue during content injection even though it is contained within a `<pre>` element. By creating a crafted wiki page, a malicious Wiki.js user may stage a stored cross-site scripting attack. This allows the attacker to execute malicious JavaScript when the page is viewed by other users. For an example see referenced GitHub Security Advisory. Commit 5ffa189383dd716f12b56b8cae2ba0d075996cf1 fixes this vulnerability by adding the v-pre directive to all `<pre>` tags during the render.
[ { "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/requarks/wiki
[]
[ "b2931471c0796dc8989d1b5779bce7c17887dadd" ]
CVE-2021-43842
2021-12-20T23:15:29
2025-01-15T02:08:35.286545
Wiki.js is a wiki app built on Node.js. Wiki.js versions 2.5.257 and earlier are vulnerable to stored cross-site scripting through a SVG file upload. By creating a crafted SVG file, a malicious Wiki.js user may stage a stored cross-site scripting attack. This allows the attacker to execute malicious JavaScript when the SVG is viewed directly by other users. Scripts do not execute when loaded inside a page via normal `<img>` tags. Commit 5d3e81496fba1f0fbd64eeb855f30f69a9040718 fixes this vulnerability by adding an optional (enabled by default) SVG sanitization step to all file uploads that match the SVG mime type. As a workaround, disable file upload for all non-trusted users. Wiki.js version 2.5.260 is the first production version to contain a patch. Version 2.5.258 is the first development build to contain a patch and is available only as a Docker image as requarks/wiki:canary-2.5.258.
null
https://github.com/requarks/wiki
[]
[ "b2931471c0796dc8989d1b5779bce7c17887dadd" ]
CVE-2021-43800
2021-12-06T19:15:07
2025-01-15T02:06:47.329049
Wiki.js is a wiki app built on Node.js. Prior to version 2.5.254, directory traversal outside of Wiki.js context is possible when a storage module with local asset cache fetching is enabled on a Windows host. A malicious user can potentially read any file on the file system by crafting a special URL that allows for directory traversal. This is only possible on a Wiki.js server running on Windows, when a storage module implementing local asset cache (e.g Local File System or Git) is enabled and that no web application firewall solution (e.g. cloudflare) strips potentially malicious URLs. Commit number 414033de9dff66a327e3f3243234852f468a9d85 fixes this vulnerability by sanitizing the path before it is passed on to the storage module. The sanitization step removes any windows directory traversal sequences from the path. As a workaround, disable any storage module with local asset caching capabilities (Local File System, Git).
[ { "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/requarks/wiki
[]
[ "b2931471c0796dc8989d1b5779bce7c17887dadd" ]
CVE-2021-43856
2021-12-27T18:15:07
2025-01-15T02:08:34.937341
Wiki.js is a wiki app built on Node.js. Wiki.js 2.5.263 and earlier is vulnerable to stored cross-site scripting through non-image file uploads for file types that can be viewed directly inline in the browser. By creating a malicious file which can execute inline JS when viewed in the browser (e.g. XML files), a malicious Wiki.js user may stage a stored cross-site scripting attack. This allows the attacker to execute malicious JavaScript when the file is viewed directly by other users. The file must be opened directly by the user and will not trigger directly in a normal Wiki.js page. A patch in version 2.5.264 fixes this vulnerability by adding an optional (enabled by default) force download flag to all non-image file types, preventing the file from being viewed inline in the browser. As a workaround, disable file upload for all non-trusted users. --- Thanks to @Haxatron for reporting this vulnerability. Initially reported via https://huntr.dev/bounties/266bff09-00d9-43ca-a4bb-bb540642811f/
[ { "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/requarks/wiki
[]
[ "b2931471c0796dc8989d1b5779bce7c17887dadd" ]
CVE-2021-25993
2021-12-29T17:15:07
2025-01-15T01:48:26.146176
In Requarks wiki.js, versions 2.0.0-beta.147 to 2.5.255 are affected by Stored XSS vulnerability, where a low privileged (editor) user can upload a SVG file that contains malicious JavaScript while uploading assets in the page. That will send the JWT tokens to the attacker’s server and will lead to account takeover when accessed by the victim.
[ { "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/requarks/wiki
[]
[ "b2931471c0796dc8989d1b5779bce7c17887dadd" ]
CVE-2021-43855
2021-12-27T18:15:07
2025-01-15T02:08:40.541379
Wiki.js is a wiki app built on node.js. Wiki.js 2.5.263 and earlier is vulnerable to stored cross-site scripting through a SVG file upload made via a custom request with a fake MIME type. By creating a crafted SVG file, a malicious Wiki.js user may stage a stored cross-site scripting attack. This allows the attacker to execute malicious JavaScript when the SVG is viewed directly by other users. Scripts do not execute when loaded inside a page via normal `<img>` tags. The malicious SVG can only be uploaded by crafting a custom request to the server with a fake MIME type. A patch in version 2.5.264 fixes this vulnerability by adding an additional file extension verification check to the optional (enabled by default) SVG sanitization step to all file uploads that match the SVG mime type. As a workaround, disable file upload for all non-trusted users.
[ { "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/requarks/wiki
[]
[ "b2931471c0796dc8989d1b5779bce7c17887dadd" ]
CVE-2022-23654
2022-02-22T20:15:07
2025-01-15T02:16:43.007566
Wiki.js is a wiki app built on Node.js. In affected versions an authenticated user with write access on a restricted set of paths can update a page outside the allowed paths by specifying a different target page ID while keeping the path intact. The access control incorrectly check the path access against the user-provided values instead of the actual path associated to the page ID. Commit https://github.com/Requarks/wiki/commit/411802ec2f654bb5ed1126c307575b81e2361c6b fixes this vulnerability by checking access control on the path associated with the page ID instead of the user-provided value. When the path is different than the current value, a second access control check is then performed on the user-provided path before the move operation.
[ { "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N", "type": "CVSS_V3" } ]
https://github.com/requarks/wiki
[]
[ "b2931471c0796dc8989d1b5779bce7c17887dadd" ]
CVE-2022-1681
2022-05-12T08:15:07
2025-01-15T02:13:09.057848
Authentication Bypass Using an Alternate Path or Channel in GitHub repository requarks/wiki prior to 2.5.281. User can get root user permissions
[ { "score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]
https://github.com/requarks/wiki
[]
[ "b2931471c0796dc8989d1b5779bce7c17887dadd" ]
CVE-2020-4052
2020-06-16T22:15:10
2025-01-15T01:45:45.401914
In Wiki.js before 2.4.107, there is a stored cross-site scripting through template injection. This vulnerability exists due to an insecure validation mechanism intended to insert v-pre tags into rendered HTML elements which contain curly-braces. By creating a crafted wiki page, a malicious Wiki.js user may stage a stored cross-site scripting attack. This allows the attacker to execute malicious JavaScript when the page is viewed by other users. This has been patched in 2.4.107.
[ { "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/requarks/wiki
[]
[ "b2931471c0796dc8989d1b5779bce7c17887dadd" ]
CVE-2020-11051
2020-05-05T21:15:11
2025-01-15T01:41:48.198666
In Wiki.js before 2.3.81, there is a stored XSS in the Markdown editor. An editor with write access to a page, using the Markdown editor, could inject an XSS payload into the content. If another editor (with write access as well) load the same page into the Markdown editor, the XSS payload will be executed as part of the preview panel. The rendered result does not contain the XSS payload as it is stripped by the HTML Sanitization security module. This vulnerability only impacts editors loading the malicious page in the Markdown editor. This has been patched in 2.3.81.
[ { "score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N", "type": "CVSS_V3" } ]
https://github.com/requarks/wiki
[]
[ "b2931471c0796dc8989d1b5779bce7c17887dadd" ]
CVE-2020-15236
2020-10-05T15:15:12
2025-01-15T01:43:10.317216
In Wiki.js before version 2.5.151, directory traversal outside of Wiki.js context is possible when a storage module with local asset cache fetching is enabled. A malicious user can potentially read any file on the file system by crafting a special URL that allows for directory traversal. This is only possible when a storage module implementing local asset cache (e.g Local File System or Git) is enabled and that no web application firewall solution (e.g. cloudflare) strips potentially malicious URLs. Commit 084dcd69d1591586ee4752101e675d5f0ac6dcdc fixes this vulnerability by sanitizing the path before it is passed on to the storage module. The sanitization step removes any directory traversal (e.g. `..` and `.`) sequences as well as invalid filesystem characters from the path. As a workaround, disable any storage module with local asset caching capabilities such as Local File System and Git.
[ { "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/requarks/wiki
[]
[ "b2931471c0796dc8989d1b5779bce7c17887dadd" ]
CVE-2020-15274
2020-10-26T19:15:12
2025-01-15T01:43:21.467018
In Wiki.js before version 2.5.162, an XSS payload can be injected in a page title and executed via the search results. While the title is properly escaped in both the navigation links and the actual page title, it is not the case in the search results. Commit a57d9af34c15adbf460dde6553d964efddf433de fixes this vulnerability (version 2.5.162) by properly escaping the text content displayed in the search results.
[ { "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/requarks/wiki
[]
[ "b2931471c0796dc8989d1b5779bce7c17887dadd" ]
CVE-2025-24884
2025-01-29T21:15:21
2025-02-04T22:42:03.550045
kube-audit-rest is a simple logger of mutation/creation requests to the k8s api. If the "full-elastic-stack" example vector configuration was used for a real cluster, the previous values of kubernetes secrets would have been disclosed in the audit messages. This vulnerability is fixed in 1.0.16.
null
https://github.com/richardoc/kube-audit-rest
[]
[ "d3f1d1a2ad682e8191fc8812fd48caf88ece281d" ]
CVE-2019-10147
2019-06-03T19:29:01
2025-02-19T02:42:40.549404
rkt through version 1.30.0 does not isolate processes in containers that are run with `rkt enter`. Processes run with `rkt enter` are not limited by cgroups during stage 2 (the actual environment in which the applications run). Compromised containers could exploit this flaw to access host resources.
[ { "score": "CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H", "type": "CVSS_V3" } ]
https://github.com/rkt/rkt
[]
[ "e04dd994baa1051f1205578d12d69eec83dbb905" ]
CVE-2019-10144
2019-06-03T19:29:01
2025-02-19T02:42:41.589410
rkt through version 1.30.0 does not isolate processes in containers that are run with `rkt enter`. Processes run with `rkt enter` are given all capabilities during stage 2 (the actual environment in which the applications run). Compromised containers could exploit this flaw to access host resources.
[ { "score": "CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H", "type": "CVSS_V3" } ]
https://github.com/rkt/rkt
[]
[ "e04dd994baa1051f1205578d12d69eec83dbb905" ]
CVE-2019-10145
2019-06-03T19:29:01
2025-02-19T02:42:41.024134
rkt through version 1.30.0 does not isolate processes in containers that are run with `rkt enter`. Processes run with `rkt enter` do not have seccomp filtering during stage 2 (the actual environment in which the applications run). Compromised containers could exploit this flaw to access host resources.
[ { "score": "CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H", "type": "CVSS_V3" } ]
https://github.com/rkt/rkt
[]
[ "e04dd994baa1051f1205578d12d69eec83dbb905" ]
CVE-2017-1000203
2017-11-17T15:29:00
2025-01-15T01:22:04.092156
ROOT version 6.9.03 and below is vulnerable to an authenticated shell metacharacter injection in the rootd daemon resulting in remote code execution
[ { "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/root-project/root
[]
[ "660e7c1bda015faaf20aa7f282b99b3fd380a1de" ]
CVE-2018-20744
2019-01-28T08:29:00
2025-01-14T07:29:26.173535
The Olivier Poitrey Go CORS handler through 1.3.0 actively converts a wildcard CORS policy into reflecting an arbitrary Origin header value, which is incompatible with the CORS security design, and could lead to CORS misconfiguration security problems.
[ { "score": "CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N", "type": "CVSS_V3" } ]
https://github.com/rs/cors
[]
[ "feef513b9575b32f84bafa580aad89b011259019" ]