First published: Fri Oct 05 2018(Updated: )
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..
Credit: security_alert@emc.com
Affected Software | Affected Version | How to fix |
---|---|---|
Pivotal Software Operations Manager | >=1.11.0<1.12.25 | |
Pivotal Software Operations Manager | >=2.0.0<2.0.16 | |
Pivotal Software Operations Manager | >=2.1.0<2.1.11 | |
Pivotal Software Operations Manager | >=2.2.0<2.2.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2018-11081 is a vulnerability in 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 that exposes the Operations Manager UAA config directly onto disk.
CVE-2018-11081 has a severity rating of 8.8 (high).
CVE-2018-11081 affects 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 by failing to write the Operations Manager UAA config onto the temp RAM disk, exposing the configs directly onto disk.
Yes, updating to Pivotal Operations Manager versions 2.2.1, 2.1.11, 2.0.16, or later resolves CVE-2018-11081.
You can find more information about CVE-2018-11081 at the following link: [https://pivotal.io/security/cve-2018-11081](https://pivotal.io/security/cve-2018-11081)