dbcve.org
Emc NetworkerApplication · Dell

CVE-2018-11050

HIGH · 8.8 CVSS v3.0 Published 2018-08-01
Fix available
A fix is available. Upgrade to after 9.2.1.3 or later.
See remediation →
93/100
Remediation priority · Urgent
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
Dell EMC NetWorker versions between 9.0 and 9.1.1.8 through 9.2.1.3, and the version 18.1.0.1 contain a Clear-Text authentication over network vulnerability in the Rabbit MQ Advanced Message Queuing Protocol (AMQP) component. User credentials are sent unencrypted to the remote AMQP service. An unauthenticated attacker in the same network collision domain, could potentially sniff the password from the network and use it to access the component using the privileges of the compromised user.

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

Dell EMC NetWorker contains a clear-text authentication vulnerability in its Rabbit MQ AMQP component. User credentials are transmitted unencrypted over the network to the remote AMQP service, allowing an unauthenticated attacker on the same network segment to sniff the plaintext password and subsequently authenticate with the compromised user's privileges.

MitigationEnable TLS/SSL encryption for the RabbitMQ AMQP connections to protect credentials in transit. If a patch is available from Dell EMC, apply the appropriate update for the specific NetWorker version.

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
Emc NetworkerApplication
Affected:<= 9.0>= 9.1.1.8, <= 9.2.1.3= 18.1.0.1

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:A/AC:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify NetWorker version
    Run 'nsrversion' command or check the installation directory for version information. On Linux: /usr/bin/nsrversion; on Windows: check the installation in Program Files.
    Affected if The installed version is 9.0 or earlier, 9.1.1.8 through 9.2.1.3, or exactly 18.1.0.1. These are the vulnerable versions.
  2. Confirm RabbitMQ AMQP component is in use
    Check for RabbitMQ processes or services running on the NetWorker server. Look for rabbitmq-server process or check NetWorker configuration for AMQP-related settings.
    Affected if RabbitMQ AMQP component is configured and actively used for communication within the NetWorker environment.
  3. Inspect RabbitMQ configuration for SSL/TLS settings
    Locate the RabbitMQ configuration file (rabbitmq.config or advanced.config, typically in /etc/rabbitmq/ on Linux or the NetWorker install directory on Windows). Look for the 'ssl_listeners' or 'ssl_options' settings.
    Affected if SSL/TLS encryption is NOT enabled - there are no ssl_listeners configured or the AMQP listeners are configured without the 'ssl' option set to true.
  4. Verify AMQP connection encryption status
    Check NetWorker server configuration files (often in nsr/config or related directories) for the AMQP connection settings. Look for connection strings or parameters that specify 'amqp://' instead of 'amqps://'.
    Affected if The AMQP connection string uses unencrypted 'amqp://' protocol rather than the encrypted 'amqps://' protocol.

A system is affected if it runs a vulnerable NetWorker version (9.0 or earlier, 9.1.1.8-9.2.1.3, or 18.1.0.1) AND has RabbitMQ AMQP configured without TLS/SSL encryption enabled for those connections.

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

Enable TLS/SSL encryption for the RabbitMQ AMQP connections to protect credentials in transit. If a patch is available from Dell EMC, apply the appropriate update for the specific NetWorker version.

Fix this in Emc Networker Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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