dbcve.org
Media ServerApplication · Synology

CVE-2022-27614

HIGH · 7.5 CVSS v3.1 Published 2022-07-28
Fix available
A fix is available. Upgrade to 1.4-2665 / 1.8.1-2876 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
Exposure of sensitive information to an unauthorized actor vulnerability in web server in Synology Media Server before 1.8.1-2876 allows remote attackers to obtain sensitive information 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

Synology Media Server contains a web server component with an information disclosure vulnerability that allows remote unauthenticated attackers to access sensitive information. The vulnerability exists in versions prior to 1.8.1-2876 and is exploitable without authentication via the web server interface.

MitigationUpgrade Synology Media Server to version 1.8.1-2876 or later. If immediate patching is not possible, consider restricting network access to the Media Server web interface through firewall rules or network segmentation to limit exposure to untrusted networks.

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.8.1-2876< 1.4-2665

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. Identify Synology Media Server version
    Access the Synology DSM web interface, navigate to Package Center, locate Synology Media Server, and record the installed version number. Alternatively, use the command line: cat /var/packages/MediaServer/INFO 2>/dev/null or check via API.
    Affected if The installed version is below 1.8.1-2876 or below 1.4-2665 (for the older branch). Compare your version against these thresholds.
  2. Verify web server component is enabled
    In DSM, go to Control Panel > Application Portal > Media Server, or check if the Media Server web interface port (typically 9927 or 9928) is listening. Use: netstat -an | grep -E '992[78]' or ss -tlnp | grep -E '992[78]'.
    Affected if The Media Server web interface is active and listening on a network port.
  3. Confirm remote network exposure
    Check firewall rules in Control Panel > Security > Firewall, or inspect iptables/nftables rules that allow inbound traffic to the Media Server web port from external networks. Determine if the interface is bound to 0.0.0.0 rather than 127.0.0.1.
    Affected if The Media Server web port accepts connections from untrusted or external network interfaces (0.0.0.0 or WAN-facing).

You are affected if Synology Media Server is installed with a version below 1.8.1-2876 (or below 1.4-2665) AND the web server component is accessible remotely without authentication.

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-2665 / 1.8.1-2876 or later
Fixed in 1.4-26651.8.1-2876
Interim mitigation

Upgrade Synology Media Server to version 1.8.1-2876 or later. If immediate patching is not possible, consider restricting network access to the Media Server web interface through firewall rules or network segmentation to limit exposure to untrusted networks.

Recommended fix High confidence

Media Server 1.8.1-2876 or later (1.8.x branch); Media Server 1.4-2665 or later (1.4.x branch)

  1. 1. Identify the currently installed Synology Media Server version in Package Center or via SSH with command: synopkg list | grep MediaServer
  2. 2. If running version 1.8.x and below 1.8.1-2876, upgrade to version 1.8.1-2876 or later
  3. 3. If running version 1.4.x and below 1.4-2665, upgrade to version 1.4-2665 or later
  4. 4. In DSM Package Center, locate Synology Media Server and click 'Update' if an update is available
  5. 5. Alternatively, manually download the updated package from Synology Download Center for your specific NAS model
  6. 6. After update completes, verify the new version is installed correctly

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-2022-27614 — 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-2022-27614 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