AvamarApplication · Emc

CVE-2016-0906

HIGH · 8.8 CVSS v3.0 Published 2016-07-06
Fix available
A fix is available. Upgrade to after 7.2.1 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 web-restore interface in Avamar Data Store (ADS) and Avamar Virtual Edition (AVE) in EMC Avamar through 7.1.2 and 7.2.x through 7.2.1 allows remote authenticated users to read or delete directories via a Linux backup-restore operation.

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

This is an authenticated directory traversal/arbitrary file access vulnerability in the web-restore interface of EMC Avamar backup systems (versions through 7.1.2 and 7.2.x through 7.2.1). Authenticated users can exploit the Linux backup-restore operation to read or delete directories outside their intended scope, indicating insufficient access controls in the web-restore functionality.

MitigationApply available vendor patches for EMC Avamar to remediate this vulnerability; if patches are unavailable, restrict network access to the web-restore interface to trusted internal users only and monitor for unauthorized restore operations.

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
AvamarApplication
Affected:<= 7.2.1

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

CVSS:3.0/AV:N/AC:L/PR:L/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. Confirm EMC Avamar installation
    Check for Avamar processes (avtar, avmgr, avamarded) or look for /opt/avamar directory structure. On the Avamar server, run 'dpkg -l | grep avamar' or 'rpm -qa | grep avamar' to list installed Avamar packages.
    Affected if System is not running EMC Avamar product
  2. Determine Avamar version
    Run 'avamar --version' or check /opt/avamar/etc/avamar.version file. Alternatively, access the web management console and check the About/System Info page for the version number.
    Affected if Installed version is 7.2.1 or lower, or any 7.1.x version through 7.1.2
  3. Verify web-restore interface accessibility
    Check if port 8543 (default web-restore/HTTPS) is listening. Run 'netstat -tlnp | grep 8543' or 'ss -tlnp | grep 8543' on the Avamar server. Also check firewall rules for inbound access to this port.
    Affected if Web-restore interface port 8543 is exposed and accessible from untrusted networks
  4. Confirm web-restore service status
    Check if the avamar-web-restore or avweb restore service is running. Run 'service avwebd status' or look for avwebd/avamar-web-restore process: 'ps aux | grep avweb'
    Affected if Web-restore service (avwebd) is running and accessible to authenticated users
  5. Review web-restore user accounts
    Examine /opt/avamar/etc/mcserver.ini or the Avamar user database for accounts with restore privileges. Check if default or test accounts exist with restore permissions.
    Affected if There are authenticated user accounts configured with restore access

A system is affected if it is running EMC Avamar version 7.2.1 or lower, has the web-restore interface enabled, and has user accounts with restore permissions accessible to untrusted 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.

From vendor data
Upgrade available Upgrade to a release after 7.2.1
Interim mitigation

Apply available vendor patches for EMC Avamar to remediate this vulnerability; if patches are unavailable, restrict network access to the web-restore interface to trusted internal users only and monitor for unauthorized restore operations.

Fix this in Avamar Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,790
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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