dbcve.org
ManagerApplication · Cloudera

CVE-2016-4950

HIGH · 7.5 CVSS v3.0 Published 2017-03-07
Fix available
A fix is available. Upgrade to after 5.5.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
Cloudera Manager 5.5 and earlier allows remote attackers to enumerate user sessions via a request to /api/v11/users/sessions.

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

Cloudera Manager versions 5.5 and earlier contain an information disclosure vulnerability where the endpoint /api/v11/users/sessions returns active user session data without proper authentication. This allows remote unauthenticated attackers to enumerate valid user sessions, potentially facilitating session hijacking or further attacks.

MitigationUpgrade Cloudera Manager to version 5.6 or later to obtain the vendor patch. Until upgraded, restrict network access to the administrative interface using firewall rules or VPN to limit exposure to untrusted networks.

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
ManagerApplication
Affected:<= 5.5.0

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
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 Cloudera Manager version
    Run 'cloudera-scm --version' or check /usr/lib/cloudera-scm-server/lib/cloudera-manager-server*.jar for version, or query the /api/v11/version endpoint
    Affected if Version is 5.5.0 or lower (e.g., 5.5.0, 5.4.x, 5.3.x, etc.)
  2. Confirm API endpoint accessibility
    Attempt to access http://<cm-host>:7180/api/v11/users/sessions from an untrusted network or non-authenticated context using curl or a browser
    Affected if The endpoint returns HTTP 200 with session data (JSON array of active sessions) without requiring authentication credentials
  3. Check network exposure of admin interface
    Review firewall rules or network ACLs to determine if port 7180 (or custom CM port) is accessible from untrusted networks
    Affected if The Cloudera Manager web interface is exposed to networks where untrusted users can reach it directly

You are affected if running Cloudera Manager version 5.5.0 or earlier AND the /api/v11/users/sessions endpoint is reachable from a network where untrusted users can access it without authentication.

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
Upgrade available Upgrade to a release after 5.5.0
Interim mitigation

Upgrade Cloudera Manager to version 5.6 or later to obtain the vendor patch. Until upgraded, restrict network access to the administrative interface using firewall rules or VPN to limit exposure to untrusted networks.

Fix this in Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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