mirror of
https://github.com/fkie-cad/nvd-json-data-feeds.git
synced 2025-05-08 03:27:17 +00:00
Auto-Update: 2025-01-21T13:00:55.110954+00:00
This commit is contained in:
parent
1bf433d63d
commit
65b84b095f
68
CVE-2024/CVE-2024-112xx/CVE-2024-11226.json
Normal file
68
CVE-2024/CVE-2024-112xx/CVE-2024-11226.json
Normal file
@ -0,0 +1,68 @@
|
||||
{
|
||||
"id": "CVE-2024-11226",
|
||||
"sourceIdentifier": "security@wordfence.com",
|
||||
"published": "2025-01-21T11:15:08.063",
|
||||
"lastModified": "2025-01-21T11:15:08.063",
|
||||
"vulnStatus": "Received",
|
||||
"cveTags": [],
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "The FireCask Like & Share Button plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'width' parameter in all versions up to, and including, 1.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page."
|
||||
}
|
||||
],
|
||||
"metrics": {
|
||||
"cvssMetricV31": [
|
||||
{
|
||||
"source": "security@wordfence.com",
|
||||
"type": "Primary",
|
||||
"cvssData": {
|
||||
"version": "3.1",
|
||||
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N",
|
||||
"baseScore": 6.4,
|
||||
"baseSeverity": "MEDIUM",
|
||||
"attackVector": "NETWORK",
|
||||
"attackComplexity": "LOW",
|
||||
"privilegesRequired": "LOW",
|
||||
"userInteraction": "NONE",
|
||||
"scope": "CHANGED",
|
||||
"confidentialityImpact": "LOW",
|
||||
"integrityImpact": "LOW",
|
||||
"availabilityImpact": "NONE"
|
||||
},
|
||||
"exploitabilityScore": 3.1,
|
||||
"impactScore": 2.7
|
||||
}
|
||||
]
|
||||
},
|
||||
"weaknesses": [
|
||||
{
|
||||
"source": "security@wordfence.com",
|
||||
"type": "Primary",
|
||||
"description": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "CWE-79"
|
||||
}
|
||||
]
|
||||
}
|
||||
],
|
||||
"references": [
|
||||
{
|
||||
"url": "https://plugins.trac.wordpress.org/browser/facebook-like-send-button/tags/1.2/class-frontend.php#L121",
|
||||
"source": "security@wordfence.com"
|
||||
},
|
||||
{
|
||||
"url": "https://plugins.trac.wordpress.org/changeset/3225838/",
|
||||
"source": "security@wordfence.com"
|
||||
},
|
||||
{
|
||||
"url": "https://wordpress.org/plugins/facebook-like-send-button/#developers",
|
||||
"source": "security@wordfence.com"
|
||||
},
|
||||
{
|
||||
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/5b9d61cd-1955-40d0-99b4-c75f480733f8?source=cve",
|
||||
"source": "security@wordfence.com"
|
||||
}
|
||||
]
|
||||
}
|
64
CVE-2024/CVE-2024-132xx/CVE-2024-13230.json
Normal file
64
CVE-2024/CVE-2024-132xx/CVE-2024-13230.json
Normal file
@ -0,0 +1,64 @@
|
||||
{
|
||||
"id": "CVE-2024-13230",
|
||||
"sourceIdentifier": "security@wordfence.com",
|
||||
"published": "2025-01-21T11:15:09.267",
|
||||
"lastModified": "2025-01-21T11:15:09.267",
|
||||
"vulnStatus": "Received",
|
||||
"cveTags": [],
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "The Social Share, Social Login and Social Comments Plugin \u2013 Super Socializer plugin for WordPress is vulnerable to Limited SQL Injection via the \u2018SuperSocializerKey\u2019 parameter in all versions up to, and including, 7.14 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional values into the already existing query that can be used to extract user metadata from the database."
|
||||
}
|
||||
],
|
||||
"metrics": {
|
||||
"cvssMetricV31": [
|
||||
{
|
||||
"source": "security@wordfence.com",
|
||||
"type": "Primary",
|
||||
"cvssData": {
|
||||
"version": "3.1",
|
||||
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
|
||||
"baseScore": 5.3,
|
||||
"baseSeverity": "MEDIUM",
|
||||
"attackVector": "NETWORK",
|
||||
"attackComplexity": "LOW",
|
||||
"privilegesRequired": "NONE",
|
||||
"userInteraction": "NONE",
|
||||
"scope": "UNCHANGED",
|
||||
"confidentialityImpact": "LOW",
|
||||
"integrityImpact": "NONE",
|
||||
"availabilityImpact": "NONE"
|
||||
},
|
||||
"exploitabilityScore": 3.9,
|
||||
"impactScore": 1.4
|
||||
}
|
||||
]
|
||||
},
|
||||
"weaknesses": [
|
||||
{
|
||||
"source": "security@wordfence.com",
|
||||
"type": "Primary",
|
||||
"description": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "CWE-89"
|
||||
}
|
||||
]
|
||||
}
|
||||
],
|
||||
"references": [
|
||||
{
|
||||
"url": "https://plugins.trac.wordpress.org/browser/super-socializer/trunk/super_socializer.php#L291",
|
||||
"source": "security@wordfence.com"
|
||||
},
|
||||
{
|
||||
"url": "https://plugins.trac.wordpress.org/changeset/3225440/",
|
||||
"source": "security@wordfence.com"
|
||||
},
|
||||
{
|
||||
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/4d7b2a7f-3c67-4df1-bb15-e7f4f0035953?source=cve",
|
||||
"source": "security@wordfence.com"
|
||||
}
|
||||
]
|
||||
}
|
76
CVE-2024/CVE-2024-134xx/CVE-2024-13444.json
Normal file
76
CVE-2024/CVE-2024-134xx/CVE-2024-13444.json
Normal file
@ -0,0 +1,76 @@
|
||||
{
|
||||
"id": "CVE-2024-13444",
|
||||
"sourceIdentifier": "security@wordfence.com",
|
||||
"published": "2025-01-21T11:15:09.450",
|
||||
"lastModified": "2025-01-21T11:15:09.450",
|
||||
"vulnStatus": "Received",
|
||||
"cveTags": [],
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "The wp-greet plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 6.2. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to update settings and inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link."
|
||||
}
|
||||
],
|
||||
"metrics": {
|
||||
"cvssMetricV31": [
|
||||
{
|
||||
"source": "security@wordfence.com",
|
||||
"type": "Primary",
|
||||
"cvssData": {
|
||||
"version": "3.1",
|
||||
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N",
|
||||
"baseScore": 6.1,
|
||||
"baseSeverity": "MEDIUM",
|
||||
"attackVector": "NETWORK",
|
||||
"attackComplexity": "LOW",
|
||||
"privilegesRequired": "NONE",
|
||||
"userInteraction": "REQUIRED",
|
||||
"scope": "CHANGED",
|
||||
"confidentialityImpact": "LOW",
|
||||
"integrityImpact": "LOW",
|
||||
"availabilityImpact": "NONE"
|
||||
},
|
||||
"exploitabilityScore": 2.8,
|
||||
"impactScore": 2.7
|
||||
}
|
||||
]
|
||||
},
|
||||
"weaknesses": [
|
||||
{
|
||||
"source": "security@wordfence.com",
|
||||
"type": "Primary",
|
||||
"description": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "CWE-352"
|
||||
}
|
||||
]
|
||||
}
|
||||
],
|
||||
"references": [
|
||||
{
|
||||
"url": "https://plugins.trac.wordpress.org/browser/wp-greet/trunk/wpg-admin.php#L124",
|
||||
"source": "security@wordfence.com"
|
||||
},
|
||||
{
|
||||
"url": "https://plugins.trac.wordpress.org/browser/wp-greet/trunk/wpg-admin.php#L350",
|
||||
"source": "security@wordfence.com"
|
||||
},
|
||||
{
|
||||
"url": "https://plugins.trac.wordpress.org/browser/wp-greet/trunk/wpg-form.php#L253",
|
||||
"source": "security@wordfence.com"
|
||||
},
|
||||
{
|
||||
"url": "https://plugins.trac.wordpress.org/changeset/3225035/",
|
||||
"source": "security@wordfence.com"
|
||||
},
|
||||
{
|
||||
"url": "https://wordpress.org/plugins/wp-greet/#developers",
|
||||
"source": "security@wordfence.com"
|
||||
},
|
||||
{
|
||||
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/dafc40bf-833a-4d42-b9bc-c7cf2b234ef5?source=cve",
|
||||
"source": "security@wordfence.com"
|
||||
}
|
||||
]
|
||||
}
|
56
CVE-2024/CVE-2024-372xx/CVE-2024-37284.json
Normal file
56
CVE-2024/CVE-2024-372xx/CVE-2024-37284.json
Normal file
@ -0,0 +1,56 @@
|
||||
{
|
||||
"id": "CVE-2024-37284",
|
||||
"sourceIdentifier": "bressers@elastic.co",
|
||||
"published": "2025-01-21T11:15:09.633",
|
||||
"lastModified": "2025-01-21T11:15:09.633",
|
||||
"vulnStatus": "Received",
|
||||
"cveTags": [],
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "Improper handling of alternate encoding occurs when Elastic Defend on Windows systems attempts to scan a file or process encoded as a multibyte character. This leads to an uncaught exception causing Elastic Defend to crash which in turn will prevent it from quarantining the file and/or killing the process."
|
||||
}
|
||||
],
|
||||
"metrics": {
|
||||
"cvssMetricV31": [
|
||||
{
|
||||
"source": "bressers@elastic.co",
|
||||
"type": "Secondary",
|
||||
"cvssData": {
|
||||
"version": "3.1",
|
||||
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
|
||||
"baseScore": 5.5,
|
||||
"baseSeverity": "MEDIUM",
|
||||
"attackVector": "LOCAL",
|
||||
"attackComplexity": "LOW",
|
||||
"privilegesRequired": "NONE",
|
||||
"userInteraction": "REQUIRED",
|
||||
"scope": "UNCHANGED",
|
||||
"confidentialityImpact": "NONE",
|
||||
"integrityImpact": "NONE",
|
||||
"availabilityImpact": "HIGH"
|
||||
},
|
||||
"exploitabilityScore": 1.8,
|
||||
"impactScore": 3.6
|
||||
}
|
||||
]
|
||||
},
|
||||
"weaknesses": [
|
||||
{
|
||||
"source": "bressers@elastic.co",
|
||||
"type": "Secondary",
|
||||
"description": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "CWE-755"
|
||||
}
|
||||
]
|
||||
}
|
||||
],
|
||||
"references": [
|
||||
{
|
||||
"url": "https://discuss.elastic.co/t/elastic-defend-8-13-3-security-update-esa-2024-24/373441",
|
||||
"source": "bressers@elastic.co"
|
||||
}
|
||||
]
|
||||
}
|
56
CVE-2024/CVE-2024-437xx/CVE-2024-43709.json
Normal file
56
CVE-2024/CVE-2024-437xx/CVE-2024-43709.json
Normal file
@ -0,0 +1,56 @@
|
||||
{
|
||||
"id": "CVE-2024-43709",
|
||||
"sourceIdentifier": "bressers@elastic.co",
|
||||
"published": "2025-01-21T11:15:09.807",
|
||||
"lastModified": "2025-01-21T11:15:09.807",
|
||||
"vulnStatus": "Received",
|
||||
"cveTags": [],
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "An allocation of resources without limits or throttling in Elasticsearch can lead to an OutOfMemoryError exception resulting in a crash via a specially crafted query using an SQL function."
|
||||
}
|
||||
],
|
||||
"metrics": {
|
||||
"cvssMetricV31": [
|
||||
{
|
||||
"source": "bressers@elastic.co",
|
||||
"type": "Secondary",
|
||||
"cvssData": {
|
||||
"version": "3.1",
|
||||
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
|
||||
"baseScore": 6.5,
|
||||
"baseSeverity": "MEDIUM",
|
||||
"attackVector": "NETWORK",
|
||||
"attackComplexity": "LOW",
|
||||
"privilegesRequired": "LOW",
|
||||
"userInteraction": "NONE",
|
||||
"scope": "UNCHANGED",
|
||||
"confidentialityImpact": "NONE",
|
||||
"integrityImpact": "NONE",
|
||||
"availabilityImpact": "HIGH"
|
||||
},
|
||||
"exploitabilityScore": 2.8,
|
||||
"impactScore": 3.6
|
||||
}
|
||||
]
|
||||
},
|
||||
"weaknesses": [
|
||||
{
|
||||
"source": "bressers@elastic.co",
|
||||
"type": "Secondary",
|
||||
"description": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "CWE-770"
|
||||
}
|
||||
]
|
||||
}
|
||||
],
|
||||
"references": [
|
||||
{
|
||||
"url": "https://discuss.elastic.co/t/elasticsearch-7-17-21-and-8-13-3-security-update-esa-2024-25/373442",
|
||||
"source": "bressers@elastic.co"
|
||||
}
|
||||
]
|
||||
}
|
56
CVE-2024/CVE-2024-529xx/CVE-2024-52973.json
Normal file
56
CVE-2024/CVE-2024-529xx/CVE-2024-52973.json
Normal file
@ -0,0 +1,56 @@
|
||||
{
|
||||
"id": "CVE-2024-52973",
|
||||
"sourceIdentifier": "bressers@elastic.co",
|
||||
"published": "2025-01-21T11:15:10.200",
|
||||
"lastModified": "2025-01-21T11:15:10.200",
|
||||
"vulnStatus": "Received",
|
||||
"cveTags": [],
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "An allocation of resources without limits or throttling in Kibana can lead to a crash caused by a specially crafted request to /api/log_entries/summary. This can be carried out by users with read access to the Observability-Logs feature in Kibana."
|
||||
}
|
||||
],
|
||||
"metrics": {
|
||||
"cvssMetricV31": [
|
||||
{
|
||||
"source": "bressers@elastic.co",
|
||||
"type": "Secondary",
|
||||
"cvssData": {
|
||||
"version": "3.1",
|
||||
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
|
||||
"baseScore": 6.5,
|
||||
"baseSeverity": "MEDIUM",
|
||||
"attackVector": "NETWORK",
|
||||
"attackComplexity": "LOW",
|
||||
"privilegesRequired": "LOW",
|
||||
"userInteraction": "NONE",
|
||||
"scope": "UNCHANGED",
|
||||
"confidentialityImpact": "NONE",
|
||||
"integrityImpact": "NONE",
|
||||
"availabilityImpact": "HIGH"
|
||||
},
|
||||
"exploitabilityScore": 2.8,
|
||||
"impactScore": 3.6
|
||||
}
|
||||
]
|
||||
},
|
||||
"weaknesses": [
|
||||
{
|
||||
"source": "bressers@elastic.co",
|
||||
"type": "Secondary",
|
||||
"description": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "CWE-770"
|
||||
}
|
||||
]
|
||||
}
|
||||
],
|
||||
"references": [
|
||||
{
|
||||
"url": "https://discuss.elastic.co/t/kibana-7-17-23-and-8-14-2-security-update-esa-2024-26/373443",
|
||||
"source": "bressers@elastic.co"
|
||||
}
|
||||
]
|
||||
}
|
37
CVE-2024/CVE-2024-579xx/CVE-2024-57930.json
Normal file
37
CVE-2024/CVE-2024-579xx/CVE-2024-57930.json
Normal file
@ -0,0 +1,37 @@
|
||||
{
|
||||
"id": "CVE-2024-57930",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2025-01-21T12:15:26.600",
|
||||
"lastModified": "2025-01-21T12:15:26.600",
|
||||
"vulnStatus": "Received",
|
||||
"cveTags": [],
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Have process_string() also allow arrays\n\nIn order to catch a common bug where a TRACE_EVENT() TP_fast_assign()\nassigns an address of an allocated string to the ring buffer and then\nreferences it in TP_printk(), which can be executed hours later when the\nstring is free, the function test_event_printk() runs on all events as\nthey are registered to make sure there's no unwanted dereferencing.\n\nIt calls process_string() to handle cases in TP_printk() format that has\n\"%s\". It returns whether or not the string is safe. But it can have some\nfalse positives.\n\nFor instance, xe_bo_move() has:\n\n TP_printk(\"move_lacks_source:%s, migrate object %p [size %zu] from %s to %s device_id:%s\",\n __entry->move_lacks_source ? \"yes\" : \"no\", __entry->bo, __entry->size,\n xe_mem_type_to_name[__entry->old_placement],\n xe_mem_type_to_name[__entry->new_placement], __get_str(device_id))\n\nWhere the \"%s\" references into xe_mem_type_to_name[]. This is an array of\npointers that should be safe for the event to access. Instead of flagging\nthis as a bad reference, if a reference points to an array, where the\nrecord field is the index, consider it safe."
|
||||
}
|
||||
],
|
||||
"metrics": {},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/3bcdc9039a6e9e6e47ed689a37b8d57894a3c571",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/631b1e09e213c86d5a4ce23d45c81af473bb0ac7",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/92bd18c74624e5eb9f96e70076aa46293f4b626f",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/a64e5295ebc4afdefe69cdf16cc286a60ff8ba4b",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/afc6717628f959941d7b33728570568b4af1c4b8",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
}
|
||||
]
|
||||
}
|
45
CVE-2024/CVE-2024-579xx/CVE-2024-57931.json
Normal file
45
CVE-2024/CVE-2024-579xx/CVE-2024-57931.json
Normal file
@ -0,0 +1,45 @@
|
||||
{
|
||||
"id": "CVE-2024-57931",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2025-01-21T12:15:26.713",
|
||||
"lastModified": "2025-01-21T12:15:26.713",
|
||||
"vulnStatus": "Received",
|
||||
"cveTags": [],
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nselinux: ignore unknown extended permissions\n\nWhen evaluating extended permissions, ignore unknown permissions instead\nof calling BUG(). This commit ensures that future permissions can be\nadded without interfering with older kernels."
|
||||
}
|
||||
],
|
||||
"metrics": {},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/712137b177b45f255ce5687e679d950fcb218256",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/900f83cf376bdaf798b6f5dcb2eae0c822e908b6",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/c1dbd28a079553de0023e1c938c713efeeee400f",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/c79324d42fa48372e0acb306a2761cc642bd4db0",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/efefe36c03a73bb81c0720ce397659a5051b73fa",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/f45a77dd24ae9ddb474303ec3975c376bd99fc51",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/f70e4b9ec69d9a74b84c17767a9a4eda8c901021",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
}
|
||||
]
|
||||
}
|
29
CVE-2024/CVE-2024-579xx/CVE-2024-57932.json
Normal file
29
CVE-2024/CVE-2024-579xx/CVE-2024-57932.json
Normal file
@ -0,0 +1,29 @@
|
||||
{
|
||||
"id": "CVE-2024-57932",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2025-01-21T12:15:26.837",
|
||||
"lastModified": "2025-01-21T12:15:26.837",
|
||||
"vulnStatus": "Received",
|
||||
"cveTags": [],
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ngve: guard XDP xmit NDO on existence of xdp queues\n\nIn GVE, dedicated XDP queues only exist when an XDP program is installed\nand the interface is up. As such, the NDO XDP XMIT callback should\nreturn early if either of these conditions are false.\n\nIn the case of no loaded XDP program, priv->num_xdp_queues=0 which can\ncause a divide-by-zero error, and in the case of interface down,\nnum_xdp_queues remains untouched to persist XDP queue count for the next\ninterface up, but the TX pointer itself would be NULL.\n\nThe XDP xmit callback also needs to synchronize with a device\ntransitioning from open to close. This synchronization will happen via\nthe GVE_PRIV_FLAGS_NAPI_ENABLED bit along with a synchronize_net() call,\nwhich waits for any RCU critical sections at call-time to complete."
|
||||
}
|
||||
],
|
||||
"metrics": {},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/35f44eed5828cf1bc7e760d1993ed8549ba41c7b",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/cbe9eb2c39d09f3c8574febcfa39d8c09d0c7cb5",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/ff7c2dea9dd1a436fc79d6273adffdcc4a7ffea3",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
}
|
||||
]
|
||||
}
|
29
CVE-2024/CVE-2024-579xx/CVE-2024-57933.json
Normal file
29
CVE-2024/CVE-2024-579xx/CVE-2024-57933.json
Normal file
@ -0,0 +1,29 @@
|
||||
{
|
||||
"id": "CVE-2024-57933",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2025-01-21T12:15:26.947",
|
||||
"lastModified": "2025-01-21T12:15:26.947",
|
||||
"vulnStatus": "Received",
|
||||
"cveTags": [],
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ngve: guard XSK operations on the existence of queues\n\nThis patch predicates the enabling and disabling of XSK pools on the\nexistence of queues. As it stands, if the interface is down, disabling\nor enabling XSK pools would result in a crash, as the RX queue pointer\nwould be NULL. XSK pool registration will occur as part of the next\ninterface up.\n\nSimilarly, xsk_wakeup needs be guarded against queues disappearing\nwhile the function is executing, so a check against the\nGVE_PRIV_FLAGS_NAPI_ENABLED flag is added to synchronize with the\ndisabling of the bit and the synchronize_net() in gve_turndown."
|
||||
}
|
||||
],
|
||||
"metrics": {},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/40338d7987d810fcaa95c500b1068a52b08eec9b",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/771d66f2bd8c4dba1286a9163ab982cecd825718",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/8e8d7037c89437af12725f454e2eaf40e8166c0f",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
}
|
||||
]
|
||||
}
|
25
CVE-2024/CVE-2024-579xx/CVE-2024-57934.json
Normal file
25
CVE-2024/CVE-2024-579xx/CVE-2024-57934.json
Normal file
@ -0,0 +1,25 @@
|
||||
{
|
||||
"id": "CVE-2024-57934",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2025-01-21T12:15:27.047",
|
||||
"lastModified": "2025-01-21T12:15:27.047",
|
||||
"vulnStatus": "Received",
|
||||
"cveTags": [],
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nfgraph: Add READ_ONCE() when accessing fgraph_array[]\n\nIn __ftrace_return_to_handler(), a loop iterates over the fgraph_array[]\nelements, which are fgraph_ops. The loop checks if an element is a\nfgraph_stub to prevent using a fgraph_stub afterward.\n\nHowever, if the compiler reloads fgraph_array[] after this check, it might\nrace with an update to fgraph_array[] that introduces a fgraph_stub. This\ncould result in the stub being processed, but the stub contains a null\n\"func_hash\" field, leading to a NULL pointer dereference.\n\nTo ensure that the gops compared against the fgraph_stub matches the gops\nprocessed later, add a READ_ONCE(). A similar patch appears in commit\n63a8dfb (\"function_graph: Add READ_ONCE() when accessing fgraph_array[]\")."
|
||||
}
|
||||
],
|
||||
"metrics": {},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/b68b2a3fbacc7be720ef589d489bcacdd05c6d38",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/d65474033740ded0a4fe9a097fce72328655b41d",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
}
|
||||
]
|
||||
}
|
25
CVE-2024/CVE-2024-579xx/CVE-2024-57935.json
Normal file
25
CVE-2024/CVE-2024-579xx/CVE-2024-57935.json
Normal file
@ -0,0 +1,25 @@
|
||||
{
|
||||
"id": "CVE-2024-57935",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2025-01-21T12:15:27.153",
|
||||
"lastModified": "2025-01-21T12:15:27.153",
|
||||
"vulnStatus": "Received",
|
||||
"cveTags": [],
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/hns: Fix accessing invalid dip_ctx during destroying QP\n\nIf it fails to modify QP to RTR, dip_ctx will not be attached. And\nduring detroying QP, the invalid dip_ctx pointer will be accessed."
|
||||
}
|
||||
],
|
||||
"metrics": {},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/0572eccf239ce4bd89bd531767ec5ab20e249290",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/a448c775f0aec6cfbee4bda561447c707153504a",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
}
|
||||
]
|
||||
}
|
29
CVE-2024/CVE-2024-579xx/CVE-2024-57936.json
Normal file
29
CVE-2024/CVE-2024-579xx/CVE-2024-57936.json
Normal file
@ -0,0 +1,29 @@
|
||||
{
|
||||
"id": "CVE-2024-57936",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2025-01-21T12:15:27.257",
|
||||
"lastModified": "2025-01-21T12:15:27.257",
|
||||
"vulnStatus": "Received",
|
||||
"cveTags": [],
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/bnxt_re: Fix max SGEs for the Work Request\n\nGen P7 supports up to 13 SGEs for now. WQE software structure\ncan hold only 6 now. Since the max send sge is reported as\n13, the stack can give requests up to 13 SGEs. This is causing\ntraffic failures and system crashes.\n\nUse the define for max SGE supported for variable size. This\nwill work for both static and variable WQEs."
|
||||
}
|
||||
],
|
||||
"metrics": {},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/3de1b50f055dc2ca7072a526cdda21f691c22dd9",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/79d330fbdffd8cee06d8bdf38d82cb62d8363a27",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/9a479088e0c8f6140b8c7752b563bc8c6c6dcc8c",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
}
|
||||
]
|
||||
}
|
25
CVE-2024/CVE-2024-579xx/CVE-2024-57937.json
Normal file
25
CVE-2024/CVE-2024-579xx/CVE-2024-57937.json
Normal file
@ -0,0 +1,25 @@
|
||||
{
|
||||
"id": "CVE-2024-57937",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2025-01-21T12:15:27.360",
|
||||
"lastModified": "2025-01-21T12:15:27.360",
|
||||
"vulnStatus": "Received",
|
||||
"cveTags": [],
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmm: reinstate ability to map write-sealed memfd mappings read-only\n\nPatch series \"mm: reinstate ability to map write-sealed memfd mappings\nread-only\".\n\nIn commit 158978945f31 (\"mm: perform the mapping_map_writable() check\nafter call_mmap()\") (and preceding changes in the same series) it became\npossible to mmap() F_SEAL_WRITE sealed memfd mappings read-only.\n\nCommit 5de195060b2e (\"mm: resolve faulty mmap_region() error path\nbehaviour\") unintentionally undid this logic by moving the\nmapping_map_writable() check before the shmem_mmap() hook is invoked,\nthereby regressing this change.\n\nThis series reworks how we both permit write-sealed mappings being mapped\nread-only and disallow mprotect() from undoing the write-seal, fixing this\nregression.\n\nWe also add a regression test to ensure that we do not accidentally\nregress this in future.\n\nThanks to Julian Orth for reporting this regression.\n\n\nThis patch (of 2):\n\nIn commit 158978945f31 (\"mm: perform the mapping_map_writable() check\nafter call_mmap()\") (and preceding changes in the same series) it became\npossible to mmap() F_SEAL_WRITE sealed memfd mappings read-only.\n\nThis was previously unnecessarily disallowed, despite the man page\ndocumentation indicating that it would be, thereby limiting the usefulness\nof F_SEAL_WRITE logic.\n\nWe fixed this by adapting logic that existed for the F_SEAL_FUTURE_WRITE\nseal (one which disallows future writes to the memfd) to also be used for\nF_SEAL_WRITE.\n\nFor background - the F_SEAL_FUTURE_WRITE seal clears VM_MAYWRITE for a\nread-only mapping to disallow mprotect() from overriding the seal - an\noperation performed by seal_check_write(), invoked from shmem_mmap(), the\nf_op->mmap() hook used by shmem mappings.\n\nBy extending this to F_SEAL_WRITE and critically - checking\nmapping_map_writable() to determine if we may map the memfd AFTER we\ninvoke shmem_mmap() - the desired logic becomes possible. This is because\nmapping_map_writable() explicitly checks for VM_MAYWRITE, which we will\nhave cleared.\n\nCommit 5de195060b2e (\"mm: resolve faulty mmap_region() error path\nbehaviour\") unintentionally undid this logic by moving the\nmapping_map_writable() check before the shmem_mmap() hook is invoked,\nthereby regressing this change.\n\nWe reinstate this functionality by moving the check out of shmem_mmap()\nand instead performing it in do_mmap() at the point at which VMA flags are\nbeing determined, which seems in any case to be a more appropriate place\nin which to make this determination.\n\nIn order to achieve this we rework memfd seal logic to allow us access to\nthis information using existing logic and eliminate the clearing of\nVM_MAYWRITE from seal_check_write() which we are performing in do_mmap()\ninstead."
|
||||
}
|
||||
],
|
||||
"metrics": {},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/464770df46095e6967334d77113972960f7ef1fa",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/8ec396d05d1b737c87311fb7311f753b02c2a6b1",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
}
|
||||
]
|
||||
}
|
45
CVE-2024/CVE-2024-579xx/CVE-2024-57938.json
Normal file
45
CVE-2024/CVE-2024-579xx/CVE-2024-57938.json
Normal file
@ -0,0 +1,45 @@
|
||||
{
|
||||
"id": "CVE-2024-57938",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2025-01-21T12:15:27.463",
|
||||
"lastModified": "2025-01-21T12:15:27.463",
|
||||
"vulnStatus": "Received",
|
||||
"cveTags": [],
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/sctp: Prevent autoclose integer overflow in sctp_association_init()\n\nWhile by default max_autoclose equals to INT_MAX / HZ, one may set\nnet.sctp.max_autoclose to UINT_MAX. There is code in\nsctp_association_init() that can consequently trigger overflow."
|
||||
}
|
||||
],
|
||||
"metrics": {},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/081bdb3a31674339313c6d702af922bc29de2c53",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/2297890b778b0e7c8200d6818154f7e461d78e94",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/271f031f4c31c07e2a85a1ba2b4c8e734909a477",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/4e86729d1ff329815a6e8a920cb554a1d4cb5b8d",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/7af63ef5fe4d480064eb22583b24ffc8b408183a",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/94b7ed0a4896420988e1776942f0a3f67167873e",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/f9c3adb083d3278f065a83c3f667f1246c74c31f",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
}
|
||||
]
|
||||
}
|
60
CVE-2025/CVE-2025-04xx/CVE-2025-0450.json
Normal file
60
CVE-2025/CVE-2025-04xx/CVE-2025-0450.json
Normal file
@ -0,0 +1,60 @@
|
||||
{
|
||||
"id": "CVE-2025-0450",
|
||||
"sourceIdentifier": "security@wordfence.com",
|
||||
"published": "2025-01-21T11:15:10.593",
|
||||
"lastModified": "2025-01-21T11:15:10.593",
|
||||
"vulnStatus": "Received",
|
||||
"cveTags": [],
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "The Betheme plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's custom JS functionality in all versions up to, and including, 27.6.1 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page."
|
||||
}
|
||||
],
|
||||
"metrics": {
|
||||
"cvssMetricV31": [
|
||||
{
|
||||
"source": "security@wordfence.com",
|
||||
"type": "Primary",
|
||||
"cvssData": {
|
||||
"version": "3.1",
|
||||
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N",
|
||||
"baseScore": 6.4,
|
||||
"baseSeverity": "MEDIUM",
|
||||
"attackVector": "NETWORK",
|
||||
"attackComplexity": "LOW",
|
||||
"privilegesRequired": "LOW",
|
||||
"userInteraction": "NONE",
|
||||
"scope": "CHANGED",
|
||||
"confidentialityImpact": "LOW",
|
||||
"integrityImpact": "LOW",
|
||||
"availabilityImpact": "NONE"
|
||||
},
|
||||
"exploitabilityScore": 3.1,
|
||||
"impactScore": 2.7
|
||||
}
|
||||
]
|
||||
},
|
||||
"weaknesses": [
|
||||
{
|
||||
"source": "security@wordfence.com",
|
||||
"type": "Primary",
|
||||
"description": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "CWE-79"
|
||||
}
|
||||
]
|
||||
}
|
||||
],
|
||||
"references": [
|
||||
{
|
||||
"url": "https://support.muffingroup.com/changelog/",
|
||||
"source": "security@wordfence.com"
|
||||
},
|
||||
{
|
||||
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/340c14ea-70b9-4f60-84b3-97328432f110?source=cve",
|
||||
"source": "security@wordfence.com"
|
||||
}
|
||||
]
|
||||
}
|
56
CVE-2025/CVE-2025-06xx/CVE-2025-0614.json
Normal file
56
CVE-2025/CVE-2025-06xx/CVE-2025-0614.json
Normal file
@ -0,0 +1,56 @@
|
||||
{
|
||||
"id": "CVE-2025-0614",
|
||||
"sourceIdentifier": "cve-coordination@incibe.es",
|
||||
"published": "2025-01-21T12:15:27.580",
|
||||
"lastModified": "2025-01-21T12:15:27.580",
|
||||
"vulnStatus": "Received",
|
||||
"cveTags": [],
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "Input validation vulnerability in Qualifio's Wheel of Fortune. This vulnerability could allow an attacker to modify a single email to contain upper and lower case characters in order to access the application and win prizes as many times as wanted."
|
||||
}
|
||||
],
|
||||
"metrics": {
|
||||
"cvssMetricV31": [
|
||||
{
|
||||
"source": "cve-coordination@incibe.es",
|
||||
"type": "Secondary",
|
||||
"cvssData": {
|
||||
"version": "3.1",
|
||||
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
|
||||
"baseScore": 5.3,
|
||||
"baseSeverity": "MEDIUM",
|
||||
"attackVector": "NETWORK",
|
||||
"attackComplexity": "LOW",
|
||||
"privilegesRequired": "NONE",
|
||||
"userInteraction": "NONE",
|
||||
"scope": "UNCHANGED",
|
||||
"confidentialityImpact": "NONE",
|
||||
"integrityImpact": "LOW",
|
||||
"availabilityImpact": "NONE"
|
||||
},
|
||||
"exploitabilityScore": 3.9,
|
||||
"impactScore": 1.4
|
||||
}
|
||||
]
|
||||
},
|
||||
"weaknesses": [
|
||||
{
|
||||
"source": "cve-coordination@incibe.es",
|
||||
"type": "Primary",
|
||||
"description": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "CWE-22"
|
||||
}
|
||||
]
|
||||
}
|
||||
],
|
||||
"references": [
|
||||
{
|
||||
"url": "https://www.incibe.es/en/incibe-cert/notices/aviso/multiple-vulnerabilities-qualifios-wheel-fortune",
|
||||
"source": "cve-coordination@incibe.es"
|
||||
}
|
||||
]
|
||||
}
|
56
CVE-2025/CVE-2025-06xx/CVE-2025-0615.json
Normal file
56
CVE-2025/CVE-2025-06xx/CVE-2025-0615.json
Normal file
@ -0,0 +1,56 @@
|
||||
{
|
||||
"id": "CVE-2025-0615",
|
||||
"sourceIdentifier": "cve-coordination@incibe.es",
|
||||
"published": "2025-01-21T12:15:27.737",
|
||||
"lastModified": "2025-01-21T12:15:27.737",
|
||||
"vulnStatus": "Received",
|
||||
"cveTags": [],
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "Input validation vulnerability in Qualifio's Wheel of Fortune. This vulnerability allows an attacker to modify an email to contain the \u2018+\u2019 symbol to access the application and win prizes as many times as wanted."
|
||||
}
|
||||
],
|
||||
"metrics": {
|
||||
"cvssMetricV31": [
|
||||
{
|
||||
"source": "cve-coordination@incibe.es",
|
||||
"type": "Secondary",
|
||||
"cvssData": {
|
||||
"version": "3.1",
|
||||
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
|
||||
"baseScore": 5.3,
|
||||
"baseSeverity": "MEDIUM",
|
||||
"attackVector": "NETWORK",
|
||||
"attackComplexity": "LOW",
|
||||
"privilegesRequired": "NONE",
|
||||
"userInteraction": "NONE",
|
||||
"scope": "UNCHANGED",
|
||||
"confidentialityImpact": "NONE",
|
||||
"integrityImpact": "LOW",
|
||||
"availabilityImpact": "NONE"
|
||||
},
|
||||
"exploitabilityScore": 3.9,
|
||||
"impactScore": 1.4
|
||||
}
|
||||
]
|
||||
},
|
||||
"weaknesses": [
|
||||
{
|
||||
"source": "cve-coordination@incibe.es",
|
||||
"type": "Primary",
|
||||
"description": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "CWE-22"
|
||||
}
|
||||
]
|
||||
}
|
||||
],
|
||||
"references": [
|
||||
{
|
||||
"url": "https://www.incibe.es/en/incibe-cert/notices/aviso/multiple-vulnerabilities-qualifios-wheel-fortune",
|
||||
"source": "cve-coordination@incibe.es"
|
||||
}
|
||||
]
|
||||
}
|
@ -2,13 +2,17 @@
|
||||
"id": "CVE-2025-21654",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2025-01-19T11:15:11.040",
|
||||
"lastModified": "2025-01-19T11:15:11.040",
|
||||
"lastModified": "2025-01-21T11:15:10.777",
|
||||
"vulnStatus": "Received",
|
||||
"cveTags": [],
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\novl: support encoding fid from inode with no alias\n\nDmitry Safonov reported that a WARN_ON() assertion can be trigered by\nuserspace when calling inotify_show_fdinfo() for an overlayfs watched\ninode, whose dentry aliases were discarded with drop_caches.\n\nThe WARN_ON() assertion in inotify_show_fdinfo() was removed, because\nit is possible for encoding file handle to fail for other reason, but\nthe impact of failing to encode an overlayfs file handle goes beyond\nthis assertion.\n\nAs shown in the LTP test case mentioned in the link below, failure to\nencode an overlayfs file handle from a non-aliased inode also leads to\nfailure to report an fid with FAN_DELETE_SELF fanotify events.\n\nAs Dmitry notes in his analyzis of the problem, ovl_encode_fh() fails\nif it cannot find an alias for the inode, but this failure can be fixed.\novl_encode_fh() seldom uses the alias and in the case of non-decodable\nfile handles, as is often the case with fanotify fid info,\novl_encode_fh() never needs to use the alias to encode a file handle.\n\nDefer finding an alias until it is actually needed so ovl_encode_fh()\nwill not fail in the common case of FAN_DELETE_SELF fanotify events."
|
||||
},
|
||||
{
|
||||
"lang": "es",
|
||||
"value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: ovl: soporte para codificar fid desde un inodo sin alias Dmitry Safonov inform\u00f3 que una aserci\u00f3n WARN_ON() puede ser activada por el espacio de usuario al llamar a inotify_show_fdinfo() para un inodo vigilado por overlayfs, cuyos alias dentry se descartaron con drop_caches. La aserci\u00f3n WARN_ON() en inotify_show_fdinfo() se elimin\u00f3, porque es posible que la codificaci\u00f3n del identificador de archivo falle por otra raz\u00f3n, pero el impacto de no codificar un identificador de archivo overlayfs va m\u00e1s all\u00e1 de esta aserci\u00f3n. Como se muestra en el caso de prueba LTP mencionado en el enlace a continuaci\u00f3n, no codificar un identificador de archivo overlayfs desde un inodo sin alias tambi\u00e9n conduce a no informar un fid con eventos fanotify FAN_DELETE_SELF. Como Dmitry se\u00f1ala en su an\u00e1lisis del problema, ovl_encode_fh() falla si no puede encontrar un alias para el inodo, pero este error se puede solucionar. ovl_encode_fh() rara vez usa el alias y en el caso de identificadores de archivos no decodificables, como suele ser el caso con la informaci\u00f3n de fid de fanotify, ovl_encode_fh() nunca necesita usar el alias para codificar un identificador de archivo. Aplaza la b\u00fasqueda de un alias hasta que realmente sea necesario para que ovl_encode_fh() no falle en el caso com\u00fan de eventos de fanotify FAN_DELETE_SELF."
|
||||
}
|
||||
],
|
||||
"metrics": {},
|
||||
@ -17,6 +21,10 @@
|
||||
"url": "https://git.kernel.org/stable/c/3c7c90274ae339e1ad443c9be1c67a20b80b9c76",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/950b604384fd75d62e860bec7135b2b62eb4d508",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/a1a541fbfa7e97c1100144db34b57553d7164ce5",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
|
35
README.md
35
README.md
@ -13,13 +13,13 @@ Repository synchronizes with the NVD every 2 hours.
|
||||
### Last Repository Update
|
||||
|
||||
```plain
|
||||
2025-01-21T11:00:49.836531+00:00
|
||||
2025-01-21T13:00:55.110954+00:00
|
||||
```
|
||||
|
||||
### Most recent CVE Modification Timestamp synchronized with NVD
|
||||
|
||||
```plain
|
||||
2025-01-21T10:15:08.110000+00:00
|
||||
2025-01-21T12:15:27.737000+00:00
|
||||
```
|
||||
|
||||
### Last Data Feed Release
|
||||
@ -33,27 +33,38 @@ Download and Changelog: [Click](https://github.com/fkie-cad/nvd-json-data-feeds/
|
||||
### Total Number of included CVEs
|
||||
|
||||
```plain
|
||||
278168
|
||||
278186
|
||||
```
|
||||
|
||||
### CVEs added in the last Commit
|
||||
|
||||
Recently added CVEs: `7`
|
||||
Recently added CVEs: `18`
|
||||
|
||||
- [CVE-2024-10936](CVE-2024/CVE-2024-109xx/CVE-2024-10936.json) (`2025-01-21T09:15:06.850`)
|
||||
- [CVE-2024-12005](CVE-2024/CVE-2024-120xx/CVE-2024-12005.json) (`2025-01-21T10:15:07.423`)
|
||||
- [CVE-2024-12104](CVE-2024/CVE-2024-121xx/CVE-2024-12104.json) (`2025-01-21T10:15:07.590`)
|
||||
- [CVE-2024-13404](CVE-2024/CVE-2024-134xx/CVE-2024-13404.json) (`2025-01-21T10:15:07.823`)
|
||||
- [CVE-2024-6466](CVE-2024/CVE-2024-64xx/CVE-2024-6466.json) (`2025-01-21T10:15:07.990`)
|
||||
- [CVE-2025-0371](CVE-2025/CVE-2025-03xx/CVE-2025-0371.json) (`2025-01-21T09:15:07.747`)
|
||||
- [CVE-2025-23184](CVE-2025/CVE-2025-231xx/CVE-2025-23184.json) (`2025-01-21T10:15:08.110`)
|
||||
- [CVE-2024-11226](CVE-2024/CVE-2024-112xx/CVE-2024-11226.json) (`2025-01-21T11:15:08.063`)
|
||||
- [CVE-2024-13230](CVE-2024/CVE-2024-132xx/CVE-2024-13230.json) (`2025-01-21T11:15:09.267`)
|
||||
- [CVE-2024-13444](CVE-2024/CVE-2024-134xx/CVE-2024-13444.json) (`2025-01-21T11:15:09.450`)
|
||||
- [CVE-2024-37284](CVE-2024/CVE-2024-372xx/CVE-2024-37284.json) (`2025-01-21T11:15:09.633`)
|
||||
- [CVE-2024-43709](CVE-2024/CVE-2024-437xx/CVE-2024-43709.json) (`2025-01-21T11:15:09.807`)
|
||||
- [CVE-2024-52973](CVE-2024/CVE-2024-529xx/CVE-2024-52973.json) (`2025-01-21T11:15:10.200`)
|
||||
- [CVE-2024-57930](CVE-2024/CVE-2024-579xx/CVE-2024-57930.json) (`2025-01-21T12:15:26.600`)
|
||||
- [CVE-2024-57931](CVE-2024/CVE-2024-579xx/CVE-2024-57931.json) (`2025-01-21T12:15:26.713`)
|
||||
- [CVE-2024-57932](CVE-2024/CVE-2024-579xx/CVE-2024-57932.json) (`2025-01-21T12:15:26.837`)
|
||||
- [CVE-2024-57933](CVE-2024/CVE-2024-579xx/CVE-2024-57933.json) (`2025-01-21T12:15:26.947`)
|
||||
- [CVE-2024-57934](CVE-2024/CVE-2024-579xx/CVE-2024-57934.json) (`2025-01-21T12:15:27.047`)
|
||||
- [CVE-2024-57935](CVE-2024/CVE-2024-579xx/CVE-2024-57935.json) (`2025-01-21T12:15:27.153`)
|
||||
- [CVE-2024-57936](CVE-2024/CVE-2024-579xx/CVE-2024-57936.json) (`2025-01-21T12:15:27.257`)
|
||||
- [CVE-2024-57937](CVE-2024/CVE-2024-579xx/CVE-2024-57937.json) (`2025-01-21T12:15:27.360`)
|
||||
- [CVE-2024-57938](CVE-2024/CVE-2024-579xx/CVE-2024-57938.json) (`2025-01-21T12:15:27.463`)
|
||||
- [CVE-2025-0450](CVE-2025/CVE-2025-04xx/CVE-2025-0450.json) (`2025-01-21T11:15:10.593`)
|
||||
- [CVE-2025-0614](CVE-2025/CVE-2025-06xx/CVE-2025-0614.json) (`2025-01-21T12:15:27.580`)
|
||||
- [CVE-2025-0615](CVE-2025/CVE-2025-06xx/CVE-2025-0615.json) (`2025-01-21T12:15:27.737`)
|
||||
|
||||
|
||||
### CVEs modified in the last Commit
|
||||
|
||||
Recently modified CVEs: `1`
|
||||
|
||||
- [CVE-2025-23086](CVE-2025/CVE-2025-230xx/CVE-2025-23086.json) (`2025-01-21T05:15:07.960`)
|
||||
- [CVE-2025-21654](CVE-2025/CVE-2025-216xx/CVE-2025-21654.json) (`2025-01-21T11:15:10.777`)
|
||||
|
||||
|
||||
## Download and Usage
|
||||
|
36
_state.csv
36
_state.csv
@ -244060,7 +244060,7 @@ CVE-2024-1093,0,0,ac60ea90a5bdbcab92bbb148d0d6ccb636fae604fade2bd9337658c1f74748
|
||||
CVE-2024-10932,0,0,28109702b795f9356a11af2c3727eebea623b98c280555fa2778753a6b0d3d2f,2025-01-04T08:15:05.713000
|
||||
CVE-2024-10933,0,0,04454997e745a68880991c602cc8325b99e3c53905740538bda66aba85b8cef1,2024-12-05T20:15:21.417000
|
||||
CVE-2024-10934,0,0,6dae70f2d9b047711f71d589675cbcb98ce87c40154b32c6e0f536ad5d783b6a,2024-11-18T17:11:56.587000
|
||||
CVE-2024-10936,1,1,de8af6a775c50d72f8c199dd8eb29b8f02cebf1221dd577bf12872aaafb8fa80,2025-01-21T09:15:06.850000
|
||||
CVE-2024-10936,0,0,de8af6a775c50d72f8c199dd8eb29b8f02cebf1221dd577bf12872aaafb8fa80,2025-01-21T09:15:06.850000
|
||||
CVE-2024-10937,0,0,f3549007a000819e9c2b92d84627c6a8f0950225e9fa8a067012e5b6f0eb9781,2024-12-05T09:15:04.377000
|
||||
CVE-2024-10939,0,0,51b8ed7e89cb6cce38a6a9e5f66ac395ad176f1b332ff5472d247565035a8f52,2024-12-16T19:15:06.400000
|
||||
CVE-2024-1094,0,0,4f6b2c2580413352eb02acf345a730d51f35d7640cec3afbef03e4f7e048ad8b,2024-11-21T08:49:46.967000
|
||||
@ -244298,6 +244298,7 @@ CVE-2024-11220,0,0,5638e4c56cecb636c7b9e9af730cca60f5085a7f9cf6e6a192a2c97c73aba
|
||||
CVE-2024-11223,0,0,d75d95a61775726397d8c97460b74fd5ed2ab0335df998c9281fea9bc6ff2b7b,2024-12-30T18:15:08.090000
|
||||
CVE-2024-11224,0,0,2cdc35f700571377d770dfe6d7a5c097f3055ab07c10acabf750a1174f4e07dd,2024-11-19T21:57:32.967000
|
||||
CVE-2024-11225,0,0,49e01dccad3ee4a4adc9a23405324c84c815ee3ae2fa63f77a3607812451f386,2024-11-22T06:15:19.283000
|
||||
CVE-2024-11226,1,1,afa1db73b8c2b090bf173ef7f76fb5cfcf845d8150d5606085134788e0c8b187,2025-01-21T11:15:08.063000
|
||||
CVE-2024-11227,0,0,4429f46befcca636641488313efda0ce9e85d610d1a8222594e7b609e2557ec7,2024-11-23T10:15:04.083000
|
||||
CVE-2024-11228,0,0,ea3ea506f494760971365e8cc08e4c50cc9e1b3e56f38ea31b32e4e82646f717,2024-11-23T12:15:18.577000
|
||||
CVE-2024-11229,0,0,f216e4e055884628872bc9827bd59bcb71e0c27eff667134ca7f40729f0e7955,2024-11-23T12:15:18.983000
|
||||
@ -245016,7 +245017,7 @@ CVE-2024-12001,0,0,75bbf94d31b41f422ac1216beeda365d0b924dd232e408edb33262f11bb39
|
||||
CVE-2024-12002,0,0,642bad4c124467ff4f581f355ddf310f5dadc994966ff22ccdf8e42852d0744f,2024-12-10T23:21:19.827000
|
||||
CVE-2024-12003,0,0,14ef5c0679ec50bb5e5014c8e7b631b4905f5419df127668fd74fc6d22bcfff5,2024-12-06T09:15:07.630000
|
||||
CVE-2024-12004,0,0,3dce40ab1e8f9f1b73bc9bad8477202dd665f9594517ea95d989e909aeed6010,2024-12-11T09:15:05.500000
|
||||
CVE-2024-12005,1,1,1766850016e926f572ec8194fc1a296e6bb93dfc6d5c258fb8f7de59daf4d89e,2025-01-21T10:15:07.423000
|
||||
CVE-2024-12005,0,0,1766850016e926f572ec8194fc1a296e6bb93dfc6d5c258fb8f7de59daf4d89e,2025-01-21T10:15:07.423000
|
||||
CVE-2024-12006,0,0,36f18b21148a0ee67abb3880ad49f0f8c4ad811090df2db1dbbfc11fa749b0af,2025-01-16T21:30:14.640000
|
||||
CVE-2024-12007,0,0,8e607a1eddf324cb0db7978994624ff72f4892cd536259d2d33593eb53a4d98b,2024-12-11T03:16:24.473000
|
||||
CVE-2024-12008,0,0,c6233d44f9ccc9833da766f9738aceabd906dd7310efd71abd35e6e9b4e35a50,2025-01-16T21:30:41.017000
|
||||
@ -245081,7 +245082,7 @@ CVE-2024-1210,0,0,f5a9389cac94cbfcfa3f0d961d1ea27115bf7afa331ce2988db15dbaf2efdf
|
||||
CVE-2024-12100,0,0,5d9bee140d619efc5bcb5724e98abb1747cc29824dfdae10a66de74940256d24,2024-12-24T06:15:32.830000
|
||||
CVE-2024-12101,0,0,cf6330eb409e982923b4b0b78cc8d64ad396889b9513f5530cedf911c9fe2802,2024-12-03T16:15:20.910000
|
||||
CVE-2024-12103,0,0,2ab2e8f87386f7081d0b465f2935a38be96d397e85c0b3ea2192a2941673c10d,2024-12-24T10:15:05.820000
|
||||
CVE-2024-12104,1,1,8d18a3955632d2f60b1f2d2d9e4277f093f000eeb635f2b8bad418cb70416321,2025-01-21T10:15:07.590000
|
||||
CVE-2024-12104,0,0,8d18a3955632d2f60b1f2d2d9e4277f093f000eeb635f2b8bad418cb70416321,2025-01-21T10:15:07.590000
|
||||
CVE-2024-12105,0,0,652104878b1388acf2a862591967482514a748c9cb01d37e99c6359ca0cc3cb2,2025-01-08T14:15:25.310000
|
||||
CVE-2024-12106,0,0,9e76ee608aca4c651df51a3d1911c7cd5490856624d29775a06f401fa9fe71c0,2025-01-06T16:54:14.560000
|
||||
CVE-2024-12107,0,0,7da8659dc821ee4f071df4b42d3ae5a3881cc2b8cc55779739dc797df4a302eb,2024-12-04T11:15:05
|
||||
@ -245909,6 +245910,7 @@ CVE-2024-13213,0,0,3077bf102e80b6ad26d9de82b06cecbfeedc1b0a01c454e5ec2b3b19555a5
|
||||
CVE-2024-13215,0,0,957a3cc32f27352db121dacda6bb51f9c346e02354a0696938a701fe4f0483cd,2025-01-15T13:15:09.263000
|
||||
CVE-2024-1322,0,0,a87df03aa9d8a817a942ae8ebad8afc3111ac175155d7ee73a384181ec986bff,2024-11-21T08:50:19.883000
|
||||
CVE-2024-1323,0,0,4b7fa94b4154618460e40e6b98637f7cb2a430b6e413bf16925f79721ae6c94f,2025-01-16T19:29:54.047000
|
||||
CVE-2024-13230,1,1,7558577363ef1493b174eeaccdeb94d8f8f1a05be6ba8cbadd5f15aa826f5566,2025-01-21T11:15:09.267000
|
||||
CVE-2024-13237,0,0,757f6068109954aeb708ce365b1ff5e5adf5204baad7d55d37a565a85d7816ad,2025-01-09T21:15:24.977000
|
||||
CVE-2024-13238,0,0,e97946c1ed27832515b261c210f4ad897caef0bf1252b79ed355ec42751c24a5,2025-01-09T21:15:25.130000
|
||||
CVE-2024-13239,0,0,91e163b85b63de6da134a1efa6398bca19ed0ada57bcebfc51e085d959e0fa81,2025-01-10T18:15:19.477000
|
||||
@ -246023,7 +246025,7 @@ CVE-2024-13394,0,0,2f438b906efb781207eeefa07105a693bc0286f21e9f9257684cfec9ce3d8
|
||||
CVE-2024-13398,0,0,1cf1394b81ba2d9f5d04722bdb6d4c350d6d6a7eb8c0a059d873a1872c1d84e5,2025-01-17T05:15:08.613000
|
||||
CVE-2024-1340,0,0,779cbb4786989b99b13d0df5bfadd47a6bb17fb76227d8a826f245b565dc9020,2024-11-21T08:50:22.180000
|
||||
CVE-2024-13401,0,0,5efe32d869945c8cf2c8e98762f61d5eb40d85526a7f385be1d59dce88509538,2025-01-17T05:15:09.077000
|
||||
CVE-2024-13404,1,1,b58f4e5da266e40a7294b1c5385e421341df230f5fb30104fb5c9ea0c1e7114b,2025-01-21T10:15:07.823000
|
||||
CVE-2024-13404,0,0,b58f4e5da266e40a7294b1c5385e421341df230f5fb30104fb5c9ea0c1e7114b,2025-01-21T10:15:07.823000
|
||||
CVE-2024-1341,0,0,090bf84c5ce2b0dfeca3a04f998237d36add49409b51be286587af2f8364beb8,2024-11-21T08:50:22.300000
|
||||
CVE-2024-1342,0,0,2f41e6eac1e33a309fc72543d371a67df7cdf22eae12449849cd3aab8e438d93,2024-10-14T22:15:03.180000
|
||||
CVE-2024-1343,0,0,7c2447499342d3573955d9e9545316db90429adf3b266826e2ed2754189f075e,2024-11-21T08:50:22.433000
|
||||
@ -246031,6 +246033,7 @@ CVE-2024-13432,0,0,7d75f67ac18cf32d5dc44570eb7cf156c877d943529d3637d5b0bb399b86a
|
||||
CVE-2024-13433,0,0,b744d44080e2e33c41984f231e71d8cc1252181c511f568444c5c86671c3eb05,2025-01-18T07:15:09.160000
|
||||
CVE-2024-13434,0,0,292fbae0324c9bc0e0a4304860c64d8e4dabea0f0444b12419bd12eebd083320,2025-01-17T05:15:09.290000
|
||||
CVE-2024-1344,0,0,3c7e3680ada5d2af6c947ff7713f6316fa39154980892782020553f5d0042cd7,2024-11-21T08:50:22.543000
|
||||
CVE-2024-13444,1,1,2a82e7dc36beac803abf8c10509e1ae610559c76a3585d9c1850f27a1808797c,2025-01-21T11:15:09.450000
|
||||
CVE-2024-1345,0,0,7c212e7b361746cfecf33f6e4ed924489ff6a3a938083dd73fe4da2b7b4649da,2024-11-21T08:50:22.667000
|
||||
CVE-2024-13454,0,0,e2d1844240dd5346b5a068b3df01d133d984159430edb62f356ca4bcac0bf3e6,2025-01-20T21:15:21.453000
|
||||
CVE-2024-1346,0,0,67674c75c08ebc67974102102d05a3921f8c61d1fe386fe7de33f2c37b3bc24d,2024-11-21T08:50:22.793000
|
||||
@ -259917,6 +259920,7 @@ CVE-2024-37280,0,0,82506e10255538602ec664d5ef7d85f7e7cc96b02dfe2ddcef5bb9ae709ea
|
||||
CVE-2024-37281,0,0,4249eefcbdc986d2244e44eaab8c4ce3c8b7e04bc410d0b79fef20d4a2687dce,2024-11-21T09:23:32.010000
|
||||
CVE-2024-37282,0,0,b5291a34bd6835cc4058846acc023216aad27c69e44906c812e14449c733e7c8,2024-11-21T09:23:32.153000
|
||||
CVE-2024-37283,0,0,ec4459cd72900aa75b10706008bd74f31d6ea48c0863dc3aa5968ea1e15e2f8e,2024-08-12T13:41:36.517000
|
||||
CVE-2024-37284,1,1,ac6ccd088383961d58c5c0ecf3e5338cc6be20b6740c1512763b9c5e4b35a030,2025-01-21T11:15:09.633000
|
||||
CVE-2024-37285,0,0,e8cc98ed37c5497fbc9f92b308c74c874cd45490ed814f99ca1ead61244ae5d6,2024-11-15T13:58:08.913000
|
||||
CVE-2024-37286,0,0,b4282d67550d8be06ee44ec1a1d7f9fab63643d7219a6e606e7fbac14d351953,2024-09-11T20:20:34.503000
|
||||
CVE-2024-37287,0,0,bcf9844fa80494210d104fcba352f6ab7b4fe100f45f4712e22ea47490257093,2024-08-22T13:33:12.477000
|
||||
@ -264732,6 +264736,7 @@ CVE-2024-43702,0,0,026195b67973267c5f7e1b66b43eadfe3de1f0eaa8dad79a11b9df4d6c345
|
||||
CVE-2024-43703,0,0,e564d47a3ea8e2e59e7c0c62fe5b37de767d270b87bc716325b902fc07b61a86,2024-12-01T23:15:06.383000
|
||||
CVE-2024-43704,0,0,82c22af109add6551b6eea89e99a6b50accfdf02d564899eae149615096d5dc8,2024-11-18T17:11:17.393000
|
||||
CVE-2024-43705,0,0,29f69c0cebaa0d9dd3b94a974b4686ab8ab2fbc5f28104cf63225fbecfd597b0,2024-12-28T17:15:07.190000
|
||||
CVE-2024-43709,1,1,09cf25b20d4028796eee5e828fe568cc7b1650ddae8136f4850d31a7a66e0f89,2025-01-21T11:15:09.807000
|
||||
CVE-2024-4371,0,0,e83d972dfd798c0045589442b000f085f252e3d21fb48583dd2590000a3618ae,2024-11-21T09:42:43.087000
|
||||
CVE-2024-43712,0,0,9ab3fe760e8f19464e8d37dd73b7335ae43d5382e27e4d6ab5795a2dd3e62314,2024-12-17T15:23:11.173000
|
||||
CVE-2024-43713,0,0,2351d2ccf5a9bdfa299b6fe1f3d7c7e3a4bbc01a6f8443c4348a36cf5880bc04,2024-12-17T14:55:13.953000
|
||||
@ -271066,6 +271071,7 @@ CVE-2024-52963,0,0,ff01669b1598f0bce0b4b90af8cc55f96a203c8a430eccd639efb9c221ab9
|
||||
CVE-2024-52967,0,0,ee495ed0ae82b5386a5a5e29b20d009f38e7fec0fdb15824df2e77e4920e6e29,2025-01-14T14:15:33.967000
|
||||
CVE-2024-52969,0,0,d48edc4c533d9acd9a260c0e4d555526245a1be1476ba79e29b9502b8c79f01c,2025-01-14T14:15:34.123000
|
||||
CVE-2024-5297,0,0,4e7f74d9629bbb9b864fb76b28bd5d406dd3be0c174577372182a6d0a600d934,2024-11-21T09:47:22.990000
|
||||
CVE-2024-52973,1,1,80557c3abfe62ff99c7924275640db641adc976d538445e17950b607d9ba9ac5,2025-01-21T11:15:10.200000
|
||||
CVE-2024-5298,0,0,329feabae44ccd7ff86530cac1ce0ba86c416ea44126377af7ea7290b6d65a10,2024-11-21T09:47:23.103000
|
||||
CVE-2024-52982,0,0,87ddbec0fddbec6a4eb61fd0607c77d31103b1dd9283c5a13ec4d5a36a8ccef0,2024-12-18T18:22:52.637000
|
||||
CVE-2024-52983,0,0,6cf30a09aaa853464d214fc07b1d213f931e08bd912522971a9cefc2fb965c45,2024-12-18T18:23:06.273000
|
||||
@ -273529,6 +273535,15 @@ CVE-2024-57927,0,0,0b956e6350555e8b5ea2acdf79ef7cfb9a66dd16a7df89342f758d8803aa3
|
||||
CVE-2024-57928,0,0,4412ceae5c4967ccbde2b773167aa35d2d70c86f93eb985ffd79716abee92366,2025-01-19T12:15:26.903000
|
||||
CVE-2024-57929,0,0,998c6814446dca86d10a4c87d5f49a55ef224c41c354b657152b370890f7274a,2025-01-19T12:15:27.013000
|
||||
CVE-2024-5793,0,0,0b18df4d2dde9f10f63097b806cad3cc9d51ae7c2ac550a36fec1a23c0e391bb,2024-11-21T09:48:20.673000
|
||||
CVE-2024-57930,1,1,28e6c7167ba130e9d2bb9fe716fd2e8f5146a8dadd573fe902b0a9d90eb763d3,2025-01-21T12:15:26.600000
|
||||
CVE-2024-57931,1,1,ef8b598f8ddd4428ab096ad25ca71fe2ac1458c1a2d30e4ee4df724312f40f52,2025-01-21T12:15:26.713000
|
||||
CVE-2024-57932,1,1,688bc5a581e562ea6a34243ed22eb114551e0d55b007f2c57ecd88c71662dd16,2025-01-21T12:15:26.837000
|
||||
CVE-2024-57933,1,1,a5f09101c1f266dd013e3ec124d1c1801c0703b5babe99bf295e942e95532e21,2025-01-21T12:15:26.947000
|
||||
CVE-2024-57934,1,1,43034e503550b569256632c4502d946f08931a3530bd54d0ff9ea3c30d627029,2025-01-21T12:15:27.047000
|
||||
CVE-2024-57935,1,1,e6daeb99554ae407cceaff9066c461bc5bc63d681f5adb174db5d16d19702a15,2025-01-21T12:15:27.153000
|
||||
CVE-2024-57936,1,1,417d6b45a5c6544407230a177f750b81a6fb6c38ea6d13678499dd9c742ed051,2025-01-21T12:15:27.257000
|
||||
CVE-2024-57937,1,1,03a617ee4ad0e6f08a572fb737e71c79db0c97a6263c69fc32916d1331b02bf3,2025-01-21T12:15:27.360000
|
||||
CVE-2024-57938,1,1,77ff62e982dad7ae42785578957ddb550a937967229142e5b9667c5d344b85c0,2025-01-21T12:15:27.463000
|
||||
CVE-2024-5795,0,0,8c27870eb8f46b4876cdd6a9335698b3a6adeccd1af066b5f5391281ef70b349,2024-11-21T09:48:20.780000
|
||||
CVE-2024-5796,0,0,10c3848976491ca5eeb295d89b1679f80388276c56109509ef1777f493022afe,2024-11-21T09:48:20.910000
|
||||
CVE-2024-5798,0,0,1cf6b5fddcb53bc6e432a6a3428f56651407d96c3d029c184944ae69fb8dd23b,2024-11-21T09:48:21.013000
|
||||
@ -274149,7 +274164,7 @@ CVE-2024-6461,0,0,86a214d0c7bd3f57cea37cd567b01f1a0e55f8d4342f6c7c46fd15b8942c8d
|
||||
CVE-2024-6463,0,0,f8d7d80ca565804c0caafdbc8214fe1eca7dc83d43861affc813af07365c0cc0,2024-07-03T21:15:04.640000
|
||||
CVE-2024-6464,0,0,8fab89d1b3aef32a257cf0d7fb909cce6ac18d5ef8dc898bb9f0cc6c52356cbf,2024-07-03T21:15:04.697000
|
||||
CVE-2024-6465,0,0,68d8747a1edb551a38d59b6ec4dd4815476646c814dc40035dcb46acd92026f8,2024-11-21T09:49:42.103000
|
||||
CVE-2024-6466,1,1,4741e2a246226c05d98e41077414cae927e260788f2017ee0f1bbbea611909bd,2025-01-21T10:15:07.990000
|
||||
CVE-2024-6466,0,0,4741e2a246226c05d98e41077414cae927e260788f2017ee0f1bbbea611909bd,2025-01-21T10:15:07.990000
|
||||
CVE-2024-6467,0,0,9106e28416ddacf000ab37b1593381e2fec3faec61ecd6e9335c0f9dfca2fd14,2024-11-21T09:49:42.217000
|
||||
CVE-2024-6468,0,0,bf6dfce1135e8cc0869c78add4d8cc7410dc08a391c67b63c78ccc7aa0f1b72a,2024-11-21T09:49:42.340000
|
||||
CVE-2024-6469,0,0,762a4dd73155da121b92d0ce24e9b3e8d90a41d9c751ed8a9040813e9a61f6c4,2024-11-21T09:49:42.447000
|
||||
@ -277239,7 +277254,7 @@ CVE-2025-0354,0,0,428d38f2781814173c07276c3123b7894bf18887b24de42981453e8b9fe91f
|
||||
CVE-2025-0355,0,0,60139aab38184d5553deea3c96ee67451ff405f2b0f65acb32b8c01c91586866,2025-01-21T04:15:07.877000
|
||||
CVE-2025-0356,0,0,00c4e703b995e5d2c2e4f165848b6efa20e85198e0b810bdb74efa5802e75a40,2025-01-21T04:15:07.980000
|
||||
CVE-2025-0369,0,0,60e0263b7bdd9bb8b2fbff594a1f912ed9cb257670ae53622ab1064bad30f4a5,2025-01-18T07:15:09.720000
|
||||
CVE-2025-0371,1,1,5204757392b802de2ea741b3e076d05df7ac5ea75604db8718cee7d5330989cb,2025-01-21T09:15:07.747000
|
||||
CVE-2025-0371,0,0,5204757392b802de2ea741b3e076d05df7ac5ea75604db8718cee7d5330989cb,2025-01-21T09:15:07.747000
|
||||
CVE-2025-0390,0,0,a9cacf0ddfe16d7ce6aba119743e725f69b4f5561bb60e372a0dcb6744d412ca,2025-01-11T08:15:26.527000
|
||||
CVE-2025-0391,0,0,ab8f7905746a492810fe86765faefb1fff997fc4d75bb4be776d20c58a35599f,2025-01-11T09:15:05.937000
|
||||
CVE-2025-0392,0,0,59785954f613ac3d294944412df9ed2ed102ba9c9ed7f965ef5916a645263c65,2025-01-11T11:15:06.657000
|
||||
@ -277275,6 +277290,7 @@ CVE-2025-0443,0,0,c1909e796cb00e8de6a9a5854d80254cec51da86d4853de7e67dd141d38121
|
||||
CVE-2025-0446,0,0,94e6a4f8238ac08191b1b1193dfc6ed660ba2c81f2654a86993face2b3a1da98,2025-01-15T15:15:15.960000
|
||||
CVE-2025-0447,0,0,3557744a211333232e7804efa6ea8142b021fe0e2643e57c3966ef0e6eae106e,2025-01-15T15:15:16.123000
|
||||
CVE-2025-0448,0,0,fd891759faceb30544c1e8bca8f73da87c02e801462e8b0ca59fcc1cdae9bb12,2025-01-15T15:15:16.277000
|
||||
CVE-2025-0450,1,1,72a68fd04846059d252f15073dbabd133ee3ab883fab4b780450285039285c87,2025-01-21T11:15:10.593000
|
||||
CVE-2025-0455,0,0,0788a35b7031b1503942329db48de69d2dae6db6b33ff6b776c7fa5eff813a90,2025-01-16T02:15:27.203000
|
||||
CVE-2025-0456,0,0,c3118eb6282d0d2d5cf0b0b18ba4321a7c4ee4642eefb293f75da78a6b102328,2025-01-16T02:15:27.387000
|
||||
CVE-2025-0457,0,0,6c68c67055a4f977d01fcaec54af3a741663b7ba3a654f25dcda2d901b15c7c0,2025-01-16T02:15:27.553000
|
||||
@ -277348,6 +277364,8 @@ CVE-2025-0584,0,0,37edd7443b159fd364fe1f94f606e27d6a33e0c9083f38da0f466f56b50d0a
|
||||
CVE-2025-0585,0,0,da99d05fd55072bf46a920856a2fb4b6ebf8e817a63e5b48426e8c31494a0fa3,2025-01-20T03:15:09.283000
|
||||
CVE-2025-0586,0,0,abf0a06c875b8bd5421f2c6f6ef5b8719d6ca1dacc61f1270de8b585f4b2e6ab,2025-01-20T03:15:09.433000
|
||||
CVE-2025-0590,0,0,ec6ed4b059a1df3da99443ca46730b85e5006c3028b17625361be7e7854142f6,2025-01-20T07:17:10.383000
|
||||
CVE-2025-0614,1,1,c85e5b141df45983a9b8023744afed1074e3155c77698a4efcba3b1933f20f8e,2025-01-21T12:15:27.580000
|
||||
CVE-2025-0615,1,1,24948b17ddad86445a37019481e808c754a1ff5ca4b2da53c27f9618c73c00c8,2025-01-21T12:15:27.737000
|
||||
CVE-2025-20016,0,0,6fccb84eb01c2cd66b422e82777f9738bfe5004121e1b551d0ae454724543c0e,2025-01-14T10:15:07.500000
|
||||
CVE-2025-20033,0,0,6c60c85e451f1d6db70378d678ddf83dacc7c823ecfb493748ed6d94114eff49,2025-01-09T07:15:28.450000
|
||||
CVE-2025-20036,0,0,a1d7639f0e568c5953a2962f5a2be630b5737d729f8c4f565a3eec7e4bf19549,2025-01-15T17:15:18.950000
|
||||
@ -277595,7 +277613,7 @@ CVE-2025-21650,0,0,8999d80331f22604edddfd75667fe17eab77150206057afd0258b361cf1da
|
||||
CVE-2025-21651,0,0,08b0d285d803ce14ca95c51ff0bb6822af7a1dfa543a30bb044ccb678d352dfa,2025-01-19T11:15:10.733000
|
||||
CVE-2025-21652,0,0,781ce4cdff4e60cfb6f8b0eb373b8634b7b2c8bf54de4c678c30aac3d57ceb30,2025-01-19T11:15:10.830000
|
||||
CVE-2025-21653,0,0,f32ca4f34b7bccc36e5debfdf592df2ad87aa1a93c5b7257a97a73e494c6108b,2025-01-19T11:15:10.940000
|
||||
CVE-2025-21654,0,0,1e4de08a34cab5d4b4d5c6f2cdca90847554e3952c3a83e001ff2672952d2415,2025-01-19T11:15:11.040000
|
||||
CVE-2025-21654,0,1,387bd74314e19ea277d2aa993508db4a58606a45347df382e4b9016f897da6e3,2025-01-21T11:15:10.777000
|
||||
CVE-2025-21655,0,0,e5a98c6155ef95beaa77c8f70c04ef1a52b9c9b57ffc8aa737b1a8a15dabbd07,2025-01-20T14:15:27.027000
|
||||
CVE-2025-22130,0,0,a71c51c8237898c4394724aa5ef423b90094196082b564075e1f1cf6c2992343,2025-01-08T16:15:38.543000
|
||||
CVE-2025-22131,0,0,8a8cd24dd50518945167d9268c0c244cc17a87d8ffed5574dca8152c7cdb7333,2025-01-20T16:15:27.880000
|
||||
@ -277925,7 +277943,7 @@ CVE-2025-23079,0,0,78406696c95877d502c4c9b4607328548f20c8246eeff924786f7d9228881
|
||||
CVE-2025-23080,0,0,165d07f7f3ac467de5017c0ed6cba0e28a556747a1eb136b531ca8b1a8ca92c9,2025-01-14T18:16:06.110000
|
||||
CVE-2025-23081,0,0,8e8adb61025ad816e7ca7d3f543c46c43aae9a6ff6f38d8ecfef81ad769cb146,2025-01-16T16:15:36.090000
|
||||
CVE-2025-23082,0,0,04a4f0f7ff5458b7d3b3235d7001e50f9111979d3e99a4d703024d8cba8b9a7c,2025-01-14T16:15:36.200000
|
||||
CVE-2025-23086,0,1,c46aadd2b0703cb39e3c65b8503fe18a80fb58d59bee9cf6756aa65ff2294990,2025-01-21T05:15:07.960000
|
||||
CVE-2025-23086,0,0,c46aadd2b0703cb39e3c65b8503fe18a80fb58d59bee9cf6756aa65ff2294990,2025-01-21T05:15:07.960000
|
||||
CVE-2025-23108,0,0,0867ae52bf9537919e00df206497183b5abf45a3a43e56579f476cc3d26e8d6c,2025-01-13T18:15:22.680000
|
||||
CVE-2025-23109,0,0,4d519c5c41161d21ebd8f814ea3659acc2224a598528dd7d3e4c7b87a5ad8cc0,2025-01-13T18:15:22.903000
|
||||
CVE-2025-23110,0,0,b9e32d20d7e6cf23b28c590dc2ad7f239b5186f27517cd303db97f7275b077fa,2025-01-10T22:15:27.550000
|
||||
@ -277937,7 +277955,7 @@ CVE-2025-23125,0,0,2e6f0fce9ee8e787d649705f4cf1025930f6b72d6ac2efc70c4c1837b8d7d
|
||||
CVE-2025-23126,0,0,aec9ca15332b86ad22382c8419cfef8190ae4b723f5c3088974b31a1f5dd4089,2025-01-11T15:15:09.100000
|
||||
CVE-2025-23127,0,0,ef1aeaee3e917139d62386eaa309c28fa46e54be8ed45ecdaab4f9d4f96931db,2025-01-11T15:15:09.173000
|
||||
CVE-2025-23128,0,0,856260a69fb4f1bb5d13296c47ffc7dac686c7ca9a44fff8151b1b7f11a740a9,2025-01-11T15:15:09.250000
|
||||
CVE-2025-23184,1,1,85dc0b5143649e34450a3676900e6e40d3e1c3056b6e1dfc30b9a36cadde4291,2025-01-21T10:15:08.110000
|
||||
CVE-2025-23184,0,0,85dc0b5143649e34450a3676900e6e40d3e1c3056b6e1dfc30b9a36cadde4291,2025-01-21T10:15:08.110000
|
||||
CVE-2025-23198,0,0,8821b8df90adb16cf3625e528f68c391c0bcfa1c8e1e079b50c30f527c621897,2025-01-16T23:15:08.410000
|
||||
CVE-2025-23199,0,0,3b82f03297e12f7b25649af5d3a8aa211e1441848bb66c00094132bcfe252a94,2025-01-16T23:15:08.567000
|
||||
CVE-2025-23200,0,0,76f8b53439f8a2997652c579cc0769759091077ab1b58d306f6ddac70c67ff17,2025-01-16T23:15:08.720000
|
||||
|
Can't render this file because it is too large.
|
Loading…
x
Reference in New Issue
Block a user