CVE-2022-43748
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 · uneditedImproper limitation of a pathname to a restricted directory ('Path Traversal') vulnerability in file operation management in Synology Presto File Server before 2.1.2-1601 allows remote attackers to 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 · moderate confidenceA Path Traversal vulnerability exists in Synology Presto File Server versions prior to 2.1.2-1601, allowing remote attackers to write arbitrary files to the filesystem via unsanitized file path inputs in the file operation management component. This high-severity flaw enables authenticated or potentially unauthenticated remote attackers to place files outside intended restricted directories.
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< 2.1.2-1601CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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.
-
Locate Synology Presto File Server installationAccess Synology DSM Package Center and locate the installed Presto File Server package, or use the command line to query installed Synology packagesAffected if The package is installed and running on the system
-
Determine installed version numberView the installed package details in Package Center or run a Synology package query command to retrieve the exact version string (for example: synopkg list or package information from the DSM web interface)Affected if The version displayed is prior to 2.1.2-1601 (for example, 2.1.1-1500 or any 2.0.x version)
-
Confirm the file operation management component is accessibleIdentify whether the Presto File Server service is network-accessible and check if the file operation management API endpoints are exposed (typically on ports used by Presto for file transfer operations)Affected if The Presto service is exposed on the network and accepts file operation requests without additional network restrictions
You are affected if Synology Presto File Server is installed and the installed version is less than 2.1.2-1601, with the file operation management component 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 · scoped2.1.2-1601
Upgrade Synology Presto File Server to version 2.1.2-1601 or later to obtain the vendor patch. Additionally, restrict network exposure of the Presto service to trusted internal networks and implement WAF rules to detect path traversal patterns in requests.
2.1.2-1601
- Access the Synology administrative interface (DSM)
- Navigate to Package Center or the Presto File Server application
- Check for available updates for Presto File Server
- Install the update to version 2.1.2-1601 or later
- Verify the installation was successful and the new version is running
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.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 $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-43748 — 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-43748 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