CVE-2021-34362
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA command injection vulnerability has been reported to affect QNAP device running Media Streaming add-on. If exploited, this vulnerability allow remote attackers to run arbitrary commands. We have already fixed this vulnerability in the following versions of Media Streaming add-on: QTS 5.0.0: Media Streaming add-on 500.0.0.3 ( 2021/08/20 ) and later QTS 4.5.4: Media Streaming add-on 500.0.0.3 ( 2021/08/20 ) and later QTS 4.3.6: Media Streaming add-on 430.1.8.12 ( 2021/08/20 ) and later QTS 4.3.3: Media Streaming add-on 430.1.8.12 ( 2021/09/29 ) and later QuTS-Hero 5.0.0: Media Streaming add-on 500.0.0.3 ( 2021/08/20 ) and later
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA command injection vulnerability in QNAP's Media Streaming add-on allows remote attackers to execute arbitrary commands on affected devices. The vulnerability stems from insufficient input validation in the add-on's interface, enabling malicious input to be passed to system shell commands.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 500.0.0.3< 430.1.8.12CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Media Streaming add-on is installedAccess QNAP App Center via web interface or run 'qpkg -i | grep -i media' via SSH to list installed packages containing 'media'Affected if The Media Streaming add-on appears in the installed packages list
-
Identify the installed Media Streaming versionIn QNAP App Center, click on Media Streaming and view the version number. Alternatively, via SSH run 'qpkg -i media-streaming' or check /share/CACHEDEV1_DATA/.qpkg/MediaStreaming/conf/MediaStreaming.ini for version info if accessibleAffected if Unable to retrieve version or version field is empty
-
Compare version against affected ranges for QTS 5.0.0/4.5.4 and QuTS-Hero 5.0.0If your NAS runs QTS 5.0.0, QTS 4.5.4, or QuTS-Hero 5.0.0, compare the installed version to 500.0.0.3. Any version lower than 500.0.0.3 is affected.Affected if Installed version is below 500.0.0.3 (for QTS 5.0.0/4.5.4 or QuTS-Hero 5.0.0 systems)
-
Compare version against affected ranges for QTS 4.3.6/4.3.3If your NAS runs QTS 4.3.6 or QTS 4.3.3, compare the installed version to 430.1.8.12. Any version lower than 430.1.8.12 is affected.Affected if Installed version is below 430.1.8.12 (for QTS 4.3.6 or 4.3.3 systems)
-
Confirm Media Streaming interface is accessibleVerify the Media Streaming add-on web interface is enabled and accessible at /mediaStreaming/ or via myqnapcloud linkAffected if The interface is exposed to network, increasing exploitability risk
You are affected if Media Streaming add-on is installed and its version falls below 500.0.0.3 (on QTS 5.0.0/4.5.4 or QuTS-Hero 5.0.0) or below 430.1.8.12 (on QTS 4.3.6/4.3.3).
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped430.1.8.12500.0.0.3
Update Media Streaming add-on to version 500.0.0.3 (for QTS 5.0.0/4.5.4 and QuTS-Hero 5.0.0) or 430.1.8.12 (for QTS 4.3.6/4.3.3) or later, as released on 2021/08/20 or later.
Media Streaming add-on 500.0.0.3 (for QTS 5.0.0, QTS 4.5.4, QuTS-Hero 5.0.0) or 430.1.8.12 (for QTS 4.3.6, QTS 4.3.3)
- 1. Log into the QNAP device as administrator
- 2. Identify the QTS or QuTS-Hero version running on the device (check Control Panel > System > Firmware)
- 3. Check the current version of Media Streaming add-on in App Center
- 4. If the device runs QTS 5.0.0, QTS 4.5.4, or QuTS-Hero 5.0.0, upgrade Media Streaming add-on to version 500.0.0.3 or later
- 5. If the device runs QTS 4.3.6, upgrade Media Streaming add-on to version 430.1.8.12 or later
- 6. If the device runs QTS 4.3.3, upgrade Media Streaming add-on to version 430.1.8.12 or later (released 2021/09/29)
- 7. Verify the upgrade was successful and the new version is installed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,592.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-34362 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-34362 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data