![]() ![]() ![]() As such, it is strongly recommended to upgrade to a fixed version of AntiSamy. The safety of this workaround relies on configurations that may change in the future and don't address the root cause of the vulnerability. ![]() However, the existing bug would still be present in AntiSamy or its parser dependency (HtmlAgilityPack). As the previously mentioned policy settings are preconditions for the mXSS attack to work, changing them as recommended should be sufficient to protect you against this vulnerability when using a vulnerable version of this library. Also it would be useful to make AntiSamy remove the `noscript` tag by adding a line described in the GitHub Security Advisory to the tag definitions under the `` node, or deleting it entirely if present. As a workaround, manually edit the AntiSamy policy file (e.g., antisamy.xml) by deleting the `preserveComments` directive or setting its value to `false`, if present. ![]() See important remediation details in the reference given below. As a result, certain crafty inputs can result in elements in comment tags being interpreted as executable when using AntiSamy's sanitized output. To be subject to this vulnerability the `preserveComments` directive must be enabled in your policy file and also allow for certain tags at the same time. Prior to version 1.2.0, there is a potential for a mutation cross-site scripting (mXSS) vulnerability in AntiSamy caused by flawed parsing of the HTML being sanitized. NET is a library for performing cleansing of HTML coming from untrusted sources. A remote attacker who modifies the node role label could steer workloads from the control plane and etcd nodes onto different worker nodes and gain broader access to the cluster. A privilege escalation flaw was found in the node restriction admission plugin of the kubernetes api server of OpenShift. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |