dbcve.org
Video StationApplication · Synology

CVE-2021-33181

CRITICAL · 9.1 CVSS v3.1 Published 2021-06-01
Fix available
A fix is available. Upgrade to 2.4.10-1632 or later.
See remediation →
97/100
Remediation priority · Urgent
Remotely reachable 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
Server-Side Request Forgery (SSRF) vulnerability in webapi component in Synology Video Station before 2.4.10-1632 allows remote authenticated users to send arbitrary request to intranet resources 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

This is a Server-Side Request Forgery (SSRF) vulnerability in the webapi component of Synology Video Station. An attacker with valid credentials can abuse the application to make the server send arbitrary requests to intranet or internal network resources, potentially accessing sensitive internal services, APIs, or infrastructure that should not be externally reachable.

MitigationUpdate Synology Video Station to version 2.4.10-1632 or later. Additionally, apply network segmentation to isolate the Synology NAS from sensitive internal resources and implement strict firewall rules to limit what destinations the NAS can reach.

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
Video StationApplication
Affected:< 2.4.10-1632

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
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/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. Confirm Video Station is installed
    Access Synology Package Center or run 'cat /var/packages/VideoStation/info.json' on the NAS to verify Video Station package is present
    Affected if Video Station package is not installed on the system
  2. Identify installed Video Station version
    In Package Center, right-click Video Station and select 'Information', or run 'synopkg version VideoStation' via SSH to retrieve the exact version number
    Affected if The installed version is lower than 2.4.10-1632 (for example, 2.4.9-1588 or earlier)
  3. Verify webapi component accessibility
    Check if the Video Station webapi endpoint responds at /webapi/entry.cgi?api=SYNO.VideoStation.Info&version=1&method=getinfo - attempt this from both LAN and remote access paths
    Affected if The webapi endpoint is reachable without authentication or with valid user credentials
  4. Assess remote access exposure
    Check Synology QuickConnect settings or port forwarding rules to determine if Video Station is accessible from outside the local network, and review DSM login settings for user account availability
    Affected if Remote access to the NAS is enabled and valid user accounts exist that could be used to exploit the webapi (the SSRF requires valid credentials)

The environment is affected if Synology Video Station is installed with a version lower than 2.4.10-1632 and the webapi component is accessible with valid user credentials.

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 2.4.10-1632 or later
Fixed in 2.4.10-1632
Interim mitigation

Update Synology Video Station to version 2.4.10-1632 or later. Additionally, apply network segmentation to isolate the Synology NAS from sensitive internal resources and implement strict firewall rules to limit what destinations the NAS can reach.

Recommended fix High confidence

2.4.10-1632

  1. Open Synology DiskStation Manager (DSM) in a web browser
  2. Navigate to Package Center
  3. Locate Video Station in the installed packages list
  4. Check for available updates - the fixed version is 2.4.10-1632
  5. If an update is available, click to update Video Station
  6. Confirm the update and wait for installation to complete
  7. Verify the installed version is 2.4.10-1632 or higher

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

Fix this in Video Station Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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