dbcve.org
Avamar ServerApplication · Dell

CVE-2024-52538

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 Script injection.

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

Dell Avamar contains a SQL injection vulnerability allowing a low-privileged attacker with remote access to inject malicious SQL commands, potentially leading to script injection. The flaw exists in versions prior to 19.12 with patch 338905 (and specific exclusions for 19.10/19.10SP1 with patch 338869).

MitigationApply vendor-supplied patch 338905 to versions prior to 19.12, or patch 338869 for versions 19.10/19.10SP1. Restrict network access to trusted users to reduce attack surface until patching is complete.

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. Identify installed Dell Avamar Server version
    Run 'avmaint version' or check the Avamar administrative console for the exact version number (for example, 19.4, 19.7, 19.8, 19.9, or 19.10)
    Affected if The installed version is one of the listed affected versions: 19.4, 19.7, 19.8, 19.9, or 19.10, and it is earlier than 19.12 without patch 338905 applied
  2. Verify patch 338905 or 338869 is applied
    Check the Avamar patch management system or run 'avmaint patchlist' to see if patches 338905 (for versions prior to 19.10) or 338869 (for version 19.10) are installed
    Affected if The target version is affected and neither patch 338905 nor patch 338869 is present
  3. Confirm remote SQL interface is accessible
    Determine if the Avamar SQL-based management interface or reporting features are exposed to the network. Check firewall rules and access controls for port 443 or the Avamar web console
    Affected if The SQL interface is network-accessible without proper segmentation or additional authentication layers
  4. Review access control for low-privileged accounts
    Check if low-privileged user accounts exist in the Avamar system that have access to SQL-facing features. Audit account permissions using 'useradm' or similar Avamar admin tools
    Affected if Low-privileged users have access to functionality that processes SQL commands without proper input sanitization
  5. Examine logs for SQL injection indicators
    Search Avamar server logs (typically in /usr/local/avamar/var/logs or via the management console) for suspicious SQL syntax, unexpected database queries, or error messages containing SQL keywords
    Affected if Logs contain patterns consistent with SQL injection attempts, such as UNION SELECT, OR 1=1, or malformed SQL in query fields

You are affected if the installed Dell Avamar Server version is 19.4, 19.7, 19.8, 19.9, or 19.10 without patch 338905 (or patch 338869 for 19.10), and the SQL interface is accessible to remote 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-supplied patch 338905 to versions prior to 19.12, or patch 338869 for versions 19.10/19.10SP1. Restrict network access to trusted users to reduce attack surface until patching is complete.

Recommended fix High confidence

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

  1. 1. Identify the current Avamar Server version using the system management interface or command line utilities.
  2. 2. Determine the appropriate patch based on your current version: For versions 19.4, 19.7, 19.8, or 19.9, obtain patch 338905.
  3. 3. For Avamar versions 19.10 or 19.10SP1, obtain patch 338869 instead.
  4. 4. Download the required patch from Dell support portal at www.dell.com using valid support credentials.
  5. 5. Apply the patch following Dell's standard patch deployment procedure for Avamar Server.
  6. 6. Verify the patch was applied successfully by checking the system version and patch status.
  7. 7. Validate the SQL injection vulnerability is remediated through security testing.

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

Fix this in Avamar Server Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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