CVE-2018-13287
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 · uneditedIncorrect default permissions vulnerability in synouser.conf in Synology Router Manager (SRM) before 1.1.7-6941-1 allows remote authenticated users to obtain sensitive information via the world readable configuration.
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 confidenceSynology Router Manager (SRM) versions prior to 1.1.7-6941-1 contain the synouser.conf configuration file with world-readable permissions (incorrect default permissions). This allows any remote authenticated user on the network to read the file and obtain sensitive information such as user credentials or system configuration data that should be restricted to privileged users.
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< 1.1.7-6941-1CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/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.
-
Determine the installed SRM versionLog into the Synology Router Manager web interface and navigate to Control Panel > System > Updates & Restore, or run 'show synoinfo' or 'cat /etc/synoinfo.conf' via SSH to retrieve the firmware version.Affected if The displayed version is earlier than 1.1.7-6941-1 (for example, 1.1.7-6915 or any build prior to 6941).
-
Locate the synouser.conf fileConnect to the router via SSH and search for the synouser.conf file, typically found in directories such as /etc/, /etc/srm/, or similar configuration paths within the SRM filesystem.Affected if The file exists on the system (its presence is required for the vulnerability to apply).
-
Inspect file permissions on synouser.confRun 'ls -la' on the synouser.conf file to view its permission bits (for example: ls -la /etc/synouser.conf or the specific path where the file is located).Affected if The permission bits grant read access to 'others' (the 'other' category), such as -r--r--r-- (mode 644 with o+r) or any mode where the third octet contains read (4) or higher permissions (for example, 744, 754, 644, 664, or 666). The vulnerability exists when regular users on the network can read th
You are affected if your SRM version is earlier than 1.1.7-6941-1 AND the synouser.conf file has world-readable permissions (read access granted to the 'others' group).
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 data1.1.7-6941-1
Upgrade Synology Router Manager to version 1.1.7-6941-1 or later, which corrects the default file permissions on synouser.conf to restrict access appropriately.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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 $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13287 — 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-13287 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