Advisory Database Sync

2026-05-22 18:04:22 -07:00 · 2024-03-14 21:31:44 +00:00
parent e46590692e
commit e53dcc8499
38 changed files with 607 additions and 67 deletions
@@ -1,7 +1,7 @@
 {
  "schema_version": "1.4.0",
  "id": "GHSA-53v4-42fg-g287",
-  "modified": "2024-02-16T15:30:26Z",
+  "modified": "2024-03-14T21:30:03Z",
  "published": "2023-11-28T18:30:23Z",
  "aliases": [
    "CVE-2022-41678"
@@ -63,10 +63,22 @@
      "type": "WEB",
      "url": "https://github.com/apache/activemq/pull/958"
    },
+    {
+      "type": "WEB",
+      "url": "https://github.com/apache/activemq/commit/5c8d457d9"
+    },
    {
      "type": "WEB",
      "url": "https://github.com/apache/activemq/commit/6120169e563b55323352431dfe9ac67a8b4de6c2"
    },
+    {
+      "type": "WEB",
+      "url": "https://github.com/apache/activemq/commit/bf65929fd"
+    },
+    {
+      "type": "WEB",
+      "url": "https://github.com/apache/activemq/commit/d8ce1d9ff"
+    },
    {
      "type": "WEB",
      "url": "https://activemq.apache.org/security-advisories.data/CVE-2022-41678-announcement.txt"
@@ -1,7 +1,7 @@
 {
  "schema_version": "1.4.0",
  "id": "GHSA-4gm2-r6xm-jqxh",
-  "modified": "2022-05-25T00:00:23Z",
+  "modified": "2024-03-14T21:30:50Z",
  "published": "2022-05-17T00:01:27Z",
  "aliases": [
    "CVE-2022-1386"
@@ -1,7 +1,7 @@
 {
  "schema_version": "1.4.0",
  "id": "GHSA-5wvr-c5h8-vf7f",
-  "modified": "2022-05-14T03:05:21Z",
+  "modified": "2024-03-14T21:30:50Z",
  "published": "2022-05-14T03:05:21Z",
  "aliases": [
    "CVE-2017-16529"
@@ -1,7 +1,7 @@
 {
  "schema_version": "1.4.0",
  "id": "GHSA-6rxj-38xv-j69g",
-  "modified": "2022-05-17T03:23:41Z",
+  "modified": "2024-03-14T21:30:49Z",
  "published": "2022-05-17T03:23:41Z",
  "aliases": [
    "CVE-2012-2143"
@@ -22,6 +22,10 @@
      "type": "WEB",
      "url": "https://bugzilla.redhat.com/show_bug.cgi?id=816956"
    },
+    {
+      "type": "WEB",
+      "url": "http://git.php.net/?p=php-src.git%3Ba=commit%3Bh=aab49e934de1fff046e659cbec46e3d053b41c34"
+    },
    {
      "type": "WEB",
      "url": "http://git.php.net/?p=php-src.git;a=commit;h=aab49e934de1fff046e659cbec46e3d053b41c34"
@@ -1,7 +1,7 @@
 {
  "schema_version": "1.4.0",
  "id": "GHSA-9vwf-r222-fcvc",
-  "modified": "2022-05-14T03:32:53Z",
+  "modified": "2024-03-14T21:30:50Z",
  "published": "2022-05-14T03:32:53Z",
  "aliases": [
    "CVE-2017-16528"
@@ -1,7 +1,7 @@
 {
  "schema_version": "1.4.0",
  "id": "GHSA-gg87-xrj2-3r8m",
-  "modified": "2022-05-14T02:03:29Z",
+  "modified": "2024-03-14T21:30:50Z",
  "published": "2022-05-14T02:03:29Z",
  "aliases": [
    "CVE-2017-10661"
@@ -1,7 +1,7 @@
 {
  "schema_version": "1.4.0",
  "id": "GHSA-gpq7-5wgv-cqmg",
-  "modified": "2022-05-14T03:05:20Z",
+  "modified": "2024-03-14T21:30:50Z",
  "published": "2022-05-14T03:05:20Z",
  "aliases": [
    "CVE-2017-16527"
@@ -1,7 +1,7 @@
 {
  "schema_version": "1.4.0",
  "id": "GHSA-rf35-pm73-38q6",
-  "modified": "2022-05-14T03:05:20Z",
+  "modified": "2024-03-14T21:30:50Z",
  "published": "2022-05-14T03:05:20Z",
  "aliases": [
    "CVE-2017-16532"
@@ -1,7 +1,7 @@
 {
  "schema_version": "1.4.0",
  "id": "GHSA-rwf8-4gv4-8fmw",
-  "modified": "2022-05-17T03:11:57Z",
+  "modified": "2024-03-14T21:30:50Z",
  "published": "2022-05-17T03:11:57Z",
  "aliases": [
    "CVE-2015-2666"
@@ -26,6 +26,10 @@
      "type": "WEB",
      "url": "https://bugzilla.redhat.com/show_bug.cgi?id=1204722"
    },
+    {
+      "type": "WEB",
+      "url": "http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git%3Ba=commit%3Bh=f84598bd7c851f8b0bf8cd0d7c3be0d73c432ff4"
+    },
    {
      "type": "WEB",
      "url": "http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=f84598bd7c851f8b0bf8cd0d7c3be0d73c432ff4"
@@ -1,7 +1,7 @@
 {
  "schema_version": "1.4.0",
  "id": "GHSA-wc9w-8x8g-533g",
-  "modified": "2022-05-13T01:26:24Z",
+  "modified": "2024-03-14T21:30:49Z",
  "published": "2022-05-13T01:26:24Z",
  "aliases": [
    "CVE-2014-9529"
@@ -30,6 +30,10 @@
      "type": "WEB",
      "url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/99641"
    },
+    {
+      "type": "WEB",
+      "url": "http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git%3Ba=commit%3Bh=a3a8784454692dd72e5d5d34dcdab17b4420e74c"
+    },
    {
      "type": "WEB",
      "url": "http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=a3a8784454692dd72e5d5d34dcdab17b4420e74c"
@@ -1,14 +1,17 @@
 {
  "schema_version": "1.4.0",
  "id": "GHSA-3hp3-h35p-gqg4",
-  "modified": "2024-02-22T18:30:28Z",
+  "modified": "2024-03-14T21:30:51Z",
  "published": "2024-02-22T18:30:28Z",
  "aliases": [
    "CVE-2023-52443"
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\napparmor: avoid crash when parsed profile name is empty\n\nWhen processing a packed profile in unpack_profile() described like\n\n \"profile :ns::samba-dcerpcd /usr/lib*/samba/{,samba/}samba-dcerpcd {...}\"\n\na string \":samba-dcerpcd\" is unpacked as a fully-qualified name and then\npassed to aa_splitn_fqname().\n\naa_splitn_fqname() treats \":samba-dcerpcd\" as only containing a namespace.\nThus it returns NULL for tmpname, meanwhile tmpns is non-NULL. Later\naa_alloc_profile() crashes as the new profile name is NULL now.\n\ngeneral protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN NOPTI\nKASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]\nCPU: 6 PID: 1657 Comm: apparmor_parser Not tainted 6.7.0-rc2-dirty #16\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.2-3-gd478f380-rebuilt.opensuse.org 04/01/2014\nRIP: 0010:strlen+0x1e/0xa0\nCall Trace:\n <TASK>\n ? strlen+0x1e/0xa0\n aa_policy_init+0x1bb/0x230\n aa_alloc_profile+0xb1/0x480\n unpack_profile+0x3bc/0x4960\n aa_unpack+0x309/0x15e0\n aa_replace_profiles+0x213/0x33c0\n policy_update+0x261/0x370\n profile_replace+0x20e/0x2a0\n vfs_write+0x2af/0xe00\n ksys_write+0x126/0x250\n do_syscall_64+0x46/0xf0\n entry_SYSCALL_64_after_hwframe+0x6e/0x76\n </TASK>\n---[ end trace 0000000000000000 ]---\nRIP: 0010:strlen+0x1e/0xa0\n\nIt seems such behaviour of aa_splitn_fqname() is expected and checked in\nother places where it is called (e.g. aa_remove_profiles). Well, there\nis an explicit comment \"a ns name without a following profile is allowed\"\ninside.\n\nAFAICS, nothing can prevent unpacked \"name\" to be in form like\n\":samba-dcerpcd\" - it is passed from userspace.\n\nDeny the whole profile set replacement in such case and inform user with\nEPROTO and an explaining message.\n\nFound by Linux Verification Center (linuxtesting.org).",
  "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": [

@@ -53,9 +56,9 @@
  ],
  "database_specific": {
    "cwe_ids": [
-
+      "CWE-476"
    ],
-    "severity": null,
+    "severity": "MODERATE",
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2024-02-22T17:15:08Z"
@@ -1,14 +1,17 @@
 {
  "schema_version": "1.4.0",
  "id": "GHSA-63f3-2rgp-79qx",
-  "modified": "2024-02-28T03:30:30Z",
+  "modified": "2024-03-14T21:30:51Z",
  "published": "2024-02-21T15:30:45Z",
  "aliases": [
    "CVE-2024-26585"
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\ntls: fix race between tx work scheduling and socket close\n\nSimilarly to previous commit, the submitting thread (recvmsg/sendmsg)\nmay exit as soon as the async crypto handler calls complete().\nReorder scheduling the work before calling complete().\nThis seems more logical in the first place, as it's\nthe inverse order of what the submitting thread will do.",
  "severity": [
-
+    {
+      "type": "CVSS_V3",
+      "score": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H"
+    }
  ],
  "affected": [

@@ -41,9 +44,9 @@
  ],
  "database_specific": {
    "cwe_ids": [
-
+      "CWE-362"
    ],
-    "severity": null,
+    "severity": "MODERATE",
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2024-02-21T15:15:09Z"
@@ -1,14 +1,17 @@
 {
  "schema_version": "1.4.0",
  "id": "GHSA-6f72-79f8-3qcp",
-  "modified": "2024-02-22T18:30:29Z",
+  "modified": "2024-03-14T21:30:51Z",
  "published": "2024-02-22T18:30:29Z",
  "aliases": [
    "CVE-2023-52444"
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix to avoid dirent corruption\n\nAs Al reported in link[1]:\n\nf2fs_rename()\n...\n\tif (old_dir != new_dir && !whiteout)\n\t\tf2fs_set_link(old_inode, old_dir_entry,\n\t\t\t\t\told_dir_page, new_dir);\n\telse\n\t\tf2fs_put_page(old_dir_page, 0);\n\nYou want correct inumber in the \"..\" link.  And cross-directory\nrename does move the source to new parent, even if you'd been asked\nto leave a whiteout in the old place.\n\n[1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/\n\nWith below testcase, it may cause dirent corruption, due to it missed\nto call f2fs_set_link() to update \"..\" link to new directory.\n- mkdir -p dir/foo\n- renameat2 -w dir/foo bar\n\n[ASSERT] (__chk_dots_dentries:1421)  --> Bad inode number[0x4] for '..', parent parent ino is [0x3]\n[FSCK] other corrupted bugs                           [Fail]",
  "severity": [
-
+    {
+      "type": "CVSS_V3",
+      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
+    }
  ],
  "affected": [

@@ -53,9 +56,9 @@
  ],
  "database_specific": {
    "cwe_ids": [
-
+      "CWE-119"
    ],
-    "severity": null,
+    "severity": "HIGH",
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2024-02-22T17:15:08Z"
@@ -1,14 +1,17 @@
 {
  "schema_version": "1.4.0",
  "id": "GHSA-84fp-h279-ggmw",
-  "modified": "2024-02-22T18:30:29Z",
+  "modified": "2024-03-14T21:30:51Z",
  "published": "2024-02-22T18:30:29Z",
  "aliases": [
    "CVE-2023-52445"
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: pvrusb2: fix use after free on context disconnection\n\nUpon module load, a kthread is created targeting the\npvr2_context_thread_func function, which may call pvr2_context_destroy\nand thus call kfree() on the context object. However, that might happen\nbefore the usb hub_event handler is able to notify the driver. This\npatch adds a sanity check before the invalid read reported by syzbot,\nwithin the context disconnection call stack.",
  "severity": [
-
+    {
+      "type": "CVSS_V3",
+      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
+    }
  ],
  "affected": [

@@ -53,9 +56,9 @@
  ],
  "database_specific": {
    "cwe_ids": [
-
+      "CWE-416"
    ],
-    "severity": null,
+    "severity": "HIGH",
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2024-02-22T17:15:08Z"
@@ -1,14 +1,17 @@
 {
  "schema_version": "1.4.0",
  "id": "GHSA-wvjr-h8mr-f8gw",
-  "modified": "2024-02-22T18:30:29Z",
+  "modified": "2024-03-14T21:30:51Z",
  "published": "2024-02-22T18:30:29Z",
  "aliases": [
    "CVE-2023-52447"
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Defer the free of inner map when necessary\n\nWhen updating or deleting an inner map in map array or map htab, the map\nmay still be accessed by non-sleepable program or sleepable program.\nHowever bpf_map_fd_put_ptr() decreases the ref-counter of the inner map\ndirectly through bpf_map_put(), if the ref-counter is the last one\n(which is true for most cases), the inner map will be freed by\nops->map_free() in a kworker. But for now, most .map_free() callbacks\ndon't use synchronize_rcu() or its variants to wait for the elapse of a\nRCU grace period, so after the invocation of ops->map_free completes,\nthe bpf program which is accessing the inner map may incur\nuse-after-free problem.\n\nFix the free of inner map by invoking bpf_map_free_deferred() after both\none RCU grace period and one tasks trace RCU grace period if the inner\nmap has been removed from the outer map before. The deferment is\naccomplished by using call_rcu() or call_rcu_tasks_trace() when\nreleasing the last ref-counter of bpf map. The newly-added rcu_head\nfield in bpf_map shares the same storage space with work field to\nreduce the size of bpf_map.",
  "severity": [
-
+    {
+      "type": "CVSS_V3",
+      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
+    }
  ],
  "affected": [

@@ -37,9 +40,9 @@
  ],
  "database_specific": {
    "cwe_ids": [
-
+      "CWE-416"
    ],
-    "severity": null,
+    "severity": "HIGH",
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2024-02-22T17:15:08Z"
@@ -0,0 +1,35 @@
+{
+  "schema_version": "1.4.0",
+  "id": "GHSA-2qqg-5pcx-4jv3",
+  "modified": "2024-03-14T21:30:51Z",
+  "published": "2024-03-14T21:30:51Z",
+  "aliases": [
+    "CVE-2024-28423"
+  ],
+  "details": "Airflow-Diagrams v2.1.0 was discovered to contain an arbitrary file upload vulnerability in the unsafe_load function at cli.py. This vulnerability allows attackers to execute arbitrary code via uploading a crafted YML file.",
+  "severity": [
+
+  ],
+  "affected": [
+
+  ],
+  "references": [
+    {
+      "type": "ADVISORY",
+      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-28423"
+    },
+    {
+      "type": "WEB",
+      "url": "https://github.com/bayuncao/vul-cve-15"
+    }
+  ],
+  "database_specific": {
+    "cwe_ids": [
+
+    ],
+    "severity": null,
+    "github_reviewed": false,
+    "github_reviewed_at": null,
+    "nvd_published_at": "2024-03-14T19:15:50Z"
+  }
+}
@@ -1,14 +1,17 @@
 {
  "schema_version": "1.4.0",
  "id": "GHSA-4rxr-8xrx-9rf3",
-  "modified": "2024-03-14T00:31:05Z",
+  "modified": "2024-03-14T21:30:51Z",
  "published": "2024-03-08T03:31:25Z",
  "aliases": [
    "CVE-2024-23270"
  ],
  "details": "The issue was addressed with improved memory handling. This issue is fixed in macOS Monterey 12.7.4, macOS Ventura 13.6.5, macOS Sonoma 14.4, iOS 17.4 and iPadOS 17.4, tvOS 17.4. An app may be able to execute arbitrary code with kernel privileges.",
  "severity": [
-
+    {
+      "type": "CVSS_V3",
+      "score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H"
+    }
  ],
  "affected": [

@@ -59,7 +62,7 @@
    "cwe_ids": [

    ],
-    "severity": null,
+    "severity": "HIGH",
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2024-03-08T02:15:49Z"
@@ -1,14 +1,17 @@
 {
  "schema_version": "1.4.0",
  "id": "GHSA-525f-hw88-w4m8",
-  "modified": "2024-03-14T00:31:05Z",
+  "modified": "2024-03-14T21:30:51Z",
  "published": "2024-03-08T03:31:25Z",
  "aliases": [
    "CVE-2024-23275"
  ],
  "details": "A race condition was addressed with additional validation. This issue is fixed in macOS Sonoma 14.4, macOS Monterey 12.7.4, macOS Ventura 13.6.5. An app may be able to access protected user data.",
  "severity": [
-
+    {
+      "type": "CVSS_V3",
+      "score": "CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N"
+    }
  ],
  "affected": [

@@ -45,9 +48,9 @@
  ],
  "database_specific": {
    "cwe_ids": [
-
+      "CWE-362"
    ],
-    "severity": null,
+    "severity": "MODERATE",
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2024-03-08T02:15:49Z"
@@ -1,14 +1,17 @@
 {
  "schema_version": "1.4.0",
  "id": "GHSA-5c5p-qh6w-cqq9",
-  "modified": "2024-03-14T00:31:05Z",
+  "modified": "2024-03-14T21:30:51Z",
  "published": "2024-03-08T03:31:25Z",
  "aliases": [
    "CVE-2024-23272"
  ],
  "details": "A logic issue was addressed with improved checks. This issue is fixed in macOS Sonoma 14.4, macOS Monterey 12.7.4, macOS Ventura 13.6.5. A user may gain access to protected parts of the file system.",
  "severity": [
-
+    {
+      "type": "CVSS_V3",
+      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N"
+    }
  ],
  "affected": [

@@ -47,7 +50,7 @@
    "cwe_ids": [

    ],
-    "severity": null,
+    "severity": "MODERATE",
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2024-03-08T02:15:49Z"
--- a/Show More
+++ b/Show More