dbcve.org
Novabackup DatacenterApplication · Novastor

CVE-2016-4899

CRITICAL · 9.8 CVSS v3.0 Published 2017-04-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
The datamover module in the Linux version of NovaBACKUP DataCenter before 09.06.03.0353 is vulnerable to remote command execution via unspecified attack 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 datamover module in NovaBACKUP DataCenter for Linux versions prior to 09.06.03.0353 contains a remote command execution vulnerability allowing unauthenticated attackers to execute arbitrary commands on the affected system. The attack vector is network-based and requires no authentication, explaining the critical CVSS score of 9.8.

MitigationUpgrade NovaBACKUP DataCenter to version 09.06.03.0353 or later. If immediate patching is not feasible, restrict network access to the datamover module and implement additional monitoring for suspicious activity.

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
Novabackup DatacenterApplication
Affected:all versions

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
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 if NovaBACKUP DataCenter for Linux is installed
    Check for the presence of NovaBACKUP DataCenter installation directories or binaries on the system. Look for common installation paths or use package management tools if available.
    Affected if NovaBACKUP DataCenter for Linux is found on the system
  2. Determine the installed version of NovaBACKUP DataCenter
    Locate and read the version information for the NovaBACKUP DataCenter installation. Compare the installed version against the affected range (all versions prior to 09.06.03.0353).
    Affected if The installed version is any version prior to 09.06.03.0353, or if the version cannot be determined but the product is present
  3. Identify if the datamover module is enabled and accessible
    Consult NovaBACKUP DataCenter documentation or configuration to determine whether the datamover module is enabled. Check if the module is exposed on the network or accessible via an API endpoint.
    Affected if The datamover module is enabled and accessible on the network
  4. Assess network exposure of the datamover service
    Review firewall rules and network configuration to determine if the datamover service port or endpoint is exposed to untrusted networks. Check for open ports associated with the datamover module.
    Affected if The datamover service is reachable from untrusted network segments or the public internet

The system is affected if NovaBACKUP DataCenter for Linux is installed with any version prior to 09.06.03.0353 and the datamover module is enabled and network-accessible.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade NovaBACKUP DataCenter to version 09.06.03.0353 or later. If immediate patching is not feasible, restrict network access to the datamover module and implement additional monitoring for suspicious activity.

Recommended fix High confidence

09.06.03.0353 or later

  1. 1. Identify the current installed version of NovaBACKUP DataCenter on the Linux system
  2. 2. Download NovaBACKUP DataCenter version 09.06.03.0353 or later from the official vendor (NovaBACKUP)
  3. 3. Review the official upgrade/release notes for version 09.06.03.0353
  4. 4. Create a complete backup of the current NovaBACKUP DataCenter configuration and data
  5. 5. Stop the NovaBACKUP DataCenter services
  6. 6. Install the updated version 09.06.03.0353 following the vendor's upgrade documentation
  7. 7. Verify the datamover module version is now 09.06.03.0353 or higher
  8. 8. Restart NovaBACKUP DataCenter services

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

Fix this in Novabackup Datacenter Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-4899 — 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-2016-4899 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