dbcve.org
Findit Network ManagerApplication · Cisco

CVE-2019-1919

HIGH · 7.8 CVSS v3.0 Published 2019-07-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
A vulnerability in the Cisco FindIT Network Management Software virtual machine (VM) images could allow an unauthenticated, local attacker who has access to the VM console to log in to the device with a static account that has root privileges. The vulnerability is due to the presence of an account with static credentials in the underlying Linux operating system. An attacker could exploit this vulnerability by logging in to the command line of the affected VM with the static account. A successful exploit could allow the attacker to log in with root-level privileges. This vulnerability affects only Cisco FindIT Network Manager and Cisco FindIT Network Probe Release 1.1.4 if these products are using Cisco-supplied VM images. No other releases or deployment models are known to be vulnerable.

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

Cisco FindIT Network Manager and Probe VM images (Release 1.1.4) contain a static Linux account with hardcoded credentials that provides root-level access. An attacker with local VM console access can authenticate using these credentials without any other authentication requirements.

MitigationIf using Cisco-supplied VM images for FindIT 1.1.4, contact Cisco for updated VM images that remove the static account. Restrict physical and console access to the VM environment as a defense-in-depth measure.

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
Findit Network ManagerApplication
Affected:= 1.1.4
Findit Network ProbeApplication
Affected:= 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
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:L/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 Cisco FindIT version
    Access the FindIT Network Manager web interface or CLI and run the command to display the software version (typically 'show version' or check the About page in the GUI). Record the exact version number.
    Affected if The installed version is exactly 1.1.4 for either Cisco FindIT Network Manager or Cisco FindIT Network Probe.
  2. Confirm VM image deployment
    Check whether the FindIT software is running on a Cisco-supplied VM image. This can be verified through hypervisor inventory (VMware, Hyper-V, etc.) or by checking VM metadata/snapshots if available.
    Affected if The system is deployed using Cisco-supplied VM images for version 1.1.4.
  3. Inspect local system accounts
    Log into the VM console (or use out-of-band management) and list all local Linux accounts (check /etc/passwd or run 'getent passwd' and 'getent shadow'). Look for any unfamiliar accounts beyond the standard administrative accounts.
    Affected if An unexpected static account exists in /etc/passwd that was not created by your organization.
  4. Verify console access controls
    Review VM console access logs and physical/logical access controls to the hypervisor and VM console. Check if console access is unrestricted or uses default/weak authentication.
    Affected if Unrestricted console access is permitted without multi-factor authentication or network isolation.

You are affected if running Cisco FindIT Network Manager or Probe version 1.1.4 as a VM image with an undocumented static local account providing root access.

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

If using Cisco-supplied VM images for FindIT 1.1.4, contact Cisco for updated VM images that remove the static account. Restrict physical and console access to the VM environment as a defense-in-depth measure.

Fix this in Findit Network Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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