ghsa

Zenario CMS 9.3.57186 is vulnerable to Cross Site Scripting (XSS) via svg,Users & Contacts.

Zenario CMS 9.3.57186 is vulnerable to Cross Site Scripting (XSS) via News articles.

Jenkins NS-ND Integration Performance Publisher Plugin 4.8.0.143 and earlier globally and unconditionally disables SSL/TLS certificate and hostname validation for the entire Jenkins controller JVM.

Jenkins OSF Builder Suite : : XML Linter Plugin 1.0.2 and earlier does not configure its XML parser to prevent XML external entity (XXE) attacks.

Jenkins SourceMonitor Plugin 0.2 and earlier does not configure its XML parser to prevent XML external entity (XXE) attacks.

A missing permission check in Jenkins XP-Dev Plugin 1.0 and earlier allows unauthenticated attackers to trigger builds of jobs corresponding to an attacker-specified repository.

Jenkins Reverse Proxy Auth Plugin 1.7.3 and earlier stores the LDAP manager password unencrypted in the global config.xml file on the Jenkins controller where it can be viewed by attackers with access to the Jenkins controller file system.

### Impact Implementations using this library with directory browsing enabled may be susceptible to [Cross Site Scripting (XSS)](https://owasp.org/www-community/attacks/xss/) attacks. ### Patches Users can upgrade to v4.1.0 ### Workarounds Set `dir_browser.enable = False` in the configuration. For instance, when using a Python dictionary to configure the library: ``` config = { # your normal configuration "dir_browser": { "enable": False }, } app = WsgiDAVApp(config) ``` ### For more information Note that an attacker cannot exploit this vulnerability, by simply uploading a file or folder with a manipulated file name. However if the WsgiDAV library is used in a scenario where untrusted data is displayed in the directory browser's user interface (e.g. 'realm' or user name, ...) XSS may happen. If you have any questions or comments about this advisory: * Open an issue in [mar10/wsgidav](https://github.com/mar10/wsgidav/) * See the [security policy](https://github....

### Impact In versions prior to v0.7.0 it was possible for an attacker to supply an invalid assertion which would trigger a panic due to a nil-pointer dereference. ### Patches The issue was patched in v0.7.0, released on March 2, 2022. ### Workarounds Callers to `gosaml2` can use `recover()` to handle panics to mitigate a potential DoS. ### References See issue #59 for details.

Insufficient Session Expiration in GitHub repository ikus060/rdiffweb prior to 2.5.0.