CVE-2025-21117
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, version 19.4 or later, contains an access token reuse vulnerability in the AUI. A low privileged local attacker could potentially exploit this vulnerability, leading to fully impersonating the user.
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 versions 19.4 and later contain an access token reuse vulnerability in the AUI (Administrative User Interface). The flaw allows a low-privileged local attacker to reuse access tokens, enabling full user impersonation.
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.10CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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 installed Dell Avamar versionRun the command to query the Avamar server version (e.g., avamar version or avamar --version). Compare the output against the affected versions: 19.4, 19.7, 19.8, 19.9, 19.10.Affected if The installed version matches exactly one of these: 19.4, 19.7, 19.8, 19.9, or 19.10.
-
Confirm AUI is enabledCheck the Avamar administrative interface configuration to determine if the Administrative User Interface (AUI) web service is running and accessible. This may involve checking the avauiconfig file, service status, or querying the AUI endpoint.Affected if The AUI is enabled and accessible on the system.
-
Review user session logs for token anomaliesExamine Avamar audit and session logs for entries showing access token reuse, particularly tokens being used across different privilege levels or from unexpected sources. Look for repeated session tokens or token activity outside expected patterns.Affected if Logs contain evidence of access tokens being reused or session tokens appearing multiple times with different user contexts.
-
Check for unexpected privileged sessionsReview active and recent user sessions in the AUI for accounts with elevated privileges that were not created by known administrators, or for sessions showing rapid privilege escalation.Affected if There are active sessions or historical session records showing user impersonation or unexpected privilege escalation.
-
Inspect AUI authentication configurationExamine the AUI authentication configuration files for settings related to token validation, session timeout, and token reuse policies. Look for misconfigurations that would allow token replay.Affected if Token validation is weak, session timeouts are excessively long, or token reuse restrictions are disabled.
You are affected if your Dell Avamar Server runs version 19.4, 19.7, 19.8, 19.9, or 19.10 AND the AUI is enabled, with any evidence of token reuse or unauthorized session activity.
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 the vendor-provided patch or security update for Dell Avamar. Review and rotate any potentially compromised access tokens, and limit local access to the AUI until the patch is applied.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-21117 — 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-21117 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