CVE-2019-3765
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 · uneditedDell EMC Avamar Server versions 7.4.1, 7.5.0, 7.5.1, 18.2 and 19.1 and Dell EMC Integrated Data Protection Appliance (IDPA) versions 2.0, 2.1, 2.2, 2.3 and 2.4 contain an Incorrect Permission Assignment for Critical Resource vulnerability. A remote authenticated malicious user potentially could exploit this vulnerability to view or modify sensitive backup data. This could be used to make backups corrupt or potentially to trick a user into restoring a backup with malicious files in place.
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 confidenceDell EMC Avamar Server and IDPA contain an Incorrect Permission Assignment vulnerability where remote authenticated users can view or modify sensitive backup data due to overly permissive access controls on critical resources. This could allow attackers to corrupt backups or trick users into restoring malicious files.
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.4.1= 7.5.0= 7.5.1= 18.2= 19.1>= 2.0, <= 2.4CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 the installed productLog into the system and determine whether it is Dell EMC Avamar Server or Dell EMC Integrated Data Protection Appliance (IDPA). Check the product name in the system console or run 'dmidecode -s system-product-name' if available.Affected if The product is Avamar Server or IDPA
-
Determine the product versionRun the appropriate version command for the product. For Avamar Server, check '/opt/avamar/var/avamar.version' or use the avmanager CLI tool. For IDPA, check the IDPA management interface or version file.Affected if The version matches 7.4.1, 7.5.0, 7.5.1, 18.2, or 19.1 for Avamar Server, or falls between 2.0 and 2.4 inclusive for IDPA
-
Inspect backup data directory permissionsLocate the backup storage directories (typically under /mnt/backup or /data on Avamar). Use 'ls -la' to list permissions on these directories. Look for permissions that allow access beyond the intended backup administrator accounts.Affected if Backup directories are readable or writable by unauthorized users, have overly permissive group permissions (such as group-readable/writable by all authenticated users), or lack proper owner restrictions
-
Check access control configurationReview the Avamar or IDPA access control configuration files. Check for entries in permission configuration files that grant excessive privileges to authenticated users beyond their role. Look for any 'world-readable' or 'group-readable' flags on sensitive backup metadata files.Affected if Configuration files show that authenticated users other than administrators can read or modify backup metadata and data files
You are affected if the installed product is Avamar Server (versions 7.4.1, 7.5.0, 7.5.1, 18.2, or 19.1) or IDPA (versions 2.0-2.4) AND the backup data directories or configuration have overly permissive access controls that allow unauthorized users to view or modify backup data.
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 dataApply vendor security patches for the affected Avamar (7.4.1, 7.5.0, 7.5.1, 18.2, 19.1) and IDPA (2.0-2.4) versions, and review file/system permissions to ensure proper access controls on backup data.
- Consultation4.0 h
- Implementation6.0 h
- Testing6.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 $5,312.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3765 — 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-2019-3765 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