Git 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.

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

2.015
2.115
2.214
2.314
2.414

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 Fix69
Temporary Fix0
Workaround0
Unavailable1
Not Defined37

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

High2
Functional0
Proof-of-Concept9
Unproven2
Not Defined94

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
Local10
Adjacent14
Network83

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
High2
Low43
None62

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
Required23
None84

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
≤20
≤30
≤48
≤514
≤616
≤718
≤831
≤916
≤104

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
≤20
≤30
≤49
≤514
≤617
≤724
≤823
≤916
≤104

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
≤20
≤31
≤414
≤517
≤627
≤712
≤831
≤91
≤104

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
≤30
≤43
≤51
≤611
≤74
≤812
≤914
≤1024

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
≤20
≤30
≤40
≤50
≤61
≤72
≤83
≤98
≤105

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

<1k18
<2k33
<5k56
<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

<1k99
<2k7
<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 (292): 0.0.1, 0.0.2, 0.0.3, 0.0.4, 0.0.5, 0.0.6, 0.0.7, 0.0.8, 0.0.9, 0.0.2008071, 0.0.2009032, 0.1, 0.1.1, 0.7, 0.7.1, 0.9, 0.9.1, 0.9.2, 0.9.3, 0.9.4, 0.9.5, 0.9.6, 0.9.7, 0.9.8, 0.9.9, 0.9.11, 0.9.12, 0.9.13, 0.9.14, 0.9.15, 0.10.1, 0.10.2, 0.22, 0.22.1, 1, 1.0, 1.0.0b, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, 1.0.8, 1.1, 1.1.1, 1.1.2, 1.1.3, 1.1.4, 1.2, 1.3, 1.3.1, 1.4, 1.4.2, 1.4.2.1, 1.4.2.2, 1.5, 1.5.1, 1.5.2, 1.5.5.3, 1.5.5.4, 1.5.6.1, 1.5.6.2, 1.5.6.3, 1.6, 1.6.0.1, 1.6.0.2, 1.7, 1.8, 1.8.1, 1.8.1.3, 1.9, 1.9.1, 1.9.2, 1.10, 1.11, 1.12, 1.13, 1.13.1, 2, 2.0, 2.0.1, 2.0.288, 2.1, 2.1.1, 2.2, 2.3, 2.3.1, 2.3.2, 2.3.3, 2.3.4, 2.3.5, 2.3.6, 2.3.7, 2.3.8, 2.3.9, 2.4, 2.4.1, 2.4.2, 2.4.3, 2.4.4, 2.4.5, 2.4.6, 2.4.7, 2.4.8, 2.4.9, 2.4.11, 2.5, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 2.5.5, 2.6, 2.6.1, 2.6.2, 2.6.3, 2.6.4, 2.6.5, 2.6.6, 2.7, 2.7.1, 2.7.2, 2.7.3, 2.7.4, 2.8, 2.8.1, 2.8.2, 2.8.3, 2.8.4, 2.9, 2.9.1, 2.9.2, 2.9.3, 2.10, 2.10.1, 2.10.2, 2.10.3, 2.10.4, 2.11, 2.11.1, 2.11.2, 2.11.3, 2.12, 2.12.1, 2.12.2, 2.12.3, 2.12.4, 2.13, 2.13.1, 2.13.2, 2.13.3, 2.13.4, 2.13.5, 2.13.6, 2.14, 2.14.1, 2.14.2, 2.14.3, 2.14.4, 2.14.5, 2.15, 2.15.1, 2.15.2, 2.15.3, 2.16, 2.16.1, 2.16.2, 2.16.3, 2.16.4, 2.16.5, 2.17, 2.17.1, 2.17.2, 2.17.3, 2.18, 2.18.1, 2.18.2, 2.19, 2.19.1, 2.19.2, 2.19.3, 2.20, 2.20.1, 2.20.2, 2.21, 2.21.1, 2.22, 2.22.1, 2.22.2, 2.23, 2.23.1, 2.24, 2.24.1, 2.25, 2.25.1, 2.25.2, 2.26, 2.27, 2.28, 2.29, 2.30, 2.30.1, 2.30.2, 2.30.3, 2.30.4, 2.30.5, 2.31, 2.31.1, 2.31.1-1, 2.31.2, 2.31.3, 2.31.4, 2.32, 2.32.1, 2.32.2, 2.32.3, 2.33, 2.33.1, 2.33.2, 2.33.3, 2.33.4, 2.34, 2.34.1, 2.34.2, 2.34.3, 2.34.4, 2.35, 2.35.1, 2.35.2, 2.35.3, 2.35.4, 2.36, 2.36.1, 2.36.2, 2.37, 2.37.1, 2.37.2, 2.37.3, 3, 3.0, 3.0.1, 3.0.2, 3.0.3, 3.0.4, 3.0.5, 3.0.6, 3.0.7, 3.1, 3.1.1, 3.1.2, 3.2, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.3, 3.4, 3.5, 3.6, 3.7, 3.8, 3.9, 3.9.1, 3.10, 3.11, 3.12, 3.13, 3.14, 4, 4.0, 4.0.1, 4.0.2, 4.1, 4.2, 4.3, 4.4, 4.8, 4.8.1, 4.8.2, 4.11, 4.11.1, 4.11.2, 4.11.3, 4.11.4, 6.0, 6.1, 6.2, 6.3, 6.4, 6.2017

Software Type: Versioning Software

PublishedBaseTempVulnerability0dayTodayExpRemCTICVE
01/18/20238.58.4Git pretty.c format_and_pad_commit integer overflow$0-$5k$0-$5kNot DefinedOfficial Fix5.19CVE-2022-41903
01/18/20238.58.4Git integer overflow$0-$5k$0-$5kNot DefinedOfficial Fix1.92CVE-2022-23521
01/17/20235.55.3ruby-git Filename Privilege Escalation$0-$5k$0-$5kNot DefinedOfficial Fix1.56CVE-2022-47318
01/10/20235.55.3git Gem deserialization$0-$5k$0-$5kNot DefinedOfficial Fix0.05CVE-2022-46648
12/06/20227.87.8simple-git ext Transport Protocol clone command injection$0-$5k$0-$5kNot DefinedOfficial Fix0.06CVE-2022-25912
10/20/20226.36.3Tuleap Git Branch Source Plugin authorization$0-$5k$0-$5kNot DefinedNot Defined0.08CVE-2022-43421
10/19/20227.47.4Git heap-based overflow$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2022-39260
10/19/20224.14.1Git Local Clone information disclosure$0-$5k$0-$5kNot DefinedOfficial Fix0.02CVE-2022-39253
08/24/20225.05.0Git Plugin Build Log insufficiently protected credentials$0-$5k$0-$5kNot DefinedNot Defined0.02CVE-2022-38663
07/27/20224.84.8Git Plugin Webhook Endpoint information disclosure$0-$5k$0-$5kNot DefinedNot Defined0.03CVE-2022-36884
07/27/20226.56.5Git Plugin Build cross-site request forgery$0-$5k$0-$5kNot DefinedNot Defined0.02CVE-2022-36882
07/27/20223.73.7Git Client Plugin SSH Host Key Verification key exchange without entity authentication$0-$5k$0-$5kNot DefinedNot Defined0.04CVE-2022-36881
07/27/20226.56.5Git Plugin Build authorization$0-$5k$0-$5kNot DefinedNot Defined0.20CVE-2022-36883
07/26/20226.26.2git-archive Exports command injection$0-$5k$0-$5kNot DefinedNot Defined0.03CVE-2020-28422
07/13/20227.27.1Git for Windows Installer git.exe untrusted search path$0-$5k$0-$5kNot DefinedOfficial Fix0.03CVE-2022-31012
07/13/20227.06.9Git access control$0-$5k$0-$5kNot DefinedOfficial Fix0.06CVE-2022-29187
07/02/20228.48.3git-clone command injection$0-$5k$0-$5kNot DefinedNot Defined0.02CVE-2022-25900
06/27/20225.55.4repo-git-downloader Git Repository incorrect regex$0-$5k$0-$5kNot DefinedNot Defined0.02CVE-2021-40899
06/11/20225.95.8git-promise command injection$0-$5k$0-$5kProof-of-ConceptUnavailable0.00CVE-2022-24376
05/18/20225.55.5Git Plugin SCM URL access control$0-$5k$0-$5kNot DefinedNot Defined0.03CVE-2022-30947
05/01/20228.58.4git-pull-or-clone spawn command injection$0-$5k$0-$5kNot DefinedOfficial Fix0.06CVE-2022-24437
04/25/20226.86.7czproject git-php isRemoteUrlReadable argument injection$0-$5k$0-$5kNot DefinedOfficial Fix0.06CVE-2022-25866
04/22/20229.89.6yarkeev git-interface Command-Line Argument os command injection$0-$5k$0-$5kNot DefinedOfficial Fix0.05CVE-2022-1440
04/20/20228.58.4Git LFS exe CreateProcess untrusted search path$0-$5k$0-$5kNot DefinedOfficial Fix0.02CVE-2022-24826
04/19/20226.86.7git fetch argument injection$0-$5k$0-$5kNot DefinedOfficial Fix0.02CVE-2022-25648

82 more entries are not shown

Interested in the pricing of exploits?

See the underground prices here!