CVE-2024-50629
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 encoding or escaping of output vulnerability in the webapi component in Synology BeeStation OS (BSM) before 1.1-65374 and Synology DiskStation Manager (DSM) before 7.1.1-42962-7, 7.2-64570-4, 7.2.1-69057-6 and 7.2.2-72806-1 allow remote attackers to read limited 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 confidenceThis is an improper output encoding/escaping vulnerability in the webapi component of Synology BeeStation OS and DiskStation Manager. The flaw allows remote unauthenticated attackers to read limited files on the system due to insufficient output sanitization in the webapi. The CVSS 5.3 indicates network-based exploitation with low complexity and no privileges required.
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.0= 1.0.1= 1.0.2= 1.1>= 7.1, < 7.1.1-42962-7>= 7.2, < 7.2-64570-4>= 7.2.1-69057, < 7.2.1-69057-6>= 7.2.2, < 7.2.2-72806-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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Identify the Synology product and firmware versionAccess the DSM login page or BeeStation interface and locate the version information typically found in Control Panel > System > System Status, or run 'cat /etc/VERSION' via SSH if availableAffected if The installed version matches one of the affected ranges: BeeStation OS 1.0, 1.0.1, 1.0.2, or 1.1; DSM 7.1.x before 7.1.1-42962-7; DSM 7.2.x before 7.2-64570-4; DSM 7.2.1-69057 before 7.2.1-69057-6; or DSM 7.2.2 before 7.2.2-72806-1
-
Confirm the webapi component is accessibleAttempt to access the webapi endpoint on the Synology device, typically at /webapi/ (e.g., https://<device-ip>/webapi/)Affected if The webapi endpoint responds with HTTP 200 or other valid responses, indicating the component is exposed and reachable over the network
-
Verify network exposure of the webapi serviceCheck router/firewall configurations to determine if port 5000 (HTTP) or 5001 (HTTPS) used by DSM/BeeStation web interface is exposed to the internet or untrusted networksAffected if The webapi service is reachable from untrusted networks (WAN/internet) without network segmentation or firewall rules blocking access
-
Check if the specific vulnerable webapi endpoint is activeProbe common webapi query endpoints such as /webapi/query.cgi with test parameters to see if the API responds (do not exploit, only observe if it accepts requests)Affected if The webapi accepts and processes requests without requiring authentication, which would confirm the attack surface exists
A user is affected if their Synology BeeStation runs version 1.0-1.1 or their DSM version falls within any of the vulnerable ranges AND the webapi component is network-accessible to untrusted parties.
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.1.1-42962-77.2.1-69057-67.2.2-72806-1
Apply the vendor-supplied firmware updates: BSM to version 1.1-65374 or later, and DSM to 7.1.1-42962-7, 7.2-64570-4, 7.2.1-69057-6, or 7.2.2-72806-1 or later. Restrict webapi access to trusted networks if immediate patching is not feasible.
Beestation OS: 1.1-65374 or later; DSM: 7.1.1-42962-7, 7.2-64570-4, 7.2.1-69057-6, or 7.2.2-72806-1 (depending on major version)
- Identify whether the system is running Synology Beestation OS or DiskStation Manager (DSM)
- For Beestation OS: Upgrade to version 1.1-65374 or later
- For DiskStation Manager 7.1.x: Upgrade to version 7.1.1-42962-7 or later
- For DiskStation Manager 7.2.0: Upgrade to version 7.2-64570-4 or later
- For DiskStation Manager 7.2.1: Upgrade to version 7.2.1-69057-6 or later
- For DiskStation Manager 7.2.2: Upgrade to version 7.2.2-72806-1 or later
- After upgrade, verify the system is running a patched version by checking the DSM/Beestation OS version information
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2024-50629 — 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-50629 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