CVE-2015-6849
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 · uneditedEMC NetWorker before 8.0.4.5, 8.1.x before 8.1.3.6, 8.2.x before 8.2.2.2, and 9.0 before build 407 allows remote attackers to cause a denial of service (process outage) via malformed RPC authentication messages.
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 confidenceEMC NetWorker backup software contains a vulnerability in its RPC authentication handling. Remote attackers can send malformed RPC authentication messages to trigger a denial of service, causing a process outage. The vulnerability affects versions 8.0.x before 8.0.4.5, 8.1.x before 8.1.3.6, 8.2.x before 8.2.2.2, and 9.0 before build 407.
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= 8.0.4.4= 8.1.0.0= 8.1.0.1= 8.1.0.2= 8.1.0.3= 8.1.0.4= 8.1.0.5= 8.1.1.0= 8.1.1.1= 8.1.1.2= 8.1.1.3= 8.1.1.4CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed EMC NetWorker versionRun 'nsr -version' or check the program's 'About' dialog. On Windows, check Add/Remove Programs. On Unix/Linux, check '/usr/bin/nsr' version or look for version file in installation directory.Affected if Version is 8.0.x before 8.0.4.5, 8.1.x before 8.1.3.6, 8.2.x before 8.2.2.2, or 9.0 before build 407. Specific versions listed include 8.0.4.4 and 8.1.0.0 through 8.1.1.4.
-
Verify NetWorker RPC service is exposedCheck if the NetWorker service (nsrd or nsrexecd) is listening on RPC ports. Run 'rpcinfo -p' on Unix or check open ports with 'netstat -an | grep 7937' (default NetWorker RPC port) on any platform.Affected if RPC service is accessible from network, as the vulnerability is remotely exploitable via malformed RPC authentication messages.
-
Confirm NetWorker processes are runningCheck for running processes: 'ps -ef | grep nsr' on Unix or check Windows services for 'EMC NetWorker' or 'Legato NetWorker' services.Affected if NetWorker processes are running and exposed to network, as the denial of service causes process outage.
You are affected if EMC NetWorker is installed with a version matching the vulnerable ranges AND the RPC service is network-accessible.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate EMC NetWorker to the patched version (8.0.4.5, 8.1.3.6, 8.2.2.2, or build 407 for 9.0). Consider network segmentation to limit exposure to untrusted networks since this is a remotely exploitable vulnerability.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-6849 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-6849 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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