Joaxcar

**Name of the Vulnerable Software and Affected Versions** GitLab CE/EE versions 13.9 through 18.6.6 GitLab CE/EE versions 18.7 through 18.7.4 GitLab CE/EE versions 18.8 through 18.8.4 **Description** An issue exists in GitLab CE/EE where an authenticated user could potentially add unauthorized email addresses to victim accounts. This is possible due to HTML injection within test case titles under specific conditions. **Recommendations** Update GitLab CE/EE to a version after 18.6.6. Update GitLab CE/EE to a version after 18.7.4. Update GitLab CE/EE to a version after 18.8.4.

**Name of the Vulnerable Software and Affected Versions** GitLab CE/EE versions 11.10 through 18.4.5 GitLab CE/EE versions 18.5 through 18.5.3 GitLab CE/EE versions 18.6 through 18.6.1 **Description** An unauthenticated user could create a denial of service condition by sending crafted GraphQL queries that bypass query complexity limits. **Recommendations** Update GitLab CE/EE to version 18.4.6 or later. Update GitLab CE/EE to version 18.5.4 or later. Update GitLab CE/EE to version 18.6.2 or later.

**Name of the Vulnerable Software and Affected Versions** GitLab CE/EE versions 15.6 through 18.4.6 GitLab CE/EE versions 18.5 through 18.5.4 GitLab CE/EE versions 18.6 through 18.6.2 **Description** GitLab has addressed an issue that could allow an authenticated user to reveal sensitive information through specially designed merge request titles. The issue affects GitLab CE/EE. **Recommendations** GitLab CE/EE versions prior to 18.4.6 should be updated. GitLab CE/EE versions prior to 18.5.4 should be updated. GitLab CE/EE versions prior to 18.6.2 should be updated.

**Name of the Vulnerable Software and Affected Versions** GitLab versions prior to 17.11.1 **Description** The issue concerns multiple vulnerabilities in GitLab, including Cross-Site Scripting (XSS), Denial of Service (DoS), and Header Injection. These vulnerabilities were addressed in a recent advisory by GitLab. **Recommendations** For versions prior to 17.11.1, update to version 17.11.1 or later to resolve the issue.

**Name of the Vulnerable Software and Affected Versions** GitLab CE/EE versions 15.7 through 16.9.7 GitLab CE/EE versions 16.10 through 16.10.5 GitLab CE/EE versions 16.11 through 16.11.2 **Description** An issue has been discovered in GitLab CE/EE that could allow an attacker to cause a denial of service by crafting unusual search terms for branch names. **Recommendations** For GitLab CE/EE versions 15.7 through 16.9.7, consider restricting access to branch name search functionality until a patch is available. For GitLab CE/EE versions 16.10 through 16.10.5, consider implementing input validation for branch name search terms to minimize the risk of exploitation. For GitLab CE/EE versions 16.11 through 16.11.2, consider disabling the branch name search feature temporarily until a fix is applied.

