Advisory Database Sync

This commit is contained in:
advisory-database[bot]
2025-01-09 18:33:42 +00:00
parent f0cfeb758b
commit 75e6818bef
111 changed files with 2298 additions and 86 deletions
@@ -38,7 +38,8 @@
],
"database_specific": {
"cwe_ids": [
"CWE-704"
"CWE-704",
"CWE-843"
],
"severity": "HIGH",
"github_reviewed": false,
@@ -29,7 +29,9 @@
}
],
"database_specific": {
"cwe_ids": [],
"cwe_ids": [
"CWE-1021"
],
"severity": "MODERATE",
"github_reviewed": false,
"github_reviewed_at": null,
@@ -29,7 +29,9 @@
}
],
"database_specific": {
"cwe_ids": [],
"cwe_ids": [
"CWE-425"
],
"severity": "MODERATE",
"github_reviewed": false,
"github_reviewed_at": null,
@@ -37,7 +37,9 @@
}
],
"database_specific": {
"cwe_ids": [],
"cwe_ids": [
"CWE-22"
],
"severity": "MODERATE",
"github_reviewed": false,
"github_reviewed_at": null,
@@ -1,13 +1,18 @@
{
"schema_version": "1.4.0",
"id": "GHSA-ffm2-8jrv-hhxj",
"modified": "2024-02-28T09:30:38Z",
"modified": "2025-01-09T18:32:06Z",
"published": "2024-02-28T09:30:38Z",
"aliases": [
"CVE-2021-47039"
],
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nataflop: potential out of bounds in do_format()\n\nThe function uses \"type\" as an array index:\n\n\tq = unit[drive].disk[type]->queue;\n\nUnfortunately the bounds check on \"type\" isn't done until later in the\nfunction. Fix this by moving the bounds check to the start.",
"severity": [],
"severity": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H"
}
],
"affected": [],
"references": [
{
@@ -28,8 +33,10 @@
}
],
"database_specific": {
"cwe_ids": [],
"severity": null,
"cwe_ids": [
"CWE-125"
],
"severity": "HIGH",
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-02-28T09:15:39Z"
@@ -26,6 +26,7 @@
],
"database_specific": {
"cwe_ids": [
"CWE-59",
"CWE-61"
],
"severity": "MODERATE",
File diff suppressed because one or more lines are too long
@@ -26,6 +26,7 @@
],
"database_specific": {
"cwe_ids": [
"CWE-59",
"CWE-61"
],
"severity": "MODERATE",
@@ -1,13 +1,18 @@
{
"schema_version": "1.4.0",
"id": "GHSA-x2mc-jwgp-h2fq",
"modified": "2024-03-01T00:30:28Z",
"modified": "2025-01-09T18:32:06Z",
"published": "2024-03-01T00:30:28Z",
"aliases": [
"CVE-2021-47055"
],
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nmtd: require write permissions for locking and badblock ioctls\n\nMEMLOCK, MEMUNLOCK and OTPLOCK modify protection bits. Thus require\nwrite permission. Depending on the hardware MEMLOCK might even be\nwrite-once, e.g. for SPI-NOR flashes with their WP# tied to GND. OTPLOCK\nis always write-once.\n\nMEMSETBADBLOCK modifies the bad block table.",
"severity": [],
"severity": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
}
],
"affected": [],
"references": [
{
@@ -52,8 +57,10 @@
}
],
"database_specific": {
"cwe_ids": [],
"severity": null,
"cwe_ids": [
"CWE-667"
],
"severity": "MODERATE",
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-02-29T23:15:07Z"
@@ -29,7 +29,9 @@
}
],
"database_specific": {
"cwe_ids": [],
"cwe_ids": [
"CWE-79"
],
"severity": "MODERATE",
"github_reviewed": false,
"github_reviewed_at": null,
@@ -1,7 +1,7 @@
{
"schema_version": "1.4.0",
"id": "GHSA-4gqc-44f8-fcvg",
"modified": "2024-04-17T12:32:04Z",
"modified": "2025-01-09T18:32:10Z",
"published": "2024-04-17T12:32:04Z",
"aliases": [
"CVE-2024-26873"
@@ -22,6 +22,10 @@
"type": "WEB",
"url": "https://git.kernel.org/stable/c/85c98073ffcfe9e46abfb9c66f3364467119d563"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/a47f0b03149af538af4442ff0702eac430ace1cb"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/e022dd3b875315a2d2001a512e98d1dc8c991f4a"
@@ -29,7 +29,9 @@
}
],
"database_specific": {
"cwe_ids": [],
"cwe_ids": [
"CWE-79"
],
"severity": "MODERATE",
"github_reviewed": false,
"github_reviewed_at": null,
@@ -29,7 +29,9 @@
}
],
"database_specific": {
"cwe_ids": [],
"cwe_ids": [
"CWE-79"
],
"severity": "MODERATE",
"github_reviewed": false,
"github_reviewed_at": null,
@@ -26,7 +26,8 @@
],
"database_specific": {
"cwe_ids": [
"CWE-120"
"CWE-120",
"CWE-787"
],
"severity": "HIGH",
"github_reviewed": false,
@@ -29,7 +29,9 @@
}
],
"database_specific": {
"cwe_ids": [],
"cwe_ids": [
"CWE-79"
],
"severity": "MODERATE",
"github_reviewed": false,
"github_reviewed_at": null,
@@ -1,7 +1,7 @@
{
"schema_version": "1.4.0",
"id": "GHSA-j6hc-65ch-6v6p",
"modified": "2024-04-09T21:31:58Z",
"modified": "2025-01-09T18:32:08Z",
"published": "2024-04-09T21:31:58Z",
"aliases": [
"CVE-2024-1463"
@@ -29,7 +29,9 @@
}
],
"database_specific": {
"cwe_ids": [],
"cwe_ids": [
"CWE-79"
],
"severity": "MODERATE",
"github_reviewed": false,
"github_reviewed_at": null,
@@ -1,7 +1,7 @@
{
"schema_version": "1.4.0",
"id": "GHSA-qh29-9j77-hqw6",
"modified": "2024-04-09T21:31:57Z",
"modified": "2025-01-09T18:32:07Z",
"published": "2024-04-09T21:31:57Z",
"aliases": [
"CVE-2024-1289"
@@ -29,7 +29,9 @@
}
],
"database_specific": {
"cwe_ids": [],
"cwe_ids": [
"CWE-639"
],
"severity": "MODERATE",
"github_reviewed": false,
"github_reviewed_at": null,
@@ -26,7 +26,8 @@
],
"database_specific": {
"cwe_ids": [
"CWE-200"
"CWE-200",
"CWE-922"
],
"severity": "MODERATE",
"github_reviewed": false,
@@ -1,7 +1,7 @@
{
"schema_version": "1.4.0",
"id": "GHSA-hxrw-3c72-p9hc",
"modified": "2024-05-21T15:31:38Z",
"modified": "2025-01-09T18:32:11Z",
"published": "2024-05-21T15:31:38Z",
"aliases": [
"CVE-2024-4452"
@@ -29,7 +29,9 @@
}
],
"database_specific": {
"cwe_ids": [],
"cwe_ids": [
"CWE-79"
],
"severity": "MODERATE",
"github_reviewed": false,
"github_reviewed_at": null,
@@ -1,13 +1,17 @@
{
"schema_version": "1.4.0",
"id": "GHSA-78wc-gq29-f2pq",
"modified": "2024-09-27T12:31:39Z",
"modified": "2025-01-09T18:32:12Z",
"published": "2024-09-27T12:31:39Z",
"aliases": [
"CVE-2024-9202"
],
"details": "In Eclipse Dataspace Components versions 0.1.3 to 0.9.0, the Connector component filters which datasets (= data offers) another party can see in a requested catalog, to ensure that only authorized parties are able to view restricted offers.\nHowever, there is the possibility to request a single dataset, which should be subject to the same filtering process, but currently is missing the correct filtering.\n\n\nThis enables parties to potentially see datasets they should not have access to, thereby exposing sensitive information. Exploiting this vulnerability requires knowing the ID of a restricted dataset, but some IDs may be guessed by trying out many IDs in an automated way.\n\n\nAffected code:\n DatasetResolverImpl, L76-79 https://github.com/eclipse-edc/Connector/blob/v0.9.0/core/control-plane/control-plane-catalog/src/main/java/org/eclipse/edc/connector/controlplane/catalog/DatasetResolverImpl.java",
"severity": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N"
},
{
"type": "CVSS_V4",
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N/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:M/U:Amber"

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