Gitlab Vulnerabilities

Timeline

The analysis of the timeline helps to identify the required approach and handling of single vulnerabilities and vulnerability collections. This overview makes it possible to see less important slices and more severe hotspots at a glance. Initiating immediate vulnerability response and prioritizing of issues is possible.

Type

The moderation team is working with the threat intelligence team to categorize software that is affected by security vulnerabilities. This helps to illustrate the assignment of these categories to determine the most affected software types.

Product

GitLab Enterprise Edition599
GitLab Community Edition506
GitLab Community19
GitLab Enterprise19
GitLab DAST Analyzer3

Grouping vulnerabilities by products helps to get an overview. This makes it possible to determine an homogeneous landscape or the most important hotspots in heterogeneous landscapes.

Remediation

Official Fix389
Temporary Fix0
Workaround0
Unavailable0
Not Defined264

Vendors and researchers are eager to find countermeasures to mitigate security vulnerabilities. These can be distinguished between multiple forms and levels of remediation which influence risks differently.

Exploitability

High0
Functional0
Proof-of-Concept0
Unproven0
Not Defined653

Researcher and attacker which are looking for security vulnerabilities try to exploit them for academic purposes or personal gain. The level and quality of exploitability can be distinguished to determine simplicity and strength of attacks.

Access Vector

Not Defined0
Physical0
Local8
Adjacent7
Network638

The approach a vulnerability it becomes important to use the expected access vector. This is typically via the network, local, or physically even.

Authentication

Not Defined0
High49
Low302
None302

To exploit a vulnerability a certail level of authentication might be required. Vulnerabilities without such a requirement are much more popular.

User Interaction

Not Defined0
Required131
None522

Some attack scenarios require some user interaction by a victim. This is typical for phishing, social engineering and cross site scripting attacks.

C3BM Index

Our unique C3BM Index (CVSSv3 Base Meta Index) cumulates the CVSSv3 Meta Base Scores of all entries over time. Comparing this index to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

CVSSv3 Base

≤10
≤21
≤38
≤457
≤5155
≤6204
≤7145
≤851
≤930
≤102

The Common Vulnerability Scoring System (CVSS) is an industry standard to define the characteristics and impacts of security vulnerabilities. The base score represents the intrinsic aspects that are constant over time and across user environments. Our unique meta score merges all available scores from different sources to aggregate to the most reliable result.

CVSSv3 Temp

≤10
≤21
≤313
≤454
≤5163
≤6203
≤7141
≤852
≤926
≤100

The Common Vulnerability Scoring System (CVSS) uses temp scores to reflect the characteristics of a vulnerability that may change over time but not across user environments. This includes reporting confidence, exploitability and remediation levels. We do also provide our unique meta score for temp scores, even though other sources rarely publish them.

VulDB

≤10
≤25
≤329
≤472
≤5192
≤6151
≤796
≤8105
≤93
≤100

The moderation team is always defining the base vector and base score for an entry. These and all other available scores are used to generate the meta score.

NVD

≤10
≤20
≤32
≤47
≤574
≤6110
≤790
≤889
≤923
≤1031

The National Vulnerability Database (NVD) is also defining CVSS vectors and scores. These are usually not complete and might differ from VulDB scores.

CNA

≤10
≤21
≤314
≤424
≤565
≤644
≤731
≤816
≤98
≤106

A CVE Numbering Authority (CNA) is responsible for assigning new CVE entries. They might also include a CVSS score. These are usually not complete and might differ from VulDB scores.

Vendor

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

Some vendors are willing to publish their own CVSS vectors and scores for vulnerabilities in their products. The coverage varies from vendor to vendor.

Research

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

There are sometimes also security researcher which provide their own CVSS vectors and scores for vulnerabilities they have found and published.

Exploit 0-day

<1k147
<2k243
<5k262
<10k0
<25k1
<50k0
<100k0
≥100k0

The moderation team is working with the threat intelligence team to determine prices for exploits. Our unique algorithm is used to identify the 0-day prices for an exploit, before it got distributed or became public. Calculated prices are aligned to prices disclosed by vulnerability broker and compared to prices we see on exploit markets.

Exploit Today

<1k604
<2k49
<5k0
<10k0
<25k0
<50k0
<100k0
≥100k0

The 0-day prices do not consider time-relevant factors. The today price does reflect price impacts like disclosure of vulnerability details, alternative exploits, availability of countermeasures. These dynamic aspects might decrease the exploit prices over time. Under certain circumstances this happens very fast.

Exploit Market Volume

Our unique calculation of exploit prices makes it possible to forecast the expected exploit market volume. The calculated prices for all possible 0-day expoits are cumulated for this task. Comparing the volume to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

🔴 CTI Activities

Our unique Cyber Threat Intelligence aims to determine the ongoing research of actors to anticipiate their acitivities. Observing exploit markets on the Darknet, discussions of vulnerabilities on mailinglists, and exchanges on social media makes it possible to identify planned attacks. Monitored actors and activities are classified whether they are offensive or defensive. They are also weighted as some actors are well-known for certain products and technologies. And some of their disclosures might contain more or less details about technical aspects and personal context. The world map highlights active actors in real-time.

