CVE-2017-8022
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 · uneditedAn issue was discovered in EMC NetWorker (prior to 8.2.4.9, all supported 9.0.x versions, prior to 9.1.1.3, prior to 9.2.0.4). The Server service (nsrd) is affected by a buffer overflow vulnerability. A remote unauthenticated attacker may potentially exploit this vulnerability to execute arbitrary code on vulnerable installations of the software, or cause a denial of service, depending on the target system's platform.
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's Server service (nsrd) contains a buffer overflow vulnerability that allows remote unauthenticated attackers to potentially execute arbitrary code or cause denial of service by sending specially crafted requests to the affected service.
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.2.4.8= 9.0.0.3= 9.0.0.4= 9.0.0.5= 9.0.0.6= 9.0.0.7= 9.0.0.8= 9.0.1.1= 9.0.1.2= 9.0.1.3= 9.0.1.4= 9.0.1.5CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify EMC NetWorker installation and versionLocate the EMC NetWorker installation directory and determine the installed version. Common methods include checking the nsrd executable version information, reviewing installation logs, or querying the package management system if installed via an OS package.Affected if The installed version matches one of the affected versions: any version <= 8.2.4.8, or any of 9.0.0.3 through 9.0.0.8, or 9.0.1.1 through 9.0.1.5.
-
Confirm the nsrd service is runningVerify that the NetWorker Server service (nsrd) is actively running on the system. This is typically done by checking running processes or service status commands appropriate to the operating system.Affected if The nsrd service is running and exposed to the network, making it reachable by remote attackers.
-
Check network exposure of nsrd serviceInspect network listener configuration and firewall rules to determine if the nsrd service port is accessible from untrusted networks. Review any port bindings and networkACL configurations.Affected if The nsrd service port is exposed to untrusted or public networks without proper network segmentation or access controls.
A system is affected if it runs a vulnerable version of EMC NetWorker (as listed in the affected versions) with the nsrd service exposed to potentially untrusted network segments.
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 dataApply vendor patches: upgrade to 8.2.4.9 or later, 9.1.1.3 or later, or 9.2.0.4 or later. If immediate patching is not possible, consider network segmentation to limit exposure of the nsrd service to untrusted networks.
- Consultation3.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,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-8022 — 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-2017-8022 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