CVE-2019-3776
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedPivotal Operations Manager, 2.1.x versions prior to 2.1.20, 2.2.x versions prior to 2.2.16, 2.3.x versions prior to 2.3.10, 2.4.x versions prior to 2.4.3, contains a reflected cross site scripting vulnerability. A remote user that is able to convince an Operations Manager user to interact with malicious content could execute arbitrary JavaScript in the user's browser.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencePivotal Operations Manager contains a reflected cross-site scripting (XSS) vulnerability in versions 2.1.x prior to 2.1.20, 2.2.x prior to 2.2.16, 2.3.x prior to 2.3.10, and 2.4.x prior to 2.4.3. An attacker can craft malicious content that, when interacted with by an authenticated Operations Manager user, causes arbitrary JavaScript to execute in the victim's browser session.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 2.1.0, < 2.1.20>= 2.2.0, < 2.2.16>= 2.3.0, < 2.3.10>= 2.4.0, < 2.4.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Operations Manager installationAccess the Ops Manager web interface or check BOSH deployments using 'bosh deployments' command. Operations Manager typically runs on a specific URL and requires authentication.Affected if Operations Manager is not installed or accessible in the environment
-
Determine installed versionLog into Ops Manager UI and locate the version number typically displayed in the footer or header area, or query the Ops Manager API at /api/v0/info endpoint for version details.Affected if Version cannot be determined or is not visible
-
Compare version to vulnerable rangesCheck if the installed version falls within: 2.1.x prior to 2.1.20, 2.2.x prior to 2.2.16, 2.3.x prior to 2.3.10, or 2.4.x prior to 2.4.3Affected if Installed version is 2.1.0 to 2.1.19, 2.2.0 to 2.2.15, 2.3.0 to 2.3.9, or 2.4.0 to 2.4.2
-
Confirm user authentication is enabledVerify that Operations Manager requires authentication. The XSS requires an authenticated user session to be exploited.Affected if Operations Manager is accessible without authentication (which is not typical for Ops Manager)
The environment is affected if Pivotal Operations Manager is installed and the running version matches one of the vulnerable ranges: 2.1.0-2.1.19, 2.2.0-2.2.15, 2.3.0-2.3.9, or 2.4.0-2.4.2.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data2.1.202.2.162.3.10
Upgrade Operations Manager to version 2.1.20 or later for 2.1.x, 2.2.16 or later for 2.2.x, 2.3.10 or later for 2.3.x, or 2.4.3 or later for 2.4.x per Pivotal's official advisory.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3776 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-3776 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data