CVE-2025-21120
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 Avamar, versions prior to 19.10 SP1 with patch 338904, contains a Trusting HTTP Permission Methods on the Server-Side vulnerability in Security. A low privileged attacker with remote access could potentially exploit this vulnerability, leading to Information exposure.
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 Avamar contains a vulnerability where the server improperly trusts HTTP permission methods, allowing a low-privileged attacker with remote access to bypass authorization controls and access sensitive information. The issue stems from insufficient validation of HTTP method permissions on the server-side.
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= 19.4= 19.7= 19.8= 19.9= 19.10= 19.12CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 Dell Avamar installation and versionLocate Avamar installation directory or check system inventory for Dell Avamar. Common paths include /opt/dell/avamar or check via system package manager. Query the Avamar version using 'avm version' command or check /etc/avamar/verison.info if accessible.Affected if The installed version matches 19.4, 19.7, 19.8, 19.9, 19.10, or 19.12.
-
Verify HTTP service is exposedCheck if Avamar web services are listening on network ports. Common ports: 80, 443, 8080, 8443. Use 'netstat -tuln | grep -E "(80|443|8080|8443)"' or 'nmap -p 80,443,8080,8443 <localhost>' to identify exposed HTTP endpoints.Affected if The Avamar HTTP/HTTPS management interface is accessible from network positions.
-
Confirm remote access capabilityDetermine if low-privileged users can reach the Avamar web interface. Check network ACLs, firewall rules, or VPN configurations that permit remote access to the Avamar management URLs. Review authentication configuration to verify user access levels.Affected if Low-privileged or unauthenticated remote users can send HTTP requests to the Avamar server.
A user is affected if their Dell Avamar installation matches versions 19.4, 19.7, 19.8, 19.9, 19.10, or 19.12 AND the HTTP management interface is accessible remotely to users with limited privileges.
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.
dbcve · scopedApply Dell Avamar version 19.10 SP1 with patch 338904 to remediate this vulnerability. Restrict network access to trusted personnel until the patch is applied.
19.10 SP1 with patch 338904
- 1. Plan maintenance window for the Avamar upgrade
- 2. Back up all critical data and configuration settings
- 3. Upgrade Dell Avamar to version 19.10 SP1
- 4. Apply patch 338904 to the upgraded system
- 5. Verify the installation and patch were applied successfully
- 6. Test that the vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-21120 — 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-2025-21120 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