dbcve.org
Networker ClientApplication · Emc

CVE-2008-6219

HIGH · 7.8 CVSS v2.0 Published 2009-02-20
Fix available
A fix is available. Upgrade to after 7.3.2 or later.
See remediation →
87/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
nsrexecd.exe in multiple EMC Networker products including EMC NetWorker Server, Storage Node, and Client 7.3.x and 7.4, 7.4.1, 7.4.2, Client and Storage Node for Open VMS 7.3.2 ECO6 and earlier, Module for Microsoft Exchange 5.1 and earlier, Module for Microsoft Applications 2.0 and earlier, Module for Meditech 2.0 and earlier, and PowerSnap 2.4 SP1 and earlier does not properly control the allocation of memory, which allows remote attackers to cause a denial of service (memory exhaustion) via multiple crafted RPC requests.

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

The nsrexecd.exe daemon in EMC NetWorker products fails to properly control memory allocation, allowing remote attackers to exhaust server memory through multiple crafted RPC requests, causing denial of service.

MitigationApply vendor-released patches for affected EMC NetWorker versions or upgrade to patched releases; consider network segmentation or firewall rules to restrict RPC access to trusted hosts if patches are unavailable.

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
Networker ClientApplication
Affected:<= 7.3<= 7.3.2= 7.4= 7.4.1= 7.4.2
Networker ModulePlugin / extension
Affected:<= 2.0<= 5.1
Networker PowersnapApplication
Affected:<= 2.4
Networker ServerApplication
Affected:<= 7.3= 7.4= 7.4.1= 7.4.2
Networker Storage NodeApplication
Affected:<= 7.3<= 7.3.2= 7.4= 7.4.1= 7.4.2

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
Authentication
None
Confidentiality
None
Integrity
None
Availability
Complete

AV:N/AC:L/Au:N/C:N/I:N/A:C

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. Verify EMC NetWorker installation
    Check for NetWorker installation by looking for the installation directory (typically C:\Program Files\LEGATO\nsr or C:\nsr on Windows, or /usr/nsr on Unix/Linux) or by querying installed software via system inventory tools. On Windows, check Registry key HKLM\SOFTWARE\LEGATO or look for nsrexecd.exe in the system.
    Affected if NetWorker software is found on the system
  2. Identify installed NetWorker version
    Query the nsrexecd.exe version by running 'nsrinfo -v' or checking the executable's version property. On Windows, right-click nsrexecd.exe and select Properties > Details. On Unix/Linux, run 'nsradmin -s localhost' or check the version via the NetWorker command line tools.
    Affected if The version matches any of the affected ranges: Client/Server/Storage Node <= 7.3, <= 7.3.2, = 7.4, = 7.4.1, = 7.4.2; Module <= 2.0, <= 5.1; Powersnap <= 2.4
  3. Confirm nsrexecd service is running
    Check if the nsrexecd daemon is actively running on the system. On Windows, open Services console and look for 'NetWorker Remote Execution Service' or run 'sc query nsrexecd'. On Unix/Linux, run 'ps -ef | grep nsrexecd' or check via 'nsradmin -s localhost'.
    Affected if The nsrexecd service is running or enabled, making the vulnerability exploitable
  4. Verify RPC listener configuration
    Confirm that the system has RPC ports open and listening. On Windows, run 'netstat -an | findstr "RPC"' or use Portqry.exe to enumerate RPC endpoints. On Unix/Linux, run 'rpcinfo -p localhost' if the rpcbind service is running.
    Affected if RPC services are exposed (port 7937-7938 default for NetWorker, or dynamic RPC ports) and accessible from the network

The system is affected if EMC NetWorker is installed with a version matching the affected ranges AND the nsrexecd daemon is running, exposing RPC services 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.

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

Apply vendor-released patches for affected EMC NetWorker versions or upgrade to patched releases; consider network segmentation or firewall rules to restrict RPC access to trusted hosts if patches are unavailable.

Fix this in Networker Client Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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