74 matches found
EUVD-2017-1605
Malware in sbrugna...
EUVD-2019-1755
Malware in sbrugna...
EUVD-2017-1586
Malware in sbrugna...
EUVD-2018-10273
Malware in sbrugna...
EUVD-2020-18783
Malware in sbrugna...
EUVD-2020-18784
Malware in sbrugna...
EUVD-2022-7527
Malicious code in bioql PyPI...
EUVD-2024-16632
Malicious code in bioql PyPI...
EUVD-2021-30628
Malicious code in bioql PyPI...
CVE-2020-26157
Leanote Desktop through 2.6.2 allows XSS because a note's title is mishandled during syncing. This leads to remote code execution because of Node integration...
CVE-2020-26158
Leanote Desktop through 2.6.2 allows XSS because a note's title is mishandled when the batch feature is triggered. This leads to remote code execution because of Node integration...
CVE-2019-1010003
Leanote prior to version 2.6 is affected by: Cross Site Scripting XSS...
CVE-2017-1000492
Leanote-desktop version v2.5 is vulnerable to a XSS which leads to code execution due to enabled node integration...
CVE-2017-1000459
Leanote version = 2.5 is vulnerable to XSS due to not sanitized input in markdown notes...
CVE-2024-0849
Leanote version 2.7.0 allows obtaining arbitrary local files. This is possible because the application is vulnerable to LFR...
CVE-2024-0849
Leanote version 2.7.0 allows obtaining arbitrary local files. This is possible because the application is vulnerable to LFR...
CVE-2024-0849
Leanote version 2.7.0 allows obtaining arbitrary local files. This is possible because the application is vulnerable to LFR...
Code injection
Leanote version 2.7.0 allows obtaining arbitrary local files. This is possible because the application is vulnerable to LFR...
CVE-2024-0849
CVE-2024-0849 (Leanote 2.7.0) is a local-file-read vulnerability caused by a Local File Reading (LFR) weakness, allowing an attacker to obtain arbitrary local files. The vulnerability is explicitly described in multiple sources as affecting Leanote version 2.7.0, with the impact being exposure of...
CVE-2024-0849 Leanote 2.7.0 - Local File Read
Leanote version 2.7.0 allows obtaining arbitrary local files. This is possible because the application is vulnerable to LFR...