782 matches found
CVE-2025-62717 Emlog Pro session verification code error due to clearing logic error
Emlog is an open source website building system. In version 2.5.23, Emlog Pro is vulnerable to a session verification code error due to a clearing logic error. This means the verification code could be reused anywhere an email verification code is required. This issue has been fixed in commit...
CVE-2025-62717
CVE-2025-62717 affects Emlog Pro 2.5.23, where a clearing-logic error in session verification code allows reuse of verification codes. The issue has a fix in commit 1f726df. Remediation: upgrade to a version including the fix (per the cited advisories). If upgrading is not possible, apply the pat...
SUSE CVE-2023-53713
In the Linux kernel, the following vulnerability has been resolved: arm64: sme: Use STR P to clear FFR context field in streaming SVE mode The FFR is a predicate register which can vary between 16 and 256 bits in size depending upon the configured vector length. When saving the SVE state in...
PT-2025-43672
Name of the Vulnerable Software and Affected Versions Emlog versions prior to the commit 1f726df Emlog Pro version 2.5.23 Description Emlog Pro version 2.5.23 contains a flaw related to session verification codes. A clearing logic error allows the reuse of email verification codes in any context...
CVE-2025-62717: Improper Authentication
Emlog is an open source website building system. In version 2.5.23, Emlog Pro is vulnerable to a session verification code error due to a clearing logic error. This means the verification code could be reused anywhere an email verification code is required. This issue has been fixed in commit...
CVE-2025-56799
Reolink desktop application 8.18.12 contains a command injection vulnerability in its scheduled cache-clearing mechanism via a crafted folder name. NOTE: this is disputed by the Supplier because a crafted folder name would arise only if the local user were attacking himself...
CVE-2025-56799
Reolink desktop application 8.18.12 contains a command injection vulnerability in its scheduled cache-clearing mechanism via a crafted folder name. NOTE: this is disputed by the Supplier because a crafted folder name would arise only if the local user were attacking himself...
CVE-2025-56799
Reolink desktop application 8.18.12 contains a command injection vulnerability in its scheduled cache-clearing mechanism via a crafted folder name. NOTE: this is disputed by the Supplier because a crafted folder name would arise only if the local user were attacking himself...
EUVD-2025-35237
Reolink desktop application 8.18.12 contains a command injection vulnerability in its scheduled cache-clearing mechanism via a crafted folder name...
CVE-2025-56799
Reolink desktop application 8.18.12 contains a command injection vulnerability in its scheduled cache-clearing mechanism via a crafted folder name. NOTE: this is disputed by the Supplier because a crafted folder name would arise only if the local user were attacking himself...
CVE-2025-56799
The Reolink Desktop Application (version 8.18.12) is vulnerable to an OS command injection via its coverCacheClearScheduler feature. The application constructs an OS shell command (using rd /s /q on Windows or rm -rf on macOS) by concatenating a temporary folder path read from a configuration fil...
CVE-2025-56799
Reolink desktop application 8.18.12 contains a command injection vulnerability in its scheduled cache-clearing mechanism via a crafted folder name. NOTE: this is disputed by the Supplier because a crafted folder name would arise only if the local user were attacking himself...
CVE-2025-56799: Improper Neutralization of Special Elements used in a Command
Reolink desktop application 8.18.12 contains a command injection vulnerability in its scheduled cache-clearing mechanism via a crafted folder name. NOTE: this is disputed by the Supplier because a crafted folder name would arise only if the local user were attacking himself...
Linux Distros Unpatched Vulnerability : CVE-2023-53642
The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - x86: fix clearuserrepgood exception handling annotation This code no longer exists in mainline, because it was removed in commit d2c95f9d6802 x86: don't use...
SUSE CVE-2022-50533
In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: mlme: fix null-ptr deref on failed assoc If association to an AP without a link 0 fails, then we crash in tracing because it assumes that either apmldaddr or link 0 BSS is valid, since we clear sdata-vif.validlink...
CVE-2023-53642
In the Linux kernel, the following vulnerability has been resolved: x86: fix clearuserrepgood exception handling annotation This code no longer exists in mainline, because it was removed in commit d2c95f9d6802 "x86: don't use REPGOOD or ERMS for user memory clearing" upstream. However, rather tha...
UBUNTU-CVE-2023-53642
In the Linux kernel, the following vulnerability has been resolved: x86: fix clearuserrepgood exception handling annotation This code no longer exists in mainline, because it was removed in commit d2c95f9d6802 "x86: don't use REPGOOD or ERMS for user memory clearing" upstream. However, rather tha...
EUVD-2025-32754
In the Linux kernel, the following vulnerability has been resolved: x86: fix clearuserrepgood exception handling annotation This code no longer exists in mainline, because it was removed in commit d2c95f9d6802 "x86: don't use REPGOOD or ERMS for user memory clearing" upstream. However, rather tha...
CVE-2023-53642 x86: fix clear_user_rep_good() exception handling annotation
In the Linux kernel, the following vulnerability has been resolved: x86: fix clearuserrepgood exception handling annotation This code no longer exists in mainline, because it was removed in commit d2c95f9d6802 "x86: don't use REPGOOD or ERMS for user memory clearing" upstream. However, rather tha...
CVE-2022-50533 wifi: mac80211: mlme: fix null-ptr deref on failed assoc
In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: mlme: fix null-ptr deref on failed assoc If association to an AP without a link 0 fails, then we crash in tracing because it assumes that either apmldaddr or link 0 BSS is valid, since we clear sdata-vif.validlink...