dbcve.org
Media ServerApplication · Synology

CVE-2018-8914

CRITICAL · 9.8 CVSS v3.0 Published 2018-05-10
Fix available
A fix is available. Upgrade to 1.4-2654 / 1.7.6-2842 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
SQL injection vulnerability in UPnP DMA in Synology Media Server before 1.7.6-2842 and before 1.4-2654 allows remote attackers to execute arbitrary SQL commands via the ObjectID parameter.

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

SQL injection vulnerability in Synology Media Server's UPnP DMA component allows remote attackers to inject and execute arbitrary SQL commands through the ObjectID parameter. The vulnerability stems from insufficient input validation on the ObjectID parameter in the UPnP service, enabling attackers to manipulate SQL queries. This is exploitable remotely without authentication due to the UPnP service being network-accessible.

MitigationUpgrade Synology Media Server to version 1.7.6-2842 or later (for version 1.7 series) or 1.4-2654 or later (for version 1.4 series). If immediate patching is not possible, restrict network access to the UPnP service via firewall rules or disable the UPnP DMA feature until the patch can be applied.

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, < 1.4-2654>= 1.7, < 1.7.6-2842

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.0/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
    SSH into the Synology NAS and run: ps | grep -i mediawiki or check for /var/packages/MediaServer directory existence
    Affected if Media Server package is installed on the system
  2. Check installed Media Server version
    On the Synology NAS, run: cat /var/packages/MediaServer/conf/VERSION or check via Package Center UI
    Affected if Version is 1.4 series before 1.4-2654, or 1.7 series before 1.7.6-2842
  3. Confirm UPnP DMA service is enabled
    Access Synology Control Panel > Media Server > DLNA/UPnP settings and verify 'Enable DLNA/UPnP media server' is checked, or query via: synoservicectl --status dlna
    Affected if UPnP DMA feature is enabled and running
  4. Check network exposure of UPnP service
    Verify the NAS is directly exposed to untrusted networks or run: netstat -tlnp | grep 5000 or check router UPnP forwarding settings
    Affected if UPnP service is accessible from WAN or untrusted networks without firewall protection

The system is affected if Synology Media Server with version 1.4 before 1.4-2654 or 1.7 before 1.7.6-2842 is installed with the UPnP DMA feature enabled and 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-2654 / 1.7.6-2842 or later
Fixed in 1.4-26541.7.6-2842
Interim mitigation

Upgrade Synology Media Server to version 1.7.6-2842 or later (for version 1.7 series) or 1.4-2654 or later (for version 1.4 series). If immediate patching is not possible, restrict network access to the UPnP service via firewall rules or disable the UPnP DMA feature until the patch can be applied.

Recommended fix High confidence

Media Server 1.4-2654 or later (1.4 branch), or 1.7.6-2842 or later (1.7 branch)

  1. 1. Identify the current version of Synology Media Server installed on the system
  2. 2. Determine which branch (1.4 or 1.7) is currently in use
  3. 3. For 1.4 branch users: upgrade to version 1.4-2654 or any later 1.4.x release
  4. 4. For 1.7 branch users: upgrade to version 1.7.6-2842 or any later 1.7.x release
  5. 5. After upgrade, verify the new version is running via the Synology administrative interface
  6. 6. Confirm the vulnerability is resolved by ensuring the ObjectID parameter is no longer vulnerable to SQL injection

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-2018-8914 — 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-2018-8914 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