CVE-2024-50395
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 authorization bypass through user-controlled key vulnerability has been reported to affect Media Streaming add-on. If exploited, the vulnerability could allow local network attackers to gain privilege. We have already fixed the vulnerability in the following version: Media Streaming add-on 500.1.1.6 ( 2024/08/02 ) 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 confidenceThis is an authorization bypass vulnerability in the Media Streaming add-on where attackers can manipulate a user-controlled key to bypass authentication checks. If exploited, local network attackers can gain elevated privileges on the affected system.
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.1.1.0, < 500.1.1.6CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/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.
-
Confirm Media Streaming add-on is installedAccess QNAP NAS via SSH or File Station and look for the Media Streaming add-on in /share/Public or the App Center. Alternatively, check QNAP's App Management interface.Affected if The add-on is not installed on the QNAP device
-
Identify installed Media Streaming versionIn QNAP App Center, click on Media Streaming and view the version details. Via CLI, check /etc/config/qpkg.conf for the Media Streaming package entry.Affected if Version is 500.1.1.0 through 500.1.1.5 (inclusive)
-
Verify Media Streaming service is enabledIn QNAP Control Panel > App Center, confirm Media Streaming status shows as Running. Via CLI, run 'ps | grep -i media' or check service status via QNAP's qts utilities.Affected if The service is actively running on the NAS
-
Assess network accessibility of the serviceCheck QNAP Control Panel > Network & Virtual Switch > Port Forwarding or Firewall rules to see if ports used by Media Streaming (typically 8080, 9000, or 1900) are exposed to untrusted networks. Also verify router port forwards.Affected if The Media Streaming service ports are accessible from networks beyond the trusted local network
The environment is affected if Media Streaming add-on version 500.1.1.0-500.1.1.5 is installed, the service is running, and the network exposure extends beyond trusted local networks.
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.
From vendor data500.1.1.6
Update Media Streaming add-on to version 500.1.1.6 or later. As a compensating control, restrict network access to the Media Streaming service to trusted local networks only until the patch is applied.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.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,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-50395 — 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-2024-50395 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