Skip to content
Fencer Vulns
medium 4.3

CVE-2020-14348 json

It was found in AMQ Online before 1.5.2 that injecting an invalid field to a user's AddressSpace configuration of the user namespace puts A…

published 2020-09-16 6 y ago modified 2026-06-17 4 mo ago also EUVD-2020-6492

cvss
4.3
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 57%
public exploits
0
none known

Summary

It was found in AMQ Online before 1.5.2 that injecting an invalid field to a user's AddressSpace configuration of the user namespace puts AMQ Online in an inconsistent state, where the AMQ Online components do not operate properly, such as the failure of provisioning and the failure of creating addresses, though this does not impact upon already existing messaging clients or brokers.

Patch / fix

  • redhat amq_online 1.5.2

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-14348 updated cvss 2.7

AMQ: Denial of Service via unrecognized field injection

  • Red Hat A-MQ Online enmasse enmasse
    affected: workaround, no fix available “The user can work around the issue by repairing the resource and removing the invalid (top-level) field.”
  • Red Hat AMQ Online 1.5.2 GA
    fixed: vendor fix “The user can work around the issue by repairing the resource and removing the invalid (top-level) field.” RHSA-2020:3209

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.81% chance of exploitation in the next 30 days, higher than 57% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:N/I:N/A:P

Affected products

  • n/a AMQ

Classification

Weakness
  • CWE-248 Uncaught Exception
  • CWE-754 Improper Check for Unusual or Exceptional Conditions

References

Sources

Fencer Vulns 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.