CVE-2019-11292
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 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.
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 Ops Manager versions prior to 2.4.27, 2.5.24, 2.6.16, and 2.7.5 write all HTTP query parameters to Tomcat's access log files. When authentication credentials are passed via query parameters (e.g., ?user=admin&password=secret), they are logged in plain text, exposing sensitive authentication information in log files accessible to attackers with log access.
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.4.0, < 2.4.27>= 2.5.0, < 2.5.24>= 2.6.0, < 2.6.16>= 2.7.0, < 2.7.5CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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.
-
Identify Ops Manager versionAccess the Ops Manager admin UI or check the product version via the API endpoint /api/v0/info, or run 'om products' if using the Ops Manager CLIAffected if version is 2.4.0-2.4.26, 2.5.0-2.5.23, 2.6.0-2.6.15, or 2.7.0-2.7.4 (i.e., in any of the affected ranges)
-
Locate Tomcat access logsNavigate to the Ops Manager VM via SSH and locate Tomcat access log files, typically in /var/log/opsmanager or a logs directory within the Ops Manager installation pathAffected if access log files exist on the system
-
Inspect logs for query string credentialsSearch the access log files for patterns matching query parameters that contain authentication data, such as '?password=', '?token=', '?secret=', or 'user=' combined with credential-like values in the URL query stringAffected if plain text credentials appear in the query string portion of logged URLs
-
Verify if authentication uses query parametersReview application configuration or network traffic to determine whether any components or users are passing authentication credentials via URL query parameters (e.g., GET requests with ?username=X&password=Y)Affected if query parameter-based authentication is in use and logs contain those parameters in plain text
You are affected if your Ops Manager version falls within the vulnerable ranges AND query string credentials are being logged in plain text in the Tomcat access logs.
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.4.272.5.242.6.16
Upgrade Pivotal Ops Manager to version 2.4.27, 2.5.24, 2.6.16, 2.7.5 or later. Additionally, ensure credentials are never passed in URL query strings—use POST request bodies or HTTP headers for authentication instead.
- Consultation4.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11292 — 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-11292 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