CVE-2016-0905
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 · uneditedAvamar Data Store (ADS) and Avamar Virtual Edition (AVE) in EMC Avamar Server before 7.3.0-233 allow local users to obtain root privileges by leveraging admin access and entering a sudo command.
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 confidenceLocal privilege escalation vulnerability in EMC Avamar Server versions before 7.3.0-233 allows users with admin-level access to obtain root privileges by exploiting sudo command configuration. The vulnerability requires local authenticated access with admin privileges, making it a privilege escalation rather than initial access vector.
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<= 7.3.0CVSS 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
- Local
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify EMC Avamar Server installationConfirm the system is running EMC Avamar Server by checking system information, product documentation, or installed packages related to AvamarAffected if The system is not EMC Avamar Server
-
Determine installed Avamar Server versionUse system commands or check Avamar version information to obtain the exact version number installed (e.g., avamar --version, or check /opt/avamar/etc/version if applicable)Affected if Version is 7.3.0 or any version lower than 7.3.0-233
-
Compare version to CVE affected rangeCompare your installed version against the affected range: versions before 7.3.0-233Affected if Installed version is before 7.3.0-233
-
Verify local admin access existsConfirm the user checking for this CVE has admin-level access to the Avamar Server systemAffected if Local authenticated admin access is present on an affected version
-
Examine sudo configuration for privilege escalation pathsReview the sudoers configuration (typically /etc/sudoers or in /etc/sudoers.d/) for any entries that allow admin users to execute commands as root without password or with elevated privilegesAffected if Sudo configuration permits admin users to obtain root privileges without proper restrictions
User is affected if running EMC Avamar Server version 7.3.0 or below (before 7.3.0-233) with admin-level local access and a sudo configuration that allows privilege escalation to root.
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.
From vendor dataUpgrade Avamar Server to version 7.3.0-233 or later, or review and remediate sudo configuration to restrict admin users from gaining unauthorized root access.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-0905 — 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-2016-0905 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