dbcve.org
Backup ExecApplication · Veritas

CVE-2005-0772

HIGH · 7.5 CVSS v3.1 Published 2005-06-28
Fix available
A fix is available. Upgrade to after 10.0 or later.
See remediation →
84/100
Remediation priority · High
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
VERITAS Backup Exec 9.0 through 10.0 for Windows Servers, and 9.0.4019 through 9.1.307 for Netware, allows remote attackers to cause a denial of service (Remote Agent crash) via (1) a crafted packet in NDMLSRVR.DLL or (2) a request packet with an invalid (non-0) "Error Status" value, which triggers a null dereference.

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

Remote denial of service vulnerability in VERITAS Backup Exec Remote Agent allows unauthenticated remote attackers to crash the agent via crafted packets to NDMLSRVR.DLL or packets with invalid error status values, triggering a null pointer dereference.

MitigationUpgrade to a supported Backup Exec version beyond 10.0, or apply available vendor patches. If immediate patching is not feasible, restrict network access to the Remote Agent service ports via firewall rules or network segmentation.

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
Backup ExecApplication
Affected:>= 9.0, <= 10.0>= 9.0.4019, <= 9.1.307

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 if Backup Exec Remote Agent is installed
    Check for the BERemote service or the presence of NDMLSRVR.DLL in the Backup Exec installation directory (typically C:\Program Files\VERITAS\Backup Exec\ or similar). Use 'services.msc' to look for 'Backup Exec Remote Agent' service, or use 'sc query' command.
    Affected if The service or DLL exists on the system and the version falls within 9.0 to 10.0 or 9.0.4019 to 9.1.307.
  2. Determine the installed Backup Exec version
    Open the Backup Exec console and check 'Help > About Backup Exec', or check the version in the registry under HKLM\SOFTWARE\VERITAS\Backup Exec\CurrentVersion, or examine the version of bemcms.exe or beremote.exe in the installation folder.
    Affected if The version number is between 9.0 and 10.0 inclusive, or between 9.0.4019 and 9.1.307 inclusive.
  3. Verify if the Remote Agent service is running
    Check the status of the Backup Exec Remote Agent service (commonly named 'BERemote' or 'Backup Exec Remote Agent') using 'services.msc' or the command 'sc query beremote'.
    Affected if The Remote Agent service is running and the version is within the affected ranges.
  4. Check for NDMLSRVR.DLL and its version
    Locate NDMLSRVR.DLL in the Backup Exec installation directory (typically in the 'agents' or 'remote agent' subfolder) and check its file version by right-clicking the file, selecting Properties, then Details.
    Affected if NDMLSRVR.DLL exists with a version corresponding to the affected Backup Exec versions.
  5. Assess network exposure of the Remote Agent
    Check if the Remote Agent port (default TCP 6106, though configurable) is listening on external interfaces by running 'netstat -an | findstr 6106' or using a port scanner against the host.
    Affected if The Remote Agent is listening on a non-loopback interface and the installed version is within the affected ranges.

The system is affected if VERITAS Backup Exec Remote Agent is installed with version 9.0 to 10.0 or 9.0.4019 to 9.1.307, and the service is running and 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.

From vendor data
Upgrade available Upgrade to a release after 10.0
Interim mitigation

Upgrade to a supported Backup Exec version beyond 10.0, or apply available vendor patches. If immediate patching is not feasible, restrict network access to the Remote Agent service ports via firewall rules or network segmentation.

Fix this in Backup Exec Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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