7 matches found
Qnap QTS and QuTS hero Improper Link Resolution Before File Access (CVE-2024-53691)
A link following vulnerability has been reported to affect several QNAP operating system versions. If exploited, the vulnerability could allow remote attackers who have gained user access to traverse the file system to unintended locations. We have already fixed the vulnerability in the following...
Exploit for CVE-2024-53691
CVE-2024-53691 - https://www.qnap.com/en/security-advisory/qsa...
CVE-2024-53691
A link following vulnerability has been reported to affect several QNAP operating system versions. If exploited, the vulnerability could allow remote attackers who have gained user access to traverse the file system to unintended locations. We have already fixed the vulnerability in the following...
CVE-2024-53691
A link following vulnerability has been reported to affect several QNAP operating system versions. If exploited, the vulnerability could allow remote attackers who have gained user access to traverse the file system to unintended locations. We have already fixed the vulnerability in the following...
CVE-2024-53691
Summary : CVE-2024-53691 affects QNAP QTS and QuTS hero. A symlink/link-following vulnerability in ZIP extraction allows an attacker with basic user access to traverse the file system to unintended locations due to improper link resolution before file access. Impact (as described) : potential fil...
CVE-2024-53691 QTS, QuTS hero
A link following vulnerability has been reported to affect several QNAP operating system versions. If exploited, the vulnerability could allow remote attackers who have gained user access to traverse the file system to unintended locations. We have already fixed the vulnerability in the following...
CVE-2024-53691 QTS, QuTS hero
A link following vulnerability has been reported to affect several QNAP operating system versions. If exploited, the vulnerability could allow remote attackers who have gained user access to traverse the file system to unintended locations. We have already fixed the vulnerability in the following...