CVSS: 4.9EPSS: 0%CPEs: 2EXPL: 0CVE-2024-20996
https://notcve.org/view.php?id=CVE-2024-20996
Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. • https://www.oracle.com/security-alerts/cpujul2024.html •
CVSS: 7.7EPSS: 0%CPEs: 5EXPL: 0CVE-2024-5795 – Denial of Service vulnerability was identified in GitHub Enterprise Server that allowed resource exhaustion
https://notcve.org/view.php?id=CVE-2024-5795
A Denial of Service vulnerability was identified in GitHub Enterprise Server that allowed an attacker to cause unbounded resource exhaustion by sending a large payload to the Git server. • https://docs.github.com/en/enterprise-server@3.10/admin/release-notes#3.10.14 https://docs.github.com/en/enterprise-server@3.11/admin/release-notes#3.11.12 https://docs.github.com/en/enterprise-server@3.12/admin/release-notes#3.12.6 https://docs.github.com/en/enterprise-server@3.13/admin/release-notes#3.13.1 https://docs.github.com/en/enterprise-server@3.9/admin/release-notes#3.9.17 • CWE-400: Uncontrolled Resource Consumption •
CVSS: 4.3EPSS: 0%CPEs: 1EXPL: 0CVE-2024-39908 – Denial of service in REXML
https://notcve.org/view.php?id=CVE-2024-39908
The REXML gem before 3.3.1 has some DoS vulnerabilities when it parses an XML that has many specific characters such as `<`, `0` and `%>`. ... La gema REXML anterior a 3.3.1 tiene algunas vulnerabilidades DoS cuando analiza un XML que tiene muchos caracteres específicos como `<`, `0` y `%>`. ... When parsing an untrusted XML with many specific characters such as `<`, `0`, and `%>`, it can lead to a denial of service. • https://github.com/ruby/rexml/security/advisories/GHSA-4xqq-m2hx-25v8 https://www.ruby-lang.org/en/news/2024/07/16/dos-rexml-cve-2024-39908 https://access.redhat.com/security/cve/CVE-2024-39908 https://bugzilla.redhat.com/show_bug.cgi? • CWE-400: Uncontrolled Resource Consumption •
CVSS: 5.5EPSS: 0%CPEs: 3EXPL: 0CVE-2022-48862 – vhost: fix hung thread due to erroneous iotlb entries
https://notcve.org/view.php?id=CVE-2022-48862
extid=0abd373e2e50d704db87 Para solucionar este problema, haga dos cosas: 1. ... Corrija vhost_iotlb_add_range_ctx() para manejar el rango [0, ULONG_MAX] dividiéndolo en dos entradas. • https://git.kernel.org/stable/c/0bbe30668d89ec8a309f28ced6d092c90fb23e8c https://git.kernel.org/stable/c/f8d88e86e90ea1002226d7ac2430152bfea003d1 https://git.kernel.org/stable/c/d9a747e6b6561280bf1791bb24c5e9e082193dad https://git.kernel.org/stable/c/e2ae38cf3d91837a493cb2093c87700ff3cbe667 • CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop') •
CVSS: 7.8EPSS: 0%CPEs: 2EXPL: 0CVE-2022-48848 – tracing/osnoise: Do not unregister events twice
https://notcve.org/view.php?id=CVE-2022-48848
En el kernel de Linux, se resolvió la siguiente vulnerabilidad: rastreo/osnoise: no cancelar el registro de eventos dos veces Nicolas informó que al usar: # trace-cmd record -e all -M 10 -p osnoise --poll resultó en la siguiente advertencia del kernel: ------------[ cortar aquí ]------------ ADVERTENCIA: CPU: 0 PID: 1217 en kernel/tracepoint.c:404 tracepoint_probe_unregister+0x280/0x370 [ ...] ... Para evitar cancelar el registro de eventos dos veces, use la variable trace_osnoise_callback_enabled existente para verificar si los eventos (y la carga de trabajo) están realmente activos antes de intentar desactivarlos. • https://git.kernel.org/stable/c/2fac8d6486d5c34e2ec7028580142b8209da3f92 https://git.kernel.org/stable/c/4e10787d18379d9b296290c2288097feddef16d4 https://git.kernel.org/stable/c/f0cfe17bcc1dd2f0872966b554a148e888833ee9 •