dbcve.org
Audio StationApplication · Synology

CVE-2022-27612

CRITICAL · 9.8 CVSS v3.1 Published 2022-07-28
Fix available
A fix is available. Upgrade to 6.5.4-3367 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 Audio Station before 6.5.4-3367 allows remote attackers to execute arbitrary commands 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 Audio Station where user-supplied input is copied into a fixed-size buffer without proper size validation. This allows remote attackers to overwrite memory and execute arbitrary commands with elevated privileges.

MitigationUpdate Synology Audio Station to version 6.5.4-3367 or later to patch the vulnerability. If immediate patching is not possible, restrict network access to the Audio Station interface and disable it if not required.

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
Audio StationApplication
Affected:< 6.5.4-3367

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 Audio Station package is installed
    On the Synology NAS, open Package Center and look for Audio Station in the installed packages list. Alternatively, SSH into the NAS and run: synopkg list --installed | grep -i audio
    Affected if Audio Station is not installed on the system, the vulnerability does not apply.
  2. Determine installed Audio Station version
    In Package Center, click on Audio Station and view the version information. Via SSH, run: synopkg list --info Audio Station | grep Version
    Affected if The installed version is lower than 6.5.4-3367 (for example, 6.5.4-3366 or earlier).
  3. Confirm CGI/web interface is enabled
    Access Synology DSM, go to Main Menu > Audio Station > Web Application. Verify the Web Station interface or CGI gateway is enabled. Check via SSH: cat /etc/nginx/sites-enabled/dsm.audio.conf 2>/dev/null || echo "CGI config not found"
    Affected if The CGI component is disabled or Audio Station web interface is not accessible, the attack surface is reduced but the vulnerable code may still exist in the package.
  4. Check network exposure of Audio Station
    Verify which network interfaces Audio Station is bound to. In DSM, go to Control Panel > Application Portal > Reverse Proxy or check firewall rules. Confirm if port 8000 (default Audio Station HTTP) or port 8001 (HTTPS) are exposed externally.
    Affected if Audio Station is exposed to untrusted networks (e.g., directly to the internet), remote exploitation is possible.

A Synology NAS with Audio Station installed, version below 6.5.4-3367, and its web/CGI interface enabled and accessible is affected by this vulnerability.

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 6.5.4-3367 or later
Fixed in 6.5.4-3367
Interim mitigation

Update Synology Audio Station to version 6.5.4-3367 or later to patch the vulnerability. If immediate patching is not possible, restrict network access to the Audio Station interface and disable it if not required.

Recommended fix High confidence

Audio Station 6.5.4-3367 or later

  1. Open Synology DSM and navigate to Package Center
  2. Find Audio Station in the package list
  3. Click on Audio Station and select 'Update' if an update is available
  4. Update to version 6.5.4-3367 or later
Caveat Standard Synology package update - brief service interruption may occur during update

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

Fix this in Audio Station Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
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,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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