dbcve.org
Avamar ServerApplication · Dell

CVE-2024-47484

CRITICAL · 9.8 CVSS v3.1 Published 2024-12-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Dell Avamar, versions prior to 19.12 with patch 338905, excluding 19.10 and 19.10SP1 with patch 338869, contains an Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability. An unauthenticated attacker with remote access could potentially exploit this vulnerability, leading to Command execution.

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

SQL injection vulnerability in Dell Avamar backup software allows unauthenticated remote attackers to inject malicious SQL commands, potentially leading to arbitrary command execution on the affected system.

MitigationApply vendor patch 338905 for Avamar versions prior to 19.12, or patch 338869 for versions 19.10 and 19.10SP1. If possible, upgrade to version 19.12 or later.

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
Avamar ServerApplication
Affected:= 19.4= 19.7= 19.8= 19.9= 19.10

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify installed Avamar Server version
    Run command 'avamar version' or inspect /etc/avamar/avamar.ini for the version string
    Affected if Version equals 19.4, 19.7, 19.8, 19.9, or 19.10
  2. Confirm Avamar web management interface is network accessible
    Check if ports 8080 or 8443 (default Avamar web console ports) are listening and reachable from network
    Affected if Web interface is exposed to network without proper segmentation
  3. Review authentication and database logs for SQL injection indicators
    Examine Avamar server logs in /data01/avamar/var/log/ or default log directory for unusual SQL syntax in failed login attempts or database queries
    Affected if Logs contain unexpected SQL fragments, syntax errors in queries, or multiple failed authentication attempts with special characters
  4. Audit database for unauthorized changes
    Query avamar database for unexpected user accounts, modified stored procedures, or new database objects
    Affected if Unknown database users, altered tables, or suspicious stored procedures exist

Environment is affected if Dell Avamar Server version 19.4, 19.7, 19.8, 19.9, or 19.10 is installed and the web management interface is network-accessible

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patch 338905 for Avamar versions prior to 19.12, or patch 338869 for versions 19.10 and 19.10SP1. If possible, upgrade to version 19.12 or later.

Recommended fix High confidence

Avamar Server 19.12 with patch 338905 (or 19.10/19.10SP1 with patch 338869)

  1. 1. Identify the current Avamar Server version by running: avamar version or checking the Avamar Administration Console
  2. 2. For affected versions 19.4, 19.7, 19.8, or 19.9: Download Avamar version 19.12 from Dell support portal
  3. 3. Apply patch 338905 to the upgraded 19.12 version
  4. 4. Alternatively, if currently on version 19.10 or 19.10SP1: Download and apply patch 338869 from Dell support portal
  5. 5. After patching, verify the installation by checking: avamar --version and confirm patch 338905 or 338869 is listed
  6. 6. Restart Avamar services if required by the patch documentation
  7. 7. In a non-production environment first, verify that critical Avamar functionality (backup, restore, management operations) still works correctly
  8. 8. After validation in non-production, apply the same upgrade/patching to production environment
Caveat Review Dell Avamar 19.12 release notes for any changes to supported features, backup formats, or compatibility with connected systems before upgrading production environments

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Avamar Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-47484 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2024-47484 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