**Name of the Vulnerable Software and Affected Versions** macOS Sequoia versions prior to 15.3 Safari versions prior to 18.3 iOS versions prior to 18.3 iPadOS versions prior to 18.3 **Description** A privacy issue was addressed with improved handling of files. Copying a URL from Web Inspector may lead to command injection. The issue is related to the Web Inspector tool in iOS, iPadOS, macOS, and Safari, which is associated with a lack of data sanitization at the management level. This may allow a remote attacker to execute arbitrary commands. **Recommendations** For macOS Sequoia versions prior to 15.3, update to macOS Sequoia 15.3 to resolve the issue. For Safari versions prior to 18.3, update to Safari 18.3 to resolve the issue. For iOS versions prior to 18.3, update to iOS 18.3 to resolve the issue. For iPadOS versions prior to 18.3, update to iPadOS 18.3 to resolve the issue. As a temporary workaround, consider avoiding copying URLs from Web Inspector until a patch is available. Restrict access to the Web Inspector tool to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** GitLab CE/EE versions 17.3 through 17.3.6 GitLab CE/EE versions 17.4 through 17.4.3 GitLab CE/EE versions 17.5 through 17.5.1 **Description** An issue has been discovered in GitLab CE/EE where improper output encoding could lead to XSS if CSP is not enabled. This could allow a remote attacker to conduct a cross-site scripting attack. **Recommendations** For GitLab CE/EE versions 17.3 through 17.3.6, update to version 17.3.7 or later. For GitLab CE/EE versions 17.4 through 17.4.3, update to version 17.4.4 or later. For GitLab CE/EE versions 17.5 through 17.5.1, update to version 17.5.2 or later. As a temporary workaround, consider enabling CSP to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** GitLab EE versions 12.9 through 17.1.6 GitLab EE versions 17.2 through 17.2.4 GitLab EE versions 17.3 through 17.3.1 **Description** An issue has been discovered in GitLab EE that could allow for an account takeover by breaking the OAuth flow under certain conditions. This is due to an open redirect vulnerability. **Recommendations** For GitLab EE versions 12.9 through 17.1.6, update to version 17.1.7 or later. For GitLab EE versions 17.2 through 17.2.4, update to version 17.2.5 or later. For GitLab EE versions 17.3 through 17.3.1, update to version 17.3.2 or later.

**Name of the Vulnerable Software and Affected Versions** GitLab versions 17.1 through 17.1.7 GitLab versions 17.2 prior to 17.2.5 GitLab versions 17.3 prior to 17.3.2 **Description** A crafted URL could be used to trick a victim into trusting an attacker-controlled application. This issue affects GitLab, allowing potential exploitation through specially made URLs. **Recommendations** For GitLab versions 17.1 through 17.1.7, update to a version after 17.1.7 to resolve the issue. For GitLab versions 17.2 prior to 17.2.5, update to version 17.2.5 or later to resolve the issue. For GitLab versions 17.3 prior to 17.3.2, update to version 17.3.2 or later to resolve the issue. As a temporary workaround, consider restricting access to URLs that could be used to trick victims into trusting attacker-controlled applications until a patch is available.

**Name of the Vulnerable Software and Affected Versions** GitLab EE versions 16.11 through 17.1.7 GitLab EE versions 17.2 through 17.2.5 GitLab EE versions 17.3 through 17.3.2 **Description** An issue has been discovered in GitLab EE due to incomplete input filtering, allowing command injection into a connected Cube server. This issue affects various versions of GitLab EE, making them vulnerable to remote command injection via the Cube Server Handler. **Recommendations** For GitLab EE versions 16.11 through 17.1.7, upgrade to version 17.1.7 or later to mitigate the risk. For GitLab EE versions 17.2 through 17.2.5, upgrade to version 17.2.5 or later to mitigate the risk. For GitLab EE versions 17.3 through 17.3.2, upgrade to version 17.3.2 or later to mitigate the risk. As a temporary workaround, consider restricting access to the connected Cube server until a patch is applied.

**Name of the Vulnerable Software and Affected Versions** iOS versions prior to 16.7.9 iPadOS versions prior to 16.7.9 Safari versions prior to 17.6 iOS versions prior to 17.6 iPadOS versions prior to 17.6 watchOS versions prior to 10.6 tvOS versions prior to 17.6 visionOS versions prior to 1.3 macOS Sonoma versions prior to 14.6 **Description** Processing maliciously crafted web content may lead to a cross site scripting attack. **Recommendations** For iOS versions prior to 16.7.9, update to iOS 16.7.9 or later. For iPadOS versions prior to 16.7.9, update to iPadOS 16.7.9 or later. For Safari versions prior to 17.6, update to Safari 17.6 or later. For iOS versions prior to 17.6, update to iOS 17.6 or later. For iPadOS versions prior to 17.6, update to iPadOS 17.6 or later. For watchOS versions prior to 10.6, update to watchOS 10.6 or later. For tvOS versions prior to 17.6, update to tvOS 17.6 or later. For visionOS versions prior to 1.3, update to visionOS 1.3 or later. For macOS Sonoma versions prior to 14.6, update to macOS Sonoma 14.6 or later.

