dbcve.org
Industrial Network DirectorApplication · Cisco

CVE-2019-1881

HIGH · 8.8 CVSS v3.0 Published 2019-06-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
A vulnerability in the web-based management interface of Cisco Industrial Network Director (IND) could allow an unauthenticated, remote attacker to conduct a cross-site request forgery (CSRF) attack and perform arbitrary actions on an affected device. The vulnerability is due to insufficient CSRF protections for the web-based management interface of the affected device. An attacker could exploit this vulnerability by persuading a user of the interface to follow a malicious link. A successful exploit could allow the attacker to use a web browser and the privileges of the user to perform arbitrary actions on an affected device. For more information about CSRF attacks and potential mitigations, see Understanding Cross-Site Request Forgery Threat 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 · high confidence

Cross-site request forgery (CSRF) vulnerability in Cisco Industrial Network Director's web-based management interface allows unauthenticated remote attackers to trick authenticated users into executing unintended actions. Insufficient anti-CSRF protections enable malicious links to trigger arbitrary operations using the victim's session privileges.

MitigationImplement anti-CSRF tokens on all state-changing requests, validate Origin/Referer headers server-side, and configure SameSite cookie attributes. Apply available Cisco patches for Cisco Industrial Network Director.

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
Affected:= 1.5\(0.250\)

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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. Confirm Cisco Industrial Network Director is installed
    Locate the installation directory or check running services for Cisco Industrial Network Director components. On Linux, check /opt/cisco/ind/ or similar paths. On Windows, check Program Files for CiscoIND.
    Affected if The product is present and running on the system
  2. Check installed version number
    Access the web management interface and navigate to the About or System Info page, or run: show version from the CLI if available. Compare the version to 1.5(0.250).
    Affected if The installed version is exactly 1.5(0.250)
  3. Verify web-based management interface is enabled
    Check if the web interface (HTTPS/HTTP on port 443/80 or custom port) is listening. Run: netstat -an | grep -E '80|443|8080' or check the service status.
    Affected if The web management interface is active and accessible over the network
  4. Inspect session cookies for SameSite attribute
    Log into the web interface using a browser, open Developer Tools, go to Application/Storage tab, and examine cookies for the session cookie. Check if SameSite attribute is set to Lax or Strict.
    Affected if The SameSite attribute is missing, set to None, or not present on session cookies
  5. Check for anti-CSRF token implementation
    Capture a web request using browser DevTools (Network tab) when performing a state-changing action (e.g., adding a user, changing settings). Inspect if a unique token parameter is included in the request body or headers.
    Affected if State-changing requests do not contain anti-CSRF tokens and rely only on session cookies

The environment is affected if Cisco Industrial Network Director version 1.5(0.250) is running with its web-based management interface accessible and the application lacks SameSite cookie attributes and anti-CSRF tokens on state-changing requests.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-CSRF tokens on all state-changing requests, validate Origin/Referer headers server-side, and configure SameSite cookie attributes. Apply available Cisco patches for Cisco Industrial Network Director.

Fix this in Industrial Network Director Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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