admin/nvd-json-data-feeds
1
0
Fork 0
mirror of https://github.com/fkie-cad/nvd-json-data-feeds.git synced 2025-06-19 17:31:42 +00:00
Code Issues Packages Projects Releases Wiki Activity

Auto-Update: 2025-06-08T02:00:20.759976+00:00

Browse Source
This commit is contained in:
cad-safe-bot 2025-06-08 02:04:13 +00:00
parent 7f01419ed6
commit b5b393e5b3
494 changed files with 1786 additions and 765 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
CVE-2011/CVE-2011-100xx/CVE-2011-10007.json
View File

@ -9,6 +9,10 @@
{
"lang": "en",
"value": "File::Find::Rule through 0.34 for Perl is vulnerable to Arbitrary Code Execution when `grep()` encounters a crafted filename.\n\nA file handle is opened with the 2 argument form of `open()` allowing an attacker controlled filename to provide the MODE parameter to `open()`, turning the filename into a command to be executed.\n\nExample:\n\n$ mkdir /tmp/poc; echo > \"/tmp/poc/|id\"\n$ perl -MFile::Find::Rule \\\n\u00a0 \u00a0 -E 'File::Find::Rule->grep(\"foo\")->in(\"/tmp/poc\")'\nuid=1000(user) gid=1000(user) groups=1000(user),100(users)"
},
{
"lang": "es",
"value": "File::Find::Rule hasta la versi\u00f3n 0.34 para Perl es vulnerable a la ejecuci\u00f3n de c\u00f3digo arbitrario cuando `grep()` encuentra un nombre de archivo manipulado. Se abre un controlador de archivo con la forma de dos argumentos `open()`, lo que permite que un atacante controle el nombre de archivo proporcionando el par\u00e1metro MODE a `open()`, convirtiendo el nombre de archivo en un comando para su ejecuci\u00f3n. Ejemplo: $ mkdir /tmp/poc; echo > \"/tmp/poc/|id\" $ perl -MFile::Find::Rule \\ -E 'File::Find::Rule->grep(\"foo\")->in(\"/tmp/poc\")' uid=1000(user) gid=1000(user) groups=1000(user),100(users)"
}
],
"metrics": {

2
CVE-2018/CVE-2018-162xx/CVE-2018-16210.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "cve@mitre.org",
"published": "2018-10-12T22:15:07.377",
"lastModified": "2024-11-21T03:52:17.730",
"vulnStatus": "Modified",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

4
CVE-2018/CVE-2018-251xx/CVE-2018-25111.json
View File

@ -9,6 +9,10 @@
{
"lang": "en",
"value": "django-helpdesk before 1.0.0 allows Sensitive Data Exposure because of os.umask(0) in models.py."
},
{
"lang": "es",
"value": "django-helpdesk anterior a 1.0.0 permite la exposici\u00f3n de datos confidenciales debido a os.umask(0) en models.py. "
}
],
"metrics": {

2
CVE-2021/CVE-2021-252xx/CVE-2021-25254.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "browser-security@yandex-team.ru",
"published": "2025-05-21T07:15:59.357",
"lastModified": "2025-05-21T20:24:58.133",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2021/CVE-2021-252xx/CVE-2021-25255.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "browser-security@yandex-team.ru",
"published": "2025-05-21T07:16:00.500",
"lastModified": "2025-05-21T20:24:58.133",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2021/CVE-2021-252xx/CVE-2021-25262.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "browser-security@yandex-team.ru",
"published": "2025-05-21T07:16:00.653",
"lastModified": "2025-05-21T20:24:58.133",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2022/CVE-2022-43xx/CVE-2022-4363.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "contact@wpscan.com",
"published": "2025-05-16T21:15:33.123",
"lastModified": "2025-05-19T13:35:20.460",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2023/CVE-2023-21xx/CVE-2023-2142.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "security@mozilla.org",
"published": "2024-11-26T12:15:18.307",
"lastModified": "2024-11-27T17:15:05.200",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

4
CVE-2023/CVE-2023-262xx/CVE-2023-26226.json
View File

@ -9,6 +9,10 @@
{
"lang": "en",
"value": "A use after free memory corruption issue exists in Yandex Browser for Desktop prior to version 24.4.0.682"
},
{
"lang": "es",
"value": "Existe un problema de corrupci\u00f3n de memoria use after free en Yandex Browser para Desktop anterior a la versi\u00f3n 24.4.0.682"
}
],
"metrics": {

2
CVE-2023/CVE-2023-400xx/CVE-2023-40000.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "audit@patchstack.com",
"published": "2024-04-16T18:15:10.600",
"lastModified": "2024-11-21T08:18:30.070",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2023/CVE-2023-67xx/CVE-2023-6786.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "contact@wpscan.com",
"published": "2025-05-15T20:15:29.520",
"lastModified": "2025-05-17T04:16:02.647",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2023/CVE-2023-70xx/CVE-2023-7086.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "contact@wpscan.com",
"published": "2025-05-15T20:15:29.950",
"lastModified": "2025-05-17T03:15:26.153",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2023/CVE-2023-70xx/CVE-2023-7088.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "contact@wpscan.com",
"published": "2025-05-15T20:15:30.040",
"lastModified": "2025-05-17T03:15:26.553",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2023/CVE-2023-71xx/CVE-2023-7168.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "contact@wpscan.com",
"published": "2025-05-15T20:15:30.120",
"lastModified": "2025-05-20T15:16:00.430",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2023/CVE-2023-72xx/CVE-2023-7239.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "contact@wpscan.com",
"published": "2025-05-15T20:15:30.920",
"lastModified": "2025-05-16T17:15:49.190",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2023/CVE-2023-72xx/CVE-2023-7297.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "contact@wpscan.com",
"published": "2025-05-15T20:15:31.007",
"lastModified": "2025-05-16T17:15:49.340",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-02xx/CVE-2024-0249.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "contact@wpscan.com",
"published": "2025-05-15T20:15:31.090",
"lastModified": "2025-05-16T17:15:49.497",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-09xx/CVE-2024-0970.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "contact@wpscan.com",
"published": "2025-05-15T20:15:32.200",
"lastModified": "2025-05-16T17:15:49.807",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-100xx/CVE-2024-10098.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "contact@wpscan.com",
"published": "2025-05-15T20:15:32.620",
"lastModified": "2025-05-20T16:15:24.010",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-101xx/CVE-2024-10149.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "contact@wpscan.com",
"published": "2025-05-15T20:15:33.037",
"lastModified": "2025-05-20T16:15:24.687",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-102xx/CVE-2024-10234.json
View File

@ -62,7 +62,7 @@
"weaknesses": [
{
"source": "secalert@redhat.com",
"type": "Primary",
"type": "Secondary",
"description": [
{
"lang": "en",

2
CVE-2024/CVE-2024-103xx/CVE-2024-10362.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "contact@wpscan.com",
"published": "2025-05-15T20:15:33.120",
"lastModified": "2025-05-20T20:15:27.700",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-104xx/CVE-2024-10475.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "contact@wpscan.com",
"published": "2025-05-15T20:15:33.207",
"lastModified": "2025-05-20T20:15:27.857",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-106xx/CVE-2024-10631.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "contact@wpscan.com",
"published": "2025-05-15T20:15:33.380",
"lastModified": "2025-05-20T16:15:24.960",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-106xx/CVE-2024-10632.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "contact@wpscan.com",
"published": "2025-05-15T20:15:33.460",
"lastModified": "2025-05-20T20:15:28.010",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-106xx/CVE-2024-10634.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "contact@wpscan.com",
"published": "2025-05-15T20:15:33.543",
"lastModified": "2025-05-20T20:15:28.323",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-111xx/CVE-2024-11140.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "contact@wpscan.com",
"published": "2025-05-15T20:15:33.970",
"lastModified": "2025-05-20T16:15:25.250",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-111xx/CVE-2024-11189.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "contact@wpscan.com",
"published": "2025-05-15T20:15:34.140",
"lastModified": "2025-05-20T20:15:29.040",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-113xx/CVE-2024-11372.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "contact@wpscan.com",
"published": "2025-05-15T20:15:35.013",
"lastModified": "2025-05-20T20:15:29.857",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-113xx/CVE-2024-11373.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "contact@wpscan.com",
"published": "2025-05-15T20:15:35.193",
"lastModified": "2025-05-20T20:15:29.993",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-116xx/CVE-2024-11691.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "security@mozilla.org",
"published": "2024-11-26T14:15:18.633",
"lastModified": "2025-01-06T18:15:18.373",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-116xx/CVE-2024-11694.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "security@mozilla.org",
"published": "2024-11-26T14:15:18.943",
"lastModified": "2024-12-13T17:15:05.960",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-116xx/CVE-2024-11696.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "security@mozilla.org",
"published": "2024-11-26T14:15:19.143",
"lastModified": "2024-12-02T18:15:08.253",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-116xx/CVE-2024-11698.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "security@mozilla.org",
"published": "2024-11-26T14:15:19.330",
"lastModified": "2024-11-27T16:15:13.130",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-117xx/CVE-2024-11705.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "security@mozilla.org",
"published": "2024-11-26T14:15:19.997",
"lastModified": "2024-11-27T16:15:14.000",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

4
CVE-2024/CVE-2024-118xx/CVE-2024-11857.json
View File

@ -9,6 +9,10 @@
{
"lang": "en",
"value": "Bluetooth HCI Adaptor from Realtek has a Link Following vulnerability. Local attackers with regular privileges can create a symbolic link with the same name as a specific file, causing the product to delete arbitrary files pointed to by the link. Subsequently, attackers can leverage arbitrary file deletion to privilege escalation."
},
{
"lang": "es",
"value": "El adaptador Bluetooth HCI de Realtek presenta una vulnerabilidad de seguimiento de enlaces. Atacantes locales con privilegios regulares pueden crear un enlace simb\u00f3lico con el mismo nombre que un archivo espec\u00edfico, lo que provoca que el producto elimine archivos arbitrarios a los que apunta el enlace. Posteriormente, los atacantes pueden aprovechar la eliminaci\u00f3n arbitraria de archivos para escalar privilegios."
}
],
"metrics": {

2
CVE-2024/CVE-2024-121xx/CVE-2024-12163.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "contact@wpscan.com",
"published": "2025-01-30T06:15:29.113",
"lastModified": "2025-01-30T16:15:29.770",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

4
CVE-2024/CVE-2024-121xx/CVE-2024-12168.json
View File

@ -9,6 +9,10 @@
{
"lang": "en",
"value": "Yandex Telemost for Desktop before 2.7.0\u00a0has a DLL Hijacking Vulnerability because an untrusted search path is used."
},
{
"lang": "es",
"value": "Yandex Telemost para Desktop anterior a 2.7.0 tiene una vulnerabilidad de secuestro de DLL porque se utiliza una ruta de b\u00fasqueda no confiable."
}
],
"metrics": {

2
CVE-2024/CVE-2024-124xx/CVE-2024-12400.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "contact@wpscan.com",
"published": "2025-01-30T06:15:29.223",
"lastModified": "2025-01-30T16:15:29.907",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-127xx/CVE-2024-12726.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "contact@wpscan.com",
"published": "2025-05-15T20:15:36.467",
"lastModified": "2025-05-20T20:15:31.820",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-128xx/CVE-2024-12873.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "contact@wpscan.com",
"published": "2025-05-15T20:15:37.850",
"lastModified": "2025-05-20T19:15:48.787",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-128xx/CVE-2024-12874.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "contact@wpscan.com",
"published": "2025-05-15T20:15:37.927",
"lastModified": "2025-05-20T20:15:33.430",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-130xx/CVE-2024-13053.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "contact@wpscan.com",
"published": "2025-05-15T20:15:38.013",
"lastModified": "2025-05-20T20:15:33.583",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

4
CVE-2024/CVE-2024-139xx/CVE-2024-13915.json
View File

@ -9,6 +9,10 @@
{
"lang": "en",
"value": "Android based smartphones from vendors such as Ulefone and\u00a0Kr\u00fcger&Matz contain \"com.pri.factorytest\" application preloaded onto devices during manufacturing process.\nThe application\u00a0\"com.pri.factorytest\"\u00a0(version name: 1.0, version code: 1)\u00a0exposes a \u201dcom.pri.factorytest.emmc.FactoryResetService\u201c service allowing any application to perform a factory reset of the device.\u00a0\nApplication update did not increment the APK version. Instead, it was bundled in OS builds released later than December 2024 (Ulefone) and most probably March 2025 (Kr\u00fcger&Matz, although the vendor has not confirmed it, so newer releases might be vulnerable as well)."
},
{
"lang": "es",
"value": "Los smartphones Android de fabricantes como Ulefone y Kr\u00fcger&Matz contienen la aplicaci\u00f3n \"com.pri.factorytest\" preinstalada durante el proceso de fabricaci\u00f3n. Esta aplicaci\u00f3n (nombre de la versi\u00f3n: 1.0, c\u00f3digo de la versi\u00f3n: 1) expone el servicio \"com.pri.factorytest.emmc.FactoryResetService\" que permite a cualquier aplicaci\u00f3n restablecer el dispositivo a la configuraci\u00f3n de f\u00e1brica. La actualizaci\u00f3n de la aplicaci\u00f3n no increment\u00f3 la versi\u00f3n del APK. En cambio, se incluy\u00f3 en compilaciones del sistema operativo publicadas despu\u00e9s de diciembre de 2024 (Ulefone) y, muy probablemente, en marzo de 2025 (Kr\u00fcger&Matz, aunque el fabricante no lo ha confirmado, por lo que las versiones m\u00e1s recientes tambi\u00e9n podr\u00edan ser vulnerables)."
}
],
"metrics": {

4
CVE-2024/CVE-2024-139xx/CVE-2024-13916.json
View File

@ -9,6 +9,10 @@
{
"lang": "en",
"value": "An\u00a0application \"com.pri.applock\", which is pre-loaded on\u00a0Kruger&Matz smartphones, allows a user to encrypt any application using user-provided PIN code or by using biometric data.\nExposed \u201dcom.android.providers.settings.fingerprint.PriFpShareProvider\u201c content provider's public method query() allows any other malicious application, without any granted Android system permissions, to exfiltrate the PIN code.\n\nVendor did not provide information about vulnerable versions.\nOnly version (version name: 13, version code: 33) was tested and confirmed to have this vulnerability"
},
{
"lang": "es",
"value": "La aplicaci\u00f3n \"com.pri.applock\", preinstalada en los smartphones Kruger&Matz, permite cifrar cualquier aplicaci\u00f3n mediante el c\u00f3digo PIN proporcionado por el usuario o datos biom\u00e9tricos. El m\u00e9todo p\u00fablico \"query()\" del proveedor de contenido \"com.android.providers.settings.fingerprint.PriFpShareProvider\", expuesto, permite que cualquier otra aplicaci\u00f3n maliciosa, sin permisos del sistema Android, extraiga el c\u00f3digo PIN. El proveedor no proporcion\u00f3 informaci\u00f3n sobre las versiones vulnerables. Solo la versi\u00f3n (nombre de la versi\u00f3n: 13, c\u00f3digo de la versi\u00f3n: 33) fue probada y se confirm\u00f3 que presenta esta vulnerabilidad."
}
],
"metrics": {

4
CVE-2024/CVE-2024-139xx/CVE-2024-13917.json
View File

@ -9,6 +9,10 @@
{
"lang": "en",
"value": "An\u00a0application \"com.pri.applock\", which is pre-loaded on\u00a0Kruger&Matz smartphones, allows a user to encrypt any application using user-provided PIN code or by using biometric data.\nExposed \u201dcom.pri.applock.LockUI\u201c activity allows any other malicious application, with no granted Android system permissions, to inject an arbitrary intent with system-level privileges to a protected application. One must know the protecting PIN number (it might be revealed by exploiting\u00a0CVE-2024-13916) or ask the user to provide it.\n\nVendor did not provide information about vulnerable versions.\nOnly version (version name: 13, version code: 33) was tested and confirmed to have this vulnerability"
},
{
"lang": "es",
"value": "La aplicaci\u00f3n \"com.pri.applock\", preinstalada en los smartphones Kruger&Matz, permite cifrar cualquier aplicaci\u00f3n mediante el c\u00f3digo PIN proporcionado por el usuario o datos biom\u00e9tricos. La actividad expuesta de \"com.pri.applock.LockUI\" permite que cualquier otra aplicaci\u00f3n maliciosa, sin permisos del sistema Android, inyecte una intenci\u00f3n arbitraria con privilegios de sistema en una aplicaci\u00f3n protegida. Es necesario conocer el n\u00famero PIN de protecci\u00f3n (podr\u00eda revelarse mediante la explotaci\u00f3n de CVE-2024-13916) o solicitar al usuario que lo proporcione. El proveedor no proporcion\u00f3 informaci\u00f3n sobre las versiones vulnerables. Solo la versi\u00f3n (nombre de la versi\u00f3n: 13, c\u00f3digo de la versi\u00f3n: 33) fue probada y se confirm\u00f3 que presenta esta vulnerabilidad."
}
],
"metrics": {

4
CVE-2024/CVE-2024-14xx/CVE-2024-1440.json
View File

@ -9,6 +9,10 @@
{
"lang": "en",
"value": "An open redirection vulnerability exists in multiple WSO2 products due to improper validation of the multi-option URL in the authentication endpoint when multi-option authentication is enabled. A malicious actor can craft a valid link that redirects users to an attacker-controlled site.\n\nBy exploiting this vulnerability, an attacker may trick users into visiting a malicious page, enabling phishing attacks to harvest sensitive information or perform other harmful actions."
},
{
"lang": "es",
"value": "Existe una vulnerabilidad de redirecci\u00f3n abierta en varios productos WSO2 debido a la validaci\u00f3n incorrecta de la URL multiopci\u00f3n en el endpoint de autenticaci\u00f3n cuando esta est\u00e1 habilitada. Un atacante puede crear un enlace v\u00e1lido que redirija a los usuarios a un sitio web controlado por el atacante. Al explotar esta vulnerabilidad, un atacante puede enga\u00f1ar a los usuarios para que visiten una p\u00e1gina maliciosa, lo que permite ataques de phishing para recopilar informaci\u00f3n confidencial o realizar otras acciones da\u00f1inas."
}
],
"metrics": {

2
CVE-2024/CVE-2024-222xx/CVE-2024-22251.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "security@vmware.com",
"published": "2024-02-29T01:44:05.870",
"lastModified": "2024-11-21T08:55:53.500",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-222xx/CVE-2024-22259.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "security@vmware.com",
"published": "2024-03-16T05:15:20.830",
"lastModified": "2025-02-13T18:16:47.843",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-222xx/CVE-2024-22269.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "security@vmware.com",
"published": "2024-05-14T16:16:10.117",
"lastModified": "2024-11-21T08:55:55.890",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-222xx/CVE-2024-22270.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "security@vmware.com",
"published": "2024-05-14T16:16:12.613",
"lastModified": "2024-11-21T08:55:56.013",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

4
CVE-2024/CVE-2024-235xx/CVE-2024-23589.json
View File

@ -9,6 +9,10 @@
{
"lang": "en",
"value": "Due to outdated Hash algorithm, HCL Glovius Cloud could allow attackers to guess the input data using brute-force or dictionary attacks efficiently using modern hardware such as GPUs or ASICs"
},
{
"lang": "es",
"value": "Debido al algoritmo Hash obsoleto, HCL Glovius Cloud podr\u00eda permitir a los atacantes adivinar los datos de entrada mediante ataques de fuerza bruta o de diccionario de manera eficiente utilizando hardware moderno como GPU o ASIC."
}
],
"metrics": {

2
CVE-2024/CVE-2024-241xx/CVE-2024-24110.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "cve@mitre.org",
"published": "2024-03-21T02:52:09.993",
"lastModified": "2024-11-21T08:58:55.667",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-242xx/CVE-2024-24272.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "cve@mitre.org",
"published": "2024-03-21T22:15:10.850",
"lastModified": "2025-03-27T20:15:23.717",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-251xx/CVE-2024-25187.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "cve@mitre.org",
"published": "2024-04-02T04:15:12.203",
"lastModified": "2024-11-21T09:00:24.440",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-258xx/CVE-2024-25830.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "cve@mitre.org",
"published": "2024-02-29T01:44:16.533",
"lastModified": "2024-11-21T09:01:23.427",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-265xx/CVE-2024-26529.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "cve@mitre.org",
"published": "2024-03-13T08:15:43.410",
"lastModified": "2024-11-21T09:02:32.617",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-265xx/CVE-2024-26540.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "cve@mitre.org",
"published": "2024-03-15T01:15:58.833",
"lastModified": "2024-11-21T09:02:32.843",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-273xx/CVE-2024-27309.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "security@apache.org",
"published": "2024-04-12T07:15:08.560",
"lastModified": "2025-02-13T18:17:28.160",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-282xx/CVE-2024-28294.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "cve@mitre.org",
"published": "2024-04-29T21:15:47.910",
"lastModified": "2024-11-21T09:06:09.403",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-283xx/CVE-2024-28390.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "cve@mitre.org",
"published": "2024-03-14T04:15:09.640",
"lastModified": "2024-11-21T09:06:15.217",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-283xx/CVE-2024-28391.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "cve@mitre.org",
"published": "2024-03-14T04:15:09.697",
"lastModified": "2024-11-21T09:06:15.450",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-284xx/CVE-2024-28458.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "cve@mitre.org",
"published": "2024-04-11T21:15:08.077",
"lastModified": "2024-11-21T09:06:24.153",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-287xx/CVE-2024-28714.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "cve@mitre.org",
"published": "2024-03-28T23:15:46.410",
"lastModified": "2024-11-21T09:06:48.243",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-287xx/CVE-2024-28715.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "cve@mitre.org",
"published": "2024-03-19T21:15:07.870",
"lastModified": "2024-11-21T09:06:48.480",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-287xx/CVE-2024-28755.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "cve@mitre.org",
"published": "2024-04-03T03:15:10.140",
"lastModified": "2024-11-21T09:06:54.030",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-288xx/CVE-2024-28836.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "cve@mitre.org",
"published": "2024-04-03T03:15:10.350",
"lastModified": "2024-11-21T09:07:02.010",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-301xx/CVE-2024-30166.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "cve@mitre.org",
"published": "2024-04-03T03:15:10.510",
"lastModified": "2024-11-21T09:11:21.147",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-309xx/CVE-2024-30950.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "cve@mitre.org",
"published": "2024-04-17T19:15:07.420",
"lastModified": "2024-11-21T09:12:37.683",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-309xx/CVE-2024-30951.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "cve@mitre.org",
"published": "2024-04-17T18:15:15.947",
"lastModified": "2024-11-22T16:15:21.960",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

4
CVE-2024/CVE-2024-30xx/CVE-2024-3056.json
View File

@ -19,7 +19,7 @@
"cvssMetricV31": [
{
"source": "secalert@redhat.com",
"type": "Primary",
"type": "Secondary",
"cvssData": {
"version": "3.1",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:N/A:H",
@ -62,7 +62,7 @@
"weaknesses": [
{
"source": "secalert@redhat.com",
"type": "Primary",
"type": "Secondary",
"description": [
{
"lang": "en",

2
CVE-2024/CVE-2024-310xx/CVE-2024-31036.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "cve@mitre.org",
"published": "2024-04-22T22:15:07.400",
"lastModified": "2024-11-21T09:12:45.570",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-310xx/CVE-2024-31040.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "cve@mitre.org",
"published": "2024-04-17T19:15:07.680",
"lastModified": "2024-11-21T09:12:45.783",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-310xx/CVE-2024-31041.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "cve@mitre.org",
"published": "2024-04-17T19:15:07.733",
"lastModified": "2024-11-21T09:12:45.993",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-316xx/CVE-2024-31613.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "cve@mitre.org",
"published": "2024-06-10T16:15:13.347",
"lastModified": "2024-11-21T09:13:45.743",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-317xx/CVE-2024-31750.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "cve@mitre.org",
"published": "2024-04-19T00:15:10.690",
"lastModified": "2024-11-21T09:13:50.730",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-317xx/CVE-2024-31783.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "cve@mitre.org",
"published": "2024-04-16T04:15:09.140",
"lastModified": "2025-03-13T16:15:19.433",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-317xx/CVE-2024-31784.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "cve@mitre.org",
"published": "2024-04-16T04:15:09.200",
"lastModified": "2024-11-21T09:13:52.640",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-331xx/CVE-2024-33117.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "cve@mitre.org",
"published": "2024-05-06T20:15:10.890",
"lastModified": "2024-12-06T21:15:07.340",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-333xx/CVE-2024-33300.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "cve@mitre.org",
"published": "2024-05-01T19:15:26.910",
"lastModified": "2024-11-21T09:16:45.987",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-338xx/CVE-2024-33809.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "cve@mitre.org",
"published": "2024-05-24T15:15:24.040",
"lastModified": "2025-03-13T15:15:44.147",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-344xx/CVE-2024-34401.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "cve@mitre.org",
"published": "2024-05-03T01:15:48.577",
"lastModified": "2024-11-21T09:18:35.513",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-348xx/CVE-2024-34852.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "cve@mitre.org",
"published": "2024-05-28T17:15:10.303",
"lastModified": "2024-11-21T09:19:29.667",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-348xx/CVE-2024-34854.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "cve@mitre.org",
"published": "2024-05-28T17:15:10.373",
"lastModified": "2024-11-21T09:19:29.877",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-353xx/CVE-2024-35373.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "cve@mitre.org",
"published": "2024-05-24T21:15:59.720",
"lastModified": "2024-11-21T09:20:13.487",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-353xx/CVE-2024-35374.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "cve@mitre.org",
"published": "2024-05-24T21:15:59.793",
"lastModified": "2024-11-21T09:20:13.697",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-356xx/CVE-2024-35618.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "cve@mitre.org",
"published": "2024-05-24T15:15:24.670",
"lastModified": "2024-11-21T09:20:31.393",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

4
CVE-2024/CVE-2024-35xx/CVE-2024-3509.json
View File

@ -9,6 +9,10 @@
{
"lang": "en",
"value": "A stored cross-site scripting (XSS) vulnerability exists in the Management Console of multiple WSO2 products due to insufficient input validation in the Rich Text Editor within the registry section.\nTo exploit this vulnerability, a malicious actor must have a valid user account with administrative access to the Management Console. If successful, the actor could inject persistent JavaScript payloads, enabling the theft of user data or execution of unauthorized actions on behalf of other users.\n\nWhile this issue enables persistent client-side script execution, session-related cookies remain protected with the httpOnly flag, preventing session hijacking."
},
{
"lang": "es",
"value": "Existe una vulnerabilidad de cross site scripting (XSS) almacenado en la consola de administraci\u00f3n de varios productos WSO2 debido a una validaci\u00f3n de entrada insuficiente en el editor de texto enriquecido de la secci\u00f3n de registro. Para explotar esta vulnerabilidad, un agente malicioso debe tener una cuenta de usuario v\u00e1lida con acceso administrativo a la consola de administraci\u00f3n. De tener \u00e9xito, el agente podr\u00eda inyectar payloads persistentes de JavaScript, lo que permite el robo de datos de usuario o la ejecuci\u00f3n de acciones no autorizadas en nombre de otros usuarios. Si bien este problema permite la ejecuci\u00f3n persistente de scripts del lado del cliente, las cookies de sesi\u00f3n permanecen protegidas con el indicador httpOnly, lo que evita el secuestro de sesi\u00f3n."
}
],
"metrics": {

2
CVE-2024/CVE-2024-365xx/CVE-2024-36523.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "cve@mitre.org",
"published": "2024-06-12T21:15:50.407",
"lastModified": "2024-11-21T09:22:19.770",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-365xx/CVE-2024-36528.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "cve@mitre.org",
"published": "2024-06-10T15:15:52.483",
"lastModified": "2024-11-21T09:22:20.440",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-365xx/CVE-2024-36531.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "cve@mitre.org",
"published": "2024-06-10T15:15:52.550",
"lastModified": "2024-11-21T09:22:20.657",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-367xx/CVE-2024-36702.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "cve@mitre.org",
"published": "2024-06-11T19:16:07.697",
"lastModified": "2024-11-21T09:22:33.263",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-376xx/CVE-2024-37663.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "cve@mitre.org",
"published": "2024-06-17T18:15:17.653",
"lastModified": "2024-11-22T16:15:24.273",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-376xx/CVE-2024-37664.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "cve@mitre.org",
"published": "2024-06-17T18:15:17.743",
"lastModified": "2024-11-22T16:15:24.463",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-376xx/CVE-2024-37665.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "cve@mitre.org",
"published": "2024-06-12T21:15:50.503",
"lastModified": "2024-11-21T09:24:12.510",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-377xx/CVE-2024-37759.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "cve@mitre.org",
"published": "2024-06-24T21:15:25.940",
"lastModified": "2024-11-21T09:24:16.593",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-377xx/CVE-2024-37767.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "cve@mitre.org",
"published": "2024-07-05T17:15:11.533",
"lastModified": "2024-11-21T09:24:17.733",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-377xx/CVE-2024-37770.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "cve@mitre.org",
"published": "2024-07-10T18:15:04.983",
"lastModified": "2024-11-21T09:24:18.330",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-383xx/CVE-2024-38341.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "psirt@us.ibm.com",
"published": "2025-05-28T16:15:32.847",
"lastModified": "2025-05-29T14:29:50.247",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

2
CVE-2024/CVE-2024-388xx/CVE-2024-38808.json
View File

@ -3,7 +3,7 @@
"sourceIdentifier": "security@vmware.com",
"published": "2024-08-20T08:15:05.023",
"lastModified": "2024-11-21T09:26:50.877",
"vulnStatus": "Awaiting Analysis",
"vulnStatus": "Undergoing Analysis",
"cveTags": [],
"descriptions": [
{

Some files were not shown because too many files have changed in this diff Show More