CVE-2024-0854
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 · uneditedURL redirection to untrusted site ('Open Redirect') vulnerability in file access component in Synology DiskStation Manager (DSM) before 6.2.4-25556-8, 7.0.1-42218-7, 7.1.1-42962-7 and 7.2.1-69057-2 allows remote authenticated users to conduct phishing attacks 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 confidenceAn open redirect vulnerability exists in the file access component of Synology DiskStation Manager (DSM). The vulnerability allows authenticated users to craft URLs that redirect users to arbitrary external sites, enabling phishing attacks. The issue affects DSM versions prior to 6.2.4-25556-8, 7.0.1-42218-7, 7.1.1-42962-7, and 7.2.1-69057-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< 7.2.1-69057-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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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.
-
Confirm DSM is installedAccess the web management interface on port 5000 or 5001, or check for DSM processes via command line (e.g., ps aux | grep -i synology)Affected if DSM web interface is accessible or Synology-related processes are running
-
Identify the installed DSM versionLog into DSM web interface and navigate to Control Panel > System > System Information, or run `cat /etc/VERSION` on the NAS command lineAffected if The version number is lower than 7.2.1-69057-2 (or 6.2.4-25556-8, 7.0.1-42218-7, 7.1.1-42962-7 for older major versions)
-
Verify file access component is enabledCheck if File Station or similar file access module is installed and active via Control Panel > Application Portal > File Station, or list enabled packages via `synopkg list --enabled`Affected if File Station or file access functionality is installed and enabled on the system
-
Check for open redirect behaviorInspect URLs generated by the file access component for the presence of redirect parameters (e.g., 'redirect=' or 'next=' query parameters); attempt a controlled test with a known safe URL to observe if external redirection occursAffected if The application accepts and follows redirect parameters pointing to external domains without sufficient validation
A user is affected if they are running any DSM version below 7.2.1-69057-2 (or the corresponding patch versions for other major releases) AND the file access component is enabled and accessible to authenticated users.
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 · scoped7.2.1-69057-2
Apply the appropriate DSM security update for the installed major version (6.2.4-25556-8, 7.0.1-42218-7, 7.1.1-42962-7, or 7.2.1-69057-2) to address the open redirect in the file access component. Consider implementing additional URL validation or Content Security Policy headers as a defense-in-depth measure.
DSM 7.2.1-69057-2 (or appropriate branch fix: 6.2.4-25556-8, 7.0.1-42218-7, 7.1.1-42962-7)
- Identify the current DSM version running on the Synology device via Control Panel > System > System Information
- Determine the appropriate upgrade path based on current version branch: for DSM 6.2.x upgrade to 6.2.4-25556-8 or later, for DSM 7.0.x upgrade to 7.0.1-42218-7 or later, for DSM 7.1.x upgrade to 7.1.1-42962-7 or later, for DSM 7.2.x upgrade to 7.2.1-69057-2 or later
- Back up critical data on the Synology device before performing the upgrade
- Apply the update via Control Panel > Update & Restore > DSM Update
- After reboot, verify the installed DSM version matches the target fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0854 — 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-2024-0854 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