dbcve.org
UmbrellaApplication · Cisco

CVE-2019-1807

HIGH · 8.8 CVSS v3.0 Published 2019-05-03
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 session management functionality of the web UI for the Cisco Umbrella Dashboard could allow an authenticated, remote attacker to access the Dashboard via an active, user session. The vulnerability exists due to the affected application not invalidating an existing session when a user authenticates to the application and changes the users credentials via another authenticated session. An attacker could exploit this vulnerability by using a separate, authenticated, active session to connect to the application through the web UI. A successful exploit could allow the attacker to maintain access to the dashboard via an authenticated user's browser session. Cisco has addressed this vulnerability in the Cisco Umbrella Dashboard. No user action is required.

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

This is a session fixation vulnerability in Cisco Umbrella Dashboard's web UI session management. When a user authenticates and changes their credentials, the application fails to invalidate existing active sessions, allowing an attacker with a separate authenticated session to maintain persistent access through the original user's browser session.

MitigationSince Cisco has addressed this vulnerability with no user action required, ensure your Cisco Umbrella Dashboard is updated to the patched version and monitor for any unauthorized session access.

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
UmbrellaApplication
Affected:all versions

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 Umbrella usage
    Identify if your organization uses the Cisco Umbrella Dashboard by checking your registered services, SSO configurations, or cloud service subscriptions for Cisco Umbrella
    Affected if Your organization uses the Cisco Umbrella Dashboard for DNS filtering, web security, or cloud security services
  2. Determine Cisco Umbrella version
    Log into the Cisco Umbrella Dashboard and navigate to Admin > Account > Account Settings to view the current version information, or check via Cisco Umbrella API using GET /api/v1/organizations/{orgId}
    Affected if The installed version is not the latest patched version released after CVE-2019-1807 fix
  3. Test session invalidation behavior
    Create an active authenticated session in the Cisco Umbrella Dashboard, then change the account password through the user settings. Using a separate browser or incognito window, attempt to use the original session cookie/token to perform actions
    Affected if The original session remains valid and can perform actions after the password has been changed, indicating session fixation vulnerability is present
  4. Review active session inventory
    In Cisco Umbrella Dashboard, go to Admin > Users > Active Sessions or equivalent session management panel. Check for any unexpected concurrent sessions, especially from IP addresses or locations not recognized
    Affected if Multiple active sessions exist for a single account where only one legitimate session should be active, which could indicate exploitation of session fixation

A user is affected if they are on a pre-patched version of Cisco Umbrella and can confirm that sessions remain valid after credential changes, or if unexpected concurrent sessions are detected.

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

Since Cisco has addressed this vulnerability with no user action required, ensure your Cisco Umbrella Dashboard is updated to the patched version and monitor for any unauthorized session access.

Fix this in Umbrella Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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