Intrigus-Lgtm

The ManifestParser class used by the repo command and the AmazonS3 class used to implement the experimental amazons3 git transport protocol are vulnerable to XML External Entity (XXE) attacks when parsing XML files. This can lead to information disclosure, denial of service, and other security issues.

The issue is related to an inappropriate implementation in V8, which can allow a remote attacker to potentially perform out of bounds memory access via a crafted HTML page. This can be exploited to execute arbitrary code. The vulnerability is associated with a buffer overflow in memory due to incorrect representation of the shift amount in 64-bit BigInt shift optimizations.

The CodeQL CLI is vulnerable to an XML External Entity attack due to an XML parser used to read auxiliary files. This vulnerability can be exploited when processing maliciously modified CodeQL databases or specially prepared QL query sources, potentially leading to a loss of privacy or exfiltration of secrets. Security researchers and QL authors who receive databases or QL source files from untrusted sources may be impacted. Those using CodeQL for routine analysis of source trees with a preselected set of trusted queries are not affected.

The issue allows for cross-site scripting (XSS) attacks via clipboard content. If a user can be tricked into copying malicious content and pasting it into the HTML editor, a part of the clipboard content is directly written to `innerHTML`, causing XSS. This enables JavaScript injection.

Name of the Vulnerable Software and Affected Versions: SUSI.AI Server versions prior to d27ed0f Description: The issue is due to insufficient input validation, leading to a directory traversal vulnerability. This allows an attacker to retrieve any admin config and file readable by the app. Additionally, some files can be moved or deleted. Recommendations: For versions prior to d27ed0f, update to version d27ed0f or later to resolve the issue. As a temporary workaround, consider restricting access to sensitive files and directories to minimize the risk of exploitation.

The loklak server application contains a path traversal vulnerability due to insufficient input validation in the APIs. This allows a directory traversal vulnerability, enabling an attacker to retrieve any admin configuration and files readable by the app available on the hosted file system. Furthermore, user-controlled content could be written to any admin config and files readable by the application.

The issue concerns Opencast's HTTP client, which disables HTTPS hostname verification for a large portion of its HTTP requests. Hostname verification is crucial when using HTTPS to ensure the presented certificate is valid for the host. Disabling it can allow for man-in-the-middle attacks. This problem is fixed in Opencast 7.9 and Opencast 8.9. After fixing the problem, Opencast will no longer accept self-signed certificates without properly importing them into the Java key store.

The issue is related to a cross-site scripting vulnerability in handling URIs. It can be triggered when a user clicks on a specifically crafted validator link.