xamxte/cve-to-cwe huggingface dataset:
CVE-2024-20935: Vulnerability in the Oracle Installed Base product of Oracle E-Business Suite (component: Engineering Change Order).  Supported versions that are affected are 12.2.3-12.2.13. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Installed Base.  Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Installed Base, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in  unauthorized update, insert or delete access to some of Oracle Installed Base accessible data as well as  unauthorized read access to a subset of Oracle Installed Base accessible data. CVSS 3.1 Base Score 6.1 (Confidentiality and Integrity impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N).
CVE-2024-20947: Vulnerability in the Oracle Common Applications product of Oracle E-Business Suite (component: CRM User Management Framework).  Supported versions that are affected are 12.2.3-12.2.13. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Common Applications.  Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Common Applications, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in  unauthorized update, insert or delete access to some of Oracle Common Applications accessible data as well as  unauthorized read access to a subset of Oracle Common Applications accessible data. CVSS 3.1 Base Score 5.4 (Confidentiality and Integrity impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N).
CVE-2024-20958: Vulnerability in the Oracle Installed Base product of Oracle E-Business Suite (component: Engineering Change Order).  Supported versions that are affected are 12.2.3-12.2.13. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Installed Base.  Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Installed Base, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in  unauthorized update, insert or delete access to some of Oracle Installed Base accessible data as well as  unauthorized read access to a subset of Oracle Installed Base accessible data. CVSS 3.1 Base Score 5.4 (Confidentiality and Integrity impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N).
CVE-2024-20980: Vulnerability in the Oracle BI Publisher product of Oracle Analytics (component: Web Server).  Supported versions that are affected are 6.4.0.0.0 and  7.0.0.0.0. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle BI Publisher.  Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle BI Publisher, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in  unauthorized update, insert or delete access to some of Oracle BI Publisher accessible data as well as  unauthorized read access to a subset of Oracle BI Publisher accessible data. CVSS 3.1 Base Score 5.4 (Confidentiality and Integrity impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N).
CVE-2024-26581: In the Linux kernel, the following vulnerability has been resolved:  netfilter: nft_set_rbtree: skip end interval element from gc  rbtree lazy gc on insert might collect an end interval element that has been just added in this transactions, skip end interval elements that are not yet active.
CVE-2024-1548: A website could have obscured the fullscreen notification by using a dropdown select input element. This could have led to user confusion and possible spoofing attacks. This vulnerability affects Firefox < 123, Firefox ESR < 115.8, and Thunderbird < 115.8.
CVE-2024-1549: If a website set a large custom cursor, portions of the cursor could have overlapped with the permission dialog, potentially resulting in user confusion and unexpected granted permissions. This vulnerability affects Firefox < 123, Firefox ESR < 115.8, and Thunderbird < 115.8.
CVE-2024-26596: In the Linux kernel, the following vulnerability has been resolved:  net: dsa: fix netdev_priv() dereference before check on non-DSA netdevice events  After the blamed commit, we started doing this dereference for every NETDEV_CHANGEUPPER and NETDEV_PRECHANGEUPPER event in the system.  static inline struct dsa_port *dsa_user_to_port(const struct net_device *dev) {  struct dsa_user_priv *p = netdev_priv(dev);   return p->dp; }  Which is obviously bogus, because not all net_devices have a netdev_priv() of type struct dsa_user_priv. But struct dsa_user_priv is fairly small, and p->dp means dereferencing 8 bytes starting with offset 16. Most drivers allocate that much private memory anyway, making our access not fault, and we discard the bogus data quickly afterwards, so this wasn't caught.  But the dummy interface is somewhat special in that it calls alloc_netdev() with a priv size of 0. So every netdev_priv() dereference is invalid, and we get this when we emit a NETDEV_PRECHANGEUPPER event with a VLAN as its new upper:  $ ip link add dummy1 type dummy $ ip link add link dummy1 name dummy1.100 type vlan id 100 [   43.309174] ================================================================== [   43.316456] BUG: KASAN: slab-out-of-bounds in dsa_user_prechangeupper+0x30/0xe8 [   43.323835] Read of size 8 at addr ffff3f86481d2990 by task ip/374 [   43.330058] [   43.342436] Call trace: [   43.366542]  dsa_user_prechangeupper+0x30/0xe8 [   43.371024]  dsa_user_netdevice_event+0xb38/0xee8 [   43.375768]  notifier_call_chain+0xa4/0x210 [   43.379985]  raw_notifier_call_chain+0x24/0x38 [   43.384464]  __netdev_upper_dev_link+0x3ec/0x5d8 [   43.389120]  netdev_upper_dev_link+0x70/0xa8 [   43.393424]  register_vlan_dev+0x1bc/0x310 [   43.397554]  vlan_newlink+0x210/0x248 [   43.401247]  rtnl_newlink+0x9fc/0xe30 [   43.404942]  rtnetlink_rcv_msg+0x378/0x580  Avoid the kernel oops by dereferencing after the type check, as customary.
CVE-2023-5775: The BackWPup plugin for WordPress is vulnerable to Plaintext Storage of Backup Destination Password in all versions up to, and including, 4.0.2. This is due to to the plugin improperly storing backup destination passwords in plaintext. This makes it possible for authenticated attackers, with administrator-level access, to retrieve the password from the password input field in the UI or from the options table where the password is stored.
CVE-2024-26601: In the Linux kernel, the following vulnerability has been resolved:  ext4: regenerate buddy after block freeing failed if under fc replay  This mostly reverts commit 6bd97bf273bd ("ext4: remove redundant mb_regenerate_buddy()") and reintroduces mb_regenerate_buddy(). Based on code in mb_free_blocks(), fast commit replay can end up marking as free blocks that are already marked as such. This causes corruption of the buddy bitmap so we need to regenerate it in that case.
CVE-2024-26602: In the Linux kernel, the following vulnerability has been resolved:  sched/membarrier: reduce the ability to hammer on sys_membarrier  On some systems, sys_membarrier can be very expensive, causing overall slowdowns for everything.  So put a lock on the path in order to serialize the accesses to prevent the ability for this to be called at too high of a frequency and saturate the machine.
CVE-2021-46913: In the Linux kernel, the following vulnerability has been resolved:  netfilter: nftables: clone set element expression template  memcpy() breaks when using connlimit in set elements. Use nft_expr_clone() to initialize the connlimit expression list, otherwise connlimit garbage collector crashes when walking on the list head copy.  [  493.064656] Workqueue: events_power_efficient nft_rhash_gc [nf_tables] [  493.064685] RIP: 0010:find_or_evict+0x5a/0x90 [nf_conncount] [  493.064694] Code: 2b 43 40 83 f8 01 77 0d 48 c7 c0 f5 ff ff ff 44 39 63 3c 75 df 83 6d 18 01 48 8b 43 08 48 89 de 48 8b 13 48 8b 3d ee 2f 00 00 <48> 89 42 08 48 89 10 48 b8 00 01 00 00 00 00 ad de 48 89 03 48 83 [  493.064699] RSP: 0018:ffffc90000417dc0 EFLAGS: 00010297 [  493.064704] RAX: 0000000000000000 RBX: ffff888134f38410 RCX: 0000000000000000 [  493.064708] RDX: 0000000000000000 RSI: ffff888134f38410 RDI: ffff888100060cc0 [  493.064711] RBP: ffff88812ce594a8 R08: ffff888134f38438 R09: 00000000ebb9025c [  493.064714] R10: ffffffff8219f838 R11: 0000000000000017 R12: 0000000000000001 [  493.064718] R13: ffffffff82146740 R14: ffff888134f38410 R15: 0000000000000000 [  493.064721] FS:  0000000000000000(0000) GS:ffff88840e440000(0000) knlGS:0000000000000000 [  493.064725] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [  493.064729] CR2: 0000000000000008 CR3: 00000001330aa002 CR4: 00000000001706e0 [  493.064733] Call Trace: [  493.064737]  nf_conncount_gc_list+0x8f/0x150 [nf_conncount] [  493.064746]  nft_rhash_gc+0x106/0x390 [nf_tables]
CVE-2023-6585: The WP JobSearch WordPress plugin before 2.3.4 does not validate files to be uploaded, which could allow unauthenticated attackers to upload arbitrary files such as PHP on the server
CVE-2023-7165: The JetBackup WordPress plugin before 2.0.9.9 doesn't use index files to prevent public directory listing of sensitive directories in certain configurations, which allows malicious actors to leak backup files.
CVE-2021-46962: In the Linux kernel, the following vulnerability has been resolved:  mmc: uniphier-sd: Fix a resource leak in the remove function  A 'tmio_mmc_host_free()' call is missing in the remove function, in order to balance a 'tmio_mmc_host_alloc()' call in the probe. This is done in the error handling path of the probe, but not in the remove function.  Add the missing call.
CVE-2024-26301: A vulnerability in the web-based management interface of ClearPass Policy Manager could allow a remote attacker authenticated with low privileges to access sensitive information. A successful exploit allows an attacker to retrieve information which could be used to potentially gain further access to network services supported by ClearPass Policy Manager.
CVE-2020-36778: In the Linux kernel, the following vulnerability has been resolved:  i2c: xiic: fix reference leak when pm_runtime_get_sync fails  The PM reference count is not expected to be incremented on return in xiic_xfer and xiic_i2c_remove.  However, pm_runtime_get_sync will increment the PM reference count even failed. Forgetting to putting operation will result in a reference leak here.  Replace it with pm_runtime_resume_and_get to keep usage counter balanced.
CVE-2020-36779: In the Linux kernel, the following vulnerability has been resolved:  i2c: stm32f7: fix reference leak when pm_runtime_get_sync fails  The PM reference count is not expected to be incremented on return in these stm32f7_i2c_xx serious functions.  However, pm_runtime_get_sync will increment the PM reference count even failed. Forgetting to putting operation will result in a reference leak here.  Replace it with pm_runtime_resume_and_get to keep usage counter balanced.
CVE-2020-36780: In the Linux kernel, the following vulnerability has been resolved:  i2c: sprd: fix reference leak when pm_runtime_get_sync fails  The PM reference count is not expected to be incremented on return in sprd_i2c_master_xfer() and sprd_i2c_remove().  However, pm_runtime_get_sync will increment the PM reference count even failed. Forgetting to putting operation will result in a reference leak here.  Replace it with pm_runtime_resume_and_get to keep usage counter balanced.
CVE-2020-36781: In the Linux kernel, the following vulnerability has been resolved:  i2c: imx: fix reference leak when pm_runtime_get_sync fails  In i2c_imx_xfer() and i2c_imx_remove(), the pm reference count is not expected to be incremented on return.  However, pm_runtime_get_sync will increment pm reference count even failed. Forgetting to putting operation will result in a reference leak here.  Replace it with pm_runtime_resume_and_get to keep usage counter balanced.
CVE-2020-36782: In the Linux kernel, the following vulnerability has been resolved:  i2c: imx-lpi2c: fix reference leak when pm_runtime_get_sync fails  The PM reference count is not expected to be incremented on return in lpi2c_imx_master_enable.  However, pm_runtime_get_sync will increment the PM reference count even failed. Forgetting to putting operation will result in a reference leak here.  Replace it with pm_runtime_resume_and_get to keep usage counter balanced.
CVE-2020-36783: In the Linux kernel, the following vulnerability has been resolved:  i2c: img-scb: fix reference leak when pm_runtime_get_sync fails  The PM reference count is not expected to be incremented on return in functions img_i2c_xfer and img_i2c_init.  However, pm_runtime_get_sync will increment the PM reference count even failed. Forgetting to putting operation will result in a reference leak here.  Replace it with pm_runtime_resume_and_get to keep usage counter balanced.
CVE-2020-36784: In the Linux kernel, the following vulnerability has been resolved:  i2c: cadence: fix reference leak when pm_runtime_get_sync fails  The PM reference count is not expected to be incremented on return in functions cdns_i2c_master_xfer and cdns_reg_slave.  However, pm_runtime_get_sync will increment pm usage counter even failed. Forgetting to putting operation will result in a reference leak here.  Replace it with pm_runtime_resume_and_get to keep usage counter balanced.
CVE-2021-46977: In the Linux kernel, the following vulnerability has been resolved:  KVM: VMX: Disable preemption when probing user return MSRs  Disable preemption when probing a user return MSR via RDSMR/WRMSR.  If the MSR holds a different value per logical CPU, the WRMSR could corrupt the host's value if KVM is preempted between the RDMSR and WRMSR, and then rescheduled on a different CPU.  Opportunistically land the helper in common x86, SVM will use the helper in a future commit.
CVE-2021-46990: In the Linux kernel, the following vulnerability has been resolved:  powerpc/64s: Fix crashes when toggling entry flush barrier  The entry flush mitigation can be enabled/disabled at runtime via a debugfs file (entry_flush), which causes the kernel to patch itself to enable/disable the relevant mitigations.  However depending on which mitigation we're using, it may not be safe to do that patching while other CPUs are active. For example the following crash:    sleeper[15639]: segfault (11) at c000000000004c20 nip c000000000004c20 lr c000000000004c20  Shows that we returned to userspace with a corrupted LR that points into the kernel, due to executing the partially patched call to the fallback entry flush (ie. we missed the LR restore).  Fix it by doing the patching under stop machine. The CPUs that aren't doing the patching will be spinning in the core of the stop machine logic. That is currently sufficient for our purposes, because none of the patching we do is to that code or anywhere in the vicinity.
CVE-2021-47000: In the Linux kernel, the following vulnerability has been resolved:  ceph: fix inode leak on getattr error in __fh_to_dentry
CVE-2021-47011: In the Linux kernel, the following vulnerability has been resolved:  mm: memcontrol: slab: fix obtain a reference to a freeing memcg  Patch series "Use obj_cgroup APIs to charge kmem pages", v5.  Since Roman's series "The new cgroup slab memory controller" applied. All slab objects are charged with the new APIs of obj_cgroup.  The new APIs introduce a struct obj_cgroup to charge slab objects.  It prevents long-living objects from pinning the original memory cgroup in the memory.  But there are still some corner objects (e.g.  allocations larger than order-1 page on SLUB) which are not charged with the new APIs.  Those objects (include the pages which are allocated from buddy allocator directly) are charged as kmem pages which still hold a reference to the memory cgroup.  E.g.  We know that the kernel stack is charged as kmem pages because the size of the kernel stack can be greater than 2 pages (e.g.  16KB on x86_64 or arm64).  If we create a thread (suppose the thread stack is charged to memory cgroup A) and then move it from memory cgroup A to memory cgroup B.  Because the kernel stack of the thread hold a reference to the memory cgroup A.  The thread can pin the memory cgroup A in the memory even if we remove the cgroup A.  If we want to see this scenario by using the following script.  We can see that the system has added 500 dying cgroups (This is not a real world issue, just a script to show that the large kmallocs are charged as kmem pages which can pin the memory cgroup in the memory).   #!/bin/bash   cat /proc/cgroups | grep memory   cd /sys/fs/cgroup/memory  echo 1 > memory.move_charge_at_immigrate   for i in range{1..500}  do   mkdir kmem_test   echo $$ > kmem_test/cgroup.procs   sleep 3600 &   echo $$ > cgroup.procs   echo `cat kmem_test/cgroup.procs` > cgroup.procs   rmdir kmem_test  done   cat /proc/cgroups | grep memory  This patchset aims to make those kmem pages to drop the reference to memory cgroup by using the APIs of obj_cgroup.  Finally, we can see that the number of the dying cgroups will not increase if we run the above test script.  This patch (of 7):  The rcu_read_lock/unlock only can guarantee that the memcg will not be freed, but it cannot guarantee the success of css_get (which is in the refill_stock when cached memcg changed) to memcg.    rcu_read_lock()   memcg = obj_cgroup_memcg(old)   __memcg_kmem_uncharge(memcg)       refill_stock(memcg)           if (stock->cached != memcg)               // css_get can change the ref counter from 0 back to 1.               css_get(&memcg->css)   rcu_read_unlock()  This fix is very like the commit:    eefbfa7fd678 ("mm: memcg/slab: fix use after free in obj_cgroup_charge")  Fix this by holding a reference to the memcg which is passed to the __memcg_kmem_uncharge() before calling __memcg_kmem_uncharge().
CVE-2021-47051: In the Linux kernel, the following vulnerability has been resolved:  spi: fsl-lpspi: Fix PM reference leak in lpspi_prepare_xfer_hardware()  pm_runtime_get_sync will increment pm usage counter even it failed. Forgetting to putting operation will result in reference leak here. Fix it by replacing it with pm_runtime_resume_and_get to keep usage counter balanced.
CVE-2023-6922: The Under Construction / Maintenance Mode from Acurax plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and including, 2.6 via the 'acx_csma_subscribe_ajax' function. This can allow authenticated attackers to extract sensitive data such as names and email addresses of subscribed visitors.
CVE-2024-0680: The WP Private Content Plus plugin for WordPress is vulnerable to information disclosure in all versions up to, and including, 3.6. This is due to the plugin not properly restricting access to posts via the REST API when a page has been made private. This makes it possible for unauthenticated attackers to view protected posts.
CVE-2024-0682: The Page Restrict plugin for WordPress is vulnerable to information disclosure in all versions up to, and including, 2.5.5. This is due to the plugin not properly restricting access to posts via the REST API when a page has been made private. This makes it possible for unauthenticated attackers to view protected posts.
CVE-2024-0975: The WordPress Access Control plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 4.0.13  via the REST API. This makes it possible for unauthenticated attackers to bypass the plugin's "Make Website Members Only" feature (when unset) and view restricted page and post content.
CVE-2024-1136: The Coming Soon Page & Maintenance Mode plugin for WordPress is vulnerable to unauthorized access of data due to an improperly implemented URL check in the wpsm_coming_soon_redirect function in all versions up to, and including, 2.2.1. This makes it possible for unauthenticated attackers to view a site with maintenance mode or coming-soon mode enabled to view the site's content.
CVE-2024-1476: The Under Construction / Maintenance Mode from Acurax plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.6 via the REST API. This makes it possible for unauthenticated attackers to obtain the contents of posts and pages when maintenance mode is active thus bypassing the protection provided by the plugin.
CVE-2023-43769: An issue was discovered in Couchbase Server through 7.1.4 before 7.1.5 and before 7.2.1. There are Unauthenticated RMI Service Ports Exposed in Analytics.
CVE-2023-6565: The InfiniteWP Client plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.12.3 via the multi-call backup option. This makes it possible for unauthenticated attackers to extract sensitive data from a temporary SQL file via repeated GET requests during the limited time window of the backup process.
CVE-2024-0616: The Passster – Password Protect Pages and Content plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 4.2.6.2 via API. This makes it possible for unauthenticated attackers to obtain post titles, slugs, IDs, content and other metadata including passwords of password-protected posts and pages.
CVE-2024-0620: The PPWP – Password Protect Pages plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.8.9 via API. This makes it possible for unauthenticated attackers to obtain post titles, IDs, slugs as well as other information including for password-protected posts.
CVE-2024-0978: The My Private Site plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.0.14 via the REST API. This makes it possible for unauthenticated attackers to bypass the plugin's site privacy feature and view restricted page and post content.
CVE-2024-1217: The Contact Form builder with drag & drop for WordPress – Kali Forms plugin for WordPress is vulnerable to unauthorized plugin deactivation due to a missing capability check on the await_plugin_deactivation function in all versions up to, and including, 2.3.41. This makes it possible for authenticated attackers, with subscriber access or higher, to deactivate any active plugins.
CVE-2024-1218: The Contact Form builder with drag & drop for WordPress – Kali Forms plugin for WordPress is vulnerable to unauthorized access and modification of data via API due to an inconsistent capability check on several REST endpoints in all versions up to, and including, 2.3.41. This makes it possible for authenticated attackers, with contributor access and higher, to obtain access to or modify forms or entries.
CVE-2024-1294: The Sunshine Photo Cart: Free Client Galleries for Photographers plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.0.24 via the 'invoice'. This makes it possible for unauthenticated attackers to extract sensitive data including customer email and physical addresses.
CVE-2024-1472: The WP Maintenance plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 6.1.6 via the REST API. This makes it possible for unauthenticated attackers to bypass the plugin's maintenance mode obtain post and page content via REST API.
CVE-2024-1475: The Coming Soon Maintenance Mode plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.0.5 via the REST API. This makes it possible for unauthenticated attackers to obtain post and page content thus bypassing the protection provided by the plugin.
CVE-2024-26548: An issue in vivotek Network Camera v.FD8166A-VVTK-0204j allows a remote attacker to execute arbitrary code via a crafted payload to the upload_file.cgi component.