dbcve.org
Media ServerApplication · Synology

CVE-2022-22683

CRITICAL · 9.8 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 →
100/100
Remediation priority · Urgent
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
Buffer copy without checking size of input ('Classic Buffer Overflow') vulnerability in cgi component in Synology Media Server before 1.8.1-2876 allows remote attackers to execute arbitrary code 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 · high confidence

A classic buffer overflow vulnerability exists in the CGI component of Synology Media Server where the software copies input data to a buffer without checking the size, allowing an attacker to overwrite adjacent memory and execute arbitrary code. The vulnerability is remotely exploitable without authentication, as indicated by the critical CVSS score of 9.8. Affected versions are those prior to version 1.8.1-2876.

MitigationUpgrade Synology Media Server to version 1.8.1-2876 or later. If immediate patching is not feasible, implement network segmentation or firewall rules to restrict unauthorized access to the media server CGI endpoints as a temporary compensating control.

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
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 checks

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

  1. Verify Synology Media Server is installed
    On the Synology DSM interface, open Package Center and check for 'Synology Media Server' in the installed packages, or use the command 'pkginfo | grep -i media' via SSH to list installed packages.
    Affected if The package is not found in Package Center or the pkginfo command returns no results, meaning the product is not installed and this CVE does not apply.
  2. Retrieve the installed version number
    In DSM Package Center, click on Synology Media Server and note the version displayed. Alternatively, run 'pkginfo -i synologymediaserver' or check the version via the package manifest in /var/packages/SynologyMediaServer.
    Affected if You cannot determine the version number from DSM or command line, preventing comparison to the affected versions.
  3. Compare version against affected ranges
    Check if the installed version is less than 1.8.1-2876 or less than 1.4-2665. Note that both version branches are independently affected.
    Affected if The installed version is lower than 1.8.1-2876 OR lower than 1.4-2665, placing the installation in an affected version range.
  4. Confirm CGI component is accessible
    Verify that the media server CGI interface is exposed to the network. This typically involves checking if the Synology Media Server web interface on port 9000 or the CGI endpoint under /webapi/entry.cgi is reachable from untrusted networks.
    Affected if The CGI component is enabled and accessible from untrusted network segments, making remote exploitation possible.

A system is affected if Synology Media Server is installed, the installed version is below 1.8.1-2876 or below 1.4-2665, and the CGI component is network-accessible.

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 feasible, implement network segmentation or firewall rules to restrict unauthorized access to the media server CGI endpoints as a temporary compensating control.

Recommended fix High confidence

Media Server 1.8.1-2876 (or 1.4-2665 for older branches)

  1. Open Synology DSM and navigate to Package Center
  2. Locate Synology Media Server in the package list
  3. Click on Media Server and select 'Update'
  4. Ensure the update installs version 1.8.1-2876 (or 1.4-2665 for older release branches)
  5. After updating, verify the Media Server version in Package Center > Installed to confirm the fix is applied
Caveat Users on very old DSM versions should verify Media Server compatibility with their DSM release before updating

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
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-22683 — 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-22683 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