dbcve.org
Operations ManagerApplication · Pivotal Software

CVE-2018-11081

HIGH · 8.8 CVSS v3.0 Published 2018-10-05
Fix available
A fix is available. Upgrade to 1.12.25 / 2.0.16 or later.
See remediation →
94/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
Pivotal Operations Manager, versions 2.2.x prior to 2.2.1, 2.1.x prior to 2.1.11, 2.0.x prior to 2.0.16, and 1.11.x prior to 2, fails to write the Operations Manager UAA config onto the temp RAM disk, thus exposing the configs directly onto disk. A remote user that has gained access to the Operations Manager VM, can now file search and find the UAA credentials for Operations Manager on the system disk..

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

Pivotal Operations Manager versions prior to 2.2.1, 2.1.11, 2.0.16, and 2.x for 1.11.x fail to write UAA (User Account and Authentication) configuration credentials to a temporary RAM disk. Instead, the sensitive UAA credentials are written directly to the system disk, making them discoverable through file searches by anyone who has gained access to the Operations Manager virtual machine.

MitigationUpgrade Operations Manager to version 2.2.1, 2.1.11, 2.0.16, or 2.x (for 1.11.x) to ensure UAA credentials are written to temp RAM disk instead of system disk. If upgrading is not immediately possible, restrict access to the VM and search for exposed credentials to rotate them.

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.11.0, < 1.12.25>= 2.0.0, < 2.0.16>= 2.1.0, < 2.1.11>= 2.2.0, < 2.2.1

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/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 Operations Manager version
    Access the Ops Manager UI and navigate to the 'Settings' > 'Advanced Features' page, or run 'om ops-manager --version' if the om CLI is installed. Alternatively, check the product tile metadata file in /var/lib/tiles/ or the installation directory.
    Affected if The installed version falls within < 1.12.25, < 2.0.16, < 2.1.11, or < 2.2.1 (or 1.11.x versions) as listed in the affected ranges.
  2. Locate UAA credential files on system disk
    Search the system disk (not in tmpfs/ramdisk) for files containing UAA-related credentials. Common locations include installation directories, configuration folders, or log directories. Use commands like 'find / -name '*uaa*' -o -name '*credential*' 2>/dev/null' to locate relevant files.
    Affected if UAA configuration files containing sensitive credentials are found written to the persistent system disk rather than a temporary RAM disk.
  3. Inspect installation log directories
    Check /var/log/ or installation-specific log directories for any UAA credential dumps, configuration exports, or backup files that may have been created during setup. Look for files with 'uaa', 'credentials', 'admin', or 'scim' in the filename.
    Affected if Log files or backup artifacts containing UAA usernames, passwords, or secrets are present on the persistent disk.
  4. Review tmp directory contents
    Examine whether the expected tmpfs/ramdisk location (/tmp or /run) actually contains UAA credential files that were not cleaned up, or conversely whether credentials were written to locations outside tmpfs.
    Affected if Credentials were written to non-tmpfs locations, indicating the vulnerability where credentials should have been written to a temporary RAM disk but were instead written to the system disk.

A user is affected if their Operations Manager version is within the affected ranges AND UAA credentials are discoverable on the persistent system disk instead of only in a temporary RAM disk location.

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 1.12.25 / 2.0.16 / 2.1.11 or later
Fixed in 1.12.252.0.162.1.11
Interim mitigation

Upgrade Operations Manager to version 2.2.1, 2.1.11, 2.0.16, or 2.x (for 1.11.x) to ensure UAA credentials are written to temp RAM disk instead of system disk. If upgrading is not immediately possible, restrict access to the VM and search for exposed credentials to rotate them.

Fix this in Operations Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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