CVE-2024-14026
Last modified
CVE-2024-14026 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. A command injection vulnerability has been reported to affect several QNAP operating system versions. If an attacker gains local network access who have also gained a user account, they can then exploit the vulnerability to execute arbitrary commands. We have already fixed the vulnerability in the following versions: QTS 5.1.9.2954 build 20241120 and later QTS 5.2.3.3006 build 20250108 and later QuTS hero h5.1.9.2954 build 20241120 and later QuTS hero h5.2.3.3006 build 20250108 and later. EPSS estimates a 0.62% chance of exploitation in the next 30 days.
Description
A command injection vulnerability has been reported to affect several QNAP operating system versions. If an attacker gains local network access who have also gained a user account, they can then exploit the vulnerability to execute arbitrary commands. We have already fixed the vulnerability in the following versions: QTS 5.1.9.2954 build 20241120 and later QTS 5.2.3.3006 build 20250108 and later QuTS hero h5.1.9.2954 build 20241120 and later QuTS hero h5.2.3.3006 build 20250108 and later
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS:4.0/AV:P/AC:L/AT:P/PR:L/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Qnap | Qts | 5.1.0.2348 | Build 20230325 |
| Qnap | Qts | 5.1.0.2399 | Build 20230515 |
| Qnap | Qts | 5.1.0.2418 | Build 20230603 |
| Qnap | Qts | 5.1.0.2444 | Build 20230629 |
| Qnap | Qts | 5.1.0.2466 | Build 20230721 |
| Qnap | Qts | 5.1.1.2491 | Build 20230815 |
| Qnap | Qts | 5.1.2.2533 | Build 20230926 |
| Qnap | Qts | 5.1.3.2578 | Build 20231110 |
| Qnap | Qts | 5.1.4.2596 | Build 20231128 |
| Qnap | Qts | 5.1.5.2645 | Build 20240116 |
| Qnap | Qts | 5.1.5.2679 | Build 20240219 |
| Qnap | Qts | 5.1.6.2722 | Build 20240402 |
| Qnap | Qts | 5.1.7.2770 | Build 20240520 |
| Qnap | Qts | 5.1.8.2823 | Build 20240712 |
| Qnap | Qts | 5.2.0.2737 | Build 20240417 |
| Qnap | Qts | 5.2.0.2744 | Build 20240424 |
| Qnap | Qts | 5.2.0.2782 | Build 20240601 |
| Qnap | Qts | 5.2.0.2802 | Build 20240620 |
| Qnap | Qts | 5.2.0.2823 | Build 20240711 |
| Qnap | Qts | 5.2.0.2851 | Build 20240808 |
| Qnap | Qts | 5.2.0.2860 | Build 20240817 |
| Qnap | Qts | 5.2.1.2930 | Build 20241025 |
| Qnap | Qts | 5.2.2.2950 | Build 20241114 |
| Qnap | Quts Hero | h5.1.0.2409 | Build 20230525 |
| Qnap | Quts Hero | h5.1.0.2424 | Build 20230609 |
| Qnap | Quts Hero | h5.1.0.2453 | Build 20230708 |
| Qnap | Quts Hero | h5.1.0.2466 | Build 20230721 |
| Qnap | Quts Hero | h5.1.1.2488 | Build 20230812 |
| Qnap | Quts Hero | h5.1.2.2534 | Build 20230927 |
| Qnap | Quts Hero | h5.1.3.2578 | Build 20231110 |
| Qnap | Quts Hero | h5.1.4.2596 | Build 20231128 |
| Qnap | Quts Hero | h5.1.5.2647 | Build 20240118 |
| Qnap | Quts Hero | h5.1.5.2680 | Build 20240220 |
| Qnap | Quts Hero | h5.1.6.2734 | Build 20240414 |
| Qnap | Quts Hero | h5.1.7.2770 | Build 20240520 |
| Qnap | Quts Hero | h5.1.7.2788 | Build 20240607 |
| Qnap | Quts Hero | h5.1.7.2794 | Build 20240613 |
| Qnap | Quts Hero | h5.1.8.2823 | Build 20240712 |
| Qnap | Quts Hero | h5.2.0.2737 | Build 20240417 |
| Qnap | Quts Hero | h5.2.0.2782 | Build 20240601 |
| Qnap | Quts Hero | h5.2.0.2789 | Build 20240607 |
| Qnap | Quts Hero | h5.2.0.2802 | Build 20240620 |
| Qnap | Quts Hero | h5.2.0.2823 | Build 20240711 |
| Qnap | Quts Hero | h5.2.0.2851 | Build 20240808 |
| Qnap | Quts Hero | h5.2.0.2860 | Build 20240817 |
| Qnap | Quts Hero | h5.2.1.2929 | Build 20241025 |
| Qnap | Quts Hero | h5.2.1.2940 | Build 20241105 |
| Qnap | Quts Hero | h5.2.2.2952 | Build 20241116 |
References
- https://www.qnap.com/en/security-advisory/qsa-24-54Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2024-14026?
How severe is CVE-2024-14026?
How do I fix CVE-2024-14026?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2024
- CVE-2024-14015The WordPress eCommerce Plugin WordPress plugin through 2.9…7.1
- CVE-2024-1402Mattermost fails to check if a custom emoji reaction exists …4.3
- CVE-2024-14020A weakness has been identified in carboneio carbone up to fb…5
- CVE-2024-14021LlamaIndex (run-llama/llama_index) versions up to and includ…7.8
- CVE-2024-14024An improper certificate validation vulnerability has been re…6.7
- CVE-2024-14025An SQL injection vulnerability has been reported to affect V…6.7
- CVE-2024-14027In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-14028Use after free vulnerability in Softing smartLink HW-DP or s…6.5
- CVE-2024-1403In OpenEdge Authentication Gateway and AdminServer prior to …9.8
- CVE-2024-14030Sereal::Decoder versions from 4.000 through 4.009_002 for Pe…8.1
- CVE-2024-14031Sereal::Encoder versions from 4.000 through 4.009_002 for Pe…8.1
- CVE-2024-14032Twitch Studio version 0.114.8 and prior contain a privilege …8.5
Are you affected by CVE-2024-14026?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
