dbcve.org
Avamar ServerApplication · Dell

CVE-2024-47977

HIGH · 8.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 →
94/100
Remediation priority · Urgent
Remotely reachable 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. A low privileged 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 a low-privileged remote attacker to inject malicious SQL commands via unsanitized user input, potentially achieving command execution on the underlying system.

MitigationApply vendor patches 338905 (for versions prior to 19.12) or 338869 (for 19.10/19.10SP1). Until patched, restrict network access to Avamar management interfaces and disable unnecessary remote access.

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm Dell Avamar Server installation and version
    Run 'avamar version' or check /opt/avamar/etc/avserver.version file to identify installed Avamar version. Also check 'dp-cli --get_all_providers' or consult Avamar administrative console for version information.
    Affected if Version is 19.4, 19.7, 19.8, 19.9, or 19.10
  2. Identify exposed management interfaces
    Review firewall rules and network configuration to determine if Avamar management ports (typically 80, 443, 3000, 8080, 8443) are accessible from untrusted networks. Use 'netstat -tuln' or 'ss -tuln' to list listening services.
    Affected if Management interfaces are exposed to internet or untrusted networks without proper access controls
  3. Review authentication logs for SQL injection attempts
    Examine Avamar server logs in /opt/avamar/var/logs/ for entries containing SQL keywords (SELECT, UNION, INSERT, DROP) in authentication parameters, unusual error messages about database syntax, or failed login attempts with malformed input.
    Affected if Logs contain suspicious SQL-like strings in user input fields or database error messages indicating injection attempts
  4. Check for unauthorized database modifications
    Query Avamar database for unexpected changes to user accounts, backup job configurations, or scheduled tasks that may indicate successful SQL injection leading to command execution.
    Affected if Unknown user accounts, modified backup jobs, or unexpected scheduled tasks exist in Avamar configuration

System is affected if Dell Avamar Server version is 19.4, 19.7, 19.8, 19.9, or 19.10 and the management interface is network-accessible to potential attackers.

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 patches 338905 (for versions prior to 19.12) or 338869 (for 19.10/19.10SP1). Until patched, restrict network access to Avamar management interfaces and disable unnecessary remote access.

Recommended fix High confidence

Avamar Server version 19.12 with patch 338905

  1. 1. Identify the current Avamar Server version by checking the system information or using Avamar administration tools
  2. 2. If currently running a version prior to 19.12, plan for an upgrade to Avamar version 19.12
  3. 3. Before upgrading, ensure you have a complete backup of the Avamar Server data and configuration
  4. 4. Perform the upgrade to Avamar version 19.12, which includes patch 338905
  5. 5. After upgrade, verify the version is correctly reported as 19.12 with patch 338905 applied
  6. 6. Test that the SQL injection vulnerability is no longer present by verifying the fix

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

Fix this in Avamar Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-47977 — 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-47977 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