**Name of the Vulnerable Software and Affected Versions** tvOS versions prior to 17.4 macOS Sonoma versions prior to 14.4 visionOS versions prior to 1.1 iOS versions prior to 17.4 iPadOS versions prior to 17.4 watchOS versions prior to 10.4 iOS versions prior to 16.7.6 iPadOS versions prior to 16.7.6 Safari versions prior to 17.4 **Description** A logic issue was addressed with improved validation. Processing maliciously crafted web content may prevent Content Security Policy from being enforced. The issue is related to insufficient input validation in WebKitGTK and WPE WebKit modules, which may allow a remote attacker to access and compromise confidential data. **Recommendations** For tvOS versions prior to 17.4, update to tvOS 17.4. For macOS Sonoma versions prior to 14.4, update to macOS Sonoma 14.4. For visionOS versions prior to 1.1, update to visionOS 1.1. For iOS versions prior to 17.4, update to iOS 17.4. For iPadOS versions prior to 17.4, update to iPadOS 17.4. For watchOS versions prior to 10.4, update to watchOS 10.4. For iOS versions prior to 16.7.6, update to iOS 16.7.6. For iPadOS versions prior to 16.7.6, update to iPadOS 16.7.6. For Safari versions prior to 17.4, update to Safari 17.4.

**Name of the Vulnerable Software and Affected Versions** Safari versions prior to 16.6 watchOS versions prior to 9.6 iOS versions prior to 15.7.8 and prior to 16.6 iPadOS versions prior to 15.7.8 and prior to 16.6 tvOS versions prior to 16.6 macOS Ventura versions prior to 13.5 **Description** The issue is related to the WebKit module in Safari and various operating systems, including watchOS, tvOS, iPadOS, iOS, and macOS. It is caused by a lack of protection for the web page structure, which may allow a remote attacker to conduct a cross-site scripting (XSS) attack. Processing a document can lead to this type of attack. **Recommendations** For Safari versions prior to 16.6, update to Safari 16.6 or later. For watchOS versions prior to 9.6, update to watchOS 9.6 or later. For iOS versions prior to 15.7.8, update to iOS 15.7.8 or later. For iOS versions prior to 16.6, update to iOS 16.6 or later. For iPadOS versions prior to 15.7.8, update to iPadOS 15.7.8 or later. For iPadOS versions prior to 16.6, update to iPadOS 16.6 or later. For tvOS versions prior to 16.6, update to tvOS 16.6 or later. For macOS Ventura versions prior to 13.5, update to macOS Ventura 13.5 or later.

**Name of the Vulnerable Software and Affected Versions** macOS Ventura versions prior to 13.5 WebKitGTK (affected versions not specified) WPE WebKit (affected versions not specified) **Description** The issue is related to errors in handling input data during code syntax analysis, which may allow a remote attacker to execute arbitrary javascript code. This can be achieved through the exploitation of vulnerabilities in the WebKitGTK and WPE WebKit modules, used for displaying web pages. **Recommendations** For macOS Ventura, update to version 13.5 to resolve the issue. For WebKitGTK, restrict access to vulnerable modules to minimize the risk of exploitation until a patch is available. For WPE WebKit, consider disabling the execution of javascript code in the affected modules as a temporary workaround until a fix is provided. At the moment, there is no information about a newer version that contains a fix for this vulnerability in WebKitGTK and WPE WebKit.

