CVE-2024-47265
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 limitation of a pathname to a restricted directory ('Path Traversal') vulnerability in encrypted share umount functionality in Synology Active Backup for Business before 2.7.1-13234, 2.7.1-23234 and 2.7.1-3234 allows remote authenticated users to write specific 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 confidencePath traversal vulnerability in encrypted share umount functionality of Synology Active Backup for Business allows authenticated remote users to write files outside restricted directories due to insufficient input validation on path parameters.
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< 2.7.1-13234< 2.7.1-3234< 2.7.1-23234CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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.
-
Verify Active Backup for Business Agent is installedCheck for the presence of the Synology Active Backup for Business Agent service or executable on the system. On Windows, look for the service named 'Active Backup for Business Agent' in Services.msc or check for installation under Program Files/Synology. On Linux, check for the abba-agent package or service.Affected if The agent software is present on the system
-
Determine installed agent versionOpen the Active Backup for Business Agent console or use the command line to retrieve the version information. On Windows, right-click the agent icon in the system tray and select 'About' or run the agent with a version flag. On Linux, check /var/log/ActiveBackupForBusiness/agent.log or use package queries.Affected if The version shown is earlier than 2.7.1-13234, 2.7.1-23234, or 2.7.1-3234
-
Confirm encrypted share feature is configuredIn the Active Backup for Business Agent settings, check if any encrypted shares (encrypted backup shares) are configured. The vulnerability exists specifically in the 'encrypted share umount' functionality, so encrypted shares must be present for the flaw to be exploitable.Affected if Encrypted backup shares are configured in the agent
-
Check agent authentication exposureVerify who has access to the Active Backup for Business Agent console or remote management interface. The vulnerability requires an 'authenticated remote user' to exploit, so assess whether the agent is accessible to untrusted users or over untrusted networks.Affected if The agent is accessible to users beyond the intended trusted administrators
The environment is affected if Synology Active Backup for Business Agent is installed with a version earlier than 2.7.1-13234, 2.7.1-23234, or 2.7.1-3234 AND encrypted shares are configured AND the agent can be accessed by 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 · scoped2.7.1-32342.7.1-132342.7.1-23234
Update Synology Active Backup for Business to version 2.7.1-13234, 2.7.1-23234, or 2.7.1-3234 or later to patch the vulnerability.
Active Backup for Business Agent version 2.7.1-13234 or later (also available in versions 2.7.1-23234 and 2.7.1-3234)
- 1. Open Synology DiskStation Manager (DSM) on your Synology device
- 2. Navigate to Package Center
- 3. Find 'Active Backup for Business' in the installed packages
- 4. Click on 'Update' to check for available updates
- 5. If an update is available, click 'Update' to install the latest version
- 6. Alternatively, manually download the updated Agent from Synology's download center and reinstall it on affected machines
- 7. Ensure the Agent version is 2.7.1-13234 or higher after update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47265 — 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-47265 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