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-2023-1496 | 2023-03-19T17:15:11 | 2025-01-15T04:39:45.172114 | Cross-site Scripting (XSS) - Reflected in GitHub repository imgproxy/imgproxy prior to 3.14.0. | [
{
"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/imgproxy/imgproxy | [] | [
"c786bde2c1818d1fdd83b6d280d85bfcef6cb1f7"
] |
CVE-2023-30019 | 2023-05-08T15:15:11 | 2025-02-19T03:33:53.283211 | imgproxy <=3.14.0 is vulnerable to Server-Side Request Forgery (SSRF) due to a lack of sanitization of the imageURL parameter. | [
{
"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/imgproxy/imgproxy | [] | [
"c786bde2c1818d1fdd83b6d280d85bfcef6cb1f7"
] |
CVE-2025-24354 | 2025-01-27T18:15:41 | 2025-01-28T15:41:48.647690 | imgproxy is server for resizing, processing, and converting images. Imgproxy does not block the 0.0.0.0 address, even with IMGPROXY_ALLOW_LOOPBACK_SOURCE_ADDRESSES set to false. This can expose services on the local host. This vulnerability is fixed in 3.27.2. | null | https://github.com/imgproxy/imgproxy | [] | [
"c786bde2c1818d1fdd83b6d280d85bfcef6cb1f7"
] |
CVE-2021-41087 | 2021-09-21T21:15:07 | 2025-01-15T02:03:49.898005 | in-toto-golang is a go implementation of the in-toto framework to protect software supply chain integrity. In affected versions authenticated attackers posing as functionaries (i.e., within a trusted set of users for a layout) are able to create attestations that may bypass DISALLOW rules in the same layout. An attacker with access to trusted private keys, may issue an attestation that contains a disallowed artifact by including path traversal semantics (e.g., foo vs dir/../foo). Exploiting this vulnerability is dependent on the specific policy applied. The problem has been fixed in version 0.3.0. | [
{
"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/in-toto/in-toto-golang | [] | [
"c80faabd12f877159b1157dff7da1559ac7ac8d7"
] |
CVE-2024-30896 | 2024-11-21T11:15:34 | 2025-02-19T03:37:57.606227 | InfluxDB OSS 2.x through 2.7.11 stores the administrative operator token under the default organization which allows authorized users with read access to the authorization resource of the default organization to retrieve the operator token. InfluxDB OSS 1.x, Enterprise, Cloud, Cloud Dedicated and Clustered are not affected. NOTE: The researcher states that InfluxDB allows allAccess administrators to retrieve all raw tokens via an "influx auth ls" command. The supplier indicates that the organizations feature is operating as intended and that users may choose to add users to non-default organizations. A future release of InfluxDB 2.x will remove the ability to retrieve tokens from the API. | null | https://github.com/influxdata/influxdb | [] | [
"fbf5d4ab5e65d3a3661aa52e1d05259d19a6a81b"
] |
CVE-2023-42658 | 2023-10-31T15:15:09 | 2025-02-19T03:34:27.944512 |
Archive command in Chef InSpec prior to 4.56.58 and 5.22.29 allow local command execution via maliciously crafted profile. | [
{
"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/inspec/inspec | [] | [
"270021a1ad2504cbc1ccc086745cf4c7a045d0da"
] |
CVE-2023-25568 | 2023-05-10T14:15:32 | 2025-01-15T04:45:03.595849 | Boxo, formerly known as go-libipfs, is a library for building IPFS applications and implementations. In versions 0.4.0 and 0.5.0, if an attacker is able allocate arbitrary many bytes in the Bitswap server, those allocations are lasting even if the connection is closed. This affects users accepting untrusted connections with the Bitswap server and also affects users using the old API stubs at `github.com/ipfs/go-libipfs/bitswap` because users then transitively import `github.com/ipfs/go-libipfs/bitswap/server`. Boxo versions 0.6.0 and 0.4.1 contain a patch for this issue. As a workaround, those who are using the stub object at `github.com/ipfs/go-libipfs/bitswap` not taking advantage of the features provided by the server can refactor their code to use the new split API that will allow them to run in a client only mode: `github.com/ipfs/go-libipfs/bitswap/client`. | [
{
"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/ipfs/boxo | [] | [
"0d695f323e0093c739fd7e9103f2bff9a99afaaf"
] |
CVE-2023-23626 | 2023-02-09T21:15:11 | 2025-01-15T04:43:10.708556 | go-bitfield is a simple bitfield package for the go language aiming to be more performant that the standard library. When feeding untrusted user input into the size parameter of `NewBitfield` and `FromBytes` functions, an attacker can trigger `panic`s. This happen when the `size` is a not a multiple of `8` or is negative. There were already a note in the `NewBitfield` documentation, however known users of this package are subject to this issue. Users are advised to upgrade. Users unable to upgrade should ensure that `size` is a multiple of 8 before calling `NewBitfield` or `FromBytes`.
| [
{
"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/ipfs/go-bitfield | [] | [
"eb25ac22dacdb82b306536ff6839d2534597abdb"
] |
CVE-2020-26279 | 2021-03-24T21:15:11 | 2025-01-15T01:45:40.788461 | go-ipfs is an open-source golang implementation of IPFS which is a global, versioned, peer-to-peer filesystem. In go-ipfs before version 0.8.0-rc1, it is possible for path traversal to occur with DAGs containing relative paths during retrieval. This can cause files to be overwritten, or written to incorrect output directories. The issue can only occur when a get is done on an affected DAG. This is fixed in version 0.8.0-rc1. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/ipfs/go-ipfs | [] | [
"ea77213e31ef2b3cad81d40bf82bb9baef3ea7b6"
] |
CVE-2020-26283 | 2021-03-24T21:15:11 | 2025-01-15T01:45:38.385658 | go-ipfs is an open-source golang implementation of IPFS which is a global, versioned, peer-to-peer filesystem. In go-ipfs before version 0.8.0, control characters are not escaped from console output. This can result in hiding input from the user which could result in the user taking an unknown, malicious action. This is fixed in version 0.8.0. | [
{
"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/ipfs/go-ipfs | [] | [
"ea77213e31ef2b3cad81d40bf82bb9baef3ea7b6"
] |
CVE-2022-23495 | 2022-12-08T22:15:10 | 2025-01-14T10:44:32.873911 | go-merkledag implements the 'DAGService' interface and adds two ipld node types, Protobuf and Raw for the ipfs project. A `ProtoNode` may be modified in such a way as to cause various encode errors which will trigger a panic on common method calls that don't allow for error returns. A `ProtoNode` should only be able to encode to valid DAG-PB, attempting to encode invalid DAG-PB forms will result in an error from the codec. Manipulation of an existing (newly created or decoded) `ProtoNode` using the modifier methods did not account for certain states that would place the `ProtoNode` into an unencodeable form. Due to conformance with the [`github.com/ipfs/go-block-format#Block`](https://pkg.go.dev/github.com/ipfs/go-block-format#Block) and [`github.com/ipfs/go-ipld-format#Node`](https://pkg.go.dev/github.com/ipfs/go-ipld-format#Node) interfaces, certain methods, which internally require a re-encode if state has changed, will panic due to the inability to return an error. This issue has been addressed across a number of pull requests. Users are advised to upgrade to version 0.8.1 for a complete set of fixes. Users unable to upgrade may attempt to mitigate this issue by sanitising inputs when allowing user-input to set a new `CidBuilder` on a `ProtoNode` and by sanitising `Tsize` (`Link#Size`) values such that they are a reasonable byte-size for sub-DAGs where derived from user-input.
| [
{
"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/ipfs/go-merkledag | [] | [
"0e4726d152e088749e0ef7404f44a4217f6f9d92"
] |
CVE-2023-23625 | 2023-02-09T21:15:11 | 2025-01-15T04:43:11.042566 | go-unixfs is an implementation of a unix-like filesystem on top of an ipld merkledag. Trying to read malformed HAMT sharded directories can cause panics and virtual memory leaks. If you are reading untrusted user input, an attacker can then trigger a panic. This is caused by bogus `fanout` parameter in the HAMT directory nodes. Users are advised to upgrade to version 0.4.3 to resolve this issue. Users unable to upgrade should not feed untrusted user data to the decoding functions.
| [
{
"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/ipfs/go-unixfs | [] | [
"323bb63cafa93c5bdd10170f35b96327760d7c1a"
] |
CVE-2023-23631 | 2023-02-09T21:15:11 | 2025-01-15T04:43:11.045967 | github.com/ipfs/go-unixfsnode is an ADL IPLD prime node that wraps go-codec-dagpb's implementation of protobuf to enable pathing. In versions priot to 1.5.2 trying to read malformed HAMT sharded directories can cause panics and virtual memory leaks.
If you are reading untrusted user input, an attacker can then trigger a panic. This is caused by bogus fanout parameter in the HAMT directory nodes. Users are advised to upgrade. There are no known workarounds for this vulnerability. | [
{
"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/ipfs/go-unixfsnode | [] | [
"ad0a9a12b49cd45953fde42e339f67ae58eb065f"
] |
CVE-2022-2584 | 2022-12-27T22:15:12 | 2025-01-30T08:52:45.752746 | The dag-pb codec can panic when decoding invalid blocks. | [
{
"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/ipld/go-codec-dagpb | [] | [
"1305732016fb5bfec1b28f9fe7a686b12a407d74"
] |
CVE-2023-22460 | 2023-01-04T15:15:09 | 2025-02-19T03:30:39.383132 | go-ipld-prime is an implementation of the InterPlanetary Linked Data (IPLD) spec interfaces, a batteries-included codec implementations of IPLD for CBOR and JSON, and tooling for basic operations on IPLD objects. Encoding data which contains a Bytes kind Node will pass a Bytes token to the JSON encoder which will panic as it doesn't expect to receive Bytes tokens. Such an encode should be treated as an error, as plain JSON should not be able to encode Bytes. This only impacts uses of the `json` codec. `dag-json` is not impacted. Use of `json` as a decoder is not impacted. This issue is fixed in v0.19.0. As a workaround, one may prefer the `dag-json` codec, which has the ability to encode bytes. | [
{
"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/ipld/go-ipld-prime | [] | [
"81efd86a0fdabf1a89fdb731f6e017968ab5b01d"
] |
CVE-2018-19793 | 2018-12-03T06:29:00 | 2025-01-14T07:27:01.547657 | jiacrontab 1.4.5 allows remote attackers to execute arbitrary commands via the crontab/task/edit?addr=localhost%3a20001 command and args parameters, as demonstrated by command=cat&args=/etc/passwd in the POST data. | [
{
"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/iwannay/jiacrontab | [] | [
"93f54326fe6bb1d8ce1f08e3bfa80ad05dc98171"
] |
CVE-2020-10750 | 2020-06-19T20:15:12 | 2025-02-19T03:01:48.918464 | Sensitive information written to a log file vulnerability was found in jaegertracing/jaeger before version 1.18.1 when the Kafka data store is used. This flaw allows an attacker with access to the container's log file to discover the Kafka credentials. | [
{
"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/jaegertracing/jaeger | [] | [
"0fe3e758e61852b753682197f40e2eb05b526811"
] |
CVE-2018-25059 | 2022-12-30T11:15:10 | 2025-01-15T01:33:36.130835 | A vulnerability was found in pastebinit up to 0.2.2 and classified as problematic. Affected by this issue is the function pasteHandler of the file server.go. The manipulation of the argument r.URL.Path leads to path traversal. Upgrading to version 0.2.3 is able to address this issue. The name of the patch is 1af2facb6d95976c532b7f8f82747d454a092272. It is recommended to upgrade the affected component. The identifier of this vulnerability is VDB-217040. | [
{
"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/jessfraz/pastebinit | [] | [
"edb60577888e36ba5139bee2b8050d8123654ab7"
] |
CVE-2023-47390 | 2023-11-11T18:15:14 | 2025-02-19T03:35:25.633313 | Headscale through 0.22.3 writes bearer tokens to info-level logs. | [
{
"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/juanfont/headscale | [] | [
"b01f1f1867136d9b2d7b1392776eb363b482c525"
] |
CVE-2024-6984 | 2024-07-29T14:15:04 | 2025-01-15T05:18:02.067191 | An issue was discovered in Juju that resulted in the leak of the sensitive context ID, which allows a local unprivileged attacker to access other sensitive data or relation accessible to the local charm. | [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/juju/juju | [] | [
"2831158d2c09328719883c432211bb6a8de07c7a"
] |
CVE-2023-0092 | 2025-01-31T02:15:28 | 2025-02-07T17:49:33.324486 | An authenticated user who has read access to the juju controller model, may construct a remote request to download an arbitrary file from the controller's filesystem. | null | https://github.com/juju/juju | [] | [
"2831158d2c09328719883c432211bb6a8de07c7a"
] |
CVE-2017-9232 | 2017-05-28T00:29:00 | 2025-01-14T07:19:49.472783 | Juju before 1.25.12, 2.0.x before 2.0.4, and 2.1.x before 2.1.3 uses a UNIX domain socket without setting appropriate permissions, allowing privilege escalation by users on the system to root. | [
{
"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/juju/juju | [] | [
"2831158d2c09328719883c432211bb6a8de07c7a"
] |
CVE-2020-36564 | 2022-12-27T22:15:11 | 2025-01-15T01:45:27.937921 | Due to improper validation of caller input, validation is silently disabled if the provided expected token is malformed, causing any user supplied token to be considered valid. | [
{
"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/justinas/nosurf | [] | [
"e51517007dc9daa543fc05e7d63f2636815757a3"
] |
CVE-2024-56514 | 2025-01-03T17:15:09 | 2025-01-15T05:17:00.837038 | Karmada is a Kubernetes management system that allows users to run cloud-native applications across multiple Kubernetes clusters and clouds. Prior to version 1.12.0, both in karmadactl and karmada-operator, it is possible to supply a filesystem path, or an HTTP(s) URL to retrieve the custom resource definitions(CRDs) needed by Karmada. The CRDs are downloaded as a gzipped tarfile and are vulnerable to a TarSlip vulnerability. An attacker able to supply a malicious CRD file into a Karmada initialization could write arbitrary files in arbitrary paths of the filesystem. From Karmada version 1.12.0, when processing custom CRDs files, CRDs archive verification is utilized to enhance file system robustness. A workaround is available. Someone who needs to set flag `--crd` to customize the CRD files required for Karmada initialization when using `karmadactl init` to set up Karmada can manually inspect the CRD files to check whether they contain sequences such as `../` that would alter file paths, to determine if they potentially include malicious files. When using karmada-operator to set up Karmada, one must upgrade one's karmada-operator to one of the fixed versions. | null | https://github.com/karmada-io/karmada | [] | [
"057cf860f41afc60f7505196c6df5979a2642068"
] |
CVE-2024-56513 | 2025-01-03T17:15:08 | 2025-01-15T05:17:00.602901 | Karmada is a Kubernetes management system that allows users to run cloud-native applications across multiple Kubernetes clusters and clouds. Prior to version 1.12.0, the PULL mode clusters registered with the `karmadactl register` command have excessive privileges to access control plane resources. By abusing these permissions, an attacker able to authenticate as the karmada-agent to a karmada cluster would be able to obtain administrative privileges over the entire federation system including all registered member clusters. Since Karmada v1.12.0, command `karmadactl register` restricts the access permissions of pull mode member clusters to control plane resources. This way, an attacker able to authenticate as the karmada-agent cannot control other member clusters in Karmada. As a workaround, one may restrict the access permissions of pull mode member clusters to control plane resources according to Karmada Component Permissions Docs. | null | https://github.com/karmada-io/karmada | [] | [
"057cf860f41afc60f7505196c6df5979a2642068"
] |
CVE-2020-2023 | 2020-06-10T18:15:11 | 2025-01-14T08:37:14.486003 | Kata Containers doesn't restrict containers from accessing the guest's root filesystem device. Malicious containers can exploit this to gain code execution on the guest and masquerade as the kata-agent. This issue affects Kata Containers 1.11 versions earlier than 1.11.1; Kata Containers 1.10 versions earlier than 1.10.5; and Kata Containers 1.9 and earlier versions. | [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L",
"type": "CVSS_V3"
}
] | https://github.com/kata-containers/runtime | [] | [
"dc550720a31582ced60d26cd7c64d746b1449864"
] |
CVE-2020-2026 | 2020-06-10T18:15:11 | 2025-01-14T08:37:26.322489 | A malicious guest compromised before a container creation (e.g. a malicious guest image or a guest running multiple containers) can trick the kata runtime into mounting the untrusted container filesystem on any host path, potentially allowing for code execution on the host. This issue affects: Kata Containers 1.11 versions earlier than 1.11.1; Kata Containers 1.10 versions earlier than 1.10.5; Kata Containers 1.9 and earlier versions. | [
{
"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/kata-containers/runtime | [] | [
"dc550720a31582ced60d26cd7c64d746b1449864"
] |
CVE-2020-2024 | 2020-05-19T21:15:10 | 2025-01-14T08:37:14.283963 | An improper link resolution vulnerability affects Kata Containers versions prior to 1.11.0. Upon container teardown, a malicious guest can trick the kata-runtime into unmounting any mount point on the host and all mount points underneath it, potentiality resulting in a host DoS. | [
{
"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/kata-containers/runtime | [] | [
"3b98b259b4672c0929f427a64d8789faed592a4d"
] |
CVE-2020-2025 | 2020-05-19T21:15:10 | 2025-01-14T08:37:14.461358 | Kata Containers before 1.11.0 on Cloud Hypervisor persists guest filesystem changes to the underlying image file on the host. A malicious guest can overwrite the image file to gain control of all subsequent guest VMs. Since Kata Containers uses the same VM image file with all VMMs, this issue may also affect QEMU and Firecracker based guests. | [
{
"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/kata-containers/runtime | [] | [
"3b98b259b4672c0929f427a64d8789faed592a4d"
] |
CVE-2021-23772 | 2021-12-24T12:15:07 | 2025-01-15T01:48:12.020846 | This affects all versions of package github.com/kataras/iris; all versions of package github.com/kataras/iris/v12. The unsafe handling of file names during upload using UploadFormFiles method may enable attackers to write to arbitrary locations outside the designated target folder. | [
{
"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/kataras/iris | [] | [
"08403f0317e7d54607782a65a5344c589087cf55"
] |
CVE-2021-34421 | 2021-11-11T23:15:09 | 2025-01-14T09:22:30.481622 | The Keybase Client for Android before version 5.8.0 and the Keybase Client for iOS before version 5.8.0 fails to properly remove exploded messages initiated by a user if the receiving user places the chat session in the background while the sending user explodes the messages. This could lead to disclosure of sensitive information which was meant to be deleted from the customer's device. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/keybase/client | [] | [
"02197a56e8d679039d771cff910447b1802d3ad8"
] |
CVE-2021-34422 | 2021-11-11T23:15:10 | 2025-01-14T09:22:27.229281 | The Keybase Client for Windows before version 5.7.0 contains a path traversal vulnerability when checking the name of a file uploaded to a team folder. A malicious user could upload a file to a shared folder with a specially crafted file name which could allow a user to execute an application which was not intended on their host machine. If a malicious user leveraged this issue with the public folder sharing feature of the Keybase client, this could lead to remote code execution. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/keybase/client | [] | [
"02197a56e8d679039d771cff910447b1802d3ad8"
] |
CVE-2021-23827 | 2021-02-23T00:15:12 | 2025-01-14T08:56:24.383103 | Keybase Desktop Client before 5.6.0 on Windows and macOS, and before 5.6.1 on Linux, allows an attacker to obtain potentially sensitive media (such as private pictures) in the Cache and uploadtemps directories. It fails to effectively clear cached pictures, even after deletion via normal methodology within the client, or by utilizing the "Explode message/Explode now" functionality. Local filesystem access is needed by the attacker. | [
{
"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/keybase/client | [] | [
"02197a56e8d679039d771cff910447b1802d3ad8"
] |
CVE-2021-34426 | 2021-12-14T20:15:07 | 2025-01-14T09:22:47.619017 | A vulnerability was discovered in the Keybase Client for Windows before version 5.6.0 when a user executed the "keybase git lfs-config" command on the command-line. In versions prior to 5.6.0, a malicious actor with write access to a user\'s Git repository could leverage this vulnerability to potentially execute arbitrary Windows commands on a user\'s local 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/keybase/client | [] | [
"02197a56e8d679039d771cff910447b1802d3ad8"
] |
CVE-2022-22779 | 2022-02-09T23:15:19 | 2025-01-14T10:50:21.736888 | The Keybase Clients for macOS and Windows before version 5.9.0 fails to properly remove exploded messages initiated by a user. This can occur if the receiving user switches to a non-chat feature and places the host in a sleep state before the sending user explodes the messages. This could lead to disclosure of sensitive information which was meant to be deleted from a user’s filesystem. | [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/keybase/client | [] | [
"02197a56e8d679039d771cff910447b1802d3ad8"
] |
CVE-2020-1731 | 2020-03-02T17:15:19 | 2025-01-14T08:35:15.734514 | A flaw was found in all versions of the Keycloak operator, before version 8.0.2,(community only) where the operator generates a random admin password when installing Keycloak, however the password remains the same when deployed to the same OpenShift namespace. | [
{
"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/keycloak/keycloak-operator | [] | [
"67404e08c7acdbb007dbe5fc602d7abf1b3378fb"
] |
CVE-2020-36405 | 2021-07-01T03:15:07 | 2025-01-14T08:48:14.356546 | Keystone Engine 0.9.2 has a use-after-free in llvm_ks::X86Operand::getToken. | [
{
"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/keystone-engine/keystone | [] | [
"dc7932ef2b2c4a793836caec6ecab485005139d6"
] |
CVE-2021-20278 | 2021-05-28T11:15:08 | 2025-02-19T03:14:10.254767 | An authentication bypass vulnerability was found in Kiali in versions before 1.31.0 when the authentication strategy `OpenID` is used. When RBAC is enabled, Kiali assumes that some of the token validation is handled by the underlying cluster. When OpenID `implicit flow` is used with RBAC turned off, this token validation doesn't occur, and this allows a malicious user to bypass the authentication. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N",
"type": "CVSS_V3"
}
] | https://github.com/kiali/kiali | [] | [
"a5769a6ac55687435024c047df12a1b5bf721b28"
] |
CVE-2022-23466 | 2022-12-06T18:15:09 | 2025-01-15T02:15:18.141638 | teler is an real-time intrusion detection and threat alert dashboard. teler prior to version 2.0.0-rc.4 is vulnerable to DOM-based cross-site scripting (XSS) in the teler dashboard. When teler requests messages from the event stream on the `/events` endpoint, the log data displayed on the dashboard are not sanitized. This only affects authenticated users and can only be exploited based on detected threats if the log contains a DOM scripting payload. This vulnerability has been fixed on version `v2.0.0-rc.4`. Users are advised to upgrade. There are no known workarounds for this 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/kitabisa/teler | [] | [
"03528d260cd151081541b5c1f6c7fb6f7b0f847e"
] |
CVE-2020-26213 | 2020-11-06T17:15:12 | 2025-01-15T01:44:31.593722 | In teler before version 0.0.1, if you run teler inside a Docker container and encounter `errors.Exit` function, it will cause denial-of-service (`SIGSEGV`) because it doesn't get process ID and process group ID of teler properly to kills. The issue is patched in teler 0.0.1 and 0.0.1-dev5.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/kitabisa/teler | [] | [
"03528d260cd151081541b5c1f6c7fb6f7b0f847e"
] |
CVE-2022-41939 | 2022-11-19T01:15:13 | 2025-01-14T11:11:58.727140 | knative.dev/func is is a client library and CLI enabling the development and deployment of Kubernetes functions. Developers using a malicious or compromised third-party buildpack could expose their registry credentials or local docker socket to a malicious `lifecycle` container. This issues has been patched in PR #1442, and is part of release 1.8.1. This issue only affects users who are using function buildpacks from third-parties; pinning the builder image to a specific content-hash with a valid `lifecycle` image will also mitigate the attack. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/knative/func | [] | [
"b5ee750fdb47eb94fd74a736ecc5ecfa28f9a854"
] |
CVE-2023-48713 | 2023-11-28T04:15:07 | 2025-01-15T05:02:01.771379 | Knative Serving builds on Kubernetes to support deploying and serving of applications and functions as serverless containers. An attacker who controls a pod to a degree where they can control the responses from the /metrics endpoint can cause Denial-of-Service of the autoscaler from an unbound memory allocation bug. This is a DoS vulnerability, where a non-privileged Knative user can cause a DoS for the cluster. This issue has been patched in version 0.39.0. | [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/knative/serving | [] | [
"bdc986539ce060c44db953fd95ec4753e9275311"
] |
CVE-2019-1020009 | 2019-07-29T15:15:12 | 2025-01-14T07:42:51.096592 | Fleet before 2.1.2 allows exposure of SMTP credentials. | [
{
"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/kolide/fleet | [] | [
"918b9facd140a2bb80cdf589b6d87e58c8cf90ff"
] |
CVE-2024-41820 | 2024-08-05T20:15:35 | 2024-10-08T04:20:34.774909 | Kubean is a cluster lifecycle management toolchain based on kubespray and other cluster LCM engine. The ClusterRole has `*` verbs of `*` resources. If a malicious user can access the worker node which has kubean's deployment, he/she can abuse these excessive permissions to do whatever he/she likes to the whole cluster, resulting in a cluster-level privilege escalation. This issue has been addressed in release version 0.18.0. Users are advised to upgrade. There are no known workarounds for this vulnerability. | null | https://github.com/kubean-io/kubean | [] | [
"3acced073f1c090e488422bd3de194a6a36df714"
] |
CVE-2022-31075 | 2022-07-11T21:15:08 | 2025-01-14T10:58:44.094541 | KubeEdge is an open source system for extending native containerized application orchestration capabilities to hosts at Edge. Prior to versions 1.11.1, 1.10.2, and 1.9.4, EdgeCore may be susceptible to a DoS attack on CloudHub if an attacker was to send a well-crafted HTTP request to `/edge.crt`. If an attacker can send a well-crafted HTTP request to CloudHub, and that request has a very large body, that request can crash the HTTP service through a memory exhaustion vector. The request body is being read into memory, and a body that is larger than the available memory can lead to a successful attack. Because the request would have to make it through authorization, only authorized users may perform this attack. The consequence of the exhaustion is that CloudHub will be in denial of service. KubeEdge is affected only when users enable the CloudHub module in the file `cloudcore.yaml`. This bug has been fixed in Kubeedge 1.11.1, 1.10.2, and 1.9.4. As a workaround, disable the CloudHub switch in the config file `cloudcore.yaml`. | [
{
"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/kubeedge/kubeedge | [] | [
"1f34430ef60d268cd69384ccec9ed0da75727d4d"
] |
CVE-2022-31073 | 2022-07-11T20:15:08 | 2025-01-14T10:58:43.947204 | KubeEdge is an open source system for extending native containerized application orchestration capabilities to hosts at Edge. Prior to versions 1.11.1, 1.10.2, and 1.9.4, the ServiceBus server on the edge side may be susceptible to a DoS attack if an HTTP request containing a very large Body is sent to it. It is possible for the node to be exhausted of memory. The consequence of the exhaustion is that other services on the node, e.g. other containers, will be unable to allocate memory and thus causing a denial of service. Malicious apps accidentally pulled by users on the host and have the access to send HTTP requests to localhost may make an attack. It will be affected only when users enable the `ServiceBus` module in the config file `edgecore.yaml`. This bug has been fixed in Kubeedge 1.11.1, 1.10.2, and 1.9.4. As a workaround, disable the `ServiceBus` module in the config file `edgecore.yaml`. | [
{
"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/kubeedge/kubeedge | [] | [
"1f34430ef60d268cd69384ccec9ed0da75727d4d"
] |
CVE-2022-31080 | 2022-07-11T21:15:08 | 2025-01-14T10:58:45.965242 | KubeEdge is an open source system for extending native containerized application orchestration capabilities to hosts at Edge. Prior to versions 1.11.1, 1.10.2, and 1.9.4, a large response received by the viaduct WSClient can cause a DoS from memory exhaustion. The entire body of the response is being read into memory which could allow an attacker to send a request that returns a response with a large body. The consequence of the exhaustion is that the process which invokes a WSClient will be in a denial of service. The software is affected If users who are authenticated to the edge side connect to `cloudhub` from the edge side through WebSocket protocol. This bug has been fixed in Kubeedge 1.11.1, 1.10.2, and 1.9.4. There are currently no known workarounds. | [
{
"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/kubeedge/kubeedge | [] | [
"1f34430ef60d268cd69384ccec9ed0da75727d4d"
] |
CVE-2022-31074 | 2022-07-11T20:15:08 | 2025-01-14T10:58:43.337549 | KubeEdge is an open source system for extending native containerized application orchestration capabilities to hosts at Edge. Prior to versions 1.11.1, 1.10.2, and 1.9.4, several endpoints in the Cloud AdmissionController may be susceptible to a DoS attack if an HTTP request containing a very large Body is sent to it. The consequence of the exhaustion is that the Cloud AdmissionController will be in denial of service. This bug has been fixed in Kubeedge 1.11.1, 1.10.2, and 1.9.4. There is currently no known workaround. | [
{
"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/kubeedge/kubeedge | [] | [
"1f34430ef60d268cd69384ccec9ed0da75727d4d"
] |
CVE-2022-31078 | 2022-07-11T21:15:08 | 2025-01-14T10:58:44.003783 | KubeEdge is an open source system for extending native containerized application orchestration capabilities to hosts at Edge. Prior to versions 1.11.1, 1.10.2, and 1.9.4, the CloudCore Router does not impose a limit on the size of responses to requests made by the REST handler. An attacker could use this weakness to make a request that will return an HTTP response with a large body and cause DoS of CloudCore. In the HTTP Handler API, the rest handler makes a request to a pre-specified handle. The handle will return an HTTP response that is then read into memory. The consequence of the exhaustion is that CloudCore will be in a denial of service. Only an authenticated user of the cloud can make an attack. It will be affected only when users enable `router` module in the config file `cloudcore.yaml`. This bug has been fixed in Kubeedge 1.11.1, 1.10.2, and 1.9.4. As a workaround, disable the router switch in the config file `cloudcore.yaml`. | [
{
"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/kubeedge/kubeedge | [] | [
"1f34430ef60d268cd69384ccec9ed0da75727d4d"
] |
CVE-2022-31079 | 2022-07-11T21:15:08 | 2025-01-14T10:58:43.662315 | KubeEdge is an open source system for extending native containerized application orchestration capabilities to hosts at Edge. Prior to versions 1.11.1, 1.10.2, and 1.9.4, the Cloud Stream server and the Edge Stream server reads the entire message into memory without imposing a limit on the size of this message. An attacker can exploit this by sending a large message to exhaust memory and cause a DoS. The Cloud Stream server and the Edge Stream server are under DoS attack in this case. The consequence of the exhaustion is that the CloudCore and EdgeCore will be in a denial of service. Only an authenticated user can cause this issue. It will be affected only when users enable `cloudStream` module in the config file `cloudcore.yaml` and enable `edgeStream` module in the config file `edgecore.yaml`. This bug has been fixed in Kubeedge 1.11.1, 1.10.2, and 1.9.4. As a workaround, disable cloudStream module in the config file `cloudcore.yaml` and disable edgeStream module in the config file `edgecore.yaml`. | [
{
"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/kubeedge/kubeedge | [] | [
"1f34430ef60d268cd69384ccec9ed0da75727d4d"
] |
CVE-2022-31076 | 2022-06-27T20:15:08 | 2025-01-14T10:58:44.179687 | KubeEdge is built upon Kubernetes and extends native containerized application orchestration and device management to hosts at the Edge. In affected versions a malicious message can crash CloudCore by triggering a nil-pointer dereference in the UDS Server. Since the UDS Server only communicates with the CSI Driver on the cloud side, the attack is limited to the local host network. As such, an attacker would already need to be an authenticated user of the Cloud. Additionally it will be affected only when users turn on the unixsocket switch in the config file cloudcore.yaml. This bug has been fixed in Kubeedge 1.11.0, 1.10.1, and 1.9.3. Users should update to these versions to resolve the issue. Users unable to upgrade should sisable the unixsocket switch of CloudHub in the config file cloudcore.yaml. | [
{
"score": "CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/kubeedge/kubeedge | [] | [
"1f34430ef60d268cd69384ccec9ed0da75727d4d"
] |
CVE-2022-31077 | 2022-06-27T21:15:07 | 2025-01-14T10:58:45.636690 | KubeEdge is built upon Kubernetes and extends native containerized application orchestration and device management to hosts at the Edge. In affected versions a malicious message response from KubeEdge can crash the CSI Driver controller server by triggering a nil-pointer dereference panic. As a consequence, the CSI Driver controller will be in denial of service. This bug has been fixed in Kubeedge 1.11.0, 1.10.1, and 1.9.3. Users should update to these versions to resolve the issue. At the time of writing, no workaround exists. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/kubeedge/kubeedge | [] | [
"1f34430ef60d268cd69384ccec9ed0da75727d4d"
] |
CVE-2024-5552 | 2024-06-06T19:16:09 | 2025-01-14T12:17:43.338113 | kubeflow/kubeflow is vulnerable to a Regular Expression Denial of Service (ReDoS) attack due to inefficient regular expression complexity in its email validation mechanism. An attacker can remotely exploit this vulnerability without authentication by providing specially crafted input that causes the application to consume an excessive amount of CPU resources. This vulnerability affects the latest version of kubeflow/kubeflow, specifically within the centraldashboard-angular backend component. The impact of exploiting this vulnerability includes resource exhaustion, and service disruption. | [
{
"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/kubeflow/kubeflow | [] | [
"c055d529cdf35ed5b9cbbab12380b27b11b55499"
] |
CVE-2023-6570 | 2023-12-14T13:15:55 | 2025-01-14T11:56:28.502352 | Server-Side Request Forgery (SSRF) in kubeflow/kubeflow | [
{
"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/kubeflow/kubeflow | [] | [
"c055d529cdf35ed5b9cbbab12380b27b11b55499"
] |
CVE-2023-6571 | 2023-12-14T13:15:55 | 2025-01-14T11:56:29.462601 | Cross-site Scripting (XSS) - Reflected in kubeflow/kubeflow | [
{
"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/kubeflow/kubeflow | [] | [
"c055d529cdf35ed5b9cbbab12380b27b11b55499"
] |
CVE-2023-22480 | 2023-01-14T01:15:15 | 2025-01-15T04:41:10.161175 | KubeOperator is an open source Kubernetes distribution focused on helping enterprises plan, deploy and operate production-level K8s clusters. In KubeOperator versions 3.16.3 and below, API interfaces with unauthorized entities and can leak sensitive information. This vulnerability could be used to take over the cluster under certain conditions. This issue has been patched in version 3.16.4.
| [
{
"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/kubeoperator/kubeoperator | [] | [
"8205703d0b66ba888ef8a7da0c800037fbf2ac72"
] |
CVE-2023-22479 | 2023-01-10T21:15:12 | 2025-01-14T11:31:09.385305 | KubePi is a modern Kubernetes panel. A session fixation attack allows an attacker to hijack a legitimate user session, versions 1.6.3 and below are susceptible. A patch will be released in version 1.6.4. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N",
"type": "CVSS_V3"
}
] | https://github.com/kubeoperator/kubepi | [] | [
"eead48749050a1bc47c710acb8267211a387a85d"
] |
CVE-2023-37916 | 2023-07-21T21:15:11 | 2025-01-14T11:49:54.074351 | KubePi is an opensource kubernetes management panel. The endpoint /kubepi/api/v1/users/search?pageNum=1&&pageSize=10 leak password hash of any user (including admin). A sufficiently motivated attacker may be able to crack leaded password hashes. This issue has been addressed in version 1.6.5. Users are advised to upgrade. 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/kubeoperator/kubepi | [] | [
"eead48749050a1bc47c710acb8267211a387a85d"
] |
CVE-2023-37917 | 2023-07-21T21:15:11 | 2025-01-14T11:49:54.658237 | KubePi is an opensource kubernetes management panel. A normal user has permission to create/update users, they can become admin by editing the `isadmin` value in the request. As a result any user may take administrative control of KubePi. This issue has been addressed in version 1.6.5. Users are advised to upgrade. There are no known workarounds for this vulnerability. | [
{
"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/kubeoperator/kubepi | [] | [
"eead48749050a1bc47c710acb8267211a387a85d"
] |
CVE-2020-8569 | 2021-01-21T17:15:14 | 2025-01-14T08:49:19.258343 | Kubernetes CSI snapshot-controller prior to v2.1.3 and v3.0.2 could panic when processing a VolumeSnapshot custom resource when: - The VolumeSnapshot referenced a non-existing PersistentVolumeClaim and the VolumeSnapshot did not reference any VolumeSnapshotClass. - The snapshot-controller crashes, is automatically restarted by Kubernetes, and processes the same VolumeSnapshot custom resource after the restart, entering an endless crashloop. Only the volume snapshot feature is affected by this vulnerability. When exploited, users can’t take snapshots of their volumes or delete the snapshots. All other Kubernetes functionality is not affected. | [
{
"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/kubernetes-csi/external-snapshotter | [] | [
"540ab05a6c403a52ec99a9e8f4e9c89b817d4edd"
] |
CVE-2022-2385 | 2022-07-12T19:15:08 | 2025-01-14T10:49:17.894010 | A security issue was discovered in aws-iam-authenticator where an allow-listed IAM identity may be able to modify their username and escalate privileges. | [
{
"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/kubernetes-sigs/aws-iam-authenticator | [] | [
"0a72c12090fb71ebefbc5036dc1b548b123a91a6"
] |
CVE-2023-2878 | 2023-06-07T15:15:09 | 2025-02-13T19:43:15.650530 | Kubernetes secrets-store-csi-driver in versions before 1.3.3 discloses service account tokens in logs. | [
{
"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/kubernetes-sigs/secrets-store-csi-driver | [] | [
"482ff2ea50f6123b536f0732a61e38dfb31bb4df"
] |
CVE-2020-8568 | 2021-01-21T17:15:14 | 2025-02-19T03:13:13.422388 | Kubernetes Secrets Store CSI Driver versions v0.0.15 and v0.0.16 allow an attacker who can modify a SecretProviderClassPodStatus/Status resource the ability to write content to the host filesystem and sync file contents to Kubernetes Secrets. This includes paths under var/lib/kubelet/pods that contain other Kubernetes Secrets. | [
{
"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/kubernetes-sigs/secrets-store-csi-driver | [] | [
"482ff2ea50f6123b536f0732a61e38dfb31bb4df"
] |
CVE-2023-1943 | 2023-10-12T00:15:10 | 2025-02-19T03:29:50.968350 | Privilege Escalation in kOps using GCE/GCP Provider in Gossip Mode.
| [
{
"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/kubernetes/kops | [] | [
"2e84499741471ba67582aa0ba6fa3f2e3bdbe3e8"
] |
CVE-2018-1002101 | 2018-12-05T21:29:00 | 2025-02-19T02:30:31.016136 | In Kubernetes versions 1.9.0-1.9.9, 1.10.0-1.10.5, and 1.11.0-1.11.1, user input was handled insecurely while setting up volume mounts on Windows nodes, which could lead to command line argument injection. | [
{
"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/kubernetes/kubernetes | [] | [
"b1b29978270dc22fecc592ac55d903350454310a"
] |
CVE-2017-1002100 | 2017-09-14T13:29:01 | 2025-01-14T07:29:44.022690 | Default access permissions for Persistent Volumes (PVs) created by the Kubernetes Azure cloud provider in versions 1.6.0 to 1.6.5 are set to "container" which exposes a URI that can be accessed without authentication on the public internet. Access to the URI string requires privileged access to the Kubernetes cluster or authenticated access to the Azure portal. | [
{
"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/kubernetes/kubernetes | [] | [
"00fb653e406a4b5bbac71a10c3e330afef960f13"
] |
CVE-2023-1174 | 2023-05-24T17:15:09 | 2025-02-19T03:29:14.554641 | This vulnerability exposes a network port in minikube running on macOS with Docker driver that could enable unexpected remote access to the minikube container. | [
{
"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/kubernetes/minikube | [] | [
"628f9de730628669604c1767c870acf4d40f0a1c"
] |
CVE-2023-1944 | 2023-05-24T17:15:09 | 2025-02-19T03:29:11.330171 | This vulnerability enables ssh access to minikube container using a default password. | [
{
"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/kubernetes/minikube | [] | [
"628f9de730628669604c1767c870acf4d40f0a1c"
] |
CVE-2018-1002103 | 2018-12-05T21:29:00 | 2025-02-19T02:27:58.674342 | In Minikube versions 0.3.0-0.29.0, minikube exposes the Kubernetes Dashboard listening on the VM IP at port 30000. In VM environments where the IP is easy to predict, the attacker can use DNS rebinding to indirectly make requests to the Kubernetes Dashboard, create a new Kubernetes Deployment running arbitrary code. If minikube mount is in use, the attacker could also directly access the host filesystem. | [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/kubernetes/minikube | [] | [
"628f9de730628669604c1767c870acf4d40f0a1c"
] |
CVE-2022-39383 | 2022-11-16T20:15:10 | 2025-01-14T11:08:44.171725 | KubeVela is an open source application delivery platform. Users using the VelaUX APIServer could be affected by this vulnerability. When using Helm Chart as the component delivery method, the request address of the warehouse is not restricted, and there is a blind SSRF vulnerability. Users who're using v1.6, please update the v1.6.1. Users who're using v1.5, please update the v1.5.8. There are no known workarounds for this issue. | [
{
"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/kubevela/kubevela | [] | [
"1b7f9aae6513e57b2c4e5f0ab1c04e89cd06e8e9"
] |
CVE-2022-36089 | 2022-09-07T23:15:14 | 2025-02-19T03:28:07.318665 | KubeVela is an application delivery platform Users using KubeVela's VelaUX APIServer could be affected by an authentication bypass vulnerability. In KubeVela prior to versions 1.4.11 and 1.5.4, VelaUX APIServer uses the `PlatformID` as the signed key to generate the JWT tokens for users. Another API called `getSystemInfo` exposes the platformID. This vulnerability allows users to use the platformID to re-generate the JWT tokens to bypass the authentication. Versions 1.4.11 and 1.5.4 contain a patch for this issue. | [
{
"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/kubevela/kubevela | [] | [
"110927ed9799ad85d398759553dec1afcfd40383"
] |
CVE-2019-3841 | 2019-03-25T18:29:00 | 2025-01-14T08:01:20.793223 | Kubevirt/virt-cdi-importer, versions 1.4.0 to 1.5.3 inclusive, were reported to disable TLS certificate validation when importing data into PVCs from container registries. This could enable man-in-the-middle attacks between a container registry and the virt-cdi-component, leading to possible undetected tampering of trusted container image content. | [
{
"score": "CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N",
"type": "CVSS_V3"
}
] | https://github.com/kubevirt/containerized-data-importer | [] | [
"31df8cd3cf2bdf452f4e718a132adcd1406a1478"
] |
CVE-2019-10175 | 2019-06-28T20:15:10 | 2025-01-14T07:42:52.675689 | A flaw was found in the containerized-data-importer in virt-cdi-cloner, version 1.4, where the host-assisted cloning feature does not determine whether the requesting user has permission to access the Persistent Volume Claim (PVC) in the source namespace. This could allow users to clone any PVC in the cluster into their own namespace, effectively allowing access to other user's data. | [
{
"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/kubevirt/containerized-data-importer | [] | [
"31df8cd3cf2bdf452f4e718a132adcd1406a1478"
] |
CVE-2023-26484 | 2023-03-15T21:15:08 | 2025-02-19T03:31:27.743607 | KubeVirt is a virtual machine management add-on for Kubernetes. In versions 0.59.0 and prior, if a malicious user has taken over a Kubernetes node where virt-handler (the KubeVirt node-daemon) is running, the virt-handler service account can be used to modify all node specs. This can be misused to lure-in system-level-privileged components which can, for instance, read all secrets on the cluster, or can exec into pods on other nodes. This way, a compromised node can be used to elevate privileges beyond the node until potentially having full privileged access to the whole cluster. The simplest way to exploit this, once a user could compromise a specific node, is to set with the virt-handler service account all other nodes to unschedulable and simply wait until system-critical components with high privileges appear on its node. No patches are available as of time of publication. As a workaround, gatekeeper users can add a webhook which will block the `virt-handler` service account to modify the spec of a node. | [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N",
"type": "CVSS_V3"
}
] | https://github.com/kubevirt/kubevirt | [] | [
"b755c56f396ed880940821688eaddbd869e33897"
] |
CVE-2020-1701 | 2021-05-27T20:15:07 | 2025-02-19T03:09:20.547135 | A flaw was found in the KubeVirt main virt-handler versions before 0.26.0 regarding the access permissions of virt-handler. An attacker with access to create VMs could attach any secret within their namespace, allowing them to read the contents of that 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/kubevirt/kubevirt | [] | [
"b755c56f396ed880940821688eaddbd869e33897"
] |
CVE-2022-1798 | 2022-09-15T16:15:10 | 2025-02-19T03:25:56.682785 | A path traversal vulnerability in KubeVirt versions up to 0.56 (and 0.55.1) on all platforms allows a user able to configure the kubevirt to read arbitrary files on the host filesystem which are publicly readable or which are readable for UID 107 or GID 107. /proc/self/<> is not accessible. | [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N",
"type": "CVSS_V3"
}
] | https://github.com/kubevirt/kubevirt | [] | [
"b755c56f396ed880940821688eaddbd869e33897"
] |
CVE-2020-14316 | 2020-07-29T19:15:14 | 2025-02-19T03:07:42.335948 | A flaw was found in kubevirt 0.29 and earlier. Virtual Machine Instances (VMIs) can be used to gain access to the host's filesystem. Successful exploitation allows an attacker to assume the privileges of the VM process on the host system. In worst-case scenarios an attacker can read and modify any file on the system where the VMI is running. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability. | [
{
"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/kubevirt/kubevirt | [] | [
"b755c56f396ed880940821688eaddbd869e33897"
] |
CVE-2025-24784 | 2025-01-30T16:15:31 | 2025-02-04T22:41:58.020779 | kubewarden-controller is a Kubernetes controller that allows you to dynamically register Kubewarden admission policies. The policy group feature, added to by the 1.17.0 release. By being namespaced, the AdmissionPolicyGroup has a well constrained impact on cluster resources. Hence, it’s considered safe to allow non-admin users to create and manage these resources in the namespaces they own. Kubewarden policies can be allowed to query the Kubernetes API at evaluation time; these types of policies are called “context aware“. Context aware policies can perform list and get operations against a Kubernetes cluster. The queries are done using the ServiceAccount of the Policy Server instance that hosts the policy. That means that access to the cluster is determined by the RBAC rules that apply to that ServiceAccount. The AdmissionPolicyGroup CRD allowed the deployment of context aware policies. This could allow an attacker to obtain information about resources that are out of their reach, by leveraging a higher access to the cluster granted to the ServiceAccount token used to run the policy. The impact of this vulnerability depends on the privileges that have been granted to the ServiceAccount used to run the Policy Server and assumes that users are using the recommended best practices of keeping the Policy Server's ServiceAccount least privileged. By default, the Kubewarden helm chart grants access to the following resources (cluster wide) only: Namespace, Pod, Deployment and Ingress. This vulnerability is fixed in 1.21.0. | null | https://github.com/kubewarden/kubewarden-controller | [] | [
"72547ccb14ee06de0316958eed48898b995dfed9"
] |
CVE-2025-24376 | 2025-01-30T16:15:31 | 2025-02-04T22:42:02.549696 | kubewarden-controller is a Kubernetes controller that allows you to dynamically register Kubewarden admission policies. By design, AdmissionPolicy and AdmissionPolicyGroup can evaluate only namespaced resources. The resources to be evaluated are determined by the rules provided by the user when defining the policy. There might be Kubernetes namespaced resources that should not be validated by AdmissionPolicy and by the AdmissionPolicyGroup policies because of their sensitive nature. For example, PolicyReport are namespaced resources that contain the list of non compliant objects found inside of a namespace. An attacker can use either an AdmissionPolicy or an AdmissionPolicyGroup to prevent the creation and update of PolicyReport objects to hide non-compliant resources. Moreover, the same attacker might use a mutating AdmissionPolicy to alter the contents of the PolicyReport created inside of the namespace. Starting from the 1.21.0 release, the validation rules applied to AdmissionPolicy and AdmissionPolicyGroup have been tightened to prevent them from validating sensitive types of namespaced resources. | null | https://github.com/kubewarden/kubewarden-controller | [] | [
"72547ccb14ee06de0316958eed48898b995dfed9"
] |
CVE-2020-13619 | 2020-07-01T17:15:13 | 2025-02-19T03:06:01.169554 | php/exec/escapeshellarg in Locutus PHP through 2.0.11 allows an attacker to achieve 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/kvz/locutus | [] | [
"a32b21c3e23e0c863646ad2d5e53bf9cda4a79d4"
] |
CVE-2021-33708 | 2021-08-10T20:15:08 | 2025-01-14T09:17:21.984961 | Due to insufficient input validation in Kyma, authenticated users can pass a Header of their choice and escalate privileges. | [
{
"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/kyma-project/kyma | [] | [
"86705e61e749feb7f1c18ea5b2975ac725511ee8"
] |
CVE-2021-38182 | 2021-12-14T16:15:08 | 2025-01-14T09:29:17.480810 | Due to insufficient input validation of Kyma, authenticated users can pass a Header of their choice and escalate privileges which can completely compromise the cluster. | [
{
"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/kyma-project/kyma | [] | [
"86705e61e749feb7f1c18ea5b2975ac725511ee8"
] |
CVE-2023-28444 | 2023-03-24T20:15:15 | 2025-01-15T04:49:36.365434 | angular-server-side-configuration helps configure an angular application at runtime on the server or in a docker container via environment variables. angular-server-side-configuration detects used environment variables in TypeScript (.ts) files during build time of an Angular CLI project. The detected environment variables are written to a ngssc.json file in the output directory.
During deployment of an Angular based app, the environment variables based on the variables from ngssc.json are inserted into the apps index.html (or defined index file). With version 15.0.0 the environment variable detection was widened to the entire project, relative to the angular.json file from the Angular CLI. In a monorepo setup, this could lead to environment variables intended for a backend/service to be detected and written to the ngssc.json, which would then be populated and exposed via index.html. This has NO IMPACT, in a plain Angular project that has no backend component. This vulnerability has been mitigated in version 15.1.0, by adding an option `searchPattern` which restricts the detection file range by default. As a workaround, manually edit or create ngssc.json or run script after ngssc.json generation.
| [
{
"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/kyubisation/angular-server-side-configuration | [] | [
"caf4e170f2f71109b1ac16331fe8744b643a1710"
] |
CVE-2024-48921 | 2024-10-29T15:15:10 | 2025-02-19T03:09:07.797713 | Kyverno is a policy engine designed for Kubernetes. A kyverno ClusterPolicy, ie. "disallow-privileged-containers," can be overridden by the creation of a PolicyException in a random namespace. By design, PolicyExceptions are consumed from any namespace. Administrators may not recognize that this allows users with privileges to non-kyverno namespaces to create exceptions. This vulnerability is fixed in 1.13.0. | [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N",
"type": "CVSS_V3"
}
] | https://github.com/kyverno/kyverno | [] | [
"8b6d3d1f6a728f44ef4b3688999650789c5c10ec"
] |
CVE-2023-42814 | 2023-11-13T21:15:07 | 2025-01-15T04:58:42.333302 | Kyverno is a policy engine designed for Kubernetes. A security vulnerability was found in Kyverno where an attacker could cause denial of service of Kyverno. The vulnerable component in Kyvernos Notary verifier. An attacker would need control over the registry from which Kyverno would fetch attestations. With such a position, the attacker could return a malicious response to Kyverno, when Kyverno would send a request to the registry. The malicious response would cause denial of service of Kyverno, such that other users' admission requests would be blocked from being processed. This is a vulnerability in a new component released in v1.11.0. The only users affected by this are those that have been building Kyverno from source at the main branch which is not encouraged. Users consuming official Kyverno releases are not affected. There are no known cases of this vulnerability being exploited in the wild.
| [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/kyverno/kyverno | [] | [
"8b6d3d1f6a728f44ef4b3688999650789c5c10ec"
] |
CVE-2023-42813 | 2023-11-13T21:15:07 | 2025-01-15T04:58:41.218009 | Kyverno is a policy engine designed for Kubernetes. A security vulnerability was found in Kyverno where an attacker could cause denial of service of Kyverno. The vulnerable component in Kyvernos Notary verifier. An attacker would need control over the registry from which Kyverno would fetch attestations. With such a position, the attacker could return a malicious response to Kyverno, when Kyverno would send a request to the registry. The malicious response would cause denial of service of Kyverno, such that other users' admission requests would be blocked from being processed. This is a vulnerability in a new component released in v1.11.0. The only users affected by this are those that have been building Kyverno from source at the main branch which is not encouraged. Users consuming official Kyverno releases are not affected. There are no known cases of this vulnerability being exploited in the wild. | [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/kyverno/kyverno | [] | [
"8b6d3d1f6a728f44ef4b3688999650789c5c10ec"
] |
CVE-2023-47630 | 2023-11-14T21:15:13 | 2025-02-19T03:35:51.255313 | Kyverno is a policy engine designed for Kubernetes. An issue was found in Kyverno that allowed an attacker to control the digest of images used by Kyverno users. The issue would require the attacker to compromise the registry that the Kyverno users fetch their images from. The attacker could then return an vulnerable image to the the user and leverage that to further escalate their position. As such, the attacker would need to know which images the Kyverno user consumes and know of one of multiple exploitable vulnerabilities in previous digests of the images. Alternatively, if the attacker has compromised the registry, they could craft a malicious image with a different digest with intentionally placed vulnerabilities and deliver the image to the user. Users pulling their images by digests and from trusted registries are not impacted by this vulnerability. There is no evidence of this being exploited in the wild. The issue has been patched in 1.10.5. All users are advised to upgrade. There are no known workarounds for this vulnerability. | [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
] | https://github.com/kyverno/kyverno | [] | [
"8b6d3d1f6a728f44ef4b3688999650789c5c10ec"
] |
CVE-2023-42815 | 2023-11-13T21:15:07 | 2025-01-15T04:58:41.078891 | Kyverno is a policy engine designed for Kubernetes. A security vulnerability was found in Kyverno where an attacker could cause denial of service of Kyverno. The vulnerability was in Kyvernos Notary verifier. An attacker would need control over the registry from which Kyverno would fetch signatures. With such a position, the attacker could return a malicious response to Kyverno, when Kyverno would send a request to the registry. The malicious response would cause denial of service of Kyverno, such that other users' admission requests would be blocked from being processed. This is a vulnerability in a new component released in v1.11.0. The only users affected by this are those that have been building Kyverno from source at the main branch which is not encouraged. Users consuming official Kyverno releases are not affected. There are no known cases of this vulnerability being exploited in the wild. | [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/kyverno/kyverno | [] | [
"8b6d3d1f6a728f44ef4b3688999650789c5c10ec"
] |
CVE-2023-42816 | 2023-11-13T21:15:08 | 2025-01-15T04:58:41.905053 | Kyverno is a policy engine designed for Kubernetes. A security vulnerability was found in Kyverno where an attacker could cause denial of service of Kyverno. The vulnerability was in Kyvernos Notary verifier. An attacker would need control over the registry from which Kyverno would fetch signatures. With such a position, the attacker could return a malicious response to Kyverno, when Kyverno would send a request to the registry. The malicious response would cause denial of service of Kyverno, such that other users' admission requests would be blocked from being processed. This is a vulnerability in a new component released in v1.11.0. The only users affected by this are those that have been building Kyverno from source at the main branch which is not encouraged. Users consuming official Kyverno releases are not affected. There are no known cases of this vulnerability being exploited in the wild. | [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/kyverno/kyverno | [] | [
"8b6d3d1f6a728f44ef4b3688999650789c5c10ec"
] |
CVE-2023-34091 | 2023-06-01T17:15:10 | 2025-02-19T03:33:56.751473 | Kyverno is a policy engine designed for Kubernetes. In versions of Kyverno prior to 1.10.0, resources which have the `deletionTimestamp` field defined can bypass validate, generate, or mutate-existing policies, even in cases where the `validationFailureAction` field is set to `Enforce`. This situation occurs as resources pending deletion were being consciously exempted by Kyverno, as a way to reduce processing load as policies are typically not applied to objects which are being deleted. However, this could potentially result in allowing a malicious user to leverage the Kubernetes finalizers feature by setting a finalizer which causes the Kubernetes API server to set the `deletionTimestamp` and then not completing the delete operation as a way to explicitly to bypass a Kyverno policy. Note that this is not applicable to Kubernetes Pods but, as an example, a Kubernetes Service resource can be manipulated using an indefinite finalizer to bypass policies. This is resolved in Kyverno 1.10.0. There is no known workaround. | [
{
"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/kyverno/kyverno | [] | [
"8b6d3d1f6a728f44ef4b3688999650789c5c10ec"
] |
CVE-2023-33191 | 2023-05-30T07:15:09 | 2025-01-14T11:45:45.734176 | Kyverno is a policy engine designed for Kubernetes. Kyverno seccomp control can be circumvented. Users of the podSecurity `validate.podSecurity` subrule in Kyverno 1.9.2 and 1.9.3 are vulnerable. This issue was patched in version 1.9.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/kyverno/kyverno | [] | [
"dab311d6b3d75ce0b20e6166dabc479b08d5c98e"
] |
CVE-2022-47633 | 2022-12-23T23:15:08 | 2025-01-14T11:17:12.681102 | An image signature validation bypass vulnerability in Kyverno 1.8.3 and 1.8.4 allows a malicious image registry (or a man-in-the-middle attacker) to inject unsigned arbitrary container images into a protected Kubernetes cluster. This is fixed in 1.8.5. This has been fixed in 1.8.5 and mitigations are available for impacted releases. | [
{
"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/kyverno/kyverno | [] | [
"8b6d3d1f6a728f44ef4b3688999650789c5c10ec"
] |
CVE-2020-36565 | 2022-12-07T17:15:09 | 2025-01-15T01:45:28.727769 | Due to improper sanitization of user input on Windows, the static file handler allows for directory traversal, allowing an attacker to read files outside of the target directory that the server has permission to read. | [
{
"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/labstack/echo | [] | [
"cb84205219f6b0962ab5bb39ab6c0911f5f1652d"
] |
CVE-2023-46575 | 2023-11-24T14:15:08 | 2025-02-19T03:40:15.832508 | A SQL injection vulnerability exists in Meshery prior to version v0.6.179, enabling a remote attacker to retrieve sensitive information and execute arbitrary code through the “order” parameter | [
{
"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/layer5io/meshery | [] | [
"0f9a8e948abaf323cff4e57863be8d19ad10ff3c"
] |
CVE-2021-31856 | 2021-04-28T06:15:07 | 2025-01-14T09:15:56.328538 | A SQL Injection vulnerability in the REST API in Layer5 Meshery 0.5.2 allows an attacker to execute arbitrary SQL commands via the /experimental/patternfiles endpoint (order parameter in GetMesheryPatterns in models/meshery_pattern_persister.go). | [
{
"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/layer5io/meshery | [] | [
"0f9a8e948abaf323cff4e57863be8d19ad10ff3c"
] |
CVE-2021-4263 | 2022-12-21T19:15:12 | 2025-01-15T02:06:27.737250 | A vulnerability, which was classified as problematic, has been found in leanote 2.6.1. This issue affects the function define of the file public/js/plugins/history.js. The manipulation of the argument content leads to cross site scripting. The attack may be initiated remotely. The identifier of the patch is 0f9733c890077942150696dcc6d2b1482b7a0a19. It is recommended to apply a patch to fix this issue. The identifier VDB-216461 was assigned to this vulnerability. | [
{
"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/leanote/leanote | [] | [
"371f5e23c3d7353598a48ea1849d7c46d05a49e9"
] |
CVE-2019-1010003 | 2019-07-11T13:15:10 | 2025-01-14T07:04:06.462471 | Leanote prior to version 2.6 is affected by: Cross Site Scripting (XSS). | [
{
"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/leanote/leanote | [] | [
"371f5e23c3d7353598a48ea1849d7c46d05a49e9"
] |
CVE-2017-1000459 | 2018-01-03T00:29:00 | 2025-01-14T06:57:21.592287 | Leanote version <= 2.5 is vulnerable to XSS due to not sanitized input in markdown notes | [
{
"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/leanote/leanote | [] | [
"371f5e23c3d7353598a48ea1849d7c46d05a49e9"
] |
CVE-2018-18553 | 2018-10-22T01:29:00 | 2025-01-14T07:25:58.877016 | Leanote 2.6.1 has XSS via the Blog Basic Setting title field, which is mishandled during rendering of the "likes" page. | [
{
"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/leanote/leanote | [] | [
"371f5e23c3d7353598a48ea1849d7c46d05a49e9"
] |
CVE-2018-17427 | 2018-10-01T08:29:00 | 2025-01-14T07:25:15.590429 | SIMDComp before 0.1.0 allows remote attackers to cause a denial of service (heap-based buffer over-read and application crash) because it can read (and then discard) extra bytes. | [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
] | https://github.com/lemire/simdcomp | [] | [
"ba62c2359c58e3005f2671122b8d8912a5a52437"
] |
Subsets and Splits