Affected Products (10): Community (19), Community Edition (506), DAST API Scanner (1), DAST Analyzer (3), Enterprise (19), Enterprise Edition (599), GitLab (1), Omnibus (1), Runner (3), gitlab-vscode-extension (1)

Link to Vendor Website: https://gitlab.com/

PublishedBaseTempVulnerabilityProdExpRemCTIEPSSCVE
04/06/20235.65.5GitLab Community Edition/Enterprise Edition Clipboard command injectionBug Tracking SoftwareNot DefinedOfficial Fix0.520.00045CVE-2023-1708
04/06/20235.35.2GitLab Enterprise Edition improper authorizationBug Tracking SoftwareNot DefinedOfficial Fix0.280.00043CVE-2023-1167
04/06/20234.24.2GitLab Community Edition/Enterprise Edition Repository Mirror information disclosureBug Tracking SoftwareNot DefinedOfficial Fix0.210.00045CVE-2023-1098
03/10/20236.26.1GitLab DAST Analyzer Request Header information disclosureBug Tracking SoftwareNot DefinedOfficial Fix0.040.00067CVE-2022-3767
03/10/20234.84.7GitLab Enterprise Edition SAML SSO access controlBug Tracking SoftwareNot DefinedOfficial Fix0.040.00083CVE-2022-4331
03/09/20235.15.1GitLab DAST Analyzer Request Header redirectBug Tracking SoftwareNot DefinedOfficial Fix0.030.00052CVE-2022-4317
03/09/20232.72.6GitLab Community Edition/Enterprise Edition Request unknown vulnerabilityBug Tracking SoftwareNot DefinedOfficial Fix0.050.00052CVE-2023-1084
03/09/20235.05.0GitLab Community Edition/Enterprise Edition cross site scriptingBug Tracking SoftwareNot DefinedOfficial Fix0.030.00175CVE-2022-4007
03/09/20236.56.4GitLab DAST Analyzer improper authenticationBug Tracking SoftwareNot DefinedOfficial Fix0.030.00074CVE-2022-4315
02/14/20236.36.2GitLab Community Edition/Enterprise Edition Project cross-site request forgeryBug Tracking SoftwareNot DefinedOfficial Fix0.040.00080CVE-2022-4138
02/14/20235.45.3GitLab Community Edition/Enterprise Edition Issue Description resource consumptionBug Tracking SoftwareNot DefinedOfficial Fix0.050.00048CVE-2022-3411
02/14/20235.45.3GitLab Community Edition/Enterprise Edition Helm Chart unrestricted uploadBug Tracking SoftwareNot DefinedOfficial Fix0.000.00049CVE-2023-0518
02/14/20234.34.2GitLab Community Edition/Enterprise Edition CI Job denial of serviceBug Tracking SoftwareNot DefinedOfficial Fix0.030.00049CVE-2022-3759
02/01/20235.35.2GitLab DAST API Scanner information disclosureBug Tracking SoftwareNot DefinedOfficial Fix0.030.00067CVE-2022-4206
01/28/20235.85.8GitLab Enterprise Edition Branch Name type confusionBug Tracking SoftwareNot DefinedOfficial Fix0.070.00048CVE-2022-4205
01/28/20234.03.9GitLab Community Edition/Enterprise Edition server-side request forgeryBug Tracking SoftwareNot DefinedOfficial Fix0.050.00046CVE-2022-4201
01/28/20234.64.6GitLab Enterprise Edition Webhook information disclosureBug Tracking SoftwareNot DefinedOfficial Fix0.050.00046CVE-2022-4255
01/27/20234.34.2GitLab Enterprise Edition server-side request forgeryBug Tracking SoftwareNot DefinedOfficial Fix0.080.00071CVE-2022-4335
01/27/20236.66.5GitLab Community Edition/Enterprise Edition cross site scriptingBug Tracking SoftwareNot DefinedOfficial Fix0.080.00113CVE-2022-3572
01/27/20235.35.2GitLab Community Edition/Enterprise Edition Release Name access controlBug Tracking SoftwareNot DefinedOfficial Fix0.080.00052CVE-2022-3482
01/27/20235.75.7GitLab Enterprise Edition README Page cross site scriptingBug Tracking SoftwareNot DefinedOfficial Fix0.040.00102CVE-2022-4092
01/27/20235.45.3GitLab Community Edition/Enterprise Edition improper authorizationBug Tracking SoftwareNot DefinedOfficial Fix0.040.00078CVE-2022-3740
01/18/20235.15.1GitLab Runner Branch Name information disclosureBug Tracking SoftwareNot DefinedOfficial Fix0.030.00196CVE-2022-2251
01/18/20234.64.5GitLab Community Edition/Enterprise Edition Link information disclosureBug Tracking SoftwareNot DefinedOfficial Fix0.040.00089CVE-2022-2907
01/12/20236.05.9GitLab Community Edition/Enterprise Edition Email race conditionBug Tracking SoftwareNot DefinedOfficial Fix0.030.00106CVE-2022-4037

628 more entries are not shown

Want to stay up to date on a daily basis?

Enable the mail alert feature now!