dbcve.org
NetworkerApplication · Emc

CVE-2015-0530

HIGH · 7.2 CVSS v2.0 Published 2015-04-17
Fix available
A fix is available. Upgrade to after 8.0.4.3 or later.
See remediation →
77/100
Remediation priority · High
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
Buffer overflow in an unspecified function in nsr_render_log in EMC NetWorker before 8.0.4.3, 8.1.x before 8.1.2.6, and 8.2.x before 8.2.1.2 allows local users to gain privileges via unknown vectors.

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 · moderate confidence

A buffer overflow vulnerability exists in the nsr_render_log function of EMC NetWorker backup software. The flaw allows a local authenticated attacker to overflow a buffer and execute arbitrary code with elevated privileges, potentially achieving root or administrator access on the affected system.

MitigationUpgrade EMC NetWorker to version 8.0.4.3, 8.1.2.6, 8.2.1.2 or later. Until patched, restrict local untrusted user access to systems running NetWorker and minimize the number of accounts with local privileges.

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
NetworkerApplication
Affected:<= 8.0.4.3= 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.4

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

AV:L/AC:L/Au:N/C:C/I:C/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. Identify NetWorker installation and version
    Run 'nsr -v' or check the installation directory for version information. On Linux/Unix, common paths include /opt/nsr/bin/nsr or /usr/sbin/nsr. On Windows, check Program Files/EMC NetWorker/nsr/bin/nsr.exe and inspect its properties for version details.
    Affected if The installed version matches 8.0.x through 8.0.4.3, or 8.1.0.x (any patch level), or 8.1.1.x through 8.1.1.4.
  2. Confirm NetWorker service is running
    Check if the NetWorker service daemon (nsrd) is running. On Linux/Unix: 'ps -ef | grep nsrd' or 'nsradmin -s localhost -c show service'. On Windows: check Services control panel for 'EMC NetWorker' service or run 'sc query nsrd'.
    Affected if The NetWorker service is active and the vulnerable nsr_render_log function is loaded in memory.
  3. Verify local authentication is enabled
    Review NetWorker authentication configuration. Check for local user accounts configured in NetWorker via 'nsradmin -c print type:NSR user' or by examining the nsrlausr file if present in the NetWorker config directory.
    Affected if Local user authentication is permitted, allowing a local authenticated attacker to trigger the vulnerable code path.
  4. Inspect log file configuration for nsr_render_log trigger
    Examine NetWorker logging configuration in nsrla.conf or nsr.conf (typically in /nsr/config on Linux/Unix or in the NetWorker config directory on Windows). Look for settings that control log rendering that would invoke the nsr_render_log function.
    Affected if Logging is enabled and configured in a manner that invokes the vulnerable function during log processing.
  5. Check file permissions on NetWorker binaries
    Verify permissions on NetWorker binaries in the installation directory. On Linux/Unix, use 'ls -la /opt/nsr/bin/' or equivalent path. On Windows, check ACLs on the NetWorker bin directory.
    Affected if Non-privileged users have write access to NetWorker binaries or config files, which could aid in exploitation but the core vulnerability applies to any local authenticated user.

A system is affected if EMC NetWorker is installed with a version matching 8.0.x through 8.0.4.3, 8.1.0.x, or 8.1.1.x through 8.1.1.4, and the service is running with local user authentication enabled.

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 8.0.4.3
Interim mitigation

Upgrade EMC NetWorker to version 8.0.4.3, 8.1.2.6, 8.2.1.2 or later. Until patched, restrict local untrusted user access to systems running NetWorker and minimize the number of accounts with local privileges.

Fix this in Networker Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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