CVE-2022-22680
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 · uneditedExposure of sensitive information to an unauthorized actor vulnerability in Web Server in Synology DiskStation Manager (DSM) before 7.0.1-42218-2 allows remote attackers to obtain sensitive information 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 · moderate confidenceThis is an information disclosure vulnerability in the Web Server component of Synology DiskStation Manager (DSM). The flaw allows remote unauthenticated attackers to obtain sensitive information through unspecified vectors. The vulnerability exists in DSM versions prior to 7.0.1-42218-2.
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.4-25556-3>= 7.0, < 7.0.1-42218-2CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 installed DSM versionLog into DSM web interface and navigate to Control Panel > System > Update & Restore, or run 'cat /etc/VERSION' via SSH to view the exact DSM version numberAffected if Version is 6.2 up to but not including 6.2.4-25556-3, OR version is 7.0 up to but not including 7.0.1-42218-2
-
Confirm build numberRun 'cat /etc/VERSION' or check the DSM login page footer which displays both version and build number (e.g., 7.0.1-42218)Affected if Build number is lower than 42218 for DSM 7.0.1 line, or lower than 25556 for DSM 6.2.4 line
-
Verify Web Server is enabledLog into DSM > Control Panel > Application Portal > Web Station, or check via CLI with 'cat /etc/webstation'Affected if Web Station or the built-in web server is enabled and running
-
Assess network exposure of DSM interfaceCheck router/firewall rules to determine if DSM web port (5000/5001 or 80/443) is exposed directly to the internet without VPN or IP restrictionAffected if DSM web interface is accessible from untrusted networks without authentication barriers
User is affected if their DSM version falls within the 6.2 to <6.2.4-25556-3 or 7.0 to <7.0.1-42218-2 range AND the web server component is accessible, even if restricted locally.
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 · scoped6.2.4-25556-37.0.1-42218-2
Update Synology DSM to version 7.0.1-42218-2 or later to remediate this vulnerability. As a defense-in-depth measure, restrict network exposure of the DSM web interface to trusted networks or VPN access only.
DSM 6.2.4-25556-3 (for 6.2.x) or DSM 7.0.1-42218-2 (for 7.0.x)
- 1. Log in to Synology DiskStation Manager (DSM) as an administrator.
- 2. Navigate to Control Panel > Update & Restore > DSM Update.
- 3. Click on 'Download Update' to check for available updates.
- 4. If using DSM 6.2.x, select version 6.2.4-25556-3 or later.
- 5. If using DSM 7.0.x, select version 7.0.1-42218-2 or later.
- 6. Confirm the update and allow the system to restart after installation.
- 7. Verify the DSM version matches or exceeds the fixed release after the update completes.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing2.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 $2,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22680 — 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-22680 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