Active Backup For Business AgentApplication · Synology

CVE-2023-52950

MEDIUM · 5.3 CVSS v3.1 Published 2024-09-26
Fix available
A fix is available. Upgrade to 2.7.0-3221 or later.
See remediation →
58/100
Remediation priority · Elevated
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
Missing encryption of sensitive data vulnerability in login component in Synology Active Backup for Business Agent before 2.7.0-3221 allows adjacent man-in-the-middle attackers to obtain user credential 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

The Synology Active Backup for Business Agent transmits user credentials in cleartext during the login process, allowing attackers on the same network segment to intercept authentication credentials through man-in-the-middle attacks. This affects versions prior to 2.7.0-3221.

MitigationUpgrade Synology Active Backup for Business Agent to version 2.7.0-3221 or later to implement proper encryption of sensitive data in transit during authentication.

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
Active Backup For Business AgentApplication
Affected:< 2.7.0-3221

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
Adjacent
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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

  1. Verify if Synology Active Backup for Business Agent is installed
    Check for the presence of the agent service or executable. On Windows, look for the service named 'Synology Active Backup for Business Agent' in Services.msc or check for installation in Program Files. On Linux, check for /usr/syno/activebackup/agent or similar installation directories.
    Affected if The agent software is present on the system
  2. Determine the installed version of the agent
    Open the Synology Active Backup for Business Agent application and view the About or Version information typically found in the Help menu, or check the executable properties of the agent binary for its version metadata.
    Affected if Unable to determine the version or version is below 2.7.0-3221
  3. Confirm the vulnerability condition
    Compare the identified version against the affected range: any version prior to 2.7.0-3221 is vulnerable. The vulnerability is exploitable when the agent communicates with the Active Backup for Business server over the network.
    Affected if Installed version is less than 2.7.0-3221 and the agent is used to connect to a server

The environment is affected if Synology Active Backup for Business Agent is installed with a version number lower than 2.7.0-3221 and the agent is actively connecting to a server.

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 2.7.0-3221 or later
Fixed in 2.7.0-3221
Interim mitigation

Upgrade Synology Active Backup for Business Agent to version 2.7.0-3221 or later to implement proper encryption of sensitive data in transit during authentication.

Recommended fix High confidence

2.7.0-3221 or later

  1. Verify current Active Backup for Business Agent version by opening the application and checking 'Help' > 'About'
  2. Download the latest Synology Active Backup for Business Agent from the official Synology download center at www.synology.com
  3. Stop any backup tasks currently running to ensure a clean upgrade
  4. Run the installer and follow the on-screen prompts to upgrade the agent
  5. After installation, verify the version shows 2.7.0-3221 or later in 'Help' > 'About'
  6. Reconnect the agent to your Synology NAS and resume backup operations

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

Fix this in Active Backup For Business Agent Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-52950 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-52950 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