CVE-2015-6912
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 · uneditedSynology Video Station before 1.5-0763 allows remote attackers to execute arbitrary shell commands via shell metacharacters in the subtitle_codepage parameter to subtitle.cgi.
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 confidenceSynology Video Station before version 1.5-0763 contains a command injection vulnerability in the subtitle_codepage parameter of subtitle.cgi. Attackers can inject shell metacharacters to execute arbitrary shell commands on the underlying Synology NAS system with the privileges of the web server.
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<= 1.5-0757CVSS 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
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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 Video Station is installedAccess Synology Package Center and look for Video Station in the installed package list, or run 'pkglist' via SSH to list installed packagesAffected if Video Station package is present on the Synology NAS
-
Check installed Video Station versionIn Package Center, click on Video Station and view the version information, or query the Synology package manager via command line for the exact installed versionAffected if Installed version is 1.5-0757 or any version lower than 1.5-0763
-
Verify network accessibility of Video Station web interfaceConfirm the Synology NAS web interface or Video Station specific port is accessible from network; check if firewall rules allow external access to DSM/Video Station portsAffected if The Video Station web interface is exposed to untrusted networks (the vulnerability is remotely exploitable)
-
Check for the vulnerable CGI endpointLocate subtitle.cgi in the Video Station web directory (typically under /var/packages/VideoStation/target/web/) and confirm it handles the subtitle_codepage parameterAffected if The subtitle.cgi script exists and accepts the subtitle_codepage parameter without sanitization
You are affected if Synology Video Station is installed and the installed version is 1.5-0757 or lower, and the web interface is network-accessible.
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.
dbcve · scopedUpgrade Synology Video Station to version 1.5-0763 or later. If immediate patching is not possible, restrict network access to the Video Station interface using firewall rules or VPN access controls.
Video Station 1.5-0763 or later
- 1. Open Synology DiskStation Manager (DSM)
- 2. Navigate to Package Center
- 3. Find Video Station in the installed packages list
- 4. Click on Video Station and select 'Update'
- 5. Confirm the update to install the patched version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-6912 — 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-2015-6912 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