**Name of the Vulnerable Software and Affected Versions** GitLab CE/EE versions prior to 15.8.5 GitLab CE/EE versions prior to 15.9.4 GitLab CE/EE versions prior to 15.10.1 **Description** An issue has been discovered in GitLab CE/EE where open redirects are possible due to framing arbitrary content on any page, allowing user-controlled markdown. **Recommendations** For versions prior to 15.8.5, update to version 15.8.5 or later. For versions prior to 15.9.4, update to version 15.9.4 or later. For versions prior to 15.10.1, update to version 15.10.1 or later.

**Name of the Vulnerable Software and Affected Versions** Grafana versions 9.1 and later **Description** The issue is related to the ability to search for a JWT in the URL query parameter `auth token` and use it as the authentication token. By enabling the "url login" configuration option, a JWT might be sent to data sources. If an attacker has access to the data source, the leaked token could be used to authenticate to Grafana. This could allow a remote attacker to gain unauthorized access to protected information. **Recommendations** For Grafana versions 9.1 and later, consider disabling the "url login" configuration option to prevent JWT tokens from being sent to data sources. As a temporary workaround, restrict access to data sources to minimize the risk of exploitation. Avoid using the `auth token` parameter in URL queries until the issue is resolved. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** GitLab EE versions prior to 15.0.5 GitLab EE versions 15.1 prior to 15.1.4 GitLab EE versions 15.2 prior to 15.2.1 **Description** The issue is related to improper access control, allowing an attacker to bypass IP allow-listing and download artifacts, although proper permissions are still required for the attack to be successful. **Recommendations** For GitLab EE versions prior to 15.0.5, update to version 15.0.5 or later. For GitLab EE versions 15.1 prior to 15.1.4, update to version 15.1.4 or later. For GitLab EE versions 15.2 prior to 15.2.1, update to version 15.2.1 or later.

**Name of the Vulnerable Software and Affected Versions** GitLab EE versions 14.5 through 14.10.4 GitLab EE versions 15.0 through 15.0.3 GitLab EE versions 15.1 through 15.1.0 **Description** Insufficient sanitization in GitLab EE's external issue tracker allows an attacker to perform cross-site scripting when a victim clicks on a maliciously crafted ZenTao link. **Recommendations** For GitLab EE versions 14.5 through 14.10.4, update to version 14.10.5 or later. For GitLab EE versions 15.0 through 15.0.3, update to version 15.0.4 or later. For GitLab EE versions 15.1 through 15.1.0, update to version 15.1.1 or later.

**Name of the Vulnerable Software and Affected Versions** GitLab Enterprise Edition versions 13.11 through 14.9.4 GitLab Enterprise Edition versions 14.10 through 14.10.3 GitLab Enterprise Edition versions 15.0 through 15.0.0 **Description** The issue is related to a Stored Cross-Site Scripting vulnerability in the Jira integration of GitLab Enterprise Edition. This vulnerability can be exploited by a remote attacker to execute arbitrary JavaScript code in GitLab on a victim's behalf via specially crafted Jira Issues. **Recommendations** For GitLab Enterprise Edition versions 13.11 through 14.9.4, update to version 14.9.5 or later. For GitLab Enterprise Edition versions 14.10 through 14.10.3, update to version 14.10.4 or later. For GitLab Enterprise Edition versions 15.0 through 15.0.0, update to version 15.0.1 or later.

**Name of the Vulnerable Software and Affected Versions** GitLab CE/EE versions 14.4 through 14.7.6 GitLab CE/EE versions 14.8 through 14.8.4 GitLab CE/EE versions 14.9 through 14.9.1 **Description** The issue is related to the lack of protection of the web page structure, allowing for remote attackers to conduct cross-site scripting attacks. Improper neutralization of user input enables attackers to inject HTML in notes, leading to potential exploitation. **Recommendations** For GitLab CE/EE versions 14.4 through 14.7.6, update to version 14.7.7 or later. For GitLab CE/EE versions 14.8 through 14.8.4, update to version 14.8.5 or later. For GitLab CE/EE versions 14.9 through 14.9.1, update to version 14.9.2 or later.