CVE-2018-13280
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 · uneditedUse of insufficiently random values vulnerability in SYNO.Encryption.GenRandomKey in Synology DiskStation Manager (DSM) before 6.2-23739 allows man-in-the-middle attackers to compromise non-HTTPS sessions 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 confidenceThe SYNO.Encryption.GenRandomKey function in Synology DiskStation Manager (DSM) versions prior to 6.2-23739 uses insufficiently random values for cryptographic key generation, allowing man-in-the-middle attackers to predict or recover session keys and compromise non-HTTPS communications.
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-23739CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:H/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.
-
Check DSM version via command lineSSH into the Synology device and run: cat /etc/VERSION (or cat /etc.defaults/VERSION for defaults)Affected if The version number displayed is less than 6.2-23739 (for example, 6.2-23732, 6.1, 6.0, etc.)
-
Check DSM version via web interfaceLog into DSM web interface, go to Control Panel > Info Center, and view the DSM version displayedAffected if The displayed version is any build prior to 6.2-23739
-
Verify version number format and compareCompare your exact version build number (the full version string like 6.2-23739) against the threshold. DSM versions follow the format major.minor-build (e.g., 6.2-23739). Any build number lower than 23739 in the 6.2 branch, or any version in branches 6.1, 6.0, 5.x, etc., is affected.Affected if Your build number is lower than 23739 (e.g., 6.2-23738, 6.2-22222) or your major.minor version is less than 6.2
You are affected if you are running any version of Synology DSM with a build number lower than 6.2-23739, regardless of whether non-HTTPS services are in active use, because the vulnerable GenRandomKey function exists in the firmware code itself.
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.
From vendor data6.2-23739
Upgrade DSM to version 6.2-23739 or later to obtain the patched random number generation, and enforce HTTPS for all sensitive sessions to eliminate the attack vector.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13280 — 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-2018-13280 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