CVE-2022-22687
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 · uneditedBuffer copy without checking size of input ('Classic Buffer Overflow') vulnerability in Authentication functionality in Synology DiskStation Manager (DSM) before 6.2.3-25426-3 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 confidenceA classic buffer overflow vulnerability exists in the authentication component of Synology DiskStation Manager (DSM). The vulnerability results from insufficient bounds checking when copying input data into a fixed-size buffer during the authentication process, allowing remote attackers to overwrite memory and execute arbitrary code without authentication.
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>= 6.2, < 6.2.3-25426-3< 3.1-23033CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify DSM product variantDetermine whether your Synology device runs DiskStation Manager (DSM) or DSM Unified Controller. This is typically visible in the product name/model or system information page.Affected if Running DSM Unified Controller versus standard DSM affects which version range applies
-
Check DSM version numberLocate the installed DSM version in the system control panel, about page, or via the `cat /proc/sys/kernel/syno_version` command if accessible. Note the full version string including build number.Affected if The full version string (e.g., 6.2.3-25426-3) is needed for accurate comparison
-
Compare standard DSM version against affected rangeIf running standard DSM, compare your version to: affected if >= 6.2 AND < 6.2.3-25426-3. The first number is the major version, the second is the update, the third is the hotfix, and the final number is the build.Affected if Your DSM version is 6.2 or newer but older than 6.2.3-25426-3
-
Compare DSM Unified Controller version against affected rangeIf running DSM Unified Controller, compare your version to: affected if < 3.1-23033. Check the version in the same manner as standard DSM.Affected if Your DSM Unified Controller version is older than 3.1-23033
-
Verify authentication component is accessibleConfirm the Synology web interface or API authentication endpoints are reachable on your network. The vulnerability exists in the authentication component, so remote network access to port 5000/5001 or the web portal is required for exploitation.Affected if The DSM login interface is network-accessible (even from local network)
Your environment is affected if you are running Synology DSM version 6.2 or later but earlier than 6.2.3-25426-3, or DSM Unified Controller earlier than version 3.1-23033, and the authentication 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 · scoped3.1-230336.2.3-25426-3
Upgrade Synology DSM to version 6.2.3-25426-3 or later to remediate this vulnerability. This is a critical priority given the CVSS 9.8 score and trivial network-exploitable nature.
DSM 6.2.3-25426-3 or later / DSM UC 3.1-23033 or later
- 1. Identify the current Synology DSM version by logging into DiskStation Manager and checking Control Panel > Support > DSM version, or via the command line: cat /etc/VERSION
- 2. Confirm the version is in the affected range: >= 6.2 but < 6.2.3-25426-3
- 3. For DiskStation Manager Unified Controller (DSM UC), confirm version is < 3.1-23033
- 4. Download the fixed version from Synology's download center: DSM 6.2.3-25426-3 or later, or DSM UC 3.1-23033 or later
- 5. Apply the update via Control Panel > Support > Install Update, or manually upload the .pat file
- 6. Verify the update was successful and the version now shows 6.2.3-25426-3 or higher (or 3.1-23033+ for DSM UC)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22687 — 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-2022-22687 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