Amq OnlineApplication · Redhat
CVE-2020-14319
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 · uneditedIt was found that the AMQ Online console is vulnerable to a Cross-Site Request Forgery (CSRF) which is exploitable in cases where preflight checks are not instigated or bypassed. For example authorised users using an older browser with Adobe Flash are vulnerable when targeted by an attacker. This flaw affects all versions of AMQ-Online prior to 1.5.2 and Enmasse versions 0.31.0-rc1 up until but not including 0.32.2.
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 · moderate confidenceA Cross-Site Request Forgery (CSRF) vulnerability exists in the AMQ Online console that allows attackers to induce authenticated users to perform unintended actions. The flaw is exploitable when preflight CSRF checks are absent or can be bypassed, with older browsers containing Adobe Flash being particularly susceptible to targeted attacks.
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
Amq OnlineApplication
< 1.5.2
EnmasseApplication
< 0.32.2CVSS 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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:H
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 the installed AMQ Online or Enmasse versionRun 'oc get enmasse -n <namespace>' or check the operator version via 'oc get deployment -n enmasse' and review the image tags or operator versionAffected if The installed version is AMQ Online below 1.5.2 or Enmasse below 0.32.2
-
Verify the console component is deployedCheck for the console deployment: 'oc get deployment -n <namespace> | grep -i console' and confirm the console pod is runningAffected if The console component is running and exposed to user browsers
-
Check if the console is network-accessibleReview the console service and route: 'oc get route -n <namespace>' and verify the console endpoint is exposed externallyAffected if The console is externally accessible, allowing attackers to craft malicious pages that target authenticated users
-
Confirm no anti-CSRF token mechanism is in placeInspect the console API responses or configuration for CSRF token headers (such as 'X-CSRF-Token' or similar) and verify if requests require token validationAffected if The console API does not require and validate CSRF tokens on state-changing operations
You are affected if your AMQ Online version is below 1.5.2 (or Enmasse below 0.32.2) and the console component is accessible to users, since the absence of CSRF protections allows attackers to induce authenticated users to perform unintended actions.
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 data0.32.21.5.2
Upgrade to AMQ-Online version 1.5.2 or later, or Enmasse version 0.32.2 or later. Additionally, implement anti-CSRF tokens and SameSite cookie attributes as defense-in-depth measures.
Fix this in Amq Online
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-14319 — 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-2020-14319 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