CVE-2023-23368
No exploitation reported by the sources we read.
- Published2023-11-03
- WeaknessCWE-78
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
An OS command injection vulnerability has been reported to affect several QNAP operating system versions. If exploited, the vulnerability could allow users to execute commands via a network. We have already fixed the vulnerability in the following versions: QTS 5.0.1.2376 build 20230421 and later QTS 4.5.4.2374 build 20230416 and later QuTS hero h5.0.1.2376 build 20230421 and later QuTS hero h4.5.4.2374 build 20230417 and later QuTScloud c5.0.1.2374 and later
Timeline
dates in UTC- 2023-11-0317:15CVE publishedNVD
- 2026-10-2319:23EPSS crossed 10 %FIRST EPSS
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2023-23368?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2023-23368?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 5.0 | = 5.0.1 | no fix published | NVD |
| 5.0 | = 5.0.1.2034 | no fix published | NVD |
| 5.0 | = 5.0.1.2079 | no fix published | NVD |
| 5.0 | = 5.0.1.2131 | no fix published | NVD |
| 5.0 | = 5.0.1.2137 | no fix published | NVD |
| 5.0 | = 5.0.1.2145 | no fix published | NVD |
| 5.0 | = 5.0.1.2173 | no fix published | NVD |
| 5.0 | = 5.0.1.2194 | no fix published | NVD |
| 5.0 | = 5.0.1.2234 | no fix published | NVD |
| 5.0 | = 5.0.1.2248 | no fix published | NVD |
| 5.0 | = 5.0.1.2277 | no fix published | NVD |
| 5.0 | = 5.0.1.2346 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| — | = h5.0.1.2045 | no fix published | NVD |
| — | = h5.0.1.2192 | no fix published | NVD |
| — | = h5.0.1.2248 | no fix published | NVD |
| — | = h5.0.1.2269 | no fix published | NVD |
| — | = h5.0.1.2277 | no fix published | NVD |
| — | = h5.0.1.2348 | no fix published | NVD |
| — | = h4.5.4.1771 | no fix published | NVD |
| — | = h4.5.4.1800 | no fix published | NVD |
| — | = h4.5.4.1813 | no fix published | NVD |
| — | = h4.5.4.1848 | no fix published | NVD |
| — | = h4.5.4.1892 | no fix published | NVD |
| — | = h4.5.4.1951 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| — | = c5.0.1.1949 | no fix published | NVD |
| — | = c5.0.1.1998 | no fix published | NVD |
| — | = c5.0.1.2044 | no fix published | NVD |
| — | = c5.0.1.2148 | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
Advisories and patches
- www.qnap.comVendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Published
- 2023-11-03
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2023-23368?
Is CVE-2023-23368 actively exploited?
What is the CVSS score for CVE-2023-23368?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.