Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-1963PUBLISHED: 2022-07-01
An issue has been discovered in GitLab CE/EE affecting all versions starting from 13.4 before 14.10.5, all versions starting from 15.0 before 15.0.4, all versions starting from 15.1 before 15.1.1. GitLab reveals if a user has enabled two-factor authentication on their account in the HTML source, to ...
CVE-2022-1981PUBLISHED: 2022-07-01
An issue has been discovered in GitLab EE affecting all versions starting from 12.2 prior to 14.10.5, 15.0 prior to 15.0.4, and 15.1 prior to 15.1.1. In GitLab, if a group enables the setting to restrict access to users belonging to specific domains, that allow-list may be bypassed if a Maintainer u...
CVE-2022-1999PUBLISHED: 2022-07-01An issue has been discovered in GitLab CE/EE affecting all versions from 8.13 prior to 14.10.5, 15.0 prior to 15.0.4, and 15.1 prior to 15.1.1. Under certain conditions, using the REST API an unprivileged user was able to change labels description.
CVE-2022-2228PUBLISHED: 2022-07-01
Information exposure in GitLab EE affecting all versions from 12.0 prior to 14.10.5, 15.0 prior to 15.0.4, and 15.1 prior to 15.1.1 allows an attacker with the appropriate access tokens to obtain CI variables in a group with using IP-based access restrictions even if the GitLab Runner is calling fro...
CVE-2022-2229PUBLISHED: 2022-07-01An improper authorization issue in GitLab CE/EE affecting all versions from 13.7 prior to 14.10.5, 15.0 prior to 15.0.4, and 15.1 prior to 15.1.1 allows an attacker to extract the value of an unprotected variable they know the name of in public projects or private projects they're a member of.
User Rank: Moderator
10/29/2014 | 12:44:05 PM
Dealing with this requires a lot of cooperation amongst groups including sysadmins, network admins, security, and developers. It may be that logging levels for particular systems need to be dialed down in order to handle the load or maybe the logs can be sent to a few other hosts for distributed processing prior to pulling them into the SIEM. Reducing full logs from the firewall/IPS/IDS to relying more on netflow analysis may be necessary. It comes down a lot to knowing the infrastructure and already having logging in place then adapting it to handle the attack.