dbcve.org
Beestation OsOperating system · Synology

CVE-2024-10445

MEDIUM · 5.3 CVSS v3.1 Published 2025-03-19
Fix available
A fix is available. Upgrade to 6.2.4-25556-8 / 7.2.1-69057-6 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Improper certificate validation vulnerability in the update functionality in Synology BeeStation OS (BSM) before 1.1-65374 and Synology DiskStation Manager (DSM) before 6.2.4-25556-8, 7.1.1-42962-7, 7.2-64570-4, 7.2.1-69057-6 and 7.2.2-72806-1 allow remote attackers to write 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 confidence

Improper certificate validation in the update functionality of Synology BeeStation OS and DiskStation Manager allows remote attackers to write limited files via unspecified vectors. The vulnerability stems from the system not properly validating certificates during the update process, potentially enabling man-in-the-middle attacks to inject malicious content.

MitigationUpdate Synology BSM to version 1.1-65374 or later, and DSM to versions 6.2.4-25556-8, 7.1.1-42962-7, 7.2-64570-4, 7.2.1-69057-6, or 7.2.2-72806-1 or later to remediate the improper certificate validation vulnerability.

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
Beestation OsOperating system
Affected:= 1.0= 1.0.1= 1.0.2= 1.1
Diskstation ManagerOperating system
Affected:>= 6.2, < 6.2.4-25556-8>= 7.2, < 7.2-64570-4>= 7.2.1-69057, < 7.2.1-69057-6>= 7.2.2, < 7.2.2-72806-1

CVSS 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
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Synology product type
    Access the web interface. For BeeStation, visit the local IP or bee.synology.com. For DiskStation Manager, access via the device IP on port 5000/5001. Note which product interface loads.
    Affected if The product is either Synology BeeStation OS or Synology DiskStation Manager (DSM)
  2. Check BeeStation OS version
    If using BeeStation, log into the web interface and navigate to Settings > About, or check the version displayed on the main dashboard. Note the exact version number.
    Affected if The installed version is 1.0, 1.0.1, 1.0.2, or 1.1 (any version before 1.1-65374)
  3. Check DSM version
    If using DSM, open Control Panel > System > System Status > DSM Update, or run `cat /etc/VERSION` via SSH. Note the full version string including build number.
    Affected if The installed version falls within: 6.2 to 6.2.4-25556-7; 7.2 to 7.2-64570-3; 7.2.1-69057 to 7.2.1-69057-5; or 7.2.2 to 7.2.2-72806-0
  4. Verify update functionality is accessible
    Confirm the system has not disabled update checking. Navigate to Control Panel > Update & Restore (DSM) or Settings > Updates (BeeStation) and verify the update check feature is available and not grayed out or administratively disabled.
    Affected if Update functionality is enabled and the system can check for or receive updates
  5. Check for automatic update configuration
    In DSM, go to Control Panel > Update & Restore > DSM Update Settings. In BeeStation, check Settings > Updates. Note whether automatic update checks are enabled.
    Affected if Automatic update checks are enabled, making the certificate validation vulnerability reachable during update attempts

You are affected if you are running any BeeStation OS version 1.0 through 1.1, or any DSM version within the affected ranges listed, and the update feature is accessible on your system.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 6.2.4-25556-8 / 7.2.1-69057-6 / 7.2.2-72806-1 or later
Fixed in 6.2.4-25556-87.2.1-69057-67.2.2-72806-1
Interim mitigation

Update Synology BSM to version 1.1-65374 or later, and DSM to versions 6.2.4-25556-8, 7.1.1-42962-7, 7.2-64570-4, 7.2.1-69057-6, or 7.2.2-72806-1 or later to remediate the improper certificate validation vulnerability.

Recommended fix High confidence

BeeStation OS 1.1-65374; DSM 6.2.4-25556-8; DSM 7.2-64570-4; DSM 7.2.1-69057-6; DSM 7.2.2-72806-1 or later

  1. 1. Identify the currently installed Synology BeeStation OS (BSM) or DiskStation Manager (DSM) version via the control panel or system information.
  2. 2. For BeeStation OS users: Upgrade to version 1.1-65374 or later.
  3. 3. For DiskStation Manager 6.2.x users: Upgrade to version 6.2.4-25556-8 or later.
  4. 4. For DiskStation Manager 7.2.x users: Upgrade to version 7.2-64570-4 or later.
  5. 5. For DiskStation Manager 7.2.1.x users: Upgrade to version 7.2.1-69057-6 or later.
  6. 6. For DiskStation Manager 7.2.2.x users: Upgrade to version 7.2.2-72806-1 or later.
  7. 7. After upgrade, verify the update functionality works correctly and confirm the new version is reflected in the system.
Caveat Standard Synology update procedures apply; ensure backups exist before updating

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Beestation Os Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-10445 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-10445 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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