mirror of
https://github.com/fkie-cad/nvd-json-data-feeds.git
synced 2025-05-08 11:37:26 +00:00
Auto-Update: 2024-03-09T09:00:30.600417+00:00
This commit is contained in:
parent
2e4c691370
commit
7b5aab7d74
47
CVE-2024/CVE-2024-11xx/CVE-2024-1123.json
Normal file
47
CVE-2024/CVE-2024-11xx/CVE-2024-1123.json
Normal file
@ -0,0 +1,47 @@
|
||||
{
|
||||
"id": "CVE-2024-1123",
|
||||
"sourceIdentifier": "security@wordfence.com",
|
||||
"published": "2024-03-09T07:15:07.233",
|
||||
"lastModified": "2024-03-09T07:15:07.233",
|
||||
"vulnStatus": "Received",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "The EventPrime \u2013 Events Calendar, Bookings and Tickets plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the save_frontend_event_submission() function in all versions up to, and including, 3.4.2. This makes it possible for authenticated attackers, with subscriber-level access and above, to overwrite the title and content of arbitrary posts. This can also be exploited by unauthenticated attackers when the allow_submission_by_anonymous_user setting is enabled."
|
||||
}
|
||||
],
|
||||
"metrics": {
|
||||
"cvssMetricV31": [
|
||||
{
|
||||
"source": "security@wordfence.com",
|
||||
"type": "Secondary",
|
||||
"cvssData": {
|
||||
"version": "3.1",
|
||||
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N",
|
||||
"attackVector": "NETWORK",
|
||||
"attackComplexity": "LOW",
|
||||
"privilegesRequired": "LOW",
|
||||
"userInteraction": "NONE",
|
||||
"scope": "UNCHANGED",
|
||||
"confidentialityImpact": "NONE",
|
||||
"integrityImpact": "HIGH",
|
||||
"availabilityImpact": "NONE",
|
||||
"baseScore": 6.5,
|
||||
"baseSeverity": "MEDIUM"
|
||||
},
|
||||
"exploitabilityScore": 2.8,
|
||||
"impactScore": 3.6
|
||||
}
|
||||
]
|
||||
},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3033882%40eventprime-event-calendar-management&new=3033882%40eventprime-event-calendar-management&sfp_email=&sfph_mail=",
|
||||
"source": "security@wordfence.com"
|
||||
},
|
||||
{
|
||||
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/351926d4-a9be-4fbd-bdf2-8bbff41d97ef?source=cve",
|
||||
"source": "security@wordfence.com"
|
||||
}
|
||||
]
|
||||
}
|
47
CVE-2024/CVE-2024-11xx/CVE-2024-1124.json
Normal file
47
CVE-2024/CVE-2024-11xx/CVE-2024-1124.json
Normal file
@ -0,0 +1,47 @@
|
||||
{
|
||||
"id": "CVE-2024-1124",
|
||||
"sourceIdentifier": "security@wordfence.com",
|
||||
"published": "2024-03-09T07:15:08.000",
|
||||
"lastModified": "2024-03-09T07:15:08.000",
|
||||
"vulnStatus": "Received",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "The EventPrime \u2013 Events Calendar, Bookings and Tickets plugin for WordPress is vulnerable to unauthorized email sending due to a missing capability check on the ep_send_attendees_email() function in all versions up to, and including, 3.4.1. This makes it possible for authenticated attackers, with subscriber-level access and above, to send arbitrary emails with arbitrary content from the site."
|
||||
}
|
||||
],
|
||||
"metrics": {
|
||||
"cvssMetricV31": [
|
||||
{
|
||||
"source": "security@wordfence.com",
|
||||
"type": "Secondary",
|
||||
"cvssData": {
|
||||
"version": "3.1",
|
||||
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N",
|
||||
"attackVector": "NETWORK",
|
||||
"attackComplexity": "LOW",
|
||||
"privilegesRequired": "LOW",
|
||||
"userInteraction": "NONE",
|
||||
"scope": "UNCHANGED",
|
||||
"confidentialityImpact": "NONE",
|
||||
"integrityImpact": "LOW",
|
||||
"availabilityImpact": "NONE",
|
||||
"baseScore": 4.3,
|
||||
"baseSeverity": "MEDIUM"
|
||||
},
|
||||
"exploitabilityScore": 2.8,
|
||||
"impactScore": 1.4
|
||||
}
|
||||
]
|
||||
},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3043888%40eventprime-event-calendar-management&new=3043888%40eventprime-event-calendar-management&sfp_email=&sfph_mail=",
|
||||
"source": "security@wordfence.com"
|
||||
},
|
||||
{
|
||||
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/346049ca-1bc5-4e02-9f38-d1f64338709d?source=cve",
|
||||
"source": "security@wordfence.com"
|
||||
}
|
||||
]
|
||||
}
|
47
CVE-2024/CVE-2024-11xx/CVE-2024-1125.json
Normal file
47
CVE-2024/CVE-2024-11xx/CVE-2024-1125.json
Normal file
@ -0,0 +1,47 @@
|
||||
{
|
||||
"id": "CVE-2024-1125",
|
||||
"sourceIdentifier": "security@wordfence.com",
|
||||
"published": "2024-03-09T07:15:08.313",
|
||||
"lastModified": "2024-03-09T07:15:08.313",
|
||||
"vulnStatus": "Received",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "The EventPrime \u2013 Events Calendar, Bookings and Tickets plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the calendar_events_delete() function in all versions up to, and including, 3.4.3. This makes it possible for authenticated attackers, with subscriber-level access and above, to delete arbitrary posts."
|
||||
}
|
||||
],
|
||||
"metrics": {
|
||||
"cvssMetricV31": [
|
||||
{
|
||||
"source": "security@wordfence.com",
|
||||
"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:L",
|
||||
"attackVector": "NETWORK",
|
||||
"attackComplexity": "LOW",
|
||||
"privilegesRequired": "NONE",
|
||||
"userInteraction": "NONE",
|
||||
"scope": "UNCHANGED",
|
||||
"confidentialityImpact": "NONE",
|
||||
"integrityImpact": "LOW",
|
||||
"availabilityImpact": "LOW",
|
||||
"baseScore": 6.5,
|
||||
"baseSeverity": "MEDIUM"
|
||||
},
|
||||
"exploitabilityScore": 3.9,
|
||||
"impactScore": 2.5
|
||||
}
|
||||
]
|
||||
},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3043888%40eventprime-event-calendar-management&new=3043888%40eventprime-event-calendar-management&sfp_email=&sfph_mail=",
|
||||
"source": "security@wordfence.com"
|
||||
},
|
||||
{
|
||||
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/b5278afb-9db3-4b1d-bb2f-e6595f0ac6dc?source=cve",
|
||||
"source": "security@wordfence.com"
|
||||
}
|
||||
]
|
||||
}
|
47
CVE-2024/CVE-2024-13xx/CVE-2024-1320.json
Normal file
47
CVE-2024/CVE-2024-13xx/CVE-2024-1320.json
Normal file
@ -0,0 +1,47 @@
|
||||
{
|
||||
"id": "CVE-2024-1320",
|
||||
"sourceIdentifier": "security@wordfence.com",
|
||||
"published": "2024-03-09T07:15:08.730",
|
||||
"lastModified": "2024-03-09T07:15:08.730",
|
||||
"vulnStatus": "Received",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "The EventPrime \u2013 Events Calendar, Bookings and Tickets plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'offline_status' parameter in all versions up to, and including, 3.4.3 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page."
|
||||
}
|
||||
],
|
||||
"metrics": {
|
||||
"cvssMetricV31": [
|
||||
{
|
||||
"source": "security@wordfence.com",
|
||||
"type": "Secondary",
|
||||
"cvssData": {
|
||||
"version": "3.1",
|
||||
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N",
|
||||
"attackVector": "NETWORK",
|
||||
"attackComplexity": "LOW",
|
||||
"privilegesRequired": "NONE",
|
||||
"userInteraction": "NONE",
|
||||
"scope": "UNCHANGED",
|
||||
"confidentialityImpact": "LOW",
|
||||
"integrityImpact": "LOW",
|
||||
"availabilityImpact": "NONE",
|
||||
"baseScore": 6.5,
|
||||
"baseSeverity": "MEDIUM"
|
||||
},
|
||||
"exploitabilityScore": 3.9,
|
||||
"impactScore": 2.5
|
||||
}
|
||||
]
|
||||
},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3043888%40eventprime-event-calendar-management&new=3043888%40eventprime-event-calendar-management&sfp_email=&sfph_mail=",
|
||||
"source": "security@wordfence.com"
|
||||
},
|
||||
{
|
||||
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/7e82e1c5-0ed4-4dee-9990-976591693eb5?source=cve",
|
||||
"source": "security@wordfence.com"
|
||||
}
|
||||
]
|
||||
}
|
47
CVE-2024/CVE-2024-17xx/CVE-2024-1767.json
Normal file
47
CVE-2024/CVE-2024-17xx/CVE-2024-1767.json
Normal file
@ -0,0 +1,47 @@
|
||||
{
|
||||
"id": "CVE-2024-1767",
|
||||
"sourceIdentifier": "security@wordfence.com",
|
||||
"published": "2024-03-09T07:15:09.173",
|
||||
"lastModified": "2024-03-09T07:15:09.173",
|
||||
"vulnStatus": "Received",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "The Blocksy theme for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's blocks in all versions up to, and including, 2.0.26 due to insufficient input sanitization and output escaping on user supplied attributes like 'className' and 'radius'. This makes it possible for authenticated attackers with contributor-level and above permissions to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page."
|
||||
}
|
||||
],
|
||||
"metrics": {
|
||||
"cvssMetricV31": [
|
||||
{
|
||||
"source": "security@wordfence.com",
|
||||
"type": "Secondary",
|
||||
"cvssData": {
|
||||
"version": "3.1",
|
||||
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N",
|
||||
"attackVector": "NETWORK",
|
||||
"attackComplexity": "LOW",
|
||||
"privilegesRequired": "LOW",
|
||||
"userInteraction": "NONE",
|
||||
"scope": "CHANGED",
|
||||
"confidentialityImpact": "LOW",
|
||||
"integrityImpact": "LOW",
|
||||
"availabilityImpact": "NONE",
|
||||
"baseScore": 6.4,
|
||||
"baseSeverity": "MEDIUM"
|
||||
},
|
||||
"exploitabilityScore": 3.1,
|
||||
"impactScore": 2.7
|
||||
}
|
||||
]
|
||||
},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://themes.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=219324%40blocksy&new=219324%40blocksy&sfp_email=&sfph_mail=",
|
||||
"source": "security@wordfence.com"
|
||||
},
|
||||
{
|
||||
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/fdeab668-9094-485f-aa01-13ba5c10ea89?source=cve",
|
||||
"source": "security@wordfence.com"
|
||||
}
|
||||
]
|
||||
}
|
88
CVE-2024/CVE-2024-23xx/CVE-2024-2329.json
Normal file
88
CVE-2024/CVE-2024-23xx/CVE-2024-2329.json
Normal file
@ -0,0 +1,88 @@
|
||||
{
|
||||
"id": "CVE-2024-2329",
|
||||
"sourceIdentifier": "cna@vuldb.com",
|
||||
"published": "2024-03-09T08:15:06.217",
|
||||
"lastModified": "2024-03-09T08:15:06.217",
|
||||
"vulnStatus": "Received",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "A vulnerability was found in Netentsec NS-ASG Application Security Gateway 6.3 and classified as critical. Affected by this issue is some unknown functionality of the file /admin/list_resource_icon.php?action=delete. The manipulation of the argument IconId leads to sql injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-256280. NOTE: The vendor was contacted early about this disclosure but did not respond in any way."
|
||||
}
|
||||
],
|
||||
"metrics": {
|
||||
"cvssMetricV31": [
|
||||
{
|
||||
"source": "cna@vuldb.com",
|
||||
"type": "Secondary",
|
||||
"cvssData": {
|
||||
"version": "3.1",
|
||||
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L",
|
||||
"attackVector": "NETWORK",
|
||||
"attackComplexity": "LOW",
|
||||
"privilegesRequired": "LOW",
|
||||
"userInteraction": "NONE",
|
||||
"scope": "UNCHANGED",
|
||||
"confidentialityImpact": "LOW",
|
||||
"integrityImpact": "LOW",
|
||||
"availabilityImpact": "LOW",
|
||||
"baseScore": 6.3,
|
||||
"baseSeverity": "MEDIUM"
|
||||
},
|
||||
"exploitabilityScore": 2.8,
|
||||
"impactScore": 3.4
|
||||
}
|
||||
],
|
||||
"cvssMetricV2": [
|
||||
{
|
||||
"source": "cna@vuldb.com",
|
||||
"type": "Secondary",
|
||||
"cvssData": {
|
||||
"version": "2.0",
|
||||
"vectorString": "AV:N/AC:L/Au:S/C:P/I:P/A:P",
|
||||
"accessVector": "NETWORK",
|
||||
"accessComplexity": "LOW",
|
||||
"authentication": "SINGLE",
|
||||
"confidentialityImpact": "PARTIAL",
|
||||
"integrityImpact": "PARTIAL",
|
||||
"availabilityImpact": "PARTIAL",
|
||||
"baseScore": 6.5
|
||||
},
|
||||
"baseSeverity": "MEDIUM",
|
||||
"exploitabilityScore": 8.0,
|
||||
"impactScore": 6.4,
|
||||
"acInsufInfo": false,
|
||||
"obtainAllPrivilege": false,
|
||||
"obtainUserPrivilege": false,
|
||||
"obtainOtherPrivilege": false,
|
||||
"userInteractionRequired": false
|
||||
}
|
||||
]
|
||||
},
|
||||
"weaknesses": [
|
||||
{
|
||||
"source": "cna@vuldb.com",
|
||||
"type": "Primary",
|
||||
"description": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "CWE-89"
|
||||
}
|
||||
]
|
||||
}
|
||||
],
|
||||
"references": [
|
||||
{
|
||||
"url": "https://github.com/flyyue2001/cve/blob/main/NS-ASG-sql-list_resource_icon.md",
|
||||
"source": "cna@vuldb.com"
|
||||
},
|
||||
{
|
||||
"url": "https://vuldb.com/?ctiid.256280",
|
||||
"source": "cna@vuldb.com"
|
||||
},
|
||||
{
|
||||
"url": "https://vuldb.com/?id.256280",
|
||||
"source": "cna@vuldb.com"
|
||||
}
|
||||
]
|
||||
}
|
20
CVE-2024/CVE-2024-255xx/CVE-2024-25501.json
Normal file
20
CVE-2024/CVE-2024-255xx/CVE-2024-25501.json
Normal file
@ -0,0 +1,20 @@
|
||||
{
|
||||
"id": "CVE-2024-25501",
|
||||
"sourceIdentifier": "cve@mitre.org",
|
||||
"published": "2024-03-09T08:15:05.973",
|
||||
"lastModified": "2024-03-09T08:15:05.973",
|
||||
"vulnStatus": "Received",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "An issue WinMail v.7.1 and v.5.1 and before allows a remote attacker to execute arbitrary code via a crafted script to the email parameter."
|
||||
}
|
||||
],
|
||||
"metrics": {},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://gist.github.com/Drun1baby/8270239bed2952dbd99cc8d4262728e8",
|
||||
"source": "cve@mitre.org"
|
||||
}
|
||||
]
|
||||
}
|
@ -2,12 +2,16 @@
|
||||
"id": "CVE-2024-26450",
|
||||
"sourceIdentifier": "cve@mitre.org",
|
||||
"published": "2024-02-28T22:15:26.730",
|
||||
"lastModified": "2024-02-29T13:49:47.277",
|
||||
"lastModified": "2024-03-09T08:15:06.120",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "Cross Site Scripting vulnerability in Piwigo before v.14.2.0 allows a remote attacker to escalate privileges via the batch function on the admin page."
|
||||
"value": "An issue exists within Piwigo before v.14.2.0 allowing a malicious user to take over the application. This exploit involves chaining a Cross Site Request Forgery vulnerability to issue a Stored Cross Site Scripting payload stored within an Admin user's dashboard, executing remote JavaScript. This can be used to upload a new PHP file under an administrator and directly call that file from the victim's instance to connect back to a malicious listener."
|
||||
},
|
||||
{
|
||||
"lang": "es",
|
||||
"value": "La vulnerabilidad de Cross Site Scripting en Piwigo anterior a v.14.2.0 permite a un atacante remoto escalar privilegios a trav\u00e9s de la funci\u00f3n por lotes en la p\u00e1gina de administraci\u00f3n."
|
||||
}
|
||||
],
|
||||
"metrics": {},
|
||||
|
24
CVE-2024/CVE-2024-280xx/CVE-2024-28089.json
Normal file
24
CVE-2024/CVE-2024-280xx/CVE-2024-28089.json
Normal file
@ -0,0 +1,24 @@
|
||||
{
|
||||
"id": "CVE-2024-28089",
|
||||
"sourceIdentifier": "cve@mitre.org",
|
||||
"published": "2024-03-09T07:15:09.577",
|
||||
"lastModified": "2024-03-09T07:15:09.577",
|
||||
"vulnStatus": "Received",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "Hitron CODA-4582 2AHKM-CODA4589 7.2.4.5.1b8 devices allow a remote attacker within Wi-Fi proximity (who has access to the router admin panel) to conduct a DOM-based stored XSS attack that can fetch remote resources. The payload is executed at index.html#advanced_location (aka the Device Location page). This can cause a denial of service or lead to information disclosure."
|
||||
}
|
||||
],
|
||||
"metrics": {},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://drive.proton.me/urls/8RVTDGP9C0#GLVSkEMRYULI",
|
||||
"source": "cve@mitre.org"
|
||||
},
|
||||
{
|
||||
"url": "https://github.com/actuator/cve/blob/main/Hitron/CVE-2024-28089",
|
||||
"source": "cve@mitre.org"
|
||||
}
|
||||
]
|
||||
}
|
25
README.md
25
README.md
@ -9,13 +9,13 @@ Repository synchronizes with the NVD every 2 hours.
|
||||
### Last Repository Update
|
||||
|
||||
```plain
|
||||
2024-03-09T07:00:29.176768+00:00
|
||||
2024-03-09T09:00:30.600417+00:00
|
||||
```
|
||||
|
||||
### Most recent CVE Modification Timestamp synchronized with NVD
|
||||
|
||||
```plain
|
||||
2024-03-09T06:15:50.797000+00:00
|
||||
2024-03-09T08:15:06.217000+00:00
|
||||
```
|
||||
|
||||
### Last Data Feed Release
|
||||
@ -29,25 +29,28 @@ Download and Changelog: [Click](https://github.com/fkie-cad/nvd-json-data-feeds/
|
||||
### Total Number of included CVEs
|
||||
|
||||
```plain
|
||||
240925
|
||||
240933
|
||||
```
|
||||
|
||||
### CVEs added in the last Commit
|
||||
|
||||
Recently added CVEs: `6`
|
||||
Recently added CVEs: `8`
|
||||
|
||||
* [CVE-2023-46426](CVE-2023/CVE-2023-464xx/CVE-2023-46426.json) (`2024-03-09T06:15:50.637`)
|
||||
* [CVE-2023-46427](CVE-2023/CVE-2023-464xx/CVE-2023-46427.json) (`2024-03-09T06:15:50.740`)
|
||||
* [CVE-2023-49340](CVE-2023/CVE-2023-493xx/CVE-2023-49340.json) (`2024-03-09T05:15:08.723`)
|
||||
* [CVE-2023-49341](CVE-2023/CVE-2023-493xx/CVE-2023-49341.json) (`2024-03-09T05:15:08.870`)
|
||||
* [CVE-2023-50015](CVE-2023/CVE-2023-500xx/CVE-2023-50015.json) (`2024-03-09T05:15:08.923`)
|
||||
* [CVE-2024-25951](CVE-2024/CVE-2024-259xx/CVE-2024-25951.json) (`2024-03-09T06:15:50.797`)
|
||||
* [CVE-2024-1123](CVE-2024/CVE-2024-11xx/CVE-2024-1123.json) (`2024-03-09T07:15:07.233`)
|
||||
* [CVE-2024-1124](CVE-2024/CVE-2024-11xx/CVE-2024-1124.json) (`2024-03-09T07:15:08.000`)
|
||||
* [CVE-2024-1125](CVE-2024/CVE-2024-11xx/CVE-2024-1125.json) (`2024-03-09T07:15:08.313`)
|
||||
* [CVE-2024-1320](CVE-2024/CVE-2024-13xx/CVE-2024-1320.json) (`2024-03-09T07:15:08.730`)
|
||||
* [CVE-2024-1767](CVE-2024/CVE-2024-17xx/CVE-2024-1767.json) (`2024-03-09T07:15:09.173`)
|
||||
* [CVE-2024-2329](CVE-2024/CVE-2024-23xx/CVE-2024-2329.json) (`2024-03-09T08:15:06.217`)
|
||||
* [CVE-2024-25501](CVE-2024/CVE-2024-255xx/CVE-2024-25501.json) (`2024-03-09T08:15:05.973`)
|
||||
* [CVE-2024-28089](CVE-2024/CVE-2024-280xx/CVE-2024-28089.json) (`2024-03-09T07:15:09.577`)
|
||||
|
||||
|
||||
### CVEs modified in the last Commit
|
||||
|
||||
Recently modified CVEs: `0`
|
||||
Recently modified CVEs: `1`
|
||||
|
||||
* [CVE-2024-26450](CVE-2024/CVE-2024-264xx/CVE-2024-26450.json) (`2024-03-09T08:15:06.120`)
|
||||
|
||||
|
||||
## Download and Usage
|
||||
|
22
_state.csv
22
_state.csv
@ -232234,8 +232234,8 @@ CVE-2023-46421,0,0,20c19b3af247cd93c6c12b505ba6b896d24101e71f7247c22397f1d65ac40
|
||||
CVE-2023-46422,0,0,5182b3b451a6b24665b985bcbdba4481577c22242c366b7f03d7fb205d48ddeb,2023-11-01T16:37:31.890000
|
||||
CVE-2023-46423,0,0,29c6043c53d4300d469e5f00a95575e9de3ac28d2c1d498f1bd8e22aadedbeb1,2023-11-01T16:37:41.027000
|
||||
CVE-2023-46424,0,0,7e9334fca9f037f0c4b2f5d577d386acd135c556e1fc09d9726e45dba7e4d855,2023-11-01T16:37:51.027000
|
||||
CVE-2023-46426,1,1,809d08be8adb70f858fa5903f61478c60bdca3d0c1d9d5ac4a5770d126e124ae,2024-03-09T06:15:50.637000
|
||||
CVE-2023-46427,1,1,6451dde6a5aa40ac65c46af7e6328b7ed5d73e53ee5b507082dfdc8a7408fd2e,2024-03-09T06:15:50.740000
|
||||
CVE-2023-46426,0,0,809d08be8adb70f858fa5903f61478c60bdca3d0c1d9d5ac4a5770d126e124ae,2024-03-09T06:15:50.637000
|
||||
CVE-2023-46427,0,0,6451dde6a5aa40ac65c46af7e6328b7ed5d73e53ee5b507082dfdc8a7408fd2e,2024-03-09T06:15:50.740000
|
||||
CVE-2023-46428,0,0,f03709d76e6aaf56c11ec05b60a8549c04afb1757c3c8e03726933870c46712e,2023-11-06T19:30:17.810000
|
||||
CVE-2023-4643,0,0,aa57b480c65e6583e3382ac73b3539d1486e0e702169fdb4a50c44bd56bfc930,2023-11-07T04:22:48.657000
|
||||
CVE-2023-46435,0,0,7c6638dab75a246acd77e2e49a895792d1a90d49fc12bde2d27e3c27d34e6bab,2023-10-30T16:20:21.103000
|
||||
@ -234188,8 +234188,8 @@ CVE-2023-49337,0,0,5d23a029ed0e63d8031b0089bd22446fabded7af6c71ba8e0cf290627c376
|
||||
CVE-2023-49338,0,0,1c5fcb5c9ab92278082e9a0f7769e43d635d96321323ff96b1c4bc08b7f9e397,2024-02-29T13:49:47.277000
|
||||
CVE-2023-49339,0,0,5e0b0c12f27e752a168c99793f0c0ee1088d5fc0e77c7aa77b0e94e5e50795d6,2024-02-13T14:01:40.577000
|
||||
CVE-2023-4934,0,0,45742cc0d80ec0a49dab27f6d0aa9e7ea22167e8e8cbe0de26584abca13e725c,2023-10-02T16:39:41.720000
|
||||
CVE-2023-49340,1,1,85e4a3843c214023f7009e6223778dacf0ff335a4b0452ec13f990f51cf1422d,2024-03-09T05:15:08.723000
|
||||
CVE-2023-49341,1,1,e5fb9757de7a9cf47b8f4bde1720e43438cd28d081ea6039046589508ac3061c,2024-03-09T05:15:08.870000
|
||||
CVE-2023-49340,0,0,85e4a3843c214023f7009e6223778dacf0ff335a4b0452ec13f990f51cf1422d,2024-03-09T05:15:08.723000
|
||||
CVE-2023-49341,0,0,e5fb9757de7a9cf47b8f4bde1720e43438cd28d081ea6039046589508ac3061c,2024-03-09T05:15:08.870000
|
||||
CVE-2023-49342,0,0,b10ee5f9bcce22db5c28eecc3da84e28b3a02b849278c1bc31042101c32d6f84,2023-12-20T21:02:43.633000
|
||||
CVE-2023-49343,0,0,8d62dff1275f70103265d4cda1e1019bb92665b6186d17ba82011cf4506f3651,2023-12-20T21:05:50.880000
|
||||
CVE-2023-49344,0,0,9755e1ae97c973e34cf38025159d3f7bf41602fe25b2bf94e6b51430f18620bf,2023-12-20T21:06:04.320000
|
||||
@ -234574,7 +234574,7 @@ CVE-2023-50001,0,0,33e47489b66bd60e9877824f089790399b23639f53e49566fa335b7b69124
|
||||
CVE-2023-50002,0,0,ad59b32b385c86725f92348f95075dd05fba97ffb9b3fde14a5d228194c9c7ba,2023-12-09T04:45:15.093000
|
||||
CVE-2023-5001,0,0,120c5181763c7387df7f687f126d9404f11130c2243d24ca423f864190eb3341,2023-11-07T04:23:17.670000
|
||||
CVE-2023-50011,0,0,06fd9011277607c300a2f1116cc8f443fed8d39fba75e4e4358f7ede2b673b13,2023-12-19T13:49:18.530000
|
||||
CVE-2023-50015,1,1,c8877dcfd62c2ac4adde322056aafec1654db5474cda878d2f601c7e18323386,2024-03-09T05:15:08.923000
|
||||
CVE-2023-50015,0,0,c8877dcfd62c2ac4adde322056aafec1654db5474cda878d2f601c7e18323386,2024-03-09T05:15:08.923000
|
||||
CVE-2023-50017,0,0,94a085d3b9a01b673efd08f3fd6d1c5bd5fec950ce7fd1026d076a4011d3d29a,2023-12-19T02:36:27.887000
|
||||
CVE-2023-50019,0,0,a40ef52011e4db27daaf0069b6fee08a9e027c75c96c570f8b4358261c22b37a,2024-01-11T17:28:54.257000
|
||||
CVE-2023-5002,0,0,0991cedcf62364817568a0faf96339db65a0ddfdacb3c1d49e93ee1fba4db72a,2023-11-07T04:23:17.827000
|
||||
@ -238277,6 +238277,9 @@ CVE-2024-1118,0,0,e3fd11a546344333b8c35c35f5363b92eb521f87d371ac843fa5cdbb7cbfe4
|
||||
CVE-2024-1120,0,0,936dd6469f361472c41cbe255905233eb8909005bcef59399cb5fdd735d69c83,2024-03-01T14:04:04.827000
|
||||
CVE-2024-1121,0,0,5242fbff2542109039f2dccd3ecf577228b85d96ab3ffc6d3c7465fcd094d166,2024-02-13T19:42:57.107000
|
||||
CVE-2024-1122,0,0,e3c7c1ad4304e630c1635693614bd197bceba74362044ae36b2d3b19524aad38,2024-02-15T19:17:26.630000
|
||||
CVE-2024-1123,1,1,9c107b33a9c78598b6d4cb189216c41a312253dd82554088b5fbe1fa2959b535,2024-03-09T07:15:07.233000
|
||||
CVE-2024-1124,1,1,7fd45c0257b35bfcb0a9a5ecc477af859ebdfa79e92eb86f8c8346309497e24d,2024-03-09T07:15:08
|
||||
CVE-2024-1125,1,1,f75fef907260e226bd45211b8eae777e3186081c448fde49a6bbc5cb8adea772,2024-03-09T07:15:08.313000
|
||||
CVE-2024-1128,0,0,23e0a7ac2eb24205bc0e57b1035d2ffc364cb8e77360b281fd3875c8acaa6717,2024-02-29T13:49:29.390000
|
||||
CVE-2024-1129,0,0,9e26e4f963c1529e8b107dd7310b33bd78874e7f902263578d3990ceccc8167b,2024-02-29T13:49:29.390000
|
||||
CVE-2024-1130,0,0,66f1630830ed1d095eb852a3f063099a0dc3b2263f9c4f8743191411b15cbd61,2024-02-29T13:49:29.390000
|
||||
@ -238377,6 +238380,7 @@ CVE-2024-1316,0,0,71137ee023059efde9ea6dfce3b572409e6580b9426330a66bdb1f551ebc3e
|
||||
CVE-2024-1317,0,0,677d2e22c876d1f8a2362f14eec614350ca5518b287bd87de6939bf8afc48e88,2024-02-29T13:49:29.390000
|
||||
CVE-2024-1318,0,0,422c230b919b2aed39d902af5834079d78461435b9de398b39e0ef988ed8aaa2,2024-02-29T13:49:29.390000
|
||||
CVE-2024-1319,0,0,4e669b4210ff650707325897da6b55c2caa5cb41a85cef69c41685513463c6d1,2024-03-05T13:41:01.900000
|
||||
CVE-2024-1320,1,1,1ec4c9d7ddd78591eeb95f58f24f0c9de688126a662923fad0897d041207c299,2024-03-09T07:15:08.730000
|
||||
CVE-2024-1322,0,0,55eb557d746bd5b316565e48cf52968ab1ba8b0aa245d5ad47a485b7878e6771,2024-02-29T13:49:29.390000
|
||||
CVE-2024-1323,0,0,f857e29b0540aed96943a25b1179a5166e6aff501672f2c505f52ee84f4e77cb,2024-02-27T14:20:06.637000
|
||||
CVE-2024-1329,0,0,c251ab89131ed5db620ce7b9371daf5508a26377e3f0f0d0996003e3074e8cd1,2024-02-15T18:27:28.837000
|
||||
@ -238556,6 +238560,7 @@ CVE-2024-1758,0,0,6de6dd43b2bb9af7fe1358bc4934bd64904e9488104279e3470618b288cbda
|
||||
CVE-2024-1760,0,0,0a20f47041faa81845898be9ba0faa3a27a19a140e382ff1058d2f999acd0fd1,2024-03-06T15:18:08.093000
|
||||
CVE-2024-1761,0,0,9e36bbb76f5c2b7f4a9f5c6274a1f378aa86f86f618e6f962a515dfe593dc5f7,2024-03-07T13:52:27.110000
|
||||
CVE-2024-1764,0,0,c434e7eb3867d4e9c121215628110f61b78b54be2a078e3d4abbb0d2595e2437,2024-03-06T15:18:08.093000
|
||||
CVE-2024-1767,1,1,af9b58271fe2cff932396ea250a3d29b3f8069abd3d5a9539a5dfec0d691577f,2024-03-09T07:15:09.173000
|
||||
CVE-2024-1769,0,0,4b17a6efe485c004cbf1cc71fd32ae864ff319587ea6998c7a1ad28d6dff65e5,2024-03-05T13:41:01.900000
|
||||
CVE-2024-1771,0,0,cc7280a085dd6f03eb9687c2eff5425926f2bc0e4a81dde799379b7786c7a87e,2024-03-06T15:18:08.093000
|
||||
CVE-2024-1773,0,0,eea85e1a4bb87da89a486d39c94ff7ae4042032c41aee54c0645824074a798c9,2024-03-08T14:02:57.420000
|
||||
@ -239721,6 +239726,7 @@ CVE-2024-23286,0,0,3a3ac4fe44c85fe94cea0225e0a064200cd84c6a8d195e01d14bfa256f0d1
|
||||
CVE-2024-23287,0,0,c58ae62f6494d2a94d4353ea0420ad2d83bdf90a920ca47b31647814cce0d864,2024-03-08T14:02:57.420000
|
||||
CVE-2024-23288,0,0,2220ac70f77367cd88bd84f6b11703e03e7de54d6801f402f025b7c5ef4a9069,2024-03-08T14:02:57.420000
|
||||
CVE-2024-23289,0,0,74d35dbe495c7642f763a5758de5555020e63f0e9c4c7fb71c0a62313b1a48a1,2024-03-08T14:02:57.420000
|
||||
CVE-2024-2329,1,1,9c8e65a4fd5d602fe14cf87a0b1612d024c6a1ed1e9c03669d8d941edd5ca8c1,2024-03-09T08:15:06.217000
|
||||
CVE-2024-23290,0,0,ae16c7bd64254777e8ec093a5acaa858f7d0f54b3f14d450d5952c05173f9f60,2024-03-08T14:02:57.420000
|
||||
CVE-2024-23291,0,0,04df7ee4b5e53fb596d12b117323f7b0b3bbb5f6de58ae6aeeee1ebbd555c499,2024-03-08T14:02:57.420000
|
||||
CVE-2024-23292,0,0,52f99bdd63acae4b605d2ded28155ff671a22b372187b5bb34f67711a2b6ca46,2024-03-08T14:02:57.420000
|
||||
@ -240496,6 +240502,7 @@ CVE-2024-25461,0,0,ff9c7389dbf883803b3d7ff0b96f823d8c83a19a6abab9dd2ebda71c398b5
|
||||
CVE-2024-25466,0,0,c4ed87974de177e036ba4c046a8b808bfb2e5d37116e1f3dbea09f35fe2aed68,2024-02-16T13:37:51.433000
|
||||
CVE-2024-25468,0,0,689cbd3de116ed2f097be6892186e0dd30daa2bde9afea2c256b5d624b13afab,2024-02-20T19:50:53.960000
|
||||
CVE-2024-25469,0,0,96be9bcc7fde8f9b63f103d576b0d22a9c84a3c5935374af13a2466b2f2f5aa2,2024-02-26T13:42:22.567000
|
||||
CVE-2024-25501,1,1,0b5a69cce4f8803c71ec78b9ab7cd2cf9ae54c805ca80db0c8cc815c858b5a95,2024-03-09T08:15:05.973000
|
||||
CVE-2024-25502,0,0,50331b6b298e51ff1fb5155b43730c3887534f74eacaa5eabfebdbefa930be85,2024-02-16T13:38:00.047000
|
||||
CVE-2024-25551,0,0,08dea6730d2a3539d15dd516547ab3c25a1bf59710632ae63632a88cbff77b71,2024-03-04T13:58:23.447000
|
||||
CVE-2024-25552,0,0,d883aeb50248972b9f86293464fb83b3894fa14aa0a35cda83456c82f7157e6f,2024-03-01T14:04:26.010000
|
||||
@ -240627,7 +240634,7 @@ CVE-2024-25931,0,0,cced732a62b8661206eb106d5ae979a2d16189f2911f7eaa9ca025496e8df
|
||||
CVE-2024-25932,0,0,b47ba5ecf2a19427a2d0c7404d84cf9b82c7d738bc913534568255e83139261d,2024-02-29T13:49:29.390000
|
||||
CVE-2024-25940,0,0,81faf8084be28ad3443bfad1349de788b40c215e318cb61e901b3079aac1c24e,2024-02-15T06:23:39.303000
|
||||
CVE-2024-25941,0,0,ca1cef65d30f17057b47421c2700ecf50e418e7bf4da35eb3fcc2989f17ef1eb,2024-02-15T06:23:39.303000
|
||||
CVE-2024-25951,1,1,ba7288e646a44ba31be2201d63c1232de8f0f6558f3bec2aba577040e985f05b,2024-03-09T06:15:50.797000
|
||||
CVE-2024-25951,0,0,ba7288e646a44ba31be2201d63c1232de8f0f6558f3bec2aba577040e985f05b,2024-03-09T06:15:50.797000
|
||||
CVE-2024-25972,0,0,03be68c424c2117dfe63b169d17d7f8ada85eec42d35f349ee6876cb9f658b31,2024-03-01T14:04:04.827000
|
||||
CVE-2024-25973,0,0,fca2cd3fc869e318a8dbf83dd06094ef0c34286b7d421da7c64a9a5612af38b9,2024-02-21T07:15:58.040000
|
||||
CVE-2024-25974,0,0,455908519f9c0b510f9276a34d5bc0fdc3808298a4e41e75f9e5535d39103827,2024-02-21T07:15:58.427000
|
||||
@ -240709,7 +240716,7 @@ CVE-2024-26350,0,0,1f62ec8cd425e84b1282a5e55493461489796820c50a425af585677fa2bae
|
||||
CVE-2024-26351,0,0,61b98d66760f09ba8a0757ca890b9ad836349a62d566c880c0eb8336d14dbb04,2024-02-22T19:07:27.197000
|
||||
CVE-2024-26352,0,0,ed876b320273da7c752d57a08640f2d98ce80b026324bdf46d0712ec0097ce54,2024-02-22T19:07:27.197000
|
||||
CVE-2024-26445,0,0,3735cabd04dab3a1baa3e135ef467df65425520025be25bd7cf66dc1b1b0bf61,2024-02-22T19:07:27.197000
|
||||
CVE-2024-26450,0,0,03bc9552fd396bb6f3ab5770b59785aeda4325d21b19ca1c5302e8ae15596e22,2024-02-29T13:49:47.277000
|
||||
CVE-2024-26450,0,1,e70e1c7044e1447bb73bfa4a556135e1953f1916a7225089ba5c38735bf8ee34,2024-03-09T08:15:06.120000
|
||||
CVE-2024-26455,0,0,b8d798122eed5fa7dc5e81852b3374f7f4b40339c21e80b998d09e1a756fc71d,2024-02-26T22:10:40.463000
|
||||
CVE-2024-26458,0,0,4b2bac12846011765db5a8d92c99fed71bd0c8fd706ee4d4f4c7e419547c7ad4,2024-02-29T13:49:29.390000
|
||||
CVE-2024-26461,0,0,904046a1bdb8d57e836285398ec79f3a5f035120c749bfa545aeddc73ebaca7d,2024-02-29T13:49:29.390000
|
||||
@ -240885,6 +240892,7 @@ CVE-2024-27949,0,0,12ee9b935394b527d1677a59b517c94d0df067a0b32bfff31d7cb2be5b4b5
|
||||
CVE-2024-27950,0,0,56d632dad56c45d949d3327de16e5b70b08683cea8ce7876ca8c59cc37ee8062,2024-03-01T14:04:04.827000
|
||||
CVE-2024-28084,0,0,2ea238298cc724e9290d5587502d4eedb8db15dd1861547724435b977511956c,2024-03-04T13:58:23.447000
|
||||
CVE-2024-28088,0,0,9a10dd503198550e89a078bdf745e1ea7de71394ab5735ab0f1469895e72b20d,2024-03-04T13:58:23.447000
|
||||
CVE-2024-28089,1,1,86c02185c28f01854145b18859cb689806d221e7f2a4a66edfd83a90b723ef69,2024-03-09T07:15:09.577000
|
||||
CVE-2024-28094,0,0,45821c38270b8552e50f50b73436d99164a20d22d9b4b8876276d92b2a0a88d9,2024-03-07T13:52:27.110000
|
||||
CVE-2024-28095,0,0,cc359d20cf58cf4c4e6a4bc345ac1d1135a557dfb7920f405bfe639456bcfe46,2024-03-07T13:52:27.110000
|
||||
CVE-2024-28096,0,0,bd233bb77c2105c8f9ae41f3196895f407f421cf037a91cc0eb753e3f00e4372,2024-03-07T13:52:27.110000
|
||||
|
Can't render this file because it is too large.
|
Loading…
x
Reference in New Issue
Block a user