CVE-2020-36195
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 · uneditedAn SQL injection vulnerability has been reported to affect QNAP NAS running Multimedia Console or the Media Streaming add-on. If exploited, the vulnerability allows remote attackers to obtain application information. QNAP has already fixed this vulnerability in the following versions of Multimedia Console and the Media Streaming add-on. QTS 4.3.3: Media Streaming add-on 430.1.8.10 and later QTS 4.3.6: Media Streaming add-on 430.1.8.8 and later QTS 4.4.x and later: Multimedia Console 1.3.4 and later We have also fixed this vulnerability in the following versions of QTS 4.3.3 and QTS 4.3.6, respectively: QTS 4.3.3.1624 Build 20210416 or later QTS 4.3.6.1620 Build 20210322 or 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 · high confidenceSQL injection vulnerability in QNAP NAS Multimedia Console and Media Streaming add-on allows remote unauthenticated attackers to obtain application information via specially crafted SQL queries.
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< 4.3.3>= 4.3.4, < 4.3.6= 4.3.3= 4.3.3.0095= 4.3.3.0096= 4.3.3.0136= 4.3.3.0154= 4.3.3.0174= 4.3.3.0188= 4.3.3.0210= 4.3.3.0229= 4.3.3.0238< 430.1.8.10< 430.1.8.8< 1.3.4CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Check Multimedia Console app versionAccess QNAP App Center via web interface or run 'qpkg -i | grep -i multimedia' via SSH to list installed Multimedia Console versionAffected if Multimedia Console version is installed and is less than 1.3.4
-
Check Media Streaming add-on versionAccess QNAP App Center via web interface or run 'qpkg -i | grep -i media' via SSH to list installed Media Streaming add-on versionAffected if Media Streaming add-on version is installed and is less than 430.1.8.10 or less than 430.1.8.8 (depending on your QTS branch)
-
Verify QTS firmware versionLog into QNAP admin web interface and check System Settings > Firmware, or run 'getcfg System.Version' via SSHAffected if QTS version is < 4.3.3; or >= 4.3.4 and < 4.3.6; or matches any of these: 4.3.3, 4.3.3.0095, 4.3.3.0096, 4.3.3.0136, 4.3.3.0154, 4.3.3.0174, 4.3.3.0188, 4.3.3.0210, 4.3.3.0229, 4.3.3.0238
-
Confirm affected apps are accessible over networkVerify that the QNAP NAS is network-accessible and Multimedia Console or Media Streaming endpoints are reachable (these apps expose web interfaces on ports 8086 and 8087 by default)Affected if NAS is externally accessible and either Multimedia Console or Media Streaming add-on is installed with a vulnerable version
You are affected if Multimedia Console < 1.3.4 or Media Streaming add-on < 430.1.8.10/430.1.8.8 is installed on a QTS version matching the affected ranges, and the apps are network-accessible.
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 · scoped1.3.44.3.34.3.6
Update QNAP QTS and affected components (Multimedia Console or Media Streaming add-on) to the patched versions specified for the respective QTS release branch.
QTS 4.3.3 (Media Streaming add-on 430.1.8.10 + QTS build 1624/20210416) or QTS 4.3.6 (Media Streaming add-on 430.1.8.8 + QTS build 1620/20210322) or QTS 4.4.x (Multimedia Console 1.3.4)
- Log into QNAP QTS as administrator
- Navigate to App Center to identify which application is installed: Media Streaming Add On or Multimedia Console
- Check current QTS version via Control Panel > System > System Information > General
- For QTS 4.3.3: Update Media Streaming add-on to version 430.1.8.10 or later via App Center, then update QTS to build 1624 (20210416) or later via Control Panel > System > Firmware Update
- For QTS 4.3.4/4.3.5: Update QTS to 4.3.6 first, then apply corresponding fixes
- For QTS 4.3.6: Update Media Streaming add-on to version 430.1.8.8 or later via App Center, then update QTS to build 1620 (20210322) or later via Control Panel > System > Firmware Update
- For QTS 4.4.x and later: Update Multimedia Console to version 1.3.4 or later via App Center
- Verify successful update by confirming the new versions in App Center and Control Panel > System > System Information
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-36195 — 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-2020-36195 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