dbcve.org
Media ServerApplication · Synology

CVE-2024-4464

HIGH · 7.5 CVSS v3.1 Published 2024-12-18
Fix available
A fix is available. Upgrade to 1.4-2680 / 2.0.5-3152 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Authorization bypass through user-controlled key vulnerability in streaming service in Synology Media Server before 1.4-2680, 2.0.5-3152 and 2.2.0-3325 allows remote attackers to read specific files via unspecified vectors.

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 confidence

Authorization bypass vulnerability in Synology Media Server allows remote attackers to read specific files by manipulating user-controlled key parameters, bypassing normal authorization checks. This is a file disclosure issue affecting multiple version branches.

MitigationUpgrade Synology Media Server to version 1.4-2680, 2.0.5-3152, or 2.2.0-3325 or later to patch the authorization bypass vulnerability.

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
Media ServerApplication
Affected:< 1.4-2680>= 2.0.0-11050, < 2.0.5-3152>= 2.2.0-3324, < 2.2.0-3325

CVSS 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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Synology Media Server is installed
    On your Synology NAS, open Package Center and look for 'Media Server' in the installed packages list, or run 'pkginfo | grep -i media-server' via SSH.
    Affected if Media Server package is not installed on the system.
  2. Locate the Media Server version
    In Package Center, click on Media Server and view the version information. Alternatively, check the version via SSH using 'cat /var/packages/MediaServer/info' or the Synology web API.
    Affected if Unable to retrieve the Media Server version from the system.
  3. Compare version against affected branch 1.4
    If the installed version starts with 1.4 (for example, 1.4-2679 or lower), check if it is less than 1.4-2680. Versions below this threshold are affected.
    Affected if Version starts with 1.4 and is less than 1.4-2680.
  4. Compare version against affected branch 2.0
    If the installed version starts with 2.0.x, verify whether it is >= 2.0.0-11050 AND < 2.0.5-3152. Versions in this range are affected.
    Affected if Version starts with 2.0 and falls between 2.0.0-11050 and 2.0.5-3151 inclusive.
  5. Compare version against affected branch 2.2
    If the installed version starts with 2.2, verify whether it is >= 2.2.0-3324 AND < 2.2.0-3325. Versions in this range are affected.
    Affected if Version starts with 2.2 and is 2.2.0-3324.

You are affected if Synology Media Server is installed and its version falls below 1.4-2680, between 2.0.0-11050 and 2.0.5-3151, or is exactly 2.2.0-3324.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.4-2680 / 2.0.5-3152 / 2.2.0-3325 or later
Fixed in 1.4-26802.0.5-31522.2.0-3325
Interim mitigation

Upgrade Synology Media Server to version 1.4-2680, 2.0.5-3152, or 2.2.0-3325 or later to patch the authorization bypass vulnerability.

Recommended fix High confidence

1.4-2680, 2.0.5-3152, or 2.2.0-3325 depending on your version branch

  1. Identify the current version of Synology Media Server installed on the system
  2. If running a version before 1.4, upgrade to version 1.4-2680
  3. If running version 2.0.0-11050 through 2.0.5-3151, upgrade to version 2.0.5-3152
  4. If running version 2.2.0-3324, upgrade to version 2.2.0-3325
  5. After upgrading, verify the Media Server version matches the target fixed release
Caveat Review Synology release notes for your version branch to check for any compatibility notes or known issues before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Media Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-4464 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-4464 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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