CVE-2024-5401
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 control of dynamically-managed code resources vulnerability in WebAPI component in Synology DiskStation Manager (DSM) before 7.1.1-42962-8 and 7.2.1-69057-2 and 7.2.2-72806 and Synology Unified Controller (DSMUC) before 3.1.4-23079 allows remote authenticated users to obtain privileges without consent 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 confidenceImproper control of dynamically-managed code resources in the WebAPI component of Synology DiskStation Manager (DSM) and Synology Unified Controller (DSMUC) allows authenticated remote users to escalate privileges. This vulnerability stems from insufficient validation of dynamically-generated code or parameters, enabling authenticated attackers to execute unauthorized code with elevated permissions.
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, < 7.2.1-69057-2>= 7.2.2-72803, < 7.2.2-72806>= 3.1-23028, < 3.1.4-23079CVSS 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
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 in useLog into DSM and navigate to Control Panel > Info Center, or run `cat /etc/VERSION` via SSH to view the installed build numberAffected if The version shown is 7.2.1-69057 through 7.2.1-69057-1, or 7.2.2-72803 through 7.2.2-72805
-
Check DSM Unified Controller version if deployedAccess DSMUC via the Hybrid Share interface or check the version through the Unified Controller admin panelAffected if The version shown is 3.1-23028 through 3.1.4-23078
-
Confirm WebAPI component is accessibleVerify the Synology WebAPI endpoint is reachable from the network. Test connectivity by accessing `https://[hostname]/webapi/query.cgi` in a browserAffected if The WebAPI endpoint responds without being blocked by firewall or access controls, as this is the attack surface for the vulnerability
-
Audit administrator accounts for unauthorized changesNavigate to Control Panel > User & Group > Administrator in DSM, or use `synouser --list` via SSH to enumerate all admin accountsAffected if Unexpected administrator accounts exist, or existing accounts show unauthorized privilege escalation since the vulnerable version was installed
You are affected if your DSM version falls within 7.2.1-69057 to 7.2.1-69057-1 or 7.2.2-72803 to 7.2.2-72805, or your DSMUC version is between 3.1-23028 and 3.1.4-23078, and the WebAPI component is 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 · scoped3.1.4-230797.2.1-69057-27.2.2-72806
Update Synology DSM to version 7.1.1-42962-8 or later for 7.1.x branches, or 7.2.1-69057-2/7.2.2-72806 or later for 7.2.x branches. Update DSMUC to version 3.1.4-23079 or later. Verify no unauthorized accounts or privilege changes occurred.
DSM 7.2.1-69057-2 or DSM 7.2.2-72806 or DSMUC 3.1.4-23079 depending on product line
- 1. Identify the current DSM or DSMUC version from Control Panel > System > System Status
- 2. For DiskStation Manager 7.2.1-69057 and later builds before 7.2.1-69057-2: Navigate to Control Panel > Update & Restore > DSM Update and apply update 7.2.1-69057-2
- 3. For DiskStation Manager 7.2.2-72803 and later builds before 7.2.2-72806: Navigate to Control Panel > Update & Restore > DSM Update and apply update 7.2.2-72806
- 4. For DiskStation Manager Unified Controller 3.1-23028 and later builds before 3.1.4-23079: Access the controller web interface, navigate to Control Panel > Update & Restore and apply update 3.1.4-23079
- 5. After update completion, verify the new version in System > System Status > DSM version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-5401 — 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-5401 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