This is done by escaping the context of the web application; the web application then delivers that data to its users along with other trusted dynamic content, without validating it.
External References: https://snyk.io/vuln/npm:angular:20150807
This issue has been addressed in the following products: Red Hat Decision Manager Via RHSA-2019:4069 https://access.redhat.com/errata/RHSA-2019:4069
This issue has been addressed in the following products: Red Hat Process Automation Via RHSA-2019:4071 https://access.redhat.com/errata/RHSA-2019:4071
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s): https://access.redhat.com/security/cve/cve-2019-14863
Hey there. I feel your pain with the Rhel node issue. It's frustrating when things go south, especially with the intricate dance of enabling FIPS on a Rhel VM. I've run into similar hurdles, and it can be a head-scratcher. Now, about your hiccup, it seems like the FIPS integrity test is throwing a curveball during the Rhel node startup. Given your steps, it might be worthwhile to double-check the FIPS configuration and ensure it aligns seamlessly with the OCP installation. Sometimes, these finicky issues boil down to the order of operations. Consider revisiting the FIOS setup on the Rhel VM, ensuring a snug fit with the public image. I'd recommend exploring any specific quirks tied to that AWS image (ami-0e166e72fda655c63). Also, a quick dive into the AWS community forums might unveil experiences from fellow adventurers. I would suggest starting here: https://andersenlab.com/find-developers/angular Hang in there... Bugs can be elusive, but so is your determination.