deardaniel/secdata-raw huggingface dataset:
CVE: CVE-2025-21973
Published: 2025-04-01
Description: In the Linux kernel, the following vulnerability has been resolved:

eth: bnxt: fix kernel panic in the bnxt_get_queue_stats{rx | tx}

When qstats-get operation is executed, callbacks of netdev_stats_ops
are called. The bnxt_get_queue_stats{rx | tx} collect per-queue stats
from sw_stats in the rings.
But {rx | tx | cp}_ring are allocated when the interface is up.
So, these rings are not allocated when the interface is down.

The qstats-get is allowed even if the interface is down. However,
the bnxt_get_queue_stats{rx | tx}() accesses cp_ring and tx_ring
without null check.
So, it needs to avoid accessing rings if the interface is down.

Reproducer:
 ip link set $interface down
 ./cli.py --spec netdev.yaml --dump qstats-get
OR
 ip link set $interface down
 python ./stats.py

Splat looks like:
 BUG: kernel NULL pointer dereference, address: [PII_REDACTED]
 #PF: supervisor read access in kernel mode
 #PF: error_code(0x0000) - not-present page
 PGD 1680fa067 P4D 1680fa067 PUD 16be3b067 PMD 0
 Oops: Oops: 0000 [#1] PREEMPT SMP NOPTI
 CPU: 0 UID: 0 PID: 1495 Comm: python3 Not tainted 6.14.0-rc4+ #32 5cd0f999d5a15c574ac72b3e4b907341
 Hardware name: ASUS System Product Name/PRIME Z690-P D4, BIOS 0603 11/01/2021
 RIP: 0010:bnxt_get_queue_stats_rx+0xf/0x70 [bnxt_en]
 Code: c6 87 b5 18 00 00 02 eb a2 66 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 44 01
 RSP: 0018:ffffabef43cdb7e0 EFLAGS: 00010282
 RAX: [PII_REDACTED] RBX: ffffffffc04c8710 RCX: [PII_REDACTED]
 RDX: ffffabef43cdb858 RSI: [PII_REDACTED] RDI: ffff8d504e850000
 RBP: ffff8d506c9f9c00 R08: [PII_REDACTED] R09: ffff8d506bcd901c
 R10: [PII_REDACTED] R11: ffff8d506bcd9000 R12: [PII_REDACTED]
 R13: ffffabef43cdb8c0 R14: ffff8d504e850000 R15: [PII_REDACTED]
 FS:  00007f2c5462b080(0000) GS:ffff8d575f600000(0000) knlGS:[PII_REDACTED]
 CS:  0010 DS: 0000 ES: 0000 CR0: [PII_REDACTED]
 CR2: [PII_REDACTED] CR3:[PII_REDACTED]fd0000 CR4:[PII_REDACTED]7506f0
 PKRU: 55555554
 Call Trace:
  <TASK>
  ? __die+0x20/0x70
  ? page_fault_oops+0x15a/0x460
  ? sched_balance_find_src_group+0x58d/0xd10
  ? exc_page_fault+0x6e/0x180
  ? asm_exc_page_fault+0x22/0x30
  ? bnxt_get_queue_stats_rx+0xf/0x70 [bnxt_en cdd546fd48563c280cfd30e9647efa420db07bf1]
  netdev_nl_stats_by_netdev+0x2b1/0x4e0
  ? xas_load+0x9/0xb0
  ? xas_find+0x183/0x1d0
  ? xa_find+0x8b/0xe0
  netdev_nl_qstats_get_dumpit+0xbf/0x1e0
  genl_dumpit+0x31/0x90
  netlink_dump+0x1a8/0x360
CVSS Score: 7.1 (HIGH)
References: https://git.kernel.org/stable/c/adb830085f0fc3a09a0fc8b64fed2e7c8d244665; https://git.kernel.org/stable/c/f059a0fd733078c3832fd0f3a3037aa5975d3d36; https://git.kernel.org/stable/c/f09af5fdfbd9b0fcee73aab1116904c53b199e97
CVE: CVE-2025-21974
Published: 2025-04-01
Description: In the Linux kernel, the following vulnerability has been resolved:

eth: bnxt: return fail if interface is down in bnxt_queue_mem_alloc()

The bnxt_queue_mem_alloc() is called to allocate new queue memory when
a queue is restarted.
It internally accesses rx buffer descriptor corresponding to the index.
The rx buffer descriptor is allocated and set when the interface is up
and it's freed when the interface is down.
So, if queue is restarted if interface is down, kernel panic occurs.

Splat looks like:
 BUG: unable to handle page fault for address:[PII_REDACTED]00b240
 #PF: supervisor read access in kernel mode
 #PF: error_code(0x0000) - not-present page
 PGD 0 P4D 0
 Oops: Oops: 0000 [#1] PREEMPT SMP NOPTI
 CPU: 3 UID: 0 PID: 1563 Comm: ncdevmem2 Not tainted 6.14.0-rc2+ #9 844ddba6e7c459cafd0bf4db9a3198e
 Hardware name: ASUS System Product Name/PRIME Z690-P D4, BIOS 0603 11/01/2021
 RIP: 0010:bnxt_queue_mem_alloc+0x3f/0x4e0 [bnxt_en]
 Code: 41 54 4d 89 c4 4d 69 c0 c0 05 00 00 55 48 89 f5 53 48 89 fb 4c 8d b5 40 05 00 00 48 83 ec 15
 RSP: 0018:ffff9dcc83fef9e8 EFLAGS: 00010202
 RAX: ffffffffc0457720 RBX: ffff934ed8d40000 RCX: [PII_REDACTED]
 RDX:[PII_REDACTED]00001f RSI: ffff934ea508f800 RDI: ffff934ea508f808
 RBP: ffff934ea508f800 R08:[PII_REDACTED]00b240 R09: ffff934e84f4b000
 R10: ffff9dcc83fefa30 R11: ffff934e84f4b000 R12:[PII_REDACTED]00001f
 R13: ffff934ed8d40ac0 R14: ffff934ea508fd40 R15: ffff934e84f4b000
 FS:  00007fa73888c740(0000) GS:ffff93559f780000(0000) knlGS:[PII_REDACTED]
 CS:  0010 DS: 0000 ES: 0000 CR0: [PII_REDACTED]
 CR2:[PII_REDACTED]00b240 CR3:[PII_REDACTED]a2e000 CR4:[PII_REDACTED]7506f0
 PKRU: 55555554
 Call Trace:
  <TASK>
  ? __die+0x20/0x70
  ? page_fault_oops+0x15a/0x460
  ? exc_page_fault+0x6e/0x180
  ? asm_exc_page_fault+0x22/0x30
  ? __pfx_bnxt_queue_mem_alloc+0x10/0x10 [bnxt_en 7f85e76f4d724ba07471d7e39d9e773aea6597b7]
  ? bnxt_queue_mem_alloc+0x3f/0x4e0 [bnxt_en 7f85e76f4d724ba07471d7e39d9e773aea6597b7]
  netdev_rx_queue_restart+0xc5/0x240
  net_devmem_bind_dmabuf_to_queue+0xf8/0x200
  netdev_nl_bind_rx_doit+0x3a7/0x450
  genl_family_rcv_msg_doit+0xd9/0x130
  genl_rcv_msg+0x184/0x2b0
  ? __pfx_netdev_nl_bind_rx_doit+0x10/0x10
  ? __pfx_genl_rcv_msg+0x10/0x10
  netlink_rcv_skb+0x54/0x100
  genl_rcv+0x24/0x40
...
CVSS Score: 5.5 (MEDIUM)
References: https://git.kernel.org/stable/c/14eb5f0d6554653f4b159835c2f77b2a9bd7e9be; https://git.kernel.org/stable/c/ca2456e073957781e1184de68551c65161b2bd30; https://git.kernel.org/stable/c/d3b8cd8a8a98c7c83a693bd651f1919be36a57f2
CVE: CVE-2025-21975
Published: 2025-04-01
Description: In the Linux kernel, the following vulnerability has been resolved:

net/mlx5: handle errors in mlx5_chains_create_table()

In mlx5_chains_create_table(), the return value of mlx5_get_fdb_sub_ns()
and mlx5_get_flow_namespace() must be checked to prevent NULL pointer
dereferences. If either function fails, the function should log error
message with mlx5_core_warn() and return error pointer.
CVSS Score: 5.5 (MEDIUM)
CWE: CWE-476
References: https://git.kernel.org/stable/c/093b4aaec97ec048623e3fe1e516fc45a954d412; https://git.kernel.org/stable/c/1598307c914ba3d2642a2b03d1ff11efbdb7c6c2; https://git.kernel.org/stable/c/15bdd93728369b2c8942a8e5d549d4b5dc04a2d9
CVE: CVE-2025-21976
Published: 2025-04-01
Description: In the Linux kernel, the following vulnerability has been resolved:

fbdev: hyperv_fb: Allow graceful removal of framebuffer

When a Hyper-V framebuffer device is unbind, hyperv_fb driver tries to
release the framebuffer forcefully. If this framebuffer is in use it
produce the following WARN and hence this framebuffer is never released.

[   44.111220] WARNING: CPU: 35 PID: 1882 at drivers/video/fbdev/core/fb_info.c:70 framebuffer_release+0x2c/0x40
< snip >
[   44.111289] Call Trace:
[   44.111290]  <TASK>
[   44.111291]  ? show_regs+0x6c/0x80
[   44.111295]  ? __warn+0x8d/0x150
[   44.111298]  ? framebuffer_release+0x2c/0x40
[   44.111300]  ? report_bug+0x182/0x1b0
[   44.111303]  ? handle_bug+0x6e/0xb0
[   44.111306]  ? exc_invalid_op+0x18/0x80
[   44.111308]  ? asm_exc_invalid_op+0x1b/0x20
[   44.111311]  ? framebuffer_release+0x2c/0x40
[   44.111313]  ? hvfb_remove+0x86/0xa0 [hyperv_fb]
[   44.111315]  vmbus_remove+0x24/0x40 [hv_vmbus]
[   44.111323]  device_remove+0x40/0x80
[   44.111325]  device_release_driver_internal+0x20b/0x270
[   44.111327]  ? bus_find_device+0xb3/0xf0

Fix this by moving the release of framebuffer and assosiated memory
to fb_ops.fb_destroy function, so that framebuffer framework handles
it gracefully.

While we fix this, also replace manual registrations/unregistration of
framebuffer with devm_register_framebuffer.
CVSS Score: 5.5 (MEDIUM)
References: https://git.kernel.org/stable/c/4545e2aa121aea304d33903099c03e29ed4fe50a; https://git.kernel.org/stable/c/a7b583dc99c6cf4a96877017be1d08247e1ef2c7; https://git.kernel.org/stable/c/ea2f45ab0e53b255f72c85ccd99e2b394fc5fceb
CVE: CVE-2025-21978
Published: 2025-04-01
Description: In the Linux kernel, the following vulnerability has been resolved:

drm/hyperv: Fix address space leak when Hyper-V DRM device is removed

When a Hyper-V DRM device is probed, the driver allocates MMIO space for
the vram, and maps it cacheable. If the device removed, or in the error
path for device probing, the MMIO space is released but no unmap is done.
Consequently the kernel address space for the mapping is leaked.

Fix this by adding iounmap() calls in the device removal path, and in the
error path during device probing.
CVSS Score: 5.5 (MEDIUM)
CWE: CWE-401
References: https://git.kernel.org/stable/c/158242b56bf465a73e1edeac0fe828a8acad4499; https://git.kernel.org/stable/c/24f1bbfb2be77dad82489c1468bbb14312aab129; https://git.kernel.org/stable/c/ad27b4a51495490b815580d9b935e8eee14d1a9c
CVE: CVE-2025-21979
Published: 2025-04-01
Description: In the Linux kernel, the following vulnerability has been resolved:

wifi: cfg80211: cancel wiphy_work before freeing wiphy

A wiphy_work can be queued from the moment the wiphy is allocated and
initialized (i.e. wiphy_new_nm). When a wiphy_work is queued, the
rdev::wiphy_work is getting queued.

If wiphy_free is called before the rdev::wiphy_work had a chance to run,
the wiphy memory will be freed, and then when it eventally gets to run
it'll use invalid memory.

Fix this by canceling the work before freeing the wiphy.
CVSS Score: 7.8 (HIGH)
CWE: CWE-416, CWE-416
References: https://git.kernel.org/stable/c/0272d4af7f92997541d8bbf4c51918b93ded6ee2; https://git.kernel.org/stable/c/72d520476a2fab6f3489e8388ab524985d6c4b90; https://git.kernel.org/stable/c/75d262ad3c36d52852d764588fcd887f0fcd9138
CVE: CVE-2025-21980
Published: 2025-04-01
Description: In the Linux kernel, the following vulnerability has been resolved:

sched: address a potential NULL pointer dereference in the GRED scheduler.

If kzalloc in gred_init returns a NULL pointer, the code follows the
error handling path, invoking gred_destroy. This, in turn, calls
gred_offload, where memset could receive a NULL pointer as input,
potentially leading to a kernel crash.

When table->opt is NULL in gred_init(), gred_change_table_def()
is not called yet, so it is not necessary to call ->ndo_setup_tc()
in gred_offload().
CVSS Score: 5.5 (MEDIUM)
CWE: CWE-476, CWE-476
References: https://git.kernel.org/stable/c/0f0a152957d64ce45b4c27c687e7d087e8f45079; https://git.kernel.org/stable/c/115ef44a98220fddfab37a39a19370497cd718b9; https://git.kernel.org/stable/c/5f996b4f80c2cef1f9c77275055e7fcba44c9199
CVE: CVE-2025-21981
Published: 2025-04-01
Description: In the Linux kernel, the following vulnerability has been resolved:

ice: fix memory leak in aRFS after reset

Fix aRFS (accelerated Receive Flow Steering) structures memory leak by
adding a checker to verify if aRFS memory is already allocated while
configuring VSI. aRFS objects are allocated in two cases:
- as part of VSI initialization (at probe), and
- as part of reset handling

However, VSI reconfiguration executed during reset involves memory
allocation one more time, without prior releasing already allocated
resources. This led to the memory leak with the following signature:

[root@os-delivery ~]# cat /sys/kernel/debug/kmemleak
unreferenced object 0xff3c1ca7252e6000 (size 8192):
  comm "kworker/0:0", pid 8, jiffies[PII_REDACTED]
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace (crc 0):
    [<ffffffff991ec485>] __kmalloc_cache_noprof+0x275/0x340
    [<ffffffffc0a6e06a>] ice_init_arfs+0x3a/0xe0 [ice]
    [<ffffffffc09f1027>] ice_vsi_cfg_def+0x607/0x850 [ice]
    [<ffffffffc09f244b>] ice_vsi_setup+0x5b/0x130 [ice]
    [<ffffffffc09c2131>] ice_init+0x1c1/0x460 [ice]
    [<ffffffffc09c64af>] ice_probe+0x2af/0x520 [ice]
    [<ffffffff994fbcd3>] local_pci_probe+0x43/0xa0
    [<ffffffff98f07103>] work_for_cpu_fn+0x13/0x20
    [<ffffffff98f0b6d9>] process_one_work+0x179/0x390
    [<ffffffff98f0c1e9>] worker_thread+0x239/0x340
    [<ffffffff98f14abc>] kthread+0xcc/0x100
    [<ffffffff98e45a6d>] ret_from_fork+0x2d/0x50
    [<ffffffff98e083ba>] ret_from_fork_asm+0x1a/0x30
    ...
CVSS Score: 5.5 (MEDIUM)
CWE: CWE-401, CWE-401
References: https://git.kernel.org/stable/c/23d97f18901ef5e4e264e3b1777fe65c760186b5; https://git.kernel.org/stable/c/3b27e6e10a32589fcd293b8933ab6de9387a460e; https://git.kernel.org/stable/c/5d30d256661fc11b6e73fac6c3783a702e1006a3
CVE: CVE-2025-21982
Published: 2025-04-01
Description: In the Linux kernel, the following vulnerability has been resolved:

pinctrl: nuvoton: npcm8xx: Add NULL check in npcm8xx_gpio_fw

devm_kasprintf() calls can return null pointers on failure.
But the return values were not checked in npcm8xx_gpio_fw().
Add NULL check in npcm8xx_gpio_fw(), to handle kernel NULL
pointer dereference error.
CVSS Score: 5.5 (MEDIUM)
CWE: CWE-476, CWE-476
References: https://git.kernel.org/stable/c/6a08a86e5aff8e65368ccd463348fdda26100821; https://git.kernel.org/stable/c/a585f6ea42ec259a9a57e3e2580fa527c92187d0; https://git.kernel.org/stable/c/acf40ab42799e4ae1397ee6f5c5941092d66f999
CVE: CVE-2025-21983
Published: 2025-04-01
Description: In the Linux kernel, the following vulnerability has been resolved:

mm/slab/kvfree_rcu: Switch to WQ_MEM_RECLAIM wq

Currently kvfree_rcu() APIs use a system workqueue which is
"system_unbound_wq" to driver RCU machinery to reclaim a memory.

Recently, it has been noted that the following kernel warning can
be observed:

<snip>
workqueue: WQ_MEM_RECLAIM nvme-wq:nvme_scan_work is flushing !WQ_MEM_RECLAIM events_unbound:kfree_rcu_work
  WARNING: CPU: 21 PID: 330 at kernel/workqueue.c:3719 check_flush_dependency+0x112/0x120
  Modules linked in: intel_uncore_frequency(E) intel_uncore_frequency_common(E) skx_edac(E) ...
  CPU: 21 UID: 0 PID: 330 Comm: kworker/u144:6 Tainted: G            E      6.13.2-0_g925d379822da #1
  Hardware name: Wiwynn Twin Lakes MP/Twin Lakes Passive MP, BIOS YMM20 02/01/2023
  Workqueue: nvme-wq nvme_scan_work
  RIP: 0010:check_flush_dependency+0x112/0x120
  Code: 05 9a 40 14 02 01 48 81 c6 c0 00 00 00 48 8b 50 18 48 81 c7 c0 00 00 00 48 89 f9 48 ...
  RSP: 0018:ffffc90000df7bd8 EFLAGS: 00010082
  RAX:[PII_REDACTED]00006a RBX: ffffffff81622390 RCX: [PII_REDACTED]
  RDX: 00000000fffeffff RSI:[PII_REDACTED]57ffa8 RDI: ffff88907f960c88
  RBP: [PII_REDACTED] R08: ffffffff83068e50 R09:[PII_REDACTED]02fffd
  R10: [PII_REDACTED] R11: [PII_REDACTED] R12: ffff8881001a4400
  R13: [PII_REDACTED] R14: ffff88907f420fb8 R15: [PII_REDACTED]
  FS:  [PII_REDACTED](0000) GS:ffff88907f940000(0000) knlGS:[PII_REDACTED]
  CR2: 00007f60c3001000 CR3: 000000107d010005 CR4:[PII_REDACTED]7726f0
  PKRU: 55555554
  Call Trace:
   <TASK>
   ? __warn+0xa4/0x140
   ? check_flush_dependency+0x112/0x120
   ? report_bug+0xe1/0x140
   ? check_flush_dependency+0x112/0x120
   ? handle_bug+0x5e/0x90
   ? exc_invalid_op+0x16/0x40
   ? asm_exc_invalid_op+0x16/0x20
   ? timer_recalc_next_expiry+0x190/0x190
   ? check_flush_dependency+0x112/0x120
   ? check_flush_dependency+0x112/0x120
   __flush_work.llvm[PII_REDACTED]586177030+0x174/0x2c0
   flush_rcu_work+0x28/0x30
   kvfree_rcu_barrier+0x12f/0x160
   kmem_cache_destroy+0x18/0x120
   bioset_exit+0x10c/0x150
   disk_release.llvm[PII_REDACTED]264378178+0x61/0xd0
   device_release+0x4f/0x90
   kobject_put+0x95/0x180
   nvme_put_ns+0x23/0xc0
   nvme_remove_invalid_namespaces+0xb3/0xd0
   nvme_scan_work+0x342/0x490
   process_scheduled_works+0x1a2/0x370
   worker_thread+0x2ff/0x390
   ? pwq_release_workfn+0x1e0/0x1e0
   kthread+0xb1/0xe0
   ? __kthread_parkme+0x70/0x70
   ret_from_fork+0x30/0x40
   ? __kthread_parkme+0x70/0x70
   ret_from_fork_asm+0x11/0x20
   </TASK>
  ---[ end trace [PII_REDACTED] ]---
<snip>

To address this switch to use of independent WQ_MEM_RECLAIM
workqueue, so the rules are not violated from workqueue framework
point of view.

Apart of that, since kvfree_rcu() does reclaim memory it is worth
to go with WQ_MEM_RECLAIM type of wq because it is designed for
this purpose.
CVSS Score: 7.8 (HIGH)
References: https://git.kernel.org/stable/c/656e35bf66a11e1adde44c4c12050086dc39f241; https://git.kernel.org/stable/c/a74979dce9e9c61f6d797c[PII_REDACTED]c4d8dc63; https://git.kernel.org/stable/c/dfd3df31c9db752234d7d2e09bef2aeabb643ce4
CVE: CVE-2025-21985
Published: 2025-04-01
Description: In the Linux kernel, the following vulnerability has been resolved:

drm/amd/display: Fix out-of-bound accesses

[WHAT & HOW]
hpo_stream_to_link_encoder_mapping has size MAX_HPO_DP2_ENCODERS(=4),
but location can have size up to 6. As a result, it is necessary to
check location against MAX_HPO_DP2_ENCODERS.

Similiarly, disp_cfg_stream_location can be used as an array index which
should be 0..5, so the ASSERT's conditions should be less without equal.
CVSS Score: 7.1 (HIGH)
CWE: CWE-125
References: https://git.kernel.org/stable/c/36793d90d76f667d26c6dd025571481ee0c96abc; https://git.kernel.org/stable/c/8adbb2a98b00926315fd513b5fe2596b5716b82d; https://git.kernel.org/stable/c/9aedc776b11038f04f4641241bb7e877781e4aa4
CVE: CVE-2025-25041
Published: 2025-04-01
Description: A vulnerability in the HPE Aruba Networking Virtual Intranet Access (VIA) client could allow malicious users to overwrite arbitrary files as NT AUTHORITY\SYSTEM (root). A successful exploit could allow the creation of a Denial-of-Service (DoS) condition affecting the Microsoft Windows Operating System. This vulnerability does not affect Linux and Android based clients.
CVSS Score: 5.5 (MEDIUM)
CWE: CWE-732
References: https://support.hpe.com/hpesc/public/docDisplay?docId=hpesbnw04841en_us&docLocale=en_US
CVE: CVE-2025-27829
Published: 2025-04-01
Description: An issue was discovered in Stormshield Network Security (SNS) 4.3.x before 4.3.35. If multicast streams are enabled on different interfaces, it may be possible to interrupt multicast traffic on some of these interfaces. That could result in a denial of the multicast routing service on the firewall.
CVSS Score: 7.3 (HIGH)
CWE: CWE-400
References: https://advisories.stormshield.eu/2025-002/
CVE: CVE-2025-28131
Published: 2025-04-01
Description: A Broken Access Control vulnerability in Nagios Network Analyzer 2024R1.0.3 allows low-privilege users with "Read-Only" access to perform administrative actions, including stopping system services and deleting critical resources. This flaw arises due to improper authorization enforcement, enabling unauthorized modifications that compromise system integrity and availability.
CVSS Score: 4.6 (MEDIUM)
CWE: CWE-285
References: https://github.com/harshal79/Privilege-Escalation-in-Nagios-Network-Analyzer.git; https://www.nagios.com/changelog/#network-analyzer
CVE: CVE-2025-28132
Published: 2025-04-01
Description: A session management flaw in Nagios Network Analyzer 2024R1.0.3 allows an attacker to reuse session tokens even after a user logs out, leading to unauthorized access and account takeover. This occurs due to insufficient session expiration, where session tokens remain valid beyond logout, allowing an attacker to impersonate users and perform actions on their behalf.
CVSS Score: 4.6 (MEDIUM)
CWE: CWE-613
References: https://github.com/harshal79/Insufficient-Session-Expiration.git; https://www.nagios.com/changelog/#network-analyzer
CVE: CVE-2018-1472
Published: 2025-04-01
Description: Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it was erroneously associated with an open source vulnerability by another vendor.
CVE: CVE-2025-29208
Published: 2025-04-01
Description: CodeZips Gym Management System v1.0 is vulnerable to SQL injection in the name parameter within /dashboard/admin/deleteroutine.php.
CVSS Score: 6.5 (MEDIUM)
CWE: CWE-89
References: https://github.com/LLz-7/CVE/blob/main/CVE_1.md
CVE: CVE-2025-26054
Published: 2025-04-01
Description: Infinxt iEdge 100 2.1.32 is vulnerable to Cross Site Scripting (XSS) via the "Description" field during LAN configuration.
CVSS Score: 5.4 (MEDIUM)
CWE: CWE-79
References: https://github.com/rohan-pt/CVE-2025-26054; https://github.com/rohan-pt/CVE-2025-26054
CVE: CVE-2025-26055
Published: 2025-04-01
Description: An OS Command Injection vulnerability exists in the Infinxt iEdge 100 2.1.32 Troubleshoot module, specifically in the tracertVal parameter of the Tracert function.
CVSS Score: 6.5 (MEDIUM)
CWE: CWE-78
References: https://github.com/rohan-pt/CVE-2025-26055
CVE: CVE-2025-26056
Published: 2025-04-01
Description: A command injection vulnerability exists in the Infinxt iEdge 100 2.1.32 in the Troubleshoot module "MTR" functionality. The vulnerability is due to improper validation of user-supplied input in the mtrIp parameter. An attacker can exploit this flaw to execute arbitrary operating system commands on the underlying system with the same privileges as the web application process.
CVSS Score: 5.4 (MEDIUM)
CWE: CWE-77
References: https://github.com/rohan-pt/CVE-2025-26056
CVE: CVE-2025-31137
Published: 2025-04-01
Description: React Router is a multi-strategy router for React bridging the gap from React 18 to React 19. There is a vulnerability in Remix/React Router that affects all Remix 2 and React Router 7 consumers using the Express adapter. Basically, this vulnerability allows anyone to spoof the URL used in an incoming Request by putting a URL pathname in the port section of a URL that is part of a Host or X-Forwarded-Host header sent to a Remix/React Router request handler. This issue has been patched and released in Remix 2.16.3 and React Router 7.4.1.
CVSS Score: 7.5 (HIGH)
CWE: CWE-444
References: https://github.com/remix-run/react-router/security/advisories/GHSA-4q56-crqp-v477
CVE: CVE-2025-3096
Published: 2025-04-01
Description: Clinic’s Patient Management System versions 2.0 suffers from a SQL injection vulnerability in the login page.
CWE: CWE-89
References: https://www.cve.org/CVERecord?id=CVE-2022-2297; https://www.sourcecodester.com/php-clinics-patient-management-system-source-code
CVE: CVE-2025-29069
Published: 2025-04-01
Description: A heap buffer overflow vulnerability has been identified in the lcms2-2.16. The vulnerability exists in the UnrollChunkyBytes function in cmspack.c, which is responsible for handling color space transformations. NOTE: this is disputed by the Supplier because the finding identified a bug in a third-party calling program, not in lcms.
CVSS Score: 7.3 (HIGH)
CWE: CWE-122
References: https://github.com/mm2/Little-CMS/issues/476; https://github.com/mm2/Little-CMS/issues/476#issuecomment[PII_REDACTED]; https://github.com/mm2/Little-CMS/issues/476#issuecomment[PII_REDACTED]
CVE: CVE-2003-20001
Published: 2025-04-01
Description: An issue was discovered on Mitel ICP VoIP 3100 devices. When a remote user attempts to log in via TELNET during the login wait time and an external call comes in, the system incorrectly divulges information about the call and any SMDR records generated by the system. The information provided includes the service type, extension number and other parameters, related to the call activity.
CVSS Score: 5.6 (MEDIUM)
CWE: CWE-200
References: http://olografix.org/acme/mitel.txt; https://packetstorm.news/files/id/31445; https://rb.gy/1smt22
CVE: CVE-2024-13941
Published: 2025-04-01
Description: A vulnerability was found in ouch-org ouch up to 0.3.1. It has been classified as critical. This affects the function ouch::archive::zip::convert_zip_date_time of the file zip.rs. The manipulation of the argument month leads to memory corruption. The attack needs to be approached locally. The exploit has been disclosed to the public and may be used. Upgrading to version 0.4.0 is able to address this issue. It is recommended to upgrade the affected component.
CVSS Score: 5.3 (MEDIUM)
CWE: CWE-119
References: https://github.com/ouch-org/ouch/issues/707; https://github.com/ouch-org/ouch/releases/tag/0.4.0; https://github.com/rustsec/advisory-db/pull/2084/files
CVE: CVE-2025-29033
Published: 2025-04-01
Description: An issue in BambooHR Build v.25.0210.170831-83b08dd allows a remote attacker to escalate privileges via the /saml/index.php?r=" HTTP GET parameter.
CVSS Score: 7.3 (HIGH)
CWE: CWE-269
References: https://github.com/nikolas-ch/CVEs/tree/main/Bamboohr_25.0210.170831-83b08dd/OpenRedirect