mirror of
https://github.com/fkie-cad/nvd-json-data-feeds.git
synced 2025-05-06 18:52:58 +00:00
Auto-Update: 2025-04-15T02:00:19.477991+00:00
This commit is contained in:
cad-safe-bot
parent
385c59bda3
commit
1709bb638d
60
CVE-2025/CVE-2025-247xx/CVE-2025-24797.json
Normal file
60
CVE-2025/CVE-2025-247xx/CVE-2025-24797.json
Normal file
@ -0,0 +1,60 @@
|
||||
{
|
||||
"id": "CVE-2025-24797",
|
||||
"sourceIdentifier": "security-advisories@github.com",
|
||||
"published": "2025-04-15T00:15:14.353",
|
||||
"lastModified": "2025-04-15T00:15:14.353",
|
||||
"vulnStatus": "Received",
|
||||
"cveTags": [],
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "Meshtastic is an open source mesh networking solution. A fault in the handling of mesh packets containing invalid protobuf data can result in an attacker-controlled buffer overflow, allowing an attacker to hijack execution flow, potentially resulting in remote code execution. This attack does not require authentication or user interaction, as long as the target device rebroadcasts packets on the default channel. This vulnerability fixed in 2.6.2."
|
||||
}
|
||||
],
|
||||
"metrics": {
|
||||
"cvssMetricV31": [
|
||||
{
|
||||
"source": "security-advisories@github.com",
|
||||
"type": "Secondary",
|
||||
"cvssData": {
|
||||
"version": "3.1",
|
||||
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:H",
|
||||
"baseScore": 9.4,
|
||||
"baseSeverity": "CRITICAL",
|
||||
"attackVector": "NETWORK",
|
||||
"attackComplexity": "LOW",
|
||||
"privilegesRequired": "NONE",
|
||||
"userInteraction": "NONE",
|
||||
"scope": "UNCHANGED",
|
||||
"confidentialityImpact": "HIGH",
|
||||
"integrityImpact": "LOW",
|
||||
"availabilityImpact": "HIGH"
|
||||
},
|
||||
"exploitabilityScore": 3.9,
|
||||
"impactScore": 5.5
|
||||
}
|
||||
]
|
||||
},
|
||||
"weaknesses": [
|
||||
{
|
||||
"source": "security-advisories@github.com",
|
||||
"type": "Primary",
|
||||
"description": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "CWE-119"
|
||||
},
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "CWE-122"
|
||||
}
|
||||
]
|
||||
}
|
||||
],
|
||||
"references": [
|
||||
{
|
||||
"url": "https://github.com/meshtastic/firmware/security/advisories/GHSA-33hw-xhfh-944r",
|
||||
"source": "security-advisories@github.com"
|
||||
}
|
||||
]
|
||||
}
|
||||
@ -2,13 +2,13 @@
|
||||
"id": "CVE-2025-31490",
|
||||
"sourceIdentifier": "security-advisories@github.com",
|
||||
"published": "2025-04-14T23:15:21.713",
|
||||
"lastModified": "2025-04-14T23:15:21.713",
|
||||
"lastModified": "2025-04-15T00:15:14.507",
|
||||
"vulnStatus": "Received",
|
||||
"cveTags": [],
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "AutoGPT is a platform that allows users to create, deploy, and manage continuous artificial intelligence agents that automate complex workflows. Prior to 0.6.1, AutoGPT allows SSRF due to DNS Rebinding in requests wrapper. AutoGPT uses a wrapper around the requests python library, located in autogpt_platform/backend/backend/util/request.py. In this wrapper, redirects are specifically NOT followed for the first request. If the wrapper is used with allow_redirects set to True (which is the default), any redirect is not followed by the initial request, but rather re-requested by the wrapper using the new location. However, there is a fundamental flaw in manually re-requesting the new location: it does not account for security-sensitive headers which should not be sent cross-origin, such as the Authorization and Proxy-Authorization header, and cookies. For example in autogpt_platform/backend/backend/blocks/github/_api.py, an Authorization header is set when retrieving data from the GitHub API. However, if GitHub suffers from an open redirect vulnerability (such as the made-up example of https://api.github.com/repos/{owner}/{repo}/issues/comments/{comment_id}/../../../../../redirect/?url=https://joshua.hu/), and the script can be coerced into visiting it with the Authorization header, the GitHub credentials in the Authorization header will be leaked. All SSRF protections are bypassable; it could allow querying local services, or other previously blocked addresses. Depends on the situation. This vulnerability is fixed in 0.6.1."
|
||||
"value": "AutoGPT is a platform that allows users to create, deploy, and manage continuous artificial intelligence agents that automate complex workflows. Prior to 0.6.1, AutoGPT allows SSRF due to DNS Rebinding in requests wrapper. AutoGPT is built with a wrapper around Python's requests library, hardening the application against SSRF. The code for this wrapper can be found in autogpt_platform/backend/backend/util/request.py. The requested hostname of a URL which is being requested is validated, ensuring that it does not resolve to any local ipv4 or ipv6 addresses. However, this check is not sufficient, as a DNS server may initially respond with a non-blocked address, with a TTL of 0. This means that the initial resolution would appear as a non-blocked address. In this case, validate_url() will return the url as successful. After validate_url() has successfully returned the url, the url is then passed to the real request() function. When the real request() function is called with the validated url, request() will once again resolve the address of the hostname, because the record will not have been cached (due to TTL 0). This resolution may be in the \"invalid range\". This type of attack is called a \"DNS Rebinding Attack\". This vulnerability is fixed in 0.6.1."
|
||||
}
|
||||
],
|
||||
"metrics": {
|
||||
@ -38,7 +38,7 @@
|
||||
"weaknesses": [
|
||||
{
|
||||
"source": "security-advisories@github.com",
|
||||
"type": "Primary",
|
||||
"type": "Secondary",
|
||||
"description": [
|
||||
{
|
||||
"lang": "en",
|
||||
|
||||
56
CVE-2025/CVE-2025-314xx/CVE-2025-31491.json
Normal file
56
CVE-2025/CVE-2025-314xx/CVE-2025-31491.json
Normal file
@ -0,0 +1,56 @@
|
||||
{
|
||||
"id": "CVE-2025-31491",
|
||||
"sourceIdentifier": "security-advisories@github.com",
|
||||
"published": "2025-04-15T00:15:14.607",
|
||||
"lastModified": "2025-04-15T00:15:14.607",
|
||||
"vulnStatus": "Received",
|
||||
"cveTags": [],
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "AutoGPT is a platform that allows users to create, deploy, and manage continuous artificial intelligence agents that automate complex workflows. Prior to 0.6.1, AutoGPT allows of leakage of cross-domain cookies and protected headers in requests redirect. AutoGPT uses a wrapper around the requests python library, located in autogpt_platform/backend/backend/util/request.py. In this wrapper, redirects are specifically NOT followed for the first request. If the wrapper is used with allow_redirects set to True (which is the default), any redirect is not followed by the initial request, but rather re-requested by the wrapper using the new location. However, there is a fundamental flaw in manually re-requesting the new location: it does not account for security-sensitive headers which should not be sent cross-origin, such as the Authorization and Proxy-Authorization header, and cookies. For example in autogpt_platform/backend/backend/blocks/github/_api.py, an Authorization header is set when retrieving data from the GitHub API. However, if GitHub suffers from an open redirect vulnerability (such as the made-up example of https://api.github.com/repos/{owner}/{repo}/issues/comments/{comment_id}/../../../../../redirect/?url=https://joshua.hu/), and the script can be coerced into visiting it with the Authorization header, the GitHub credentials in the Authorization header will be leaked. This allows leaking auth headers and private cookies. This vulnerability is fixed in 0.6.1."
|
||||
}
|
||||
],
|
||||
"metrics": {
|
||||
"cvssMetricV31": [
|
||||
{
|
||||
"source": "security-advisories@github.com",
|
||||
"type": "Secondary",
|
||||
"cvssData": {
|
||||
"version": "3.1",
|
||||
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N",
|
||||
"baseScore": 8.6,
|
||||
"baseSeverity": "HIGH",
|
||||
"attackVector": "NETWORK",
|
||||
"attackComplexity": "LOW",
|
||||
"privilegesRequired": "NONE",
|
||||
"userInteraction": "NONE",
|
||||
"scope": "CHANGED",
|
||||
"confidentialityImpact": "HIGH",
|
||||
"integrityImpact": "NONE",
|
||||
"availabilityImpact": "NONE"
|
||||
},
|
||||
"exploitabilityScore": 3.9,
|
||||
"impactScore": 4.0
|
||||
}
|
||||
]
|
||||
},
|
||||
"weaknesses": [
|
||||
{
|
||||
"source": "security-advisories@github.com",
|
||||
"type": "Primary",
|
||||
"description": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "CWE-200"
|
||||
}
|
||||
]
|
||||
}
|
||||
],
|
||||
"references": [
|
||||
{
|
||||
"url": "https://github.com/Significant-Gravitas/AutoGPT/security/advisories/GHSA-ggcm-93qg-gfhp",
|
||||
"source": "security-advisories@github.com"
|
||||
}
|
||||
]
|
||||
}
|
||||
68
CVE-2025/CVE-2025-314xx/CVE-2025-31494.json
Normal file
68
CVE-2025/CVE-2025-314xx/CVE-2025-31494.json
Normal file
@ -0,0 +1,68 @@
|
||||
{
|
||||
"id": "CVE-2025-31494",
|
||||
"sourceIdentifier": "security-advisories@github.com",
|
||||
"published": "2025-04-15T00:15:14.740",
|
||||
"lastModified": "2025-04-15T00:15:14.740",
|
||||
"vulnStatus": "Received",
|
||||
"cveTags": [],
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "AutoGPT is a platform that allows users to create, deploy, and manage continuous artificial intelligence agents that automate complex workflows. The AutoGPT Platform's WebSocket API transmitted node execution updates to subscribers based on the graph_id+graph_version. Additionally, there was no check prohibiting users from subscribing with another user's graph_id+graph_version. As a result, node execution updates from one user's graph execution could be received by another user within the same instance. This vulnerability does not occur between different instances or between users and non-users of the platform. Single-user instances are not affected. In private instances with a user white-list, the impact is limited by the fact that all potential unintended recipients of these node execution updates must have been admitted by the administrator. This vulnerability is fixed in 0.6.1."
|
||||
}
|
||||
],
|
||||
"metrics": {
|
||||
"cvssMetricV31": [
|
||||
{
|
||||
"source": "security-advisories@github.com",
|
||||
"type": "Secondary",
|
||||
"cvssData": {
|
||||
"version": "3.1",
|
||||
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N",
|
||||
"baseScore": 3.5,
|
||||
"baseSeverity": "LOW",
|
||||
"attackVector": "NETWORK",
|
||||
"attackComplexity": "LOW",
|
||||
"privilegesRequired": "LOW",
|
||||
"userInteraction": "REQUIRED",
|
||||
"scope": "UNCHANGED",
|
||||
"confidentialityImpact": "LOW",
|
||||
"integrityImpact": "NONE",
|
||||
"availabilityImpact": "NONE"
|
||||
},
|
||||
"exploitabilityScore": 2.1,
|
||||
"impactScore": 1.4
|
||||
}
|
||||
]
|
||||
},
|
||||
"weaknesses": [
|
||||
{
|
||||
"source": "security-advisories@github.com",
|
||||
"type": "Primary",
|
||||
"description": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "CWE-200"
|
||||
},
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "CWE-284"
|
||||
}
|
||||
]
|
||||
}
|
||||
],
|
||||
"references": [
|
||||
{
|
||||
"url": "https://github.com/Significant-Gravitas/AutoGPT/pull/9660",
|
||||
"source": "security-advisories@github.com"
|
||||
},
|
||||
{
|
||||
"url": "https://github.com/Significant-Gravitas/AutoGPT/releases/tag/autogpt-platform-beta-v0.6.1",
|
||||
"source": "security-advisories@github.com"
|
||||
},
|
||||
{
|
||||
"url": "https://github.com/Significant-Gravitas/AutoGPT/security/advisories/GHSA-958f-37vw-jx8f",
|
||||
"source": "security-advisories@github.com"
|
||||
}
|
||||
]
|
||||
}
|
||||
82
CVE-2025/CVE-2025-324xx/CVE-2025-32428.json
Normal file
82
CVE-2025/CVE-2025-324xx/CVE-2025-32428.json
Normal file
@ -0,0 +1,82 @@
|
||||
{
|
||||
"id": "CVE-2025-32428",
|
||||
"sourceIdentifier": "security-advisories@github.com",
|
||||
"published": "2025-04-15T00:15:14.880",
|
||||
"lastModified": "2025-04-15T00:15:14.880",
|
||||
"vulnStatus": "Received",
|
||||
"cveTags": [],
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "Jupyter Remote Desktop Proxy allows you to run a Linux Desktop on a JupyterHub. jupyter-remote-desktop-proxy was meant to rely on UNIX sockets readable only by the current user since version 3.0.0, but when used with TigerVNC, the VNC server started by jupyter-remote-desktop-proxy were still accessible via the network. This vulnerability does not affect users having TurboVNC as the vncserver executable. This issue is fixed in 3.0.1."
|
||||
}
|
||||
],
|
||||
"metrics": {
|
||||
"cvssMetricV40": [
|
||||
{
|
||||
"source": "security-advisories@github.com",
|
||||
"type": "Secondary",
|
||||
"cvssData": {
|
||||
"version": "4.0",
|
||||
"vectorString": "CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
|
||||
"baseScore": 9.0,
|
||||
"baseSeverity": "CRITICAL",
|
||||
"attackVector": "ADJACENT",
|
||||
"attackComplexity": "LOW",
|
||||
"attackRequirements": "PRESENT",
|
||||
"privilegesRequired": "NONE",
|
||||
"userInteraction": "NONE",
|
||||
"vulnConfidentialityImpact": "HIGH",
|
||||
"vulnIntegrityImpact": "HIGH",
|
||||
"vulnAvailabilityImpact": "HIGH",
|
||||
"subConfidentialityImpact": "HIGH",
|
||||
"subIntegrityImpact": "HIGH",
|
||||
"subAvailabilityImpact": "HIGH",
|
||||
"exploitMaturity": "NOT_DEFINED",
|
||||
"confidentialityRequirement": "NOT_DEFINED",
|
||||
"integrityRequirement": "NOT_DEFINED",
|
||||
"availabilityRequirement": "NOT_DEFINED",
|
||||
"modifiedAttackVector": "NOT_DEFINED",
|
||||
"modifiedAttackComplexity": "NOT_DEFINED",
|
||||
"modifiedAttackRequirements": "NOT_DEFINED",
|
||||
"modifiedPrivilegesRequired": "NOT_DEFINED",
|
||||
"modifiedUserInteraction": "NOT_DEFINED",
|
||||
"modifiedVulnConfidentialityImpact": "NOT_DEFINED",
|
||||
"modifiedVulnIntegrityImpact": "NOT_DEFINED",
|
||||
"modifiedVulnAvailabilityImpact": "NOT_DEFINED",
|
||||
"modifiedSubConfidentialityImpact": "NOT_DEFINED",
|
||||
"modifiedSubIntegrityImpact": "NOT_DEFINED",
|
||||
"modifiedSubAvailabilityImpact": "NOT_DEFINED",
|
||||
"Safety": "NOT_DEFINED",
|
||||
"Automatable": "NOT_DEFINED",
|
||||
"Recovery": "NOT_DEFINED",
|
||||
"valueDensity": "NOT_DEFINED",
|
||||
"vulnerabilityResponseEffort": "NOT_DEFINED",
|
||||
"providerUrgency": "NOT_DEFINED"
|
||||
}
|
||||
}
|
||||
]
|
||||
},
|
||||
"weaknesses": [
|
||||
{
|
||||
"source": "security-advisories@github.com",
|
||||
"type": "Primary",
|
||||
"description": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "CWE-668"
|
||||
}
|
||||
]
|
||||
}
|
||||
],
|
||||
"references": [
|
||||
{
|
||||
"url": "https://github.com/jupyterhub/jupyter-remote-desktop-proxy/commit/7dd54c25a4253badd8ea68895437e5a66a59090d",
|
||||
"source": "security-advisories@github.com"
|
||||
},
|
||||
{
|
||||
"url": "https://github.com/jupyterhub/jupyter-remote-desktop-proxy/security/advisories/GHSA-vrq4-9hc3-cgp7",
|
||||
"source": "security-advisories@github.com"
|
||||
}
|
||||
]
|
||||
}
|
||||
24
README.md
24
README.md
@ -13,13 +13,13 @@ Repository synchronizes with the NVD every 2 hours.
|
||||
### Last Repository Update
|
||||
|
||||
```plain
|
||||
2025-04-14T23:55:19.331356+00:00
|
||||
2025-04-15T02:00:19.477991+00:00
|
||||
```
|
||||
|
||||
### Most recent CVE Modification Timestamp synchronized with NVD
|
||||
|
||||
```plain
|
||||
2025-04-14T23:15:22.270000+00:00
|
||||
2025-04-15T00:15:14.880000+00:00
|
||||
```
|
||||
|
||||
### Last Data Feed Release
|
||||
@ -27,32 +27,30 @@ Repository synchronizes with the NVD every 2 hours.
|
||||
Download and Changelog: [Click](https://github.com/fkie-cad/nvd-json-data-feeds/releases/latest)
|
||||
|
||||
```plain
|
||||
2025-04-14T00:00:10.087584+00:00
|
||||
2025-04-15T00:00:04.351148+00:00
|
||||
```
|
||||
|
||||
### Total Number of included CVEs
|
||||
|
||||
```plain
|
||||
289819
|
||||
289823
|
||||
```
|
||||
|
||||
### CVEs added in the last Commit
|
||||
|
||||
Recently added CVEs: `5`
|
||||
Recently added CVEs: `4`
|
||||
|
||||
- [CVE-2025-31490](CVE-2025/CVE-2025-314xx/CVE-2025-31490.json) (`2025-04-14T23:15:21.713`)
|
||||
- [CVE-2025-3590](CVE-2025/CVE-2025-35xx/CVE-2025-3590.json) (`2025-04-14T22:15:16.650`)
|
||||
- [CVE-2025-3591](CVE-2025/CVE-2025-35xx/CVE-2025-3591.json) (`2025-04-14T22:15:16.827`)
|
||||
- [CVE-2025-3592](CVE-2025/CVE-2025-35xx/CVE-2025-3592.json) (`2025-04-14T22:15:17.000`)
|
||||
- [CVE-2025-3593](CVE-2025/CVE-2025-35xx/CVE-2025-3593.json) (`2025-04-14T23:15:22.270`)
|
||||
- [CVE-2025-24797](CVE-2025/CVE-2025-247xx/CVE-2025-24797.json) (`2025-04-15T00:15:14.353`)
|
||||
- [CVE-2025-31491](CVE-2025/CVE-2025-314xx/CVE-2025-31491.json) (`2025-04-15T00:15:14.607`)
|
||||
- [CVE-2025-31494](CVE-2025/CVE-2025-314xx/CVE-2025-31494.json) (`2025-04-15T00:15:14.740`)
|
||||
- [CVE-2025-32428](CVE-2025/CVE-2025-324xx/CVE-2025-32428.json) (`2025-04-15T00:15:14.880`)
|
||||
|
||||
|
||||
### CVEs modified in the last Commit
|
||||
|
||||
Recently modified CVEs: `2`
|
||||
Recently modified CVEs: `1`
|
||||
|
||||
- [CVE-2010-5305](CVE-2010/CVE-2010-53xx/CVE-2010-5305.json) (`2025-04-14T22:15:15.097`)
|
||||
- [CVE-2025-3589](CVE-2025/CVE-2025-35xx/CVE-2025-3589.json) (`2025-04-14T22:15:16.523`)
|
||||
- [CVE-2025-31490](CVE-2025/CVE-2025-314xx/CVE-2025-31490.json) (`2025-04-15T00:15:14.507`)
|
||||
|
||||
|
||||
## Download and Usage
|
||||
|
||||
18
_state.csv
18
_state.csv
@ -46917,7 +46917,7 @@ CVE-2010-5301,0,0,583f9fd1855b9ace664450510c74afa0308b2c32502d708f3d3f65ee639063
|
||||
CVE-2010-5302,0,0,b62265de4c92e92a54d7af21e552ac20d2c2227e399750b58f8eff05f4537bed,2025-04-12T10:46:40.837000
|
||||
CVE-2010-5303,0,0,919bf68db8b6d2c5950419ce6e7250d2013f50cfb20cc8a56a52d0fd01c71453,2025-04-12T10:46:40.837000
|
||||
CVE-2010-5304,0,0,48036b1f373720fee56e102c186ef2e310b690ba81271d62a16d97190ca830d7,2024-11-21T01:22:59.840000
|
||||
CVE-2010-5305,0,1,085485fc6a88b06e190d257793ca8788456f836c5ff6f108a4a47ab93628111e,2025-04-14T22:15:15.097000
|
||||
CVE-2010-5305,0,0,085485fc6a88b06e190d257793ca8788456f836c5ff6f108a4a47ab93628111e,2025-04-14T22:15:15.097000
|
||||
CVE-2010-5306,0,0,9f3ea0a94065bb5498fad05090ddf3c76e0c9df583a4b7bc215d0969343ab9d1,2025-04-12T10:46:40.837000
|
||||
CVE-2010-5307,0,0,bc576dd47d7c761bc7f31868f952c0a795c38e45f0b3ab832ee30e5beaaf3737,2025-04-12T10:46:40.837000
|
||||
CVE-2010-5308,0,0,6ef7cedc49106e184c9711ac6468d3345c3d283034bdc91feba0c63406f7004c,2025-04-12T10:46:40.837000
|
||||
@ -285812,6 +285812,7 @@ CVE-2025-24793,0,0,e28f23f8765521f3c09231efc18389c18020ab59aed59a8a8b47cb836c195
|
||||
CVE-2025-24794,0,0,c04b940ac82a2657417f797fe796501aa31f53e5a08053b008970823006b7cde,2025-01-29T21:15:21.397000
|
||||
CVE-2025-24795,0,0,4e7d355e1e973178e45904614970e5915bed2547d76d074d93927fc694a1b13e,2025-01-29T21:15:21.533000
|
||||
CVE-2025-24796,0,0,a9610c1be84a5c4d5741f879bb27b31db5774f479b1300b84fcf068018c2ff21,2025-03-06T19:15:26.953000
|
||||
CVE-2025-24797,1,1,6d531857e815ac53b52af9e915a94ef35ddd350720e98f673a44bd90c7039695,2025-04-15T00:15:14.353000
|
||||
CVE-2025-24799,0,0,b91362920a1bdf5922f70455160d5f7b874b44c2ef0aa4aa4a1b91e413396201,2025-03-18T19:15:48.927000
|
||||
CVE-2025-2480,0,0,8c114ab82f1a69ecb2cba58c867ae8116e5c5738533441fe65cb3b622f3d42be,2025-03-20T17:15:38.523000
|
||||
CVE-2025-24800,0,0,7ed7267931cd5ab7815e3084be7a388ce38e4d4a267ef28098f1d5b3017953e4,2025-01-28T16:15:45.063000
|
||||
@ -288792,8 +288793,10 @@ CVE-2025-31487,0,0,b82f95e4ce12b67bc4c5d4168a317e50698188e3e02053101fd5378a82a78
|
||||
CVE-2025-31488,0,0,41eabe2a806d521b5b533a51fb5b17aa17d50bd34ad511fec1512904c0a777c0,2025-04-07T14:17:50.220000
|
||||
CVE-2025-31489,0,0,86b687749f556cb33a8356498a01d508d0da05ad595a76560944268496b2bd46,2025-04-07T14:18:34.453000
|
||||
CVE-2025-3149,0,0,61479a4dbdbba6ab59d1ae99d855a79e55a52858fd9b2654fa6a6f9d8eddf660,2025-04-07T14:18:34.453000
|
||||
CVE-2025-31490,1,1,917ff630af83ea47c41d16e718bd314636a74f1547232a664fbb09ccb5995a37,2025-04-14T23:15:21.713000
|
||||
CVE-2025-31490,0,1,0cafa0ab8d8d0d42959a84d336317e1b550f51ce341b5aa05e9a2cc21e9e3151,2025-04-15T00:15:14.507000
|
||||
CVE-2025-31491,1,1,562840cf6e00e5762031c3cedbde8359aa5f406b185c37abd2f48c09cb32da52,2025-04-15T00:15:14.607000
|
||||
CVE-2025-31492,0,0,c3a8af2b78a6ecf7a731e5159a73f99e4e0787364701aa4aef00fbbfc177b209,2025-04-07T14:17:50.220000
|
||||
CVE-2025-31494,1,1,207a685d5409362a0a46c45eefe6a25f9dce0b96179f64016c46f799a6629111,2025-04-15T00:15:14.740000
|
||||
CVE-2025-31496,0,0,12f17064ea4e4584d7a91216d2d100c9a89220efe7b8206230e9a4ff7e506dee,2025-04-08T18:13:53.347000
|
||||
CVE-2025-31498,0,0,f84cf018b9a7f2d3baed2463f19bf6204e206ba0c9a21e4ea32e21746b404d29,2025-04-08T18:13:53.347000
|
||||
CVE-2025-3150,0,0,a30a7688ae10248ab6f92b08d529b33559f00224524ffa44e9f5b1d925f39cc6,2025-04-07T14:18:34.453000
|
||||
@ -289445,6 +289448,7 @@ CVE-2025-32414,0,0,2fcec998435005e0d1d3c8610833b216e4c5fa674ee9df013c153e6a84f33
|
||||
CVE-2025-3242,0,0,7a3796558c3172b29f1754f0aa43f7d570abcefa6f88716250c661d5fd24e293,2025-04-07T14:18:15.560000
|
||||
CVE-2025-32426,0,0,97f7719ef42c67257e2006b52ab9747f51788ff83c926fc892139743aec5a5b7,2025-04-11T15:39:52.920000
|
||||
CVE-2025-32427,0,0,0416426b54022f69535fafb066a105f3453a61c3cc047d8982deab84a0710a9d,2025-04-11T15:39:52.920000
|
||||
CVE-2025-32428,1,1,551be7594efb01a7025b1cf12cc4254f5b15addb9a78b7a8bfc72869a34d2ddd,2025-04-15T00:15:14.880000
|
||||
CVE-2025-3243,0,0,b05341f12b748941f8ca2dc4c2b8a53c07658570f17c96676f3c5904a6066c66,2025-04-07T14:18:15.560000
|
||||
CVE-2025-3244,0,0,a20bb1d848a28a44d0b8d510e43cbe068220041e655dcf96cf8633b9bc977caf,2025-04-07T14:18:15.560000
|
||||
CVE-2025-3245,0,0,396ea3bbe154112d349f915c8c28a6610578699cecf486191d9d012a69d9c5b9,2025-04-07T14:18:15.560000
|
||||
@ -289813,8 +289817,8 @@ CVE-2025-3572,0,0,ce93ec390a9611703e154796a1c8b29e4cb3ba90d0f017a2ea9b391560345b
|
||||
CVE-2025-3585,0,0,3f56099df0d5cbe2a28c49e0084d09a46fec0a860dece5bd91eb4466f785fbfe,2025-04-14T19:15:36.990000
|
||||
CVE-2025-3587,0,0,0b5d7c64b9281d67b2da75b50cd511d58c4d6400c863ce33e2f51939e792bcae,2025-04-14T21:15:18.220000
|
||||
CVE-2025-3588,0,0,325725e21d51ea302750035b03dc4eb21568d3831b2e5a943f3da0a80eb56df1,2025-04-14T21:15:18.343000
|
||||
CVE-2025-3589,0,1,a592537be3fbeac11d3200f5fcb1c68d9cfb7d33ce5e2420cabe44a4017bad83,2025-04-14T22:15:16.523000
|
||||
CVE-2025-3590,1,1,aa07cf51d9a0d561b10043bb7261822f0af57d8d6d4fee0ad683485554a00b63,2025-04-14T22:15:16.650000
|
||||
CVE-2025-3591,1,1,86fad0a948ecf8f921345a86491b837545045bf239c666008f3a1038a8e13f8f,2025-04-14T22:15:16.827000
|
||||
CVE-2025-3592,1,1,1454212ef6249f5a5ec56ab9bb8016685ead208040c766cd4c83cd18b7c61f0e,2025-04-14T22:15:17
|
||||
CVE-2025-3593,1,1,1a81b98ecfba1979c3a4ccc38ff5bb341262b9aec183ca57e86bed8f737e2cd2,2025-04-14T23:15:22.270000
|
||||
CVE-2025-3589,0,0,a592537be3fbeac11d3200f5fcb1c68d9cfb7d33ce5e2420cabe44a4017bad83,2025-04-14T22:15:16.523000
|
||||
CVE-2025-3590,0,0,aa07cf51d9a0d561b10043bb7261822f0af57d8d6d4fee0ad683485554a00b63,2025-04-14T22:15:16.650000
|
||||
CVE-2025-3591,0,0,86fad0a948ecf8f921345a86491b837545045bf239c666008f3a1038a8e13f8f,2025-04-14T22:15:16.827000
|
||||
CVE-2025-3592,0,0,1454212ef6249f5a5ec56ab9bb8016685ead208040c766cd4c83cd18b7c61f0e,2025-04-14T22:15:17
|
||||
CVE-2025-3593,0,0,1a81b98ecfba1979c3a4ccc38ff5bb341262b9aec183ca57e86bed8f737e2cd2,2025-04-14T23:15:22.270000
|
||||
|
||||
|
Can't render this file because it is too large.
|
Loading…
x
Reference in New Issue
Block a user