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-2018-17854
2018-10-01T08:29:02
2025-01-14T07:25:29.224090
SIMDComp before 0.1.1 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. NOTE: this issue exists because of an incomplete fix for CVE-2018-17427.
[ { "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" ]
CVE-2024-21664
2024-01-09T20:15:43
2025-01-15T05:06:41.799086
jwx is a Go module implementing various JWx (JWA/JWE/JWK/JWS/JWT, otherwise known as JOSE) technologies. Calling `jws.Parse` with a JSON serialized payload where the `signature` field is present while `protected` is absent can lead to a nil pointer dereference. The vulnerability can be used to crash/DOS a system doing JWS verification. This vulnerability has been patched in versions 2.0.19 and 1.2.28.
[ { "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/lestrrat-go/jwx
[]
[ "42d47a75de7858fc60492f617a6ec4a9eda7d8dd" ]
CVE-2023-49290
2023-12-05T00:15:09
2025-01-15T05:01:55.154464
lestrrat-go/jwx is a Go module implementing various JWx (JWA/JWE/JWK/JWS/JWT, otherwise known as JOSE) technologies. A p2c parameter set too high in JWE's algorithm PBES2-* could lead to a denial of service. The JWE key management algorithms based on PBKDF2 require a JOSE Header Parameter called p2c (PBES2 Count). This parameter dictates the number of PBKDF2 iterations needed to derive a CEK wrapping key. Its primary purpose is to intentionally slow down the key derivation function, making password brute-force and dictionary attacks more resource- intensive. Therefore, if an attacker sets the p2c parameter in JWE to a very large number, it can cause a lot of computational consumption, resulting in a denial of service. This vulnerability has been addressed in commit `64f2a229b` which has been included in release version 1.2.27 and 2.0.18. 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:L", "type": "CVSS_V3" } ]
https://github.com/lestrrat-go/jwx
[]
[ "42d47a75de7858fc60492f617a6ec4a9eda7d8dd" ]
CVE-2024-43406
2024-08-20T15:15:24
2024-10-08T04:21:49.649192
LF Edge eKuiper is a lightweight IoT data analytics and stream processing engine running on resource-constraint edge devices. A user could utilize and exploit SQL Injection to allow the execution of malicious SQL query via Get method in sqlKvStore. This vulnerability is fixed in 1.14.2.
[ { "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/lf-edge/ekuiper
[]
[ "4c4206dae5e5dd036629f5d40cc1bfaa7320b0e1" ]
CVE-2021-29417
2021-03-29T19:15:13
2025-01-14T09:03:21.063515
gitjacker before 0.1.0 allows remote attackers to execute arbitrary code via a crafted .git directory because of directory traversal.
[ { "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/liamg/gitjacker
[]
[ "262d7bb95adc1168c2b908cb317c9122eb4b0573" ]
CVE-2023-40583
2023-08-25T21:15:09
2025-02-19T03:34:24.960959
libp2p is a networking stack and library modularized out of The IPFS Project, and bundled separately for other tools to use. In go-libp2p, by using signed peer records a malicious actor can store an arbitrary amount of data in a remote node’s memory. This memory does not get garbage collected and so the victim can run out of memory and crash. If users of go-libp2p in production are not monitoring memory consumption over time, it could be a silent attack i.e. the attacker could bring down nodes over a period of time (how long depends on the node resources i.e. a go-libp2p node on a virtual server with 4 gb of memory takes about 90 sec to bring down; on a larger server, it might take a bit longer.) This issue was patched in version 0.27.4.
[ { "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/libp2p/go-libp2p
[]
[ "bfee9f593553b3cdaecc351f04b98aac78b8d8af" ]
CVE-2022-23492
2022-12-08T01:15:09
2025-02-19T03:25:19.550264
go-libp2p is the offical libp2p implementation in the Go programming language. Version `0.18.0` and older of go-libp2p are vulnerable to targeted resource exhaustion attacks. These attacks target libp2p’s connection, stream, peer, and memory management. An attacker can cause the allocation of large amounts of memory, ultimately leading to the process getting killed by the host’s operating system. While a connection manager tasked with keeping the number of connections within manageable limits has been part of go-libp2p, this component was designed to handle the regular churn of peers, not a targeted resource exhaustion attack. Users are advised to upgrade their version of go-libp2p to version `0.18.1` or newer. Users unable to upgrade may consult the denial of service (dos) mitigation page for more information on how to incorporate mitigation strategies, monitor your application, and respond to attacks.
[ { "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/libp2p/go-libp2p
[]
[ "bfee9f593553b3cdaecc351f04b98aac78b8d8af" ]
CVE-2022-23487
2022-12-07T21:15:10
2025-02-19T03:24:15.252849
js-libp2p is the official javascript Implementation of libp2p networking stack. Versions older than `v0.38.0` of js-libp2p are vulnerable to targeted resource exhaustion attacks. These attacks target libp2p’s connection, stream, peer, and memory management. An attacker can cause the allocation of large amounts of memory, ultimately leading to the process getting killed by the host’s operating system. While a connection manager tasked with keeping the number of connections within manageable limits has been part of js-libp2p, this component was designed to handle the regular churn of peers, not a targeted resource exhaustion attack. Users are advised to update their js-libp2p dependency to `v0.38.0` or greater. 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/libp2p/go-libp2p
[]
[ "bfee9f593553b3cdaecc351f04b98aac78b8d8af" ]
CVE-2018-19114
2018-11-08T18:29:00
2025-01-14T07:26:23.412716
An issue was discovered in MinDoc through v1.0.2. It allows attackers to gain privileges by uploading an image file with contents that represent an admin session, and then sending a Cookie: header with a mindoc_id value containing the relative pathname of this uploaded file. For example, the mindoc_id (aka session ID) could be of the form aa/../../uploads/blog/201811/attach_#.jpg where '#' is a hex value displayed in the upload field of a manage/blogs/edit/ screen.
[ { "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/lifei6671/mindoc
[]
[ "1d8d74afb16dbc275a07f72acaa3463c40493c83" ]
CVE-2020-26895
2020-10-21T02:15:12
2025-02-19T03:38:23.279759
Prior to 0.10.0-beta, LND (Lightning Network Daemon) would have accepted a counterparty high-S signature and broadcast tx-relay invalid local commitment/HTLC transactions. This can be exploited by any peer with an open channel regardless of the victim situation (e.g., routing node, payment-receiver, or payment-sender). The impact is a loss of funds in certain situations.
[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N", "type": "CVSS_V3" } ]
https://github.com/lightningnetwork/lnd
[]
[ "07437f6ec41fcb8a1fcb06e5f7e8873685212d15" ]
CVE-2023-32684
2023-05-30T18:15:10
2025-01-15T04:53:15.048205
Lima launches Linux virtual machines, typically on macOS, for running containerd. Prior to version 0.16.0, a virtual machine instance with a malicious disk image could read a single file on the host filesystem, even when no filesystem is mounted from the host. The official templates of Lima and the well-known third party products (Colima, Rancher Desktop, and Finch) are unlikely to be affected by this issue. To exploit this issue, the attacker has to embed the target file path (an absolute or a relative path from the instance directory) in a malicious disk image, as the qcow2 (or vmdk) backing file path string. As Lima refuses to run as the root, it is practically impossible for the attacker to read the entire host disk via `/dev/rdiskN`. Also, practically, the attacker cannot read at least the first 512 bytes (MBR) of the target file. The issue has been patched in Lima in version 0.16.0 by prohibiting using a backing file path in the VM base image.
[ { "score": "CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N", "type": "CVSS_V3" } ]
https://github.com/lima-vm/lima
[]
[ "261b4cdd315d2fbdfe49023eb7e1cb8ea87d625b" ]
CVE-2024-40632
2024-07-15T22:15:03
2025-01-15T05:15:35.555689
Linkerd is an open source, ultralight, security-first service mesh for Kubernetes. In affected versions when the application being run by linkerd is susceptible to SSRF, an attacker could potentially trigger a denial-of-service (DoS) attack by making requests to localhost:4191/shutdown. Linkerd could introduce an optional environment variable to control a token that must be passed as a header. Linkerd should reject shutdown requests that do not include this header. This issue has been addressed in release version edge-24.6.2 and all users are advised to upgrade. There are no known workarounds for this vulnerability.
null
https://github.com/linkerd/linkerd2
[]
[ "a91542fe802d64117df5e93d1cdb29dfd8896843" ]
CVE-2023-49805
2023-12-11T23:15:08
2025-01-15T05:02:07.648468
Uptime Kuma is an easy-to-use self-hosted monitoring tool. Prior to version 1.23.9, the application uses WebSocket (with Socket.io), but it does not verify that the source of communication is valid. This allows third-party website to access the application on behalf of their client. When connecting to the server using Socket.IO, the server does not validate the `Origin` header leading to other site being able to open connections to the server and communicate with it. Other websites still need to authenticate to access most features, however this can be used to circumvent firewall protections made in place by people deploying the application. Without origin validation, Javascript executed from another origin would be allowed to connect to the application without any user interaction. Without login credentials, such a connection is unable to access protected endpoints containing sensitive data of the application. However, such a connection may allow attacker to further exploit unseen vulnerabilities of the application. Users with "No-auth" mode configured who are relying on a reverse proxy or firewall to provide protection to the application would be especially vulnerable as it would grant the attacker full access to the application. In version 1.23.9, additional verification of the HTTP Origin header has been added to the socket.io connection handler. By default, if the `Origin` header is present, it would be checked against the Host header. Connection would be denied if the hostnames do not match, which would indicate that the request is cross-origin. Connection would be allowed if the `Origin` header is not present. Users can override this behavior by setting environment variable `UPTIME_KUMA_WS_ORIGIN_CHECK=bypass`.
[ { "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/louislam/dockge
[]
[ "8296c7b18f9c85799a69e7e67993ead080053401" ]
CVE-2023-49804
2023-12-11T23:15:07
2025-01-15T05:02:08.529031
Uptime Kuma is an easy-to-use self-hosted monitoring tool. Prior to version 1.23.9, when a user changes their login password in Uptime Kuma, a previously logged-in user retains access without being logged out. This behavior persists consistently, even after system restarts or browser restarts. This vulnerability allows unauthorized access to user accounts, compromising the security of sensitive information. The same vulnerability was partially fixed in CVE-2023-44400, but logging existing users out of their accounts was forgotten. To mitigate the risks associated with this vulnerability, the maintainers made the server emit a `refresh` event (clients handle this by reloading) and then disconnecting all clients except the one initiating the password change. It is recommended to update Uptime Kuma to version 1.23.9.
[ { "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/louislam/dockge
[]
[ "8296c7b18f9c85799a69e7e67993ead080053401" ]
CVE-2024-56331
2024-12-20T20:15:24
2025-01-15T05:16:52.954260
Uptime Kuma is an open source, self-hosted monitoring tool. An **Improper URL Handling Vulnerability** allows an attacker to access sensitive local files on the server by exploiting the `file:///` protocol. This vulnerability is triggered via the **"real-browser"** request type, which takes a screenshot of the URL provided by the attacker. By supplying local file paths, such as `file:///etc/passwd`, an attacker can read sensitive data from the server. This vulnerability arises because the system does not properly validate or sanitize the user input for the URL field. Specifically: 1. The URL input (`<input data-v-5f5c86d7="" id="url" type="url" class="form-control" pattern="https?://.+" required="">`) allows users to input arbitrary file paths, including those using the `file:///` protocol, without server-side validation. 2. The server then uses the user-provided URL to make a request, passing it to a browser instance that performs the "real-browser" request, which takes a screenshot of the content at the given URL. If a local file path is entered (e.g., `file:///etc/passwd`), the browser fetches and captures the file’s content. Since the user input is not validated, an attacker can manipulate the URL to request local files (e.g., `file:///etc/passwd`), and the system will capture a screenshot of the file's content, potentially exposing sensitive data. Any **authenticated user** who can submit a URL in "real-browser" mode is at risk of exposing sensitive data through screenshots of these files. This issue has been addressed in version 1.23.16 and all users are advised to upgrade. There are no known workarounds for this vulnerability.
null
https://github.com/louislam/uptime-kuma
[]
[ "2b57b3e863954c9d9cf7911b76f600bb8de4c41b" ]
CVE-2023-26777
2023-04-04T15:15:09
2025-02-13T17:46:22.530282
Cross Site Scripting vulnerability found in : louislam Uptime Kuma v.1.19.6 and before allows a remote attacker to execute arbitrary commands via the description, title, footer, and incident creation parameter of the status_page.js endpoint.
[ { "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/louislam/uptime-kuma
[]
[ "2b57b3e863954c9d9cf7911b76f600bb8de4c41b" ]
CVE-2023-36821
2023-07-05T22:15:09
2025-01-14T11:48:43.087199
Uptime Kuma, a self-hosted monitoring tool, allows an authenticated attacker to install a maliciously crafted plugin in versions prior to 1.22.1, which may lead to remote code execution. Uptime Kuma allows authenticated users to install plugins from an official list of plugins. This feature is currently disabled in the web interface, but the corresponding API endpoints are still available after login. After downloading a plugin, it's installed by calling `npm install` in the installation directory of the plugin. Because the plugin is not validated against the official list of plugins or installed with `npm install --ignore-scripts`, a maliciously crafted plugin taking advantage of npm scripts can gain remote code execution. Version 1.22.1 contains a patch for this issue.
[ { "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/louislam/uptime-kuma
[]
[ "2b57b3e863954c9d9cf7911b76f600bb8de4c41b" ]
CVE-2023-36822
2023-07-05T22:15:09
2025-01-14T11:48:48.029152
Uptime Kuma, a self-hosted monitoring tool, has a path traversal vulnerability in versions prior to 1.22.1. Uptime Kuma allows authenticated users to install plugins from an official list of plugins. This feature is currently disabled in the web interface, but the corresponding API endpoints are still available after login. Before a plugin is downloaded, the plugin installation directory is checked for existence. If it exists, it's removed before the plugin installation. Because the plugin is not validated against the official list of plugins or sanitized, the check for existence and the removal of the plugin installation directory are prone to path traversal. This vulnerability allows an authenticated attacker to delete files from the server Uptime Kuma is running on. Depending on which files are deleted, Uptime Kuma or the whole system may become unavailable due to data loss.
[ { "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/louislam/uptime-kuma
[]
[ "2b57b3e863954c9d9cf7911b76f600bb8de4c41b" ]
CVE-2023-25811
2023-02-21T21:15:11
2025-01-14T11:35:02.749914
Uptime Kuma is a self-hosted monitoring tool. In versions prior to 1.20.0 the Uptime Kuma `name` parameter allows a persistent XSS attack. 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/louislam/uptime-kuma
[]
[ "2b57b3e863954c9d9cf7911b76f600bb8de4c41b" ]
CVE-2023-25810
2023-02-21T21:15:11
2025-01-14T11:35:02.404802
Uptime Kuma is a self-hosted monitoring tool. In versions prior to 1.20.0 the Uptime Kuma status page allows a persistent XSS attack. 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/louislam/uptime-kuma
[]
[ "2b57b3e863954c9d9cf7911b76f600bb8de4c41b" ]
CVE-2023-44400
2023-10-09T16:15:10
2025-01-15T04:58:57.202631
Uptime Kuma is a self-hosted monitoring tool. Prior to version 1.23.3, attackers with access to a user's device can gain persistent account access. This is caused by missing verification of Session Tokens after password changes and/or elapsed inactivity periods. Version 1.23.3 has a patch for the issue.
[ { "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/louislam/uptime-kuma
[]
[ "2b57b3e863954c9d9cf7911b76f600bb8de4c41b" ]
CVE-2023-49276
2023-12-01T22:15:10
2025-01-15T05:01:58.697745
Uptime Kuma is an open source self-hosted monitoring tool. In affected versions the Google Analytics element in vulnerable to Attribute Injection leading to Cross-Site-Scripting (XSS). Since the custom status interface can set an independent Google Analytics ID and the template has not been sanitized, there is an attribute injection vulnerability here, which can lead to XSS attacks. This vulnerability has been addressed in commit `f28dccf4e` which is included in release version 1.23.7. Users are advised to upgrade. There are no known workarounds for 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/louislam/uptime-kuma
[]
[ "2b57b3e863954c9d9cf7911b76f600bb8de4c41b" ]
CVE-2022-1561
2022-08-01T13:15:09
2025-01-14T09:31:21.210375
Lura and KrakenD-CE versions older than v2.0.2 and KrakenD-EE versions older than v2.0.0 do not sanitize URL parameters correctly, allowing a malicious user to alter the backend URL defined for a pipe when remote users send crafty URL requests. The vulnerability does not affect KrakenD itself, but the consumed backend might be vulnerable.
[ { "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/luraproject/lura
[]
[ "eb879b75fe77194d48fb11646514462e8ea82c7b" ]
CVE-2023-37036
2025-01-21T23:15:10
2025-02-18T22:06:54.985452
A Null pointer dereference vulnerability in the Mobile Management Entity (MME) in Magma <= 1.8.0 (fixed in v1.9 commit 08472ba98b8321f802e95f5622fa90fec2dea486) allows network-adjacent attackers to crash the MME via an S1AP `Uplink NAS Transport` packet missing an expected `ENB_UE_S1AP_ID` field.
[ { "score": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "type": "CVSS_V3" } ]
https://github.com/magma/magma
[]
[ "49ed2e691622f23a552deb874b27825d2c745b61" ]
CVE-2023-37037
2025-01-21T23:15:11
2025-02-18T22:06:51.557348
A Null pointer dereference vulnerability in the Mobile Management Entity (MME) in Magma <= 1.8.0 (fixed in v1.9 commit 08472ba98b8321f802e95f5622fa90fec2dea486) allows network-adjacent attackers to crash the MME via an S1AP `S1Setup Request` packet missing an expected `Supported TAs` field.
[ { "score": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "type": "CVSS_V3" } ]
https://github.com/magma/magma
[]
[ "49ed2e691622f23a552deb874b27825d2c745b61" ]
CVE-2024-24417
2025-01-21T23:15:11
2025-02-18T22:07:01.769801
The Linux Foundation Magma <= 1.8.0 (fixed in v1.9 commit 08472ba98b8321f802e95f5622fa90fec2dea486) was discovered to contain a buffer overflow in the decode_protocol_configuration_options function at /3gpp/3gpp_24.008_sm_ies.c. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted NAS packet.
[ { "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/magma/magma
[]
[ "49ed2e691622f23a552deb874b27825d2c745b61" ]
CVE-2024-24423
2025-01-21T23:15:12
2025-02-18T22:06:59.704834
The Linux Foundation Magma <= 1.8.0 (fixed in v1.9 commit 08472ba98b8321f802e95f5622fa90fec2dea486) was discovered to contain a buffer overflow in the decode_esm_message_container function at /nas/ies/EsmMessageContainer.cpp. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted NAS packet.
[ { "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/magma/magma
[]
[ "49ed2e691622f23a552deb874b27825d2c745b61" ]
CVE-2023-37031
2025-01-21T23:15:10
2025-02-18T22:06:57.957587
A Null pointer dereference vulnerability in the Mobile Management Entity (MME) in Magma <= 1.8.0 (fixed in v1.9 commit 08472ba98b8321f802e95f5622fa90fec2dea486) allows network-adjacent attackers to crash the MME via an S1AP `eNB Configuration Transfer` packet missing its required `Target eNB ID` field.
[ { "score": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "type": "CVSS_V3" } ]
https://github.com/magma/magma
[]
[ "49ed2e691622f23a552deb874b27825d2c745b61" ]
CVE-2023-37029
2025-01-21T23:15:10
2025-01-30T01:59:36.782026
Magma versions <= 1.8.0 (fixed in v1.9 commit 08472ba98b8321f802e95f5622fa90fec2dea486) are susceptible to an assertion-based crash when an oversized NAS packet is received. An attacker may leverage this behavior to repeatedly crash the MME via either a compromised base station or via an unauthenticated cellphone within range of a base station managed by the MME, causing a denial of service.
[ { "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/magma/magma
[]
[ "49ed2e691622f23a552deb874b27825d2c745b61" ]
CVE-2023-37030
2025-01-21T23:15:10
2025-02-18T22:06:52.011231
A Null pointer dereference vulnerability in the Mobile Management Entity (MME) in Magma <= 1.8.0 (fixed in v1.9 commit 08472ba98b8321f802e95f5622fa90fec2dea486) allows network-adjacent attackers to crash the MME via an S1AP `Initial UE Message` packet missing an expected `eNB_UE_S1AP_ID` field.
[ { "score": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "type": "CVSS_V3" } ]
https://github.com/magma/magma
[]
[ "49ed2e691622f23a552deb874b27825d2c745b61" ]
CVE-2024-24419
2025-01-21T23:15:11
2025-02-18T22:07:01.037821
The Linux Foundation Magma <= 1.8.0 (fixed in v1.9 commit 08472ba98b8321f802e95f5622fa90fec2dea486) was discovered to contain a buffer overflow in the decode_traffic_flow_template_packet_filter function at /3gpp/3gpp_24.008_sm_ies.c. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted NAS packet.
[ { "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/magma/magma
[]
[ "49ed2e691622f23a552deb874b27825d2c745b61" ]
CVE-2024-24416
2025-01-21T23:15:11
2025-02-18T22:06:58.434811
The Linux Foundation Magma <= 1.8.0 (fixed in v1.9 commit 08472ba98b8321f802e95f5622fa90fec2dea486) was discovered to contain a buffer overflow in the decode_access_point_name_ie function at /3gpp/3gpp_24.008_sm_ies.c. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted NAS packet.
[ { "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/magma/magma
[]
[ "49ed2e691622f23a552deb874b27825d2c745b61" ]
CVE-2024-24418
2025-01-21T23:15:11
2025-02-18T22:07:02.465599
The Linux Foundation Magma <= 1.8.0 (fixed in v1.9 commit 08472ba98b8321f802e95f5622fa90fec2dea486) was discovered to contain a buffer overflow in the decode_pdn_address function at /nas/ies/PdnAddress.cpp. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted NAS packet.
[ { "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/magma/magma
[]
[ "49ed2e691622f23a552deb874b27825d2c745b61" ]
CVE-2024-24422
2025-01-21T23:15:12
2025-02-18T22:07:00.028706
The Linux Foundation Magma <= 1.8.0 (fixed in v1.9 commit 08472ba98b8321f802e95f5622fa90fec2dea486) was discovered to contain a stack overflow in the decode_protocol_configuration_options function at /3gpp/3gpp_24.008_sm_ies.c. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted NAS packet.
[ { "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/magma/magma
[]
[ "49ed2e691622f23a552deb874b27825d2c745b61" ]
CVE-2023-37033
2025-01-21T23:15:10
2025-02-18T22:06:58.874639
A Null pointer dereference vulnerability in the Mobile Management Entity (MME) in Magma <= 1.8.0 (fixed in v1.9 commit 08472ba98b8321f802e95f5622fa90fec2dea486) allows network-adjacent attackers to crash the MME via an S1AP `Initial UE Message` packet missing an expected `EUTRAN_CGI` field.
[ { "score": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "type": "CVSS_V3" } ]
https://github.com/magma/magma
[]
[ "49ed2e691622f23a552deb874b27825d2c745b61" ]
CVE-2023-37038
2025-01-21T23:15:11
2025-02-18T22:06:52.460974
A Null pointer dereference vulnerability in the Mobile Management Entity (MME) in Magma <= 1.8.0 (fixed in v1.9 commit 08472ba98b8321f802e95f5622fa90fec2dea486) allows network-adjacent attackers to crash the MME via an S1AP `Uplink NAS Transport` packet missing an expected `MME_UE_S1AP_ID` field.
[ { "score": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "type": "CVSS_V3" } ]
https://github.com/magma/magma
[]
[ "49ed2e691622f23a552deb874b27825d2c745b61" ]
CVE-2023-37034
2025-01-21T23:15:10
2025-02-18T22:06:58.792054
A Null pointer dereference vulnerability in the Mobile Management Entity (MME) in Magma <= 1.8.0 (fixed in v1.9 commit 08472ba98b8321f802e95f5622fa90fec2dea486) allows network-adjacent attackers to crash the MME via an S1AP `Initial UE Message` packet missing an expected `TAI` field.
[ { "score": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "type": "CVSS_V3" } ]
https://github.com/magma/magma
[]
[ "49ed2e691622f23a552deb874b27825d2c745b61" ]
CVE-2023-37032
2025-01-21T23:15:10
2025-02-18T22:06:56.425101
A Stack-based buffer overflow in the Mobile Management Entity (MME) of Magma versions <= 1.8.0 (fixed in v1.9 commit 08472ba98b8321f802e95f5622fa90fec2dea486) allows remote attackers to crash the MME with an unauthenticated cellphone by sending a NAS packet containing an oversized `Emergency Number List` Information Element.
[ { "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/magma/magma
[]
[ "49ed2e691622f23a552deb874b27825d2c745b61" ]
CVE-2020-14306
2020-09-16T18:15:13
2025-01-14T08:22:02.071063
An incorrect access control flaw was found in the operator, openshift-service-mesh/istio-rhel8-operator all versions through 1.1.3. This flaw allows an attacker with a basic level of access to the cluster to deploy a custom gateway/pod to any namespace, potentially gaining access to privileged service account tokens. 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:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]
https://github.com/maistra/istio-operator
[]
[ "bf27bd25783eba2aa64593ff63e1031d4e179a4c" ]
CVE-2021-4238
2022-12-27T22:15:12
2025-01-15T02:06:13.194240
Randomly-generated alphanumeric strings contain significantly less entropy than expected. The RandomAlphaNumeric and CryptoRandomAlphaNumeric functions always return strings containing at least one digit from 0 to 9. This significantly reduces the amount of entropy in short strings generated by these functions.
[ { "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/masterminds/goutils
[]
[ "41ac8693c5c10a92ea1ff5ac3a7f95646f6123b0" ]
CVE-2022-36009
2022-08-19T21:15:08
2025-01-15T02:31:13.432776
gomatrixserverlib is a Go library for matrix protocol federation. Dendrite is a Matrix homeserver written in Go, an alternative to Synapse. The power level parsing within gomatrixserverlib was failing to parse the `"events_default"` key of the `m.room.power_levels` event, defaulting the event default power level to zero in all cases. Power levels are the matrix terminology for user access level. In rooms where the `"events_default"` power level had been changed, this could result in events either being incorrectly authorised or rejected by Dendrite servers. gomatrixserverlib contains a fix as of commit `723fd49` and Dendrite 0.9.3 has been updated accordingly. Matrix rooms where the `"events_default"` power level has not been changed from the default of zero are not vulnerable. Users are advised to upgrade. 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:H/A:H", "type": "CVSS_V3" } ]
https://github.com/matrix-org/dendrite
[]
[ "ef7262a7a21f6106b8130a7ad8a1911cbd46a82f" ]
CVE-2022-39200
2022-09-12T20:15:12
2025-01-15T02:28:12.085457
Dendrite is a Matrix homeserver written in Go. In affected versions events retrieved from a remote homeserver using the `/get_missing_events` path did not have their signatures verified correctly. This could potentially allow a remote homeserver to provide invalid/modified events to Dendrite via this endpoint. Note that this does not apply to events retrieved through other endpoints (e.g. `/event`, `/state`) as they have been correctly verified. Homeservers that have federation disabled are not vulnerable. The problem has been fixed in Dendrite 0.9.8. Users are advised to upgrade. There are no known workarounds for this issue.
[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N", "type": "CVSS_V3" } ]
https://github.com/matrix-org/dendrite
[]
[ "ef7262a7a21f6106b8130a7ad8a1911cbd46a82f" ]
CVE-2022-1333
2022-04-13T18:15:09
2025-02-19T03:25:00.889085
Mattermost Playbooks plugin v1.24.0 and earlier fails to properly check the limit on the number of webhooks, which allows authenticated and authorized users to create a specifically drafted Playbook which could trigger a large amount of webhook requests leading to Denial of Service.
[ { "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/mattermost/mattermost-plugin-playbooks
[]
[ "53da83c17a425103819e4f688d2e21516cbf6a38" ]
CVE-2022-1548
2022-05-03T21:15:08
2025-02-19T03:25:16.146243
Mattermost Playbooks plugin 1.25 and earlier fails to properly restrict user-level permissions, which allows playbook members to escalate their membership privileges and perform actions restricted to playbook admins.
[ { "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/mattermost/mattermost-plugin-playbooks
[]
[ "53da83c17a425103819e4f688d2e21516cbf6a38" ]
CVE-2023-33967
2023-05-31T18:15:09
2025-01-15T04:53:39.733116
EaseProbe is a tool that can do health/status checking. An SQL injection issue was discovered in EaseProbe before 2.1.0 when using MySQL/PostgreSQL data checking. This problem has been fixed in v2.1.0.
[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]
https://github.com/megaease/easeprobe
[]
[ "8b36e4424bedfadd2e6101f662f2d5fe74ff73b0" ]
CVE-2022-24968
2022-02-11T22:15:07
2025-02-19T03:23:14.452798
In Mellium mellium.im/xmpp through 0.21.0, an attacker capable of spoofing DNS TXT records can redirect a WebSocket connection request to a server under their control without causing TLS certificate verification to fail. This occurs because the wrong host name is selected during this verification.
[ { "score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N", "type": "CVSS_V3" } ]
https://github.com/mellium/xmpp
[]
[ "e76b53fd804dbf840f4e0b419c2bab74e1a78fbc" ]
CVE-2024-56800
2024-12-30T19:15:08
2025-01-15T05:27:42.084128
Firecrawl is a web scraper that allows users to extract the content of a webpage for a large language model. Versions prior to 1.1.1 contain a server-side request forgery (SSRF) vulnerability. The scraping engine could be exploited by crafting a malicious site that redirects to a local IP address. This allowed exfiltration of local network resources through the API. The cloud service was patched on December 27th, 2024, and the maintainers have checked that no user data was exposed by this vulnerability. Scraping engines used in the open sourced version of Firecrawl were patched on December 29th, 2024, except for the playwright services which the maintainers have determined to be un-patchable. All users of open-source software (OSS) Firecrawl should upgrade to v1.1.1. As a workaround, OSS Firecrawl users should supply the playwright services with a secure proxy. A proxy can be specified through the `PROXY_SERVER` env in the environment variables. Please refer to the documentation for instructions. Ensure that the proxy server one is using is setup to block all traffic going to link-local IP addresses.
null
https://github.com/mendableai/firecrawl
[]
[ "c5b6495e48e82c08e49039104ce4f33675c09aaf" ]
CVE-2021-35342
2021-08-27T10:15:07
2025-01-14T09:19:15.284476
The useradm service 1.14.0 (in Northern.tech Mender Enterprise 2.7.x before 2.7.1) and 1.13.0 (in Northern.tech Mender Enterprise 2.6.x before 2.6.1) allows users to access the system with their JWT token after logout, because of missing invalidation (if the JWT verification cache is enabled).
[ { "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/mendersoftware/useradm
[]
[ "54d0194f1832054f854b25172d740ac51ce541da" ]
CVE-2024-29031
2024-03-21T23:15:11
2025-01-15T05:14:19.545094
Meshery is an open source, cloud native manager that enables the design and management of Kubernetes-based infrastructure and applications. A SQL injection vulnerability in Meshery prior to version 0.7.17 allows a remote attacker to obtain sensitive information via the `order` parameter of `GetMeshSyncResources`. Version 0.7.17 contains a patch for this issue.
null
https://github.com/meshery/meshery
[]
[ "7d361114a1e7a25ff1803915f4dd5564e4a8f605" ]
CVE-2024-35182
2024-05-27T19:15:08
2025-01-15T05:16:41.594146
Meshery is an open source, cloud native manager that enables the design and management of Kubernetes-based infrastructure and applications. A SQL injection vulnerability in Meshery prior to version 0.7.22 may lead to arbitrary file write by using a SQL injection stacked queries payload, and the ATTACH DATABASE command. Additionally, attackers may be able to access and modify any data stored in the database, like performance profiles (which may contain session cookies), Meshery application data, or any Kubernetes configuration added to the system. The Meshery project exposes the function `GetAllEvents` at the API URL `/api/v2/events`. The sort query parameter read in `events_streamer.go` is directly used to build a SQL query in `events_persister.go`. Version 0.7.22 fixes this issue by using the `SanitizeOrderInput` function.
null
https://github.com/meshery/meshery
[]
[ "7d361114a1e7a25ff1803915f4dd5564e4a8f605" ]
CVE-2024-35181
2024-05-27T19:15:08
2025-01-15T05:17:07.152102
Meshery is an open source, cloud native manager that enables the design and management of Kubernetes-based infrastructure and applications. A SQL injection vulnerability in Meshery prior to version 0.7.22 may lead to arbitrary file write by using a SQL injection stacked queries payload, and the ATTACH DATABASE command. Additionally, attackers may be able to access and modify any data stored in the database, like performance profiles (which may contain session cookies), Meshery application data, or any Kubernetes configuration added to the system. The Meshery project exposes the function `GetMeshSyncResourcesKinds` at the API URL `/api/system/meshsync/resources/kinds`. The order query parameter is directly used to build a SQL query in `meshync_handler.go`. Version 0.7.22 fixes this issue.
null
https://github.com/meshery/meshery
[]
[ "7d361114a1e7a25ff1803915f4dd5564e4a8f605" ]
CVE-2024-43803
2024-09-03T19:15:14
2024-12-20T21:13:23.260261
The Bare Metal Operator (BMO) implements a Kubernetes API for managing bare metal hosts in Metal3. The `BareMetalHost` (BMH) CRD allows the `userData`, `metaData`, and `networkData` for the provisioned host to be specified as links to Kubernetes Secrets. There are fields for both the `Name` and `Namespace` of the Secret, meaning that versions of the baremetal-operator prior to 0.8.0, 0.6.2, and 0.5.2 will read a `Secret` from any namespace. A user with access to create or edit a `BareMetalHost` can thus exfiltrate a `Secret` from another namespace by using it as e.g. the `userData` for provisioning some host (note that this need not be a real host, it could be a VM somewhere). BMO will only read a key with the name `value` (or `userData`, `metaData`, or `networkData`), so that limits the exposure somewhat. `value` is probably a pretty common key though. Secrets used by _other_ `BareMetalHost`s in different namespaces are always vulnerable. It is probably relatively unusual for anyone other than cluster administrators to have RBAC access to create/edit a `BareMetalHost`. This vulnerability is only meaningful, if the cluster has users other than administrators and users' privileges are limited to their respective namespaces. The patch prevents BMO from accepting links to Secrets from other namespaces as BMH input. Any BMH configuration is only read from the same namespace only. The problem is patched in BMO releases v0.7.0, v0.6.2 and v0.5.2 and users should upgrade to those versions. Prior upgrading, duplicate the BMC Secrets to the namespace where the corresponding BMH is. After upgrade, remove the old Secrets. As a workaround, an operator can configure BMO RBAC to be namespace scoped for Secrets, instead of cluster scoped, to prevent BMO from accessing Secrets from other namespaces.
null
https://github.com/metal3-io/baremetal-operator
[]
[ "e3abcb2889e01af0e9a3fcea6add41847922ba80" ]
CVE-2023-30841
2023-04-26T19:15:09
2025-01-14T11:42:00.303472
Baremetal Operator (BMO) is a bare metal host provisioning integration for Kubernetes. Prior to version 0.3.0, ironic and ironic-inspector deployed within Baremetal Operator using the included `deploy.sh` store their `.htpasswd` files as ConfigMaps instead of Secrets. This causes the plain-text username and hashed password to be readable by anyone having a cluster-wide read-access to the management cluster, or access to the management cluster's Etcd storage. This issue is patched in baremetal-operator PR#1241, and is included in BMO release 0.3.0 onwards. As a workaround, users may modify the kustomizations and redeploy the BMO, or recreate the required ConfigMaps as Secrets per instructions in baremetal-operator PR#1241.
[ { "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/metal3-io/baremetal-operator
[]
[ "e3abcb2889e01af0e9a3fcea6add41847922ba80" ]
CVE-2019-10743
2019-10-29T19:15:16
2025-01-14T07:56:51.026896
All versions of archiver allow attacker to perform a Zip Slip attack via the "unarchive" functions. It is exploited using a specially crafted zip archive, that holds path traversal filenames. When exploited, a filename in a malicious archive is concatenated to the target extraction directory, which results in the final path ending up outside of the target folder. For instance, a zip may hold a file with a "../../file.exe" location and thus break out of the target folder. If an executable or a configuration file is overwritten with a file containing malicious code, the problem can turn into an arbitrary code execution issue quite easily.
[ { "score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N", "type": "CVSS_V3" } ]
https://github.com/mholt/archiver
[]
[ "45ba413222e433902bfac0f63eae69c285357cc3" ]
CVE-2018-1002207
2018-07-25T17:29:02
2025-01-15T01:29:47.295910
mholt/archiver golang package before e4ef56d48eb029648b0e895bb0b6a393ef0829c3 is vulnerable to directory traversal, allowing attackers to write to arbitrary files via a ../ (dot dot slash) in an archive entry that is mishandled during extraction. This vulnerability is also known as 'Zip-Slip'.
[ { "score": "CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N", "type": "CVSS_V3" } ]
https://github.com/mholt/archiver
[]
[ "cdc68dd1f170b8dfc1a0d2231b5bb0967ed67006" ]
CVE-2023-50463
2023-12-10T23:15:07
2025-01-14T12:06:48.660749
The caddy-geo-ip (aka GeoIP) middleware through 0.6.0 for Caddy 2, when trust_header X-Forwarded-For is used, allows attackers to spoof their source IP address via an X-Forwarded-For header, which may bypass a protection mechanism (trusted_proxy directive in reverse_proxy or IP address range restrictions).
[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N", "type": "CVSS_V3" } ]
https://github.com/mholt/caddy
[]
[ "a5f20829cb87c3474b68e7af4def46e71b8864e0" ]
CVE-2022-29718
2022-06-02T21:15:07
2025-01-14T10:56:51.271104
Caddy v2.4 was discovered to contain an open redirect vulnerability. A remote unauthenticated attacker may exploit this vulnerability to redirect users to arbitrary web URLs by tricking the victim users to click on crafted links.
[ { "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/mholt/caddy
[]
[ "30b6d1f47a35d00fca7cff0daa2ff59a98c5a85e" ]
CVE-2018-19148
2018-11-10T19:29:00
2025-02-19T02:29:00.185588
Caddy through 0.11.0 sends incorrect certificates for certain invalid requests, making it easier for attackers to enumerate hostnames. Specifically, when unable to match a Host header with a vhost in its configuration, it serves the X.509 certificate for a randomly selected vhost in its configuration. Repeated requests (with a nonexistent hostname in the Host header) permit full enumeration of all certificates on the server. This generally permits an attacker to easily and accurately discover the existence of and relationships among hostnames that weren't meant to be public, though this information could likely have been discovered via other methods with additional effort.
[ { "score": "CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N", "type": "CVSS_V3" } ]
https://github.com/mholt/caddy
[]
[ "a5f20829cb87c3474b68e7af4def46e71b8864e0" ]
CVE-2018-21246
2020-06-15T17:15:09
2025-02-19T02:35:22.997922
Caddy before 0.10.13 mishandles TLS client authentication, as demonstrated by an authentication bypass caused by the lack of the StrictHostMatching mode.
[ { "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/mholt/caddy
[]
[ "a5f20829cb87c3474b68e7af4def46e71b8864e0" ]
CVE-2025-22149
2025-01-09T18:15:30
2025-01-15T05:17:21.927970
JWK Set (JSON Web Key Set) is a JWK and JWK Set Go implementation. Prior to 0.6.0, the project's provided HTTP client's local JWK Set cache should do a full replacement when the goroutine refreshes the remote JWK Set. The current behavior is to overwrite or append. This is a security issue for use cases that utilize the provided auto-caching HTTP client and where key removal from a JWK Set is equivalent to revocation. The affected auto-caching HTTP client was added in version v0.5.0 and fixed in v0.6.0. The only workaround would be to remove the provided auto-caching HTTP client and replace it with a custom implementation. This involves setting the HTTPClientStorageOptions.RefreshInterval to zero (or not specifying the value).
null
https://github.com/micahparks/jwkset
[]
[ "ce57ded280d99191ea54e3c4c5460c58207c3bbf" ]
CVE-2021-28955
2021-03-22T07:15:12
2025-01-14T09:04:09.485241
git-bug before 0.7.2 has an Uncontrolled Search Path Element. It will execute git.bat from the current directory in certain PATH situations (most often seen on Windows).
[ { "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/michaelmure/git-bug
[]
[ "2d64b85db71a17ff3277bbbf7ac9d8e81f8e416c" ]
CVE-2024-41258
2024-07-31T21:15:18
2024-10-08T04:20:11.181371
An issue was discovered in filestash v0.4. The usage of the ssh.InsecureIgnoreHostKey() disables host key verification, possibly allowing attackers to obtain sensitive information via a man-in-the-middle attack.
[ { "score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N", "type": "CVSS_V3" } ]
https://github.com/mickael-kerjean/filestash
[]
[ "0c105c1ac5197ebfcbdd7ca08cde2c7314912d7d" ]
CVE-2024-41256
2024-07-31T21:15:18
2024-10-08T04:20:11.296480
Default configurations in the ShareProofVerifier function of filestash v0.4 causes the application to skip the TLS certificate verification process when sending out email verification codes, possibly allowing attackers to access sensitive data via a man-in-the-middle attack.
[ { "score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N", "type": "CVSS_V3" } ]
https://github.com/mickael-kerjean/filestash
[]
[ "0c105c1ac5197ebfcbdd7ca08cde2c7314912d7d" ]
CVE-2021-29272
2021-03-27T18:15:13
2025-01-14T09:03:14.561779
bluemonday before 1.0.5 allows XSS because certain Go lowercasing converts an uppercase Cyrillic character, defeating a protection mechanism against the "script" string.
[ { "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/microcosm-cc/bluemonday
[]
[ "3cce251c9ed2a9ee66c8f8984fff3d19d45999df" ]
CVE-2018-8115
2018-05-02T19:29:00
2025-02-19T02:40:34.108892
A remote code execution vulnerability exists when the Windows Host Compute Service Shim (hcsshim) library fails to properly validate input while importing a container image, aka "Windows Host Compute Service Shim Remote Code Execution Vulnerability." This affects Windows Host Compute.
[ { "score": "CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H", "type": "CVSS_V3" } ]
https://github.com/microsoft/hcsshim
[]
[ "8fccb44c85288f54389c412b2ec466e4481fd252" ]
CVE-2024-47083
2024-09-25T22:15:03
2024-10-08T04:27:20.119157
Power Platform Terraform Provider allows managing environments and other resources within Power Platform. Versions prior to 3.0.0 have an issue in the Power Platform Terraform Provider where sensitive information, specifically the `client_secret` used in the service principal authentication, may be exposed in logs. This exposure occurs due to an error in the logging code that causes the `client_secret` to not be properly masked when logs are persisted or viewed. Users should upgrade to version 3.0.0 to receive a patched version of the provider that removes all logging of sensitive content. Users who have used this provider with the affected versions should take the following additional steps to mitigate the risk: Immediately rotate the `client_secret` for any service principal that has been configured using this Terraform provider. This will invalidate any potentially exposed secrets. Those who have set the `TF_LOG_PATH` environment variable or configured Terraform to persist logs to a file or an external system, consider disabling this until they have updated to a fixed version of the provider. Those who have existing logs that may contain the `client_secret` should remove or sanitize these logs to prevent unauthorized access. This includes logs on disk, in monitoring systems, or in logging services.
[ { "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/microsoft/terraform-provider-power-platform
[]
[ "e1532012b2d5b26c608fd35e929a4941c8fdaf01" ]
CVE-2024-26165
2024-03-12T17:15:55
2025-01-15T05:11:41.137826
Visual Studio Code Elevation of Privilege 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/microsoft/vscode
[]
[ "3db7e09f3b61f915d03bbfa58e258d6eee843f35" ]
CVE-2024-43601
2024-10-08T18:15:27
2024-11-08T22:48:41.277595
Visual Studio Code for Linux Remote Code Execution Vulnerability
[ { "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/microsoft/vscode
[]
[ "3db7e09f3b61f915d03bbfa58e258d6eee843f35" ]
CVE-2023-21779
2023-01-10T22:15:19
2025-01-14T11:24:08.219850
Visual Studio Code Remote Code Execution Vulnerability
[ { "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/microsoft/vscode
[]
[ "3db7e09f3b61f915d03bbfa58e258d6eee843f35" ]
CVE-2023-24893
2023-04-11T21:15:19
2025-01-14T11:35:19.791316
Visual Studio Code Remote Code Execution Vulnerability
[ { "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/microsoft/vscode
[]
[ "3db7e09f3b61f915d03bbfa58e258d6eee843f35" ]
CVE-2023-33144
2023-06-14T00:15:12
2025-01-14T11:46:07.481865
Visual Studio Code Spoofing Vulnerability
[ { "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N", "type": "CVSS_V3" } ]
https://github.com/microsoft/vscode
[]
[ "3db7e09f3b61f915d03bbfa58e258d6eee843f35" ]
CVE-2023-36742
2023-09-12T17:15:10
2025-01-14T11:50:26.465299
Visual Studio Code Remote Code Execution Vulnerability
[ { "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/microsoft/vscode
[]
[ "3db7e09f3b61f915d03bbfa58e258d6eee843f35" ]
CVE-2023-29338
2023-05-09T18:15:13
2025-01-14T11:41:23.478568
Visual Studio Code Spoofing Vulnerability
[ { "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N", "type": "CVSS_V3" } ]
https://github.com/microsoft/vscode
[]
[ "3db7e09f3b61f915d03bbfa58e258d6eee843f35" ]
CVE-2021-28473
2021-04-13T20:15:21
2025-01-14T09:04:43.381955
Visual Studio Code Remote Code Execution Vulnerability
null
https://github.com/microsoft/vscode
[]
[ "3db7e09f3b61f915d03bbfa58e258d6eee843f35" ]
CVE-2021-28469
2021-04-13T20:15:20
2025-01-14T09:04:47.335931
Visual Studio Code Remote Code Execution Vulnerability
null
https://github.com/microsoft/vscode
[]
[ "3db7e09f3b61f915d03bbfa58e258d6eee843f35" ]
CVE-2021-28457
2021-04-13T20:15:20
2025-01-14T09:04:45.719406
Visual Studio Code Remote Code Execution Vulnerability
null
https://github.com/microsoft/vscode
[]
[ "3db7e09f3b61f915d03bbfa58e258d6eee843f35" ]
CVE-2021-28477
2021-04-13T20:15:21
2025-01-14T09:04:28.338041
Visual Studio Code Remote Code Execution Vulnerability
null
https://github.com/microsoft/vscode
[]
[ "3db7e09f3b61f915d03bbfa58e258d6eee843f35" ]
CVE-2021-28471
2021-04-13T20:15:21
2025-01-14T09:04:39.598727
Remote Development Extension for Visual Studio Code Remote Code Execution Vulnerability
null
https://github.com/microsoft/vscode
[]
[ "3db7e09f3b61f915d03bbfa58e258d6eee843f35" ]
CVE-2021-28475
2021-04-13T20:15:21
2025-01-14T09:04:41.492332
Visual Studio Code Remote Code Execution Vulnerability
null
https://github.com/microsoft/vscode
[]
[ "3db7e09f3b61f915d03bbfa58e258d6eee843f35" ]
CVE-2021-34479
2021-07-14T18:15:11
2025-01-14T09:20:37.563018
Microsoft Visual Studio Spoofing Vulnerability
null
https://github.com/microsoft/vscode
[]
[ "3db7e09f3b61f915d03bbfa58e258d6eee843f35" ]
CVE-2021-34529
2021-07-14T18:15:12
2025-01-14T09:20:38.074095
Visual Studio Code Remote Code Execution Vulnerability
null
https://github.com/microsoft/vscode
[]
[ "3db7e09f3b61f915d03bbfa58e258d6eee843f35" ]
CVE-2021-34528
2021-07-14T18:15:12
2025-01-14T09:20:28.724374
Visual Studio Code Remote Code Execution Vulnerability
null
https://github.com/microsoft/vscode
[]
[ "3db7e09f3b61f915d03bbfa58e258d6eee843f35" ]
CVE-2021-31211
2021-05-11T19:15:10
2025-01-14T09:14:09.023379
Visual Studio Code Remote Code Execution Vulnerability
null
https://github.com/microsoft/vscode
[]
[ "3db7e09f3b61f915d03bbfa58e258d6eee843f35" ]
CVE-2021-31214
2021-05-11T19:15:10
2025-01-14T09:13:54.206479
Visual Studio Code Remote Code Execution Vulnerability
null
https://github.com/microsoft/vscode
[]
[ "3db7e09f3b61f915d03bbfa58e258d6eee843f35" ]
CVE-2021-43891
2021-12-15T15:15:11
2025-01-14T10:03:13.746564
Visual Studio Code Remote Code Execution Vulnerability
[ { "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/microsoft/vscode
[]
[ "3db7e09f3b61f915d03bbfa58e258d6eee843f35" ]
CVE-2022-24526
2022-03-09T17:15:16
2025-01-14T10:52:17.808141
Visual Studio Code Spoofing Vulnerability
null
https://github.com/microsoft/vscode
[]
[ "3db7e09f3b61f915d03bbfa58e258d6eee843f35" ]
CVE-2022-30129
2022-05-10T21:15:13
2025-01-14T10:59:07.553184
Visual Studio Code Remote Code Execution Vulnerability
null
https://github.com/microsoft/vscode
[]
[ "3db7e09f3b61f915d03bbfa58e258d6eee843f35" ]
CVE-2022-41034
2022-10-11T19:15:20
2025-01-14T11:11:56.144610
Visual Studio Code Remote Code Execution Vulnerability
[ { "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/microsoft/vscode
[]
[ "3db7e09f3b61f915d03bbfa58e258d6eee843f35" ]
CVE-2019-1414
2020-01-24T21:15:13
2025-02-19T02:48:57.997113
An elevation of privilege vulnerability exists in Visual Studio Code when it exposes a debug listener to users of a local computer, aka 'Visual Studio Code Elevation of Privilege Vulnerability'.
[ { "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/microsoft/vscode
[]
[ "3db7e09f3b61f915d03bbfa58e258d6eee843f35" ]
CVE-2020-1416
2020-07-14T23:15:17
2025-01-14T08:23:49.610821
An elevation of privilege vulnerability exists in Visual Studio and Visual Studio Code when they load software dependencies, aka 'Visual Studio and Visual Studio Code Elevation of Privilege Vulnerability'.
[ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ]
https://github.com/microsoft/vscode
[]
[ "3db7e09f3b61f915d03bbfa58e258d6eee843f35" ]
CVE-2020-16881
2020-09-11T17:15:17
2025-01-14T08:36:10.099116
<p>A remote code execution vulnerability exists in Visual Studio Code when a user is tricked into opening a malicious 'package.json' file. An attacker who successfully exploited the vulnerability could run arbitrary code in the context of the current user. If the current user is logged on with administrative user rights, an attacker could take control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.</p> <p>To exploit this vulnerability, an attacker would need to convince a target to clone a repository and open it in Visual Studio Code. Attacker-specified code would execute when the target opens the malicious 'package.json' file.</p> <p>The update address the vulnerability by modifying the way Visual Studio Code handles JSON files.</p>
null
https://github.com/microsoft/vscode
[]
[ "3db7e09f3b61f915d03bbfa58e258d6eee843f35" ]
CVE-2018-17419
2019-03-07T23:29:00
2025-02-19T02:32:00.788960
An issue was discovered in setTA in scan_rr.go in the Miek Gieben DNS library before 1.0.10 for Go. A dns.ParseZone() parsing error causes a segmentation violation, leading to denial of service.
[ { "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/miekg/dns
[]
[ "426ea785a99b1dad4755492b923feb327d9251a6" ]
CVE-2023-27591
2023-03-17T20:15:13
2025-01-14T11:36:38.967829
Miniflux is a feed reader. Prior to version 2.0.43, an unauthenticated user can retrieve Prometheus metrics from a publicly reachable Miniflux instance where the `METRICS_COLLECTOR` configuration option is enabled and `METRICS_ALLOWED_NETWORKS` is set to `127.0.0.1/8` (the default). A patch is available in Miniflux 2.0.43. As a workaround, set `METRICS_COLLECTOR` to `false` (default) or run Miniflux behind a trusted reverse-proxy.
[ { "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/miniflux/v2
[]
[ "b2fd84e0d376a3af6329b9bb2e772ce38a25c31c" ]
CVE-2023-27592
2023-03-17T20:15:13
2025-01-14T11:36:41.194130
Miniflux is a feed reader. Since v2.0.25, Miniflux will automatically proxy images served over HTTP to prevent mixed content errors. When an outbound request made by the Go HTTP client fails, the `html.ServerError` is returned unescaped without the expected Content Security Policy header added to valid responses. By creating an RSS feed item with the inline description containing an `<img>` tag with a `srcset` attribute pointing to an invalid URL like `http:a<script>alert(1)</script>`, we can coerce the proxy handler into an error condition where the invalid URL is returned unescaped and in full. This results in JavaScript execution on the Miniflux instance as soon as the user is convinced (e.g. by a message in the alt text) to open the broken image. An attacker can execute arbitrary JavaScript in the context of a victim Miniflux user when they open a broken image in a crafted RSS feed. This can be used to perform actions on the Miniflux instance as that user and gain administrative access to the Miniflux instance if it is reachable and the victim is an administrator. A patch is available in version 2.0.43. As a workaround sisable image proxy; default value is `http-only`.
[ { "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/miniflux/v2
[]
[ "b2fd84e0d376a3af6329b9bb2e772ce38a25c31c" ]
CVE-2023-33955
2023-05-30T07:15:10
2025-01-15T04:54:28.797902
Minio Console is the UI for MinIO Object Storage. Unicode RIGHT-TO-LEFT OVERRIDE characters can be used to mask the original filename. This issue has been patched in version 0.28.0.
[ { "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/minio/console
[]
[ "31fbdd515cea4cc9ee20f9995b751eac96da5a09" ]
CVE-2021-41266
2021-11-15T21:15:07
2025-02-19T03:23:38.661555
Minio console is a graphical user interface for the for MinIO operator. Minio itself is a multi-cloud object storage project. Affected versions are subject to an authentication bypass issue in the Operator Console when an external IDP is enabled. All users on release v0.12.2 and before are affected and are advised to update to 0.12.3 or newer. Users unable to upgrade should add automountServiceAccountToken: false to the operator-console deployment in Kubernetes so no service account token will get mounted inside the pod, then disable the external identity provider authentication by unset the CONSOLE_IDP_URL, CONSOLE_IDP_CLIENT_ID, CONSOLE_IDP_SECRET and CONSOLE_IDP_CALLBACK environment variable and instead use the Kubernetes service account token.
[ { "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/minio/console
[]
[ "31fbdd515cea4cc9ee20f9995b751eac96da5a09" ]
CVE-2024-24747
2024-01-31T22:15:54
2025-01-15T05:08:55.555414
MinIO is a High Performance Object Storage. When someone creates an access key, it inherits the permissions of the parent key. Not only for `s3:*` actions, but also `admin:*` actions. Which means unless somewhere above in the access-key hierarchy, the `admin` rights are denied, access keys will be able to simply override their own `s3` permissions to something more permissive. The vulnerability is fixed in RELEASE.2024-01-31T20-20-33Z.
[ { "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/minio/minio
[]
[ "372a08be49a2213a4a01de1fb7b271d98f38215c", "64288d6eb53cc134a1f85851dcaf7dee76fecca6" ]
CVE-2024-36107
2024-05-28T19:15:10
2025-01-15T05:14:21.119202
MinIO is a High Performance Object Storage released under GNU Affero General Public License v3.0. `If-Modified-Since` and `If-Unmodified-Since` headers when used with anonymous requests by sending a random object name requests can be used to determine if an object exists or not on the server on a specific bucket and also gain access to some amount of information such as `Last-Modified (of the latest version)`, `Etag (of the latest version)`, `x-amz-version-id (of the latest version)`, `Expires (metadata value of the latest version)`, `Cache-Control (metadata value of the latest version)`. This conditional check was being honored before validating if the anonymous access is indeed allowed on the metadata of an object. This issue has been addressed in commit `e0fe7cc3917`. Users must upgrade to RELEASE.2024-05-27T19-17-46Z for the fix. There are no known workarounds for this issue.
null
https://github.com/minio/minio
[]
[ "372a08be49a2213a4a01de1fb7b271d98f38215c", "64288d6eb53cc134a1f85851dcaf7dee76fecca6" ]
CVE-2024-55949
2024-12-16T20:15:13
2025-01-15T05:16:56.267061
MinIO is a high-performance, S3 compatible object store, open sourced under GNU AGPLv3 license. Minio is subject to a privilege escalation in IAM import API, all users are impacted since MinIO commit `580d9db85e04f1b63cc2909af50f0ed08afa965f`. This issue has been addressed in commit `f246c9053f9603e610d98439799bdd2a6b293427` which is included in RELEASE.2024-12-13T22-19-12Z. There are no workarounds possible, all users are advised to upgrade immediately.
null
https://github.com/minio/minio
[]
[ "372a08be49a2213a4a01de1fb7b271d98f38215c", "64288d6eb53cc134a1f85851dcaf7dee76fecca6" ]
CVE-2023-28432
2023-03-22T21:15:18
2025-02-19T03:33:53.718523
Minio is a Multi-Cloud Object Storage framework. In a cluster deployment starting with RELEASE.2019-12-17T23-16-33Z and prior to RELEASE.2023-03-20T20-16-18Z, MinIO returns all environment variables, including `MINIO_SECRET_KEY` and `MINIO_ROOT_PASSWORD`, resulting in information disclosure. All users of distributed deployment are impacted. All users are advised to upgrade to RELEASE.2023-03-20T20-16-18Z.
[ { "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/minio/minio
[]
[ "372a08be49a2213a4a01de1fb7b271d98f38215c" ]