dbcve.org
Operations ManagerApplication · Pivotal

CVE-2016-0930

CRITICAL · 9.8 CVSS v3.0 Published 2016-09-18
Fix available
A fix is available. Upgrade to after 1.6.18 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Pivotal Cloud Foundry (PCF) Ops Manager before 1.6.19 and 1.7.x before 1.7.10, when vCloud or vSphere is used, has a default password for compilation VMs, which allows remote attackers to obtain SSH access by connecting within an installation-time period during which these VMs exist.

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

PCF Ops Manager versions prior to 1.6.19 and 1.7.x prior to 1.7.10 use a default password for compilation VMs when deployed on vCloud or vSphere platforms. Attackers can obtain SSH access to these temporary compilation VMs during the installation window when they exist, potentially gaining privileged access to the cloud foundry environment.

MitigationUpgrade Ops Manager to version 1.6.19 or later / 1.7.10 or later. If patching is not immediately possible, ensure compilation VMs are network-isolated from untrusted networks during the installation phase.

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
Operations ManagerApplication
Affected:<= 1.6.18= 1.7.0= 1.7.1= 1.7.2= 1.7.3= 1.7.4= 1.7.5= 1.7.6= 1.7.7= 1.7.8= 1.7.9

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

CVSS:3.0/AV:N/AC:L/PR:N/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. Check Ops Manager version
    Log into the Ops Manager UI or check the installation directory for the Ops Manager version file. In the Ops Manager UI, the version is displayed on the login page or in the product tile. Alternatively, check the deployed Ops Manager VM for its version.
    Affected if The installed version is 1.6.x through 1.6.18, or 1.7.0 through 1.7.9
  2. Identify the underlying IaaS platform
    Determine whether the Ops Manager and Cloud Foundry deployment is running on vCloud Director or vSphere. Check the infrastructure configuration,Ops Manager installation settings, or consult your infrastructure team to confirm the IaaS provider.
    Affected if The deployment targets vCloud or vSphere platforms (this vulnerability does not affect other IaaS platforms such as AWS, Azure, or OpenStack)
  3. Review compilation VM lifecycle
    Determine if compilation VMs were created during any Ops Manager installation or upgrade performed with the affected versions. Compilation VMs are temporary VMs created during the deployment phase and should not persist after installation completes. Check for any residual compilation VMs or deployment logs showing compilation VM creation.
    Affected if Compilation VMs existed or still exist during or after installation on the affected Ops Manager versions
  4. Assess network exposure of compilation VMs
    Review network ACLs, security groups, and firewall rules applied to the infrastructure during the installation window. Determine if the network segments containing compilation VMs were accessible from untrusted networks or the public internet.
    Affected if Compilation VMs were accessible from networks outside the trusted administrative infrastructure during the installation phase

You are affected if Ops Manager version is 1.6.x through 1.6.18 or 1.7.0 through 1.7.9, deployed on vCloud or vSphere, and compilation VMs were accessible during the installation window.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 1.6.18
Interim mitigation

Upgrade Ops Manager to version 1.6.19 or later / 1.7.10 or later. If patching is not immediately possible, ensure compilation VMs are network-isolated from untrusted networks during the installation phase.

Recommended fix High confidence

Ops Manager 1.6.19+ or 1.7.10+ (or migrate to latest stable 1.x release)

  1. Upgrade Ops Manager 1.6.x to version 1.6.19 or later
  2. If running Ops Manager 1.7.0-1.7.2, upgrade to version 1.7.10 or later
  3. After upgrading, verify compilation VMs no longer use default credentials during deployment
  4. Consult Pivotal documentation for upgrade procedures specific to your deployment type (vCloud or vSphere)
Caveat PCF upgrade procedures may require downtime and configuration verification; test in staging before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Operations 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 the upgrade done

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-2016-0930 — 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-0930 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