Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2019-3790: 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

34
Routine
MEDIUM 6.1UPGRADE

CVE-2019-3790 is a medium-severity flaw (CVSS 6.1) affecting operations manager. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

  • No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score6.1 (Medium)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededHigh
User interactionRequired
EPSS exploit chance0.7% (top 49%)
CISA exploited listNo
WeaknessCWE-324, CWE-613
Published2019-06-06
Last modified2026-06-17
Publisher (CNA): Dell · Vendor: pivotal software

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

pivotal software operations manager UPGRADE
Affected: >= 2.2.0 and < 2.2.23 · >= 2.3.0 and < 2.3.16 · >= 2.4.0 and < 2.4.11 · >= 2.5.0 and < 2.5.3
Fixed in: 2.2.23, 2.3.16, 2.4.11, 2.5.3
Safe to downgrade to: a release before 2.2.0
1. Check installed version
apt-cache policy operations-manager || rpm -q operations-manager || operations-manager --version
2. UPGRADE to 2.2.23 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade operations-manager
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade operations-manager
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 2.2.0 (Debian / Ubuntu)
apt-cache madison operations-manager sudo apt install operations-manager=<VERSION_BEFORE_2.2.0> sudo apt-mark hold operations-manager
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list operations-manager sudo dnf downgrade operations-manager-<VERSION_BEFORE_2.2.0> sudo dnf versionlock add operations-manager
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2019-3790?

operations manager: upgrade to 2.2.23, 2.3.16, 2.4.11, 2.5.3. Exact commands for each OS are on this page.

Is CVE-2019-3790 being exploited?

CVE-2019-3790 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2019-3790 affect?

CVE-2019-3790 affects operations manager. Severity is medium (CVSS 6.1). 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 authentica

How urgent is CVE-2019-3790?

Priority 34/100. No elevated risk signals yet.

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.