Latest Critical Vulnerabilities Affecting GitLab, Apple’s Magic Keyboard, and Juniper Networks’ Junos OS
[Update] January 25, 2024: “Over 5,300 GitLab Instances Are Vulnerable to Exploitation”
The digital landscape is continually evolving, marked by the constant emergence of new security loopholes that serve as potential gateways for attackers to infiltrate our most vital assets. This highlights the critical need to strengthen the security of both personal and business environments. In this blog post, we will shed light on the latest critical vulnerabilities, impacting GitLab, Apple’s Magic Keyboard firmware, and Juniper Networks’ Junos O
GitLab Has Patched Critical Vulnerabilities, Including a Zero-Click Leading to Account Takeover (CVE-2023-7028, CVE-2023-5356)
GitLab has recently rolled out security updates for both Community Edition (CE) and Enterprise Edition (EE). These updates aim to address several vulnerabilities, with the most severe among them being a zero-click exploit.
CVE-2023-7028 (CVSS v3: 10.0, Critical):
CVE-2023-7028 stems from an issue in the email verification process, allowing an attacker to deliver password reset requests to an unverified email address. Successful exploitation does not require user interaction, and could lead to account takeover; the vulnerability carries the maximum severity score of 10.0, representing the urgency of mitigating this potential threat.
Takeover of a GitLab account poses significant risks for an organization. Attackers could compromise sensitive data and API keys; furthermore, they could inject malicious code into repositories. Importantly, even if an attacker successfully changes the password by exploiting the vulnerability, the use of Two-Factor Authentication (2FA) can prevent their attempts to log in to the GitLab account.
Currently, there are no reports of exploitation related to the vulnerability. GitLab reports that the critical security vulnerability affects self-managed instances that are running the following versions:
- 16.1 prior to 16.1.6
- 16.2 prior to 16.2.9
- 16.3 prior to 16.3.7
- 16.4 prior to 16.4.5
- 16.5 prior to 16.5.6
- 16.6 prior to 16.6.4
- 16.7 prior to 16.7.2
GitLab recommends taking the following steps to identify if you have been compromised:
- Check gitlab-rails/production_json.log for HTTP requests to the /users/password path with params.value.email consisting of a JSON array with multiple email addresses.
- Check gitlab-rails/audit_json.log for entries with meta.caller.id of PasswordsController#create and target_details consisting of a JSON array with multiple email addresses.
CVE-2023-5356 (CVSS v3: 9.6, Critical):
Stemming from incorrect authorization checks, the second critical vulnerability patched by GitLab is tracked as CVE-2023-5356, which could allow an attacker to misuse Slack and Mattermost integrations integrations for the execution of slash commands. Slash commands serve as a convenient method for utilizing and integrating applications within the workspace, and this vulnerability permits such actions to be executed as another user.
GitLab CE/EE is susceptible to CVE-2023-5356 across various versions, including those from 8.13 before 16.5.6, 16.6 before 16.6.4, and 16.7 before 16.7.2. Organizations operating GitLab instances within these version ranges should take immediate action to address this security concern.
Over 5,300 GitLab Instances Are Vulnerable to Exploitation
According to a Shadowserver report, 5,379 GitLab instances are exposed online and vulnerable to CVE-2023-7028. The United States (964), Germany (730), and Russia (721) seem to account for the majority of these exposed instances.
Additional Vulnerabilities in the GitLab Security Update
Due to the high-severity vulnerability, tracked as CVE-2023-4812, an attacker can bypass the required CODEOWNERS approval by modifying an already approved merge request.
The issue affects GitLab across various versions, including those from 15.3 before 16.5.5, 16.6 before 16.6.4, and 16.7 before 16.7.2. Organizations utilizing GitLab instances within these version ranges are urged to take immediate action to mitigate the potential risks associated with this security vulnerability.
CVE-2023-6955 allows an attacker to create a workspace in one group associated with an agent from another group, essentially leading to the creation of workspaces under different root namespaces, due to an improper access control.
On the other hand, CVE-2023-2030 highlights a low-severity vulnerability where commit signature validation ignores headers after the signature. Exploiting this vulnerability could potentially allow an attacker to modify the metadata of signed commits.
How to Secure Your GitLab; Apply the Updates and Enable 2FA
GitLab has addressed these security vulnerabilities in versions 16.5.6, 16.6.4, and 16.7.2, the fix has also been backported to versions 16.1.6, 16.2.9, 16.3.7, and 16.4.5. To strengthen security and mitigate potential threats, it is strongly recommended to promptly upgrade your GitLab instances to the patched versions.
Additionally, users, especially those with elevated privileges, are advised to enable 2FA. For detailed information, refer to the security release on GitLab.
Critical Vulnerability in Juniper Could Lead to DoS, RCE, and Enable Root Privileges (CVE-2024-21591)
Juniper Networks has released security updates to fix a critical vulnerability affecting Junos OS in SRX Series firewalls and EX Series switches.
Tracked as CVE-2024-21591 (CVSS v3: 9.8), the vulnerability resides in the J-Web configuration interfaces of these devices and could be exploited by unauthenticated, network-based threat actors. It is attributed to the use of an insecure function allowing attackers to overwrite arbitrary memory.
Juniper Networks reports no evidence of exploitation in the wild, but a Shodan search reveals over 9,000 accessible J-Web interfaces on the internet, underscoring the expansive range of potentially vulnerable devices.
Which Products/Versions Are Affected?
The vulnerability affects Juniper Networks Junos OS SRX Series and EX Series in various versions:
- Junos OS versions earlier than 20.4R3-S9
- Junos OS 21.2 versions earlier than 21.2R3-S7
- Junos OS 21.3 versions earlier than 21.3R3-S5
- Junos OS 21.4 versions earlier than 21.4R3-S5
- Junos OS 22.1 versions earlier than 22.1R3-S4
- Junos OS 22.2 versions earlier than 22.2R3-S3
- Junos OS 22.3 versions earlier than 22.3R3-S2
- Junos OS 22.4 versions earlier than 22.4R2-S2, 22.4R3
It is strongly advised to apply the security updates to prevent potential exploitation. If immediate updating is not feasible, disabling J-Web or restricting access to trusted hosts is recommended as a workaround.
Proactive Vulnerability Management with SOCRadar
SOCRadar provides tools for quickly identifying, assessing, and mitigating vulnerabilities, as well as insights into potential threats to help you stay on top of the threat landscape.
Utilizing SOCRadar’s Attack Surface Management (ASM) module, you can easily monitor potential exposure points in your digital infrastructure. ASM enables organizations to proactively identify and mitigate potential threats by providing real-time insights into your attack surface and emerging vulnerabilities.
Furthermore, SOCRadar provides comprehensive Vulnerability Intelligence, delivering you the most recent updates on known vulnerabilities and emerging hacker trends.
SOCRadar’s solutions provide organizations with the critical information they need to stay ahead of potential threats and gather insights to quickly respond to threats, effectively assisting their vulnerability management strategies.
Sign up for a free edition to experience the full capabilities of SOCRadar XTI.