dbcve.org
UmbrellaApplication · Cisco

CVE-2018-0435

CRITICAL · 9.1 CVSS v3.0 Published 2018-10-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
97/100
Remediation priority · Urgent
Remotely reachable 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 Umbrella API could allow an authenticated, remote attacker to view and modify data across their organization and other organizations. The vulnerability is due to insufficient authentication configurations for the API interface of Cisco Umbrella. An attacker could exploit this vulnerability to view and potentially modify data for their organization or other organizations. A successful exploit could allow the attacker to read or modify data across multiple organizations.

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 · moderate confidence

A vulnerability in the Cisco Umbrella API allows an authenticated attacker to view and modify data across multiple organizations due to insufficient authentication configurations. The flaw enables cross-tenant data access, potentially allowing reading or modification of data belonging to other organizations.

MitigationApply vendor-provided patches or updates for Cisco Umbrella API authentication. Review and enforce proper API authentication and authorization controls to ensure proper tenant isolation.

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
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
High

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/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 Umbrella API usage
    Review your environment for any integration with Cisco Umbrella API, including custom scripts, third-party tools, or automated workflows that connect to Umbrella's API endpoints
    Affected if Your organization uses Cisco Umbrella API for any integration or automation
  2. Verify API authentication configuration
    Check your API integration settings in the Cisco Umbrella dashboard under API > Settings to confirm whether API keys or tokens are configured with organization-level privileges rather than per-tenant privileges
    Affected if API keys are configured with organization-level access that spans multiple tenants or if authentication is shared across organizations
  3. Inspect API key scope and permissions
    Review the API credentials used for Umbrella integrations and verify whether they have permissions scoped to only your specific organization or if they inadvertently grant access to other organizations
    Affected if API credentials grant cross-organization access or have overly broad permissions beyond your tenant
  4. Check for cross-tenant data access attempts
    Review API access logs if available, looking for API calls that accessed data from organization identifiers (ORG IDs) different from your own
    Affected if API access logs show data being retrieved or modified for organization IDs that do not match your organization
  5. Confirm tenant isolation in API responses
    Test API calls to retrieve data and verify that responses only contain data belonging to your organization and not data from other tenant organizations
    Affected if API responses contain or allow access to data belonging to other organizations

Your organization is affected if you use Cisco Umbrella API and your API authentication configuration allows cross-tenant access or lacks proper tenant isolation controls.

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

Apply vendor-provided patches or updates for Cisco Umbrella API authentication. Review and enforce proper API authentication and authorization controls to ensure proper tenant isolation.

Fix this in Umbrella Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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