Industrial Network DirectorApplication · Cisco
CVE-2019-1976
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 · uneditedA vulnerability in the “plug-and-play” services component of Cisco Industrial Network Director (IND) could allow an unauthenticated, remote attacker to access sensitive information on an affected device. The vulnerability is due to improper access restrictions on the web-based management interface. An attacker could exploit this vulnerability by sending a crafted HTTP request to an affected device. A successful exploit could allow the attacker to access running configuration information about devices managed by the IND, including administrative credentials.
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 confidenceAn information disclosure vulnerability in Cisco Industrial Network Director's plug-and-play services component allows unauthenticated remote attackers to bypass access restrictions on the web-based management interface. By sending crafted HTTP requests, attackers can retrieve running configuration data and administrative credentials stored on the affected device.
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
Industrial Network DirectorApplication
< 1.6.0
Network Level ServiceApplication
= 1.6\(0.369\)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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Cisco Industrial Network Director installationLocate the Cisco Industrial Network Director application on the system or network inventory. Confirm the product name matches 'Cisco Industrial Network Director' exactly.Affected if The product is Cisco Industrial Network Director and version is below 1.6.0
-
Verify installed versionAccess the web-based management interface and navigate to the About or System Information section to view the running version. Alternatively, use the command line interface if available to retrieve version information.Affected if Version is displayed as less than 1.6.0 (for example, 1.5.x or earlier)
-
Confirm web management interface exposureDetermine if the web-based management interface is accessible from network locations outside the trusted internal network. Attempt to reach the interface via HTTP/HTTPS from an untrusted network segment or external IP.Affected if The management interface is accessible from untrusted networks without additional authentication barriers
-
Check plug-and-play service statusWithin the Cisco Industrial Network Director web interface, navigate to the plug-and-play services configuration panel. Verify whether the plug-and-play service is enabled and listening for incoming connections.Affected if Plug-and-play services are enabled and the interface is network-accessible
A system is affected if it runs Cisco Industrial Network Director version below 1.6.0 with the web management interface network-accessible and plug-and-play services enabled.
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.
dbcve · scoped1.6.0
Restrict network access to the Cisco IND management interface using firewall rules or IP ACLs until a vendor patch is applied. If exposed to the internet, immediately disable remote access or implement additional authentication layers.
Cisco Industrial Network Director version 1.6.0 or later
- 1. Identify all Cisco Industrial Network Director (IND) installations in the environment
- 2. Check the current version of IND by accessing the web-based management interface or using the system CLI
- 3. If the version is below 1.6.0, download the updated software version 1.6.0 or later from the Cisco Software Download Center (tools.cisco.com)
- 4. Review Cisco release notes for any configuration or compatibility considerations before upgrading
- 5. Apply the upgrade following Cisco's standard IND installation and upgrade procedures
- 6. After upgrading, verify that the web-based management interface is accessible and the version reflects 1.6.0 or later
- 7. Confirm that the previously accessible sensitive information without authentication is no longer exposed
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Industrial Network Director
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1976 — 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-2019-1976 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