Ops Manager uaa client issues tokens after refresh token expiration

published 2019-06-06 7y ago modified 2026-06-17 4mo ago also EUVD-2019-13421

cvss: 6.1; version 3.0, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.7%; EPSS 0.7% chance of exploitation in 30 days, percentile 51%
public exploits: 0; none known

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.

Patch / fix

fixed in 1

Pivotal Pivotal Ops Manager 2.2.23, 2.3.16, 2.4.11, 2.5.3

Is CVE-2019-3790 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.65% chance of exploitation in the next 30 days, higher than 51% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.0	6.1	CVSS:3.0/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:N
NVD	3.0	5.4	CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
NVD	2.0	5.5	AV:N/AC:L/Au:S/C:P/I:P/A:N

Affected products

Pivotal Pivotal Ops Manager

Classification

Weakness

CWE-324 Use of a Key Past its Expiration Date
CWE-613 DEPRECATED: Insufficient Session Expiration

References

pivotal.io /security/cve-2019-3790
vendor-advisory
securityfocus.com /bid/108512
vdb-entry, third-party-advisory

Sources

CVE List CVE-2019-3790
NVD CVE-2019-3790

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.