CVE-2023-0142
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 · uneditedUncontrolled search path element vulnerability in Backup Management functionality in Synology DiskStation Manager (DSM) before 6.2.4-25556-8, 7.0.1-42218-7 and 7.1-42661 allows remote authenticated users with administrator privileges to read or write arbitrary files 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 confidenceUncontrolled search path element vulnerability in Synology DSM's Backup Management functionality allows authenticated administrators to read/write arbitrary files by manipulating the search path. This path injection flaw exists in versions prior to 6.2.4-25556-8, 7.0.1-42218-7, and 7.1-42661.
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= 3.1>= 1.2, < 1.3.1-9346= 1.3.1-9346>= 6.2, < 7.1-42661CVSS 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
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 Synology DiskStation Manager versionAccess the web interface (DSM) and go to Control Panel > System > DSM Update, or run `cat /etc/VERSION` via SSH to retrieve the installed DSM version number and build number.Affected if The installed version is lower than 7.1-42661, 7.0.1-42218, or 6.2.4-25556 (for DSM 6.2.x) OR exactly equals 3.1 for DiskStation Manager Unified Controller.
-
Check Synology Router Manager versionAccess the web interface (SRM) and go to Control Panel > System > Update & Restore, or run `cat /etc.defaults/VERSION` via SSH on the router device.Affected if The installed SRM version is 1.2.x through 1.3.1-9346 (any version from 1.2 up to and including 1.3.1-9346).
-
Verify Backup Management feature is in useLog into DSM as administrator and navigate to Backup & Replication > Backup to verify if any backup tasks using Backup Management are configured, or check for presence of backup-related packages via `grep -r backup /var/packages/` or Package Center.Affected if Backup Management functionality is actively configured or the Backup & Replication service is enabled on the system.
-
Confirm administrator access existsVerify that you have administrative privileges on the Synology device. This vulnerability requires an authenticated administrator session to exploit the search path manipulation.Affected if You have valid administrator credentials with write access to Backup Management configuration, which is a prerequisite for exploitation.
Your environment is affected if you are running any Synology DSM version 6.2 through 7.1-42660 (excluding 6.2.4-25556-8, 7.0.1-42218-7, and 7.1-42661), SRM 1.2 to 1.3.1-9346, or DiskStation Manager Unified Controller 3.1, AND you have Backup Management enabled with administrator access.
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 · scoped1.3.1-93467.1-42661
Upgrade Synology DSM to version 6.2.4-25556-8, 7.0.1-42218-7, 7.1-42661 or later to remediate the vulnerability.
DSM 7.1-42661 or later (or latest DSM 7.x); for SRM: 1.3.1-9346 or later
- 1. Identify the current DSM version by logging into the web interface and checking Control Panel > System > Update & Restore > DSM Update
- 2. For DiskStation Manager (DSM): Upgrade to version 7.1-42661 or later (recommended: latest DSM 7.x release)
- 3. For Router Manager (SRM): Upgrade to version 1.3.1-9346 or later (recommended: latest SRM 1.3.x release)
- 4. For Diskstation Manager Unified Controller (DUC): Upgrade to version 3.1 or later if available
- 5. After upgrade, verify the new version by checking Control Panel > System > System Information
- 6. Test Backup Management functionality to ensure the vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-0142 — 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-2023-0142 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