Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
Vulnrichment: - CVE Program Container: References: - https://github.com/OISF/suricata/security/advisories/GHSA-wmg4-jqx5-4h9v - https://github.com/OISF/suricata/commit/dd71ef0af222a566e54dfc479dd1951dd17d7ceb - https://redmine.openinfosecfoundation.org/issues/7366
CVE ID: CVE-2024-55627 State: PUBLISHED Published: 2025-01-06T17:50:41.554Z Last Updated: 2025-01-06T19:15:13.448Z Severity: MEDIUM (CVSS 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H) Vendors: OISF Products: suricata Problem Types: CWE-191, CWE-122 Description: Suricata is a network Intrusion Detection System, Intrusion Prevention System and Network Security Monitoring engine. Prior to 7.0.8, a specially crafted TCP stream can lead to a very large buffer overflow while being zero-filled during initialization with memset due to an unsigned integer underflow. The issue has been addressed in Suricata 7.0.8. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://github.com/
s been addressed in Suricata 7.0.8. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://github.com/OISF/suricata/security/advisories/GHSA-h2mv-7gg8-8x7v - https://github.com/OISF/suricata/commit/282509f70c4ce805098e59535af445362e3e9ebd - https://github.com/OISF/suricata/commit/8900041405dbb5f9584edae994af2100733fb4be - https://github.com/OISF/suricata/commit/9a53ec43b13f0039a083950511a18bf6f408e432 - https://redmine.openinfosecfoundation.org/issues/7393
CVE ID: CVE-2024-55628 State: PUBLISHED Published: 2025-01-06T18:02:10.692Z Last Updated: 2025-01-06T19:14:33.486Z Severity: HIGH (CVSS 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) Vendors: OISF Products: suricata Problem Types: CWE-405, CWE-779 Description: Suricata is a network Intrusion Detection System, Intrusion Prevention System and Network Security Monitoring engine. Prior to version 7.0.8, DNS resource name compression can lead to small DNS messages containing very large hostnames which can be costly to decode, and lead to very large DNS log records. While there are limits in place, they were too generous. The issue has been addressed in Suricata 7.0.8. Additional Analyst Notes:
e are limits in place, they were too generous. The issue has been addressed in Suricata 7.0.8. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://github.com/OISF/suricata/security/advisories/GHSA-96w4-jqwf-qx2j - https://github.com/OISF/suricata/commit/19cf0f81335d9f787d587450f7105ad95a648951 - https://github.com/OISF/suricata/commit/37f4c52b22fcdde4adf9b479cb5700f89d00768d - https://github.com/OISF/suricata/commit/3a5671739f5b25e5dd973a74ca5fd8ea40e1ae2d - https://redmine.openinfosecfoundation.org/issues/7280
CVE ID: CVE-2024-55629 State: PUBLISHED Published: 2025-01-06T18:04:08.180Z Last Updated: 2025-01-06T18:51:58.364Z Severity: HIGH (CVSS 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N) Vendors: OISF Products: suricata Problem Types: CWE-437 Description: Suricata is a network Intrusion Detection System, Intrusion Prevention System and Network Security Monitoring engine. Prior to 7.0.8, TCP streams with TCP urgent data (out of band data) can lead to Suricata analyzing data differently than the applications at the TCP endpoints, leading to possible evasions. Suricata 7.0.8 includes options to allow users to configure how to handle TCP urgent data. In IPS mode, you can use a rule such as drop t
cludes options to allow users to configure how to handle TCP urgent data. In IPS mode, you can use a rule such as drop tcp any any -> any any (sid:1; tcp.flags:U*;) to drop all the packets with urgent flag set. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://github.com/OISF/suricata/security/advisories/GHSA-69wr-vhwg-84h2 - https://github.com/OISF/suricata/commit/6882bcb3e51bd3cf509fb6569cc30f48d7bb53d7 - https://github.com/OISF/suricata/commit/779f9d8ba35c3f9b5abfa327d3a4209861bd2eb8 - https://redmine.openinfosecfoundation.org/issues/7411
CVE ID: CVE-2024-55630 State: PUBLISHED Published: 2025-02-07T22:23:04.109Z Last Updated: 2025-02-10T17:18:47.395Z Severity: LOW (CVSS 3.3 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L) Vendors: laurent22 Products: joplin Problem Types: CWE-20 Description: Joplin is a free, open source note taking and to-do application, which can handle a large number of notes organised into notebooks. Joplin's HTML sanitizer allows the `name` attribute to be specified. If `name` is set to the same value as an existing `document` property (e.g. `querySelector`), that property is replaced with the element. This vulnerability's only known impact is denial of service. The note viewer fails to refresh until close
h the element. This vulnerability's only known impact is denial of service. The note viewer fails to refresh until closed and re-opened with a different note. This issue has been addressed in version 3.2.8 and all users are advised to upgrade. There are no known workarounds for this vulnerability. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://github.com/laurent22/joplin/security/advisories/GHSA-5cch-jr52-qffh - https://github.com/laurent22/joplin/commit/e70efcbd60ce62f06e77c183b362c74e636c02d9 - https://en.wikipedia.org/wiki/DOM_clobbering
CVE ID: CVE-2024-55631 State: PUBLISHED Published: 2024-12-31T16:15:20.397Z Last Updated: 2024-12-31T17:25:40.482Z Severity: HIGH (CVSS 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) Vendors: Trend Micro, Inc. Products: Trend Micro Apex One, Trend Micro Apex One as a Service Problem Types: CWE-269 Description: An engine link following vulnerability in Trend Micro Apex One could allow a local attacker to escalate privileges on affected installations. Please note: an attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://success.trendmicro.com/
oit this vulnerability. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://success.trendmicro.com/en-US/solution/KA-0018217
CVE ID: CVE-2024-55632 State: PUBLISHED Published: 2024-12-31T16:16:01.207Z Last Updated: 2024-12-31T17:25:15.416Z Severity: HIGH (CVSS 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) Vendors: Trend Micro, Inc. Products: Trend Micro Apex One, Trend Micro Apex One as a Service Problem Types: CWE-269 Description: A security agent link following vulnerability in Trend Micro Apex One could allow a local attacker to escalate privileges on affected installations. Please note: an attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://success.trendmic
to exploit this vulnerability. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://success.trendmicro.com/en-US/solution/KA-0018217
CVE ID: CVE-2024-55633 State: PUBLISHED Published: 2024-12-12T14:36:02.325Z Last Updated: 2025-02-12T09:35:43.626Z Vendors: Apache Software Foundation Products: Apache Superset Problem Types: CWE-863 Description: Improper Authorization vulnerability in Apache Superset. On Postgres analytic databases an attacker with SQLLab access can craft a specially designed SQL DML statement that is Incorrectly identified as a read-only query, enabling its execution. Non postgres analytics database connections and postgres analytics database connections set with a readonly user (advised) are not vulnerable. This issue affects Apache Superset: before 4.1.0. Users are recommended to upgrade to version 4.1.0
are not vulnerable. This issue affects Apache Superset: before 4.1.0. Users are recommended to upgrade to version 4.1.0, which fixes the issue. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://lists.apache.org/thread/bwmd17fcvljt9q4cgctp4v09zh3qs7fb
CVE ID: CVE-2024-55634 State: PUBLISHED Published: 2024-12-09T23:21:15.943Z Last Updated: 2024-12-11T16:39:12.440Z Vendors: Drupal Products: Drupal Core Problem Types: CWE-178, CWE-289 Description: A vulnerability in Drupal Core allows Privilege Escalation.This issue affects Drupal Core: from 8.0.0 before 10.2.11, from 10.3.0 before 10.3.9, from 11.0.0 before 11.0.8. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://www.drupal.org/sa-core-2024-004
CVE ID: CVE-2024-55635 State: PUBLISHED Published: 2024-12-09T23:23:38.742Z Last Updated: 2024-12-10T21:18:04.893Z Vendors: Drupal Products: Drupal Core Problem Types: CWE-79 Description: Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Drupal Core allows Cross-Site Scripting (XSS).This issue affects Drupal Core: from 7.0 before 7.102. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://www.drupal.org/sa-core-2024-005
CVE ID: CVE-2024-55636 State: PUBLISHED Published: 2024-12-09T23:24:27.729Z Last Updated: 2024-12-16T17:09:36.830Z Vendors: Drupal Products: Drupal Core Problem Types: CWE-915 Description: Deserialization of Untrusted Data vulnerability in Drupal Core allows Object Injection.This issue affects Drupal Core: from 8.0.0 before 10.2.11, from 10.3.0 before 10.3.9, from 11.0.0 before 11.0.8. Drupal core contains a chain of methods that is exploitable when an insecure deserialization vulnerability exists on the site. This so called gadget chain presents no direct threat, but is a vector that can be used to achieve remote code execution if the application deserializes untrusted data due to another v
vector that can be used to achieve remote code execution if the application deserializes untrusted data due to another vulnerability. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://www.drupal.org/sa-core-2024-006
CVE ID: CVE-2024-55637 State: PUBLISHED Published: 2024-12-09T23:25:32.356Z Last Updated: 2024-12-16T17:10:40.749Z Vendors: Drupal Products: Drupal Core Problem Types: CWE-915 Description: Deserialization of Untrusted Data vulnerability in Drupal Core allows Object Injection.This issue affects Drupal Core: from 8.0.0 before 10.2.11, from 10.3.0 before 10.3.9, from 11.0.0 before 11.0.8. Drupal core contains a chain of methods that is exploitable when an insecure deserialization vulnerability exists on the site. This so-called gadget chain presents no direct threat but is a vector that can be used to achieve remote code execution if the application deserializes untrusted data due to another vu
ector that can be used to achieve remote code execution if the application deserializes untrusted data due to another vulnerability. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://www.drupal.org/sa-core-2024-007
CVE ID: CVE-2024-55638 State: PUBLISHED Published: 2024-12-09T23:26:30.780Z Last Updated: 2024-12-16T17:11:20.896Z Vendors: Drupal Products: Drupal Core Problem Types: CWE-915 Description: Deserialization of Untrusted Data vulnerability in Drupal Core allows Object Injection.This issue affects Drupal Core: from 7.0 before 7.102, from 8.0.0 before 10.2.11, from 10.3.0 before 10.3.9. Drupal core contains a chain of methods that is exploitable when an insecure deserialization vulnerability exists on the site. This so-called gadget chain presents no direct threat but is a vector that can be used to achieve remote code execution if the application deserializes untrusted data due to another vulner
r that can be used to achieve remote code execution if the application deserializes untrusted data due to another vulnerability. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://www.drupal.org/sa-core-2024-008
CVE ID: CVE-2024-55639 State: PUBLISHED Published: 2025-01-11T12:29:55.309Z Last Updated: 2025-05-04T09:57:11.827Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: net: renesas: rswitch: avoid use-after-put for a device tree node The device tree node saved in the rswitch_device structure is used at several driver locations. So passing this node to of_node_put() after the first use is wrong. Move of_node_put() for this node to exit paths. References: - https://git.kernel.org/stable/c/bf8c6755f02029d1eddc3ff19b870240f054afc7 - https://git.kernel.org/stable/c/92007a28f95413058a7268dc84e5f44b700165d1 - https://git.kernel.org/stable/c
240f054afc7 - https://git.kernel.org/stable/c/92007a28f95413058a7268dc84e5f44b700165d1 - https://git.kernel.org/stable/c/66b7e9f85b8459c823b11e9af69dbf4be5eb6be8
CVE ID: CVE-2024-55641 State: PUBLISHED Published: 2025-01-11T12:29:56.052Z Last Updated: 2025-05-04T09:57:13.136Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: xfs: unlock inodes when erroring out of xfs_trans_alloc_dir Debugging a filesystem patch with generic/475 caused the system to hang after observing the following sequences in dmesg: XFS (dm-0): metadata I/O error in "xfs_imap_to_bp+0x61/0xe0 [xfs]" at daddr 0x491520 len 32 error 5 XFS (dm-0): metadata I/O error in "xfs_btree_read_buf_block+0xba/0x160 [xfs]" at daddr 0x3445608 len 8 error 5 XFS (dm-0): metadata I/O error in "xfs_imap_to_bp+0x61/0xe0 [xfs]" at daddr 0x13
[xfs]" at daddr 0x3445608 len 8 error 5 XFS (dm-0): metadata I/O error in "xfs_imap_to_bp+0x61/0xe0 [xfs]" at daddr 0x138e1c0 len 32 error 5 XFS (dm-0): log I/O error -5 XFS (dm-0): Metadata I/O Error (0x1) detected at xfs_trans_read_buf_map+0x1ea/0x4b0 [xfs] (fs/xfs/xfs_trans_buf.c:311). Shutting down filesystem. XFS (dm-0): Please unmount the filesystem and rectify the problem(s) XFS (dm-0): Internal error dqp->q_ino.reserved < dqp->q_ino.count at line 869 of file fs/xfs/xfs_trans_dquot.c. Caller xfs_trans_dqresv+0x236/0x440 [xfs] XFS (dm-0): Corruption detected. Unmount and run xfs_repair XFS (dm-0): Unmounting Filesystem be6bcbcc-9921-4deb-8d16-7cc94e335fa7 The system is stuck in unmount
and run xfs_repair XFS (dm-0): Unmounting Filesystem be6bcbcc-9921-4deb-8d16-7cc94e335fa7 The system is stuck in unmount trying to lock a couple of inodes so that they can be purged. The dquot corruption notice above is a clue to what happened -- a link() call tried to set up a transaction to link a child into a directory. Quota reservation for the transaction failed after IO errors shut down the filesystem, but then we forgot to unlock the inodes on our way out. Fix that. References: - https://git.kernel.org/stable/c/6aefe5d97ae57b1343dc60d8bb6a4ed070e5bcea - https://git.kernel.org/stable/c/53b001a21c9dff73b64e8c909c41991f01d5d00f
CVE ID: CVE-2024-55642 State: PUBLISHED Published: 2025-01-11T12:29:56.848Z Last Updated: 2025-10-01T19:57:21.270Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: block: Prevent potential deadlocks in zone write plug error recovery Zone write plugging for handling writes to zones of a zoned block device always execute a zone report whenever a write BIO to a zone fails. The intent of this is to ensure that the tracking of a zone write pointer is always correct to ensure that the alignment to a zone write pointer of write BIOs can be checked on submission and that we can always correctly emulate zone append operations using regula
of write BIOs can be checked on submission and that we can always correctly emulate zone append operations using regular write BIOs. However, this error recovery scheme introduces a potential deadlock if a device queue freeze is initiated while BIOs are still plugged in a zone write plug and one of these write operation fails. In such case, the disk zone write plug error recovery work is scheduled and executes a report zone. This in turn can result in a request allocation in the underlying driver to issue the report zones command to the device. But with the device queue freeze already started, this allocation will block, preventing the report zone execution and the continuation of the proce
eeze already started, this allocation will block, preventing the report zone execution and the continuation of the processing of the plugged BIOs. As plugged BIOs hold a queue usage reference, the queue freeze itself will never complete, resulting in a deadlock. Avoid this problem by completely removing from the zone write plugging code the use of report zones operations after a failed write operation, instead relying on the device user to either execute a report zones, reset the zone, finish the zone, or give up writing to the device (which is a fairly common pattern for file systems which degrade to read-only after write failures). This is not an unreasonnable requirement as all well-behav
ile systems which degrade to read-only after write failures). This is not an unreasonnable requirement as all well-behaved applications, FSes and device mapper already use report zones to recover from write errors whenever possible by comparing the current position of a zone write pointer with what their assumption about the position is. The changes to remove the automatic error recovery are as follows: - Completely remove the error recovery work and its associated resources (zone write plug list head, disk error list, and disk zone_wplugs_work work struct). This also removes the functions disk_zone_wplug_set_error() and disk_zone_wplug_clear_error(). - Change the BLK_ZONE_WPLUG_ERROR zone w
es the functions disk_zone_wplug_set_error() and disk_zone_wplug_clear_error(). - Change the BLK_ZONE_WPLUG_ERROR zone write plug flag into BLK_ZONE_WPLUG_NEED_WP_UPDATE. This new flag is set for a zone write plug whenever a write opration targetting the zone of the zone write plug fails. This flag indicates that the zone write pointer offset is not reliable and that it must be updated when the next report zone, reset zone, finish zone or disk revalidation is executed. - Modify blk_zone_write_plug_bio_endio() to set the BLK_ZONE_WPLUG_NEED_WP_UPDATE flag for the target zone of a failed write BIO. - Modify the function disk_zone_wplug_set_wp_offset() to clear this new flag, thus implementing
of a failed write BIO. - Modify the function disk_zone_wplug_set_wp_offset() to clear this new flag, thus implementing recovery of a correct write pointer offset with the reset (all) zone and finish zone operations. - Modify blkdev_report_zones() to always use the disk_report_zones_cb() callback so that disk_zone_wplug_sync_wp_offset() can be called for any zone marked with the BLK_ZONE_WPLUG_NEED_WP_UPDATE flag. This implements recovery of a correct write pointer offset for zone write plugs marked with BLK_ZONE_WPLUG_NEED_WP_UPDATE and within the range of the report zones operation executed by the user. - Modify blk_revalidate_seq_zone() to call disk_zone_wplug_sync_wp_offset() for all seq
operation executed by the user. - Modify blk_revalidate_seq_zone() to call disk_zone_wplug_sync_wp_offset() for all sequential write required zones when a zoned block device is revalidated, thus always resolving any inconsistency between the write pointer offset of zone write plugs and the actual write pointer position of sequential zones. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/7fa80134cf266325fa61139320091001c9b3c477 - https://git.kernel.org/stable/c/fe0418eb9bd69a19a948b297c8de815e05f3cde1
CVE ID: CVE-2024-55651 State: PUBLISHED Published: 2025-05-07T23:49:46.016Z Last Updated: 2025-05-08T13:58:11.917Z Vendors: portabilis Products: i-educar Problem Types: CWE-79 Description: i-Educar is free, fully online school management software. Version 2.9 of the application fails to properly validate and sanitize user supplied input, leading to a stored cross-site scripting vulnerability that resides within the user type (Tipo de Usuário) input field. Through this attacker vector a malicious user might be able to retrieve information belonging to another user, which may lead to sensitive information leakage or other malicious actions. As of time of publication, no patched versions are kn
lead to sensitive information leakage or other malicious actions. As of time of publication, no patched versions are known to exist. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://github.com/portabilis/i-educar/security/advisories/GHSA-8fjj-9937-g84w
CVE ID: CVE-2024-55652 State: PUBLISHED Published: 2024-12-11T22:41:16.664Z Last Updated: 2024-12-12T16:32:39.666Z Severity: MEDIUM (CVSS 6.5 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N) Vendors: pwndoc Products: pwndoc Problem Types: CWE-1336 Description: PenDoc is a penetration testing reporting application. Prior to commit 1d4219c596f4f518798492e48386a20c6e9a2fe6, an attacker can write a malicious docx template containing expressions that escape the JavaScript sandbox to execute arbitrary code on the system. An attacker who can control the contents of the template document is able to execute arbitrary code on the system. By default, only users with the `admin` role are able to create or
ent is able to execute arbitrary code on the system. By default, only users with the `admin` role are able to create or update templates. Commit 1d4219c596f4f518798492e48386a20c6e9a2fe6 patches the issue. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://github.com/pwndoc/pwndoc/security/advisories/GHSA-jw5r-6927-hwpc - https://github.com/pwndoc/pwndoc/commit/1d4219c596f4f518798492e48386a20c6e9a2fe6 - https://github.com/pwndoc/pwndoc/blob/main/backend/src/lib/report-filters.js#L258-L260
CVE ID: CVE-2024-55653 State: PUBLISHED Published: 2024-12-10T22:56:07.488Z Last Updated: 2024-12-11T16:04:21.230Z Severity: MEDIUM (CVSS 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H) Vendors: pwndoc Products: pwndoc Problem Types: CWE-20 Description: PwnDoc is a penetration test report generator. In versions up to and including 0.5.3, an authenticated user is able to crash the backend by raising a `UnhandledPromiseRejection` on audits which exits the backend. The user doesn't need to know the audit id, since a bad audit id will also raise the rejection. With the backend being unresponsive, the whole application becomes unusable for all users of the application. As of time of publication
d being unresponsive, the whole application becomes unusable for all users of the application. As of time of publication, no known patches are available. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://github.com/pwndoc/pwndoc/security/advisories/GHSA-ggqg-3f7v-c8rc
CVE ID: CVE-2024-55655 State: PUBLISHED Published: 2024-12-10T23:06:42.193Z Last Updated: 2024-12-11T16:03:42.578Z Vendors: sigstore Products: sigstore-python Problem Types: CWE-20, CWE-325 Description: sigstore-python is a Python tool for generating and verifying Sigstore signatures. Versions of sigstore-python newer than 2.0.0 but prior to 3.6.0 perform insufficient validation of the "integration time" present in "v2" and "v3" bundles during the verification flow: the "integration time" is verified *if* a source of signed time (such as an inclusion promise) is present, but is otherwise trusted if no source of signed time is present. This does not affect "v1" bundles, as the "v1" bundle for
t is otherwise trusted if no source of signed time is present. This does not affect "v1" bundles, as the "v1" bundle format always requires an inclusion promise. Sigstore uses signed time to support verification of signatures made against short-lived signing keys. The impact and severity of this weakness is *low*, as Sigstore contains multiple other enforcing components that prevent an attacker who modifies the integration timestamp within a bundle from impersonating a valid signature. In particular, an attacker who modifies the integration timestamp can induce a Denial of Service, but in no different manner than already possible with bundle access (e.g. modifying the signature itself such t