Product Gitlab

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.

Last Year

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.

Version

13.2.147
13.2.047
13.2.247
13.1.040
13.1.140

Grouping all affected versions of a specific product helps to determine existing issues. This makes it possible to determine vendors and products which need attention when it comes to remediations.

Remediation

Official Fix83
Temporary Fix0
Workaround0
Unavailable0
Not Defined47

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

High1
Functional0
Proof-of-Concept2
Unproven0
Not Defined127

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
Local3
Adjacent12
Network115

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
High18
Low83
None29

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
Required35
None95

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.

Last Year

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
≤31
≤414
≤533
≤644
≤725
≤89
≤92
≤101

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
≤31
≤418
≤537
≤641
≤725
≤84
≤92
≤101

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
≤22
≤35
≤421
≤550
≤617
≤723
≤811
≤90
≤101

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
≤410
≤512
≤613
≤725
≤815
≤98
≤103

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
≤30
≤42
≤51
≤66
≤73
≤82
≤90
≤100

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

<1k50
<2k41
<5k39
<10k0
<25k0
<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

<1k116
<2k13
<5k1
<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.

Last Year

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 Versions (281): 1.0, 1.0.4, 1.1, 1.2, 1.3, 1.4, 1.4.1, 1.4.2, 1.5, 1.5.1, 1.5.2, 1.5.3, 1.5.4, 1.5.5, 1.5.6, 1.5.7, 1.5.8, 1.5.9, 1.5.11, 1.6, 1.7, 1.7.1, 1.7.2, 1.7.3, 2.0, 2.1, 2.2, 2.3, 2.4, 2.5, 2.6, 2.7, 2.8, 2.9, 2.10, 2.11, 2.12, 2.13, 2.14, 2.15, 2.16, 2.17, 2.18, 2.19, 2.20, 2.21, 2.22, 2.23, 2.24, 2.25, 2.26, 2.27, 2.28, 3, 3.0, 3.0.1, 3.0.2, 3.1, 3.2, 3.3, 3.4, 3.5, 3.6, 3.7, 3.8, 3.9, 3.10, 3.11, 3.12, 3.13, 3.14, 3.15, 5, 5.0.1, 5.1, 5.2, 5.3, 5.4, 5.4.1, 5.4.2, 6, 6.0, 6.1, 6.2, 6.2.1, 6.2.2, 6.6, 6.6.1, 7.4, 7.4.1, 7.4.2, 7.12, 8.0, 8.1, 8.2, 8.3, 8.4, 8.5, 8.6, 8.7, 8.9, 8.11.0-rc6, 8.14, 8.14.1, 8.14.2, 8.14.3, 8.14.4, 8.14.5, 8.14.6, 8.14.7, 8.14.8, 8.15, 8.15.1, 8.15.2, 8.15.3, 8.15.4, 8.15.5, 8.15.7, 8.16, 8.16.1, 8.16.2, 8.16.3, 8.16.4, 8.17.3, 9.1, 9.4, 9.4.1, 10.3, 10.3.1, 10.3.2, 10.3.3, 10.3.4, 10.3.5, 10.3.6, 10.3.7, 10.3.8, 10.4, 10.4.1, 10.4.2, 10.4.3, 10.4.4, 10.4.5, 10.5, 10.5.1, 10.5.2, 10.5.3, 10.5.4, 10.5.5, 10.8, 11.0, 11.1, 11.2, 11.3, 11.4, 11.5, 11.6, 11.7, 11.8, 12.0, 12.1, 12.2, 12.2.1, 12.2.2, 12.2.3, 12.3, 12.4, 12.5, 12.6, 12.6.1, 12.7, 12.7.1, 12.7.2, 12.8, 12.9, 12.10.1, 12.10.2, 12.10.3, 12.10.4, 12.10.5, 12.10.6, 12.10.7, 12.10.8, 12.10.9, 12.10.11, 12.10.12, 13, 13.0, 13.0.1, 13.0.2, 13.0.3, 13.0.4, 13.0.5, 13.0.6, 13.0.7, 13.0.8, 13.0.9, 13.0.11, 13.0.12, 13.0.13, 13.1, 13.1.1, 13.1.2, 13.1.3, 13.1.4, 13.1.5, 13.1.6, 13.1.7, 13.1.8, 13.1.9, 13.2, 13.2.1, 13.2.2, 13.2.3, 13.2.4, 13.2.5, 13.2.6, 13.2.7, 13.2.8, 13.2.9, 13.3, 13.3.1, 13.3.2, 13.3.3, 13.3.4, 13.3.5, 13.3.6, 13.4, 13.4.1, 13.5, 13.6, 13.7, 13.9, 13.9.1, 13.9.2, 13.9.3, 13.9.4, 13.9.5, 13.9.6, 13.9.7, 13.10, 13.10.1, 13.10.2, 13.10.3, 13.10.4, 13.11, 13.11.1, 13.11.2, 13.11.3, 13.11.4, 13.11.5, 13.12, 13.12.1, 13.12.2, 13.12.3, 13.12.4, 13.12.5, 14, 14.0, 14.0.1, 14.0.2, 14.0.3, 14.0.4, 14.0.5, 14.0.6, 14.0.7, 14.0.8, 14.1, 14.1.1, 14.1.2, 14.1.3, 14.2, 14.2.1, 14.2.2, 14.2.3, 14.2.4, 14.2.5, 14.3, 14.3.1, 14.3.2, 14.3.3, 14.4

Software Type: Bug Tracking Software

PublishedBaseTempVulnerability0dayTodayExpRemCTICVE
12/06/20214.14.1GitLab LDAP improper authentication$0-$5k$0-$5kNot DefinedNot Defined1.57CVE-2021-39890
12/06/20215.25.2GitLab Database information disclosure$0-$5k$0-$5kNot DefinedNot Defined1.36CVE-2021-22170
11/05/20213.13.1GitLab Regular Expression denial of service$0-$5k$0-$5kNot DefinedNot Defined0.05CVE-2021-39914
10/12/20215.15.0GitLab Privilege Escalation$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2021-22263
10/06/20214.64.6GitLab Jira Integration cross site scripting$0-$5k$0-$5kNot DefinedNot Defined0.07CVE-2021-22261
10/06/20214.64.6GitLab Jira Integration cross site scripting$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2021-39878
10/06/20215.95.9GitLab Jira Cloud Integration access control$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2021-22262
10/06/20214.34.3GitLab Project Import access control$0-$5k$0-$5kNot DefinedNot Defined0.05CVE-2021-22258
10/06/20215.95.9GitLab Business Logic access control$0-$5k$0-$5kNot DefinedNot Defined0.04CVE-2021-39866
10/06/20216.86.6GitLab Invited Group Member unknown vulnerability$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2021-22264
10/06/20215.95.8GitLab Invited Group Member access control$0-$5k$0-$5kNot DefinedOfficial Fix0.05CVE-2021-22264
10/06/20215.35.2GitLab Route user.keys information disclosure$0-$5k$0-$5kNot DefinedOfficial Fix0.06CVE-2021-22257
10/06/20215.35.3GitLab File Parser denial of service$0-$5k$0-$5kNot DefinedNot Defined0.07CVE-2021-39893
10/05/20212.02.0GitLab SendEntry information disclosure$0-$5k$0-$5kNot DefinedNot Defined0.07CVE-2021-39900
10/05/20216.06.0GitLab resource consumption$0-$5k$0-$5kNot DefinedNot Defined0.09CVE-2021-39877
08/21/20213.53.5GitLab Design Feature cross site scripting$0-$5k$0-$5kNot DefinedNot Defined0.05CVE-2021-22238
08/21/20214.34.1GitLab Webhook denial of service$0-$5k$0-$5kNot DefinedOfficial Fix0.08CVE-2021-22246
07/08/20214.84.8GitLab Makrdown cross site scripting$0-$5k$0-$5kNot DefinedNot Defined0.04CVE-2021-22225
07/08/20215.45.1GitLab GraphQL API cross-site request forgery$0-$5k$0-$5kNot DefinedOfficial Fix0.05CVE-2021-22224
07/08/20214.34.1GitLab cross site scripting$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2021-22227
07/07/20214.34.3GitLab GraphQL access control$0-$5k$0-$5kNot DefinedNot Defined0.08CVE-2021-22228
06/12/20216.36.3GitLab Webhook server-side request forgery$0-$5k$0-$5kNot DefinedNot Defined0.06CVE-2021-22175
06/09/20214.34.3GitLab Blob Viewer cross site scripting$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2021-22220
06/09/20215.35.1GitLab Password Expiration improper authentication$0-$5k$0-$5kNot DefinedOfficial Fix0.05CVE-2021-22221
05/07/20216.36.3GitLab Timestamp permission$0-$5k$0-$5kNot DefinedNot Defined0.07CVE-2021-22208

105 more entries are not shown

Interested in the pricing of exploits?

See the underground prices here!