CVE-2024-48248
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 · uneditedNAKIVO Backup & Replication before 11.0.0.88174 allows absolute path traversal for reading files via getImageByPath to /c/router (this may lead to remote code execution across the enterprise because PhysicalDiscovery has cleartext credentials).
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 confidenceNAKIVO Backup & Replication before version 11.0.0.88174 contains an absolute path traversal vulnerability in the getImageByPath function accessible via the /c/router endpoint. An unauthenticated attacker can read arbitrary files from the filesystem, potentially exposing cleartext credentials stored in the PhysicalDiscovery component which can then be leveraged for remote code execution across the enterprise.
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< 11.0.0.88174CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if NAKIVO Backup & Replication is installedCheck for running processes or services named 'NAKIVO', 'Transporter', or 'Director'. On Windows, look in Services for 'NAKIVO Backup & Replication Director'. On Linux, check for processes under /opt/nakivo or similar installation directories.Affected if NAKIVO Backup & Replication Director service or process is found running on the system
-
Determine the installed versionCheck the Director version by logging into the web interface and looking at the About/Help section, or check version files in the installation directory (typically contains a file named 'version' or 'build' in the installation root). Compare the version number against 11.0.0.88174.Affected if The installed version is lower than 11.0.0.88174 or the version cannot be determined and the product is present
-
Verify if the /c/router endpoint is network-accessibleFrom an external host, attempt to access the /c/router endpoint (e.g., curl http://target:port/c/router). Also check firewall rules or reverse proxy configurations that may allow or block access to this path.Affected if The /c/router endpoint responds to unauthenticated HTTP requests from external sources
-
Locate PhysicalDiscovery configuration filesSearch the filesystem for files named 'PhysicalDiscovery', 'physical_discovery', or containing 'PhysicalDiscovery' in the filename. Common paths include the Director configuration directory, typically under the installation directory in a 'config' or 'discovery' subfolder.Affected if PhysicalDiscovery configuration files exist on the system and are readable by the web service account
-
Review access logs for path traversal attemptsExamine web server logs (typically found in the Director's logs directory) for requests to /c/router that include path parameters like 'path=' pointing to system files such as /etc/passwd, Windows system files, or configuration files containing credentials.Affected if Log entries show unauthenticated requests to /c/router with directory traversal patterns in the path parameter
If NAKIVO Backup & Replication Director is installed with a version below 11.0.0.88174 and the /c/router endpoint is network-accessible, the system is vulnerable to unauthenticated arbitrary file read via path traversal.
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 · scoped11.0.0.88174
Upgrade to NAKIVO Backup & Replication version 11.0.0.88174 or later. If immediate patching is not feasible, implement network-level restrictions to limit access to the /c/router endpoint and monitor for suspicious file access patterns.
11.0.0.88174
- Back up the current NAKIVO Backup & Replication configuration and data according to vendor documentation
- Download NAKIVO Backup & Replication version 11.0.0.88174 or later from the official NAKIVO download portal (helpcenter.nakivo.com)
- Apply the upgrade by following the official upgrade instructions for your deployment type (VMware, Hyper-V, or AWS)
- After upgrade, verify the /c/router endpoint no longer accepts path traversal requests
- Confirm the application version shows 11.0.0.88174 or later in the Director web interface
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-48248 — 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-48248 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