dbcve.org
Enterprise BackupApplication · Unitrends

CVE-2014-3008

HIGH · 10.0 CVSS v2.0 Published 2014-04-28
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
Public exploit 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
Unitrends Enterprise Backup 7.3.0 allows remote authenticated users to execute arbitrary commands via shell metacharacters in the comm parameter to recoveryconsole/bpl/snmpd.php.

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 · high confidence

Command injection vulnerability in Unitrends Enterprise Backup 7.3.0 allows authenticated users to execute arbitrary OS commands by injecting shell metacharacters into the 'comm' parameter of the recoveryconsole/bpl/snmpd.php SNMP configuration script.

MitigationRestrict access to the recoveryconsole interface, disable SNMP services if unused, or apply vendor patch. Implement strict input validation on the comm parameter to sanitize shell metacharacters before passing to system calls.

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
Enterprise BackupApplication
Affected:= 7.3.0

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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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 Unitrends Enterprise Backup version
    Check the installed version of Unitrends Enterprise Backup. On the appliance, you can typically find this via the web interface footer, or by running: grep -i version /opt/backup/images/current_version 2>/dev/null or examining the RPM package: rpm -q unitrends-backup
    Affected if The installed version is exactly 7.3.0
  2. Verify the vulnerable SNMP script exists
    Check if the file recoveryconsole/bpl/snmpd.php exists in the web root. Common paths include /var/www/html/recoveryconsole/bpl/snmpd.php or similar. Locate the web document root and search for this path.
    Affected if The file recoveryconsole/bpl/snmpd.php exists on the system
  3. Confirm SNMP service is configured
    Check if SNMP service is enabled or has been configured. Inspect the Unitrends SNMP settings through the web UI under Recovery Console > SNMP Configuration, or check for SNMP-related configuration files in /etc/snmp/ or the Unitrends config directory.
    Affected if SNMP configuration feature is accessible or SNMP service is running
  4. Check if recoveryconsole interface is exposed
    Verify the recoveryconsole web interface is accessible. Test connectivity to the recoveryconsole endpoint (typically at /recoveryconsole/ or /recoveryconsole/bpl/) on the backup server.
    Affected if The recoveryconsole interface is accessible from the network without proper access restrictions
  5. Audit access logs for the vulnerable endpoint
    Review web server access logs for requests to recoveryconsole/bpl/snmpd.php, particularly those containing shell metacharacters like | ; $ ( ) or command substitutions. Check /var/log/httpd/access_log or equivalent.
    Affected if There are log entries showing access to snmpd.php with suspicious parameters containing shell metacharacters

You are affected if Unitrends Enterprise Backup version 7.3.0 is installed AND the recoveryconsole/bpl/snmpd.php script is accessible AND SNMP configuration can be accessed by authenticated users.

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

Restrict access to the recoveryconsole interface, disable SNMP services if unused, or apply vendor patch. Implement strict input validation on the comm parameter to sanitize shell metacharacters before passing to system calls.

Recommended fix Moderate confidence

Contact Unitrends/Datto support for the patched version of Enterprise Backup (versions after 7.3.0 contain the fix)

  1. 1. Identify the current Unitrends Enterprise Backup version in use by checking the system or documentation.
  2. 2. Contact Unitrends (now known as Datto) support to obtain the specific patched version or security update for version 7.3.0.
  3. 3. If an upgrade path is provided by the vendor, schedule a maintenance window to apply the update.
  4. 4. After upgrading, verify the snmpd.php file has been patched or replaced with a version that properly sanitizes the 'comm' parameter.
  5. 5. As a temporary mitigation if upgrade is not immediately possible, restrict access to the recoveryconsole/bpl/snmpd.php endpoint using web server access controls or firewall rules to only trusted IP addresses.
  6. 6. Implement input validation and sanitization on the 'comm' parameter in snmpd.php if patch deployment is delayed: ensure only expected alphanumeric characters are accepted before passing to any system calls.
Caveat Before upgrading, backup all data and verify compatibility with any integrated systems; major version upgrades may change functionality

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

Fix this in Enterprise Backup Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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