Versioning Software 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.

Vendor

Identifying all affected vendors is a good starting point for an overview. This makes it possible to determine an homogeneous landscape or the most important hotspots in heterogeneous landscapes.

Product

Apache Subversion44
Git34
Git Plugin10
Git Parameter Plugin4
Git Client Plugin3

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 Fix94
Temporary Fix0
Workaround0
Unavailable2
Not Defined51

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

High5
Functional0
Proof-of-Concept14
Unproven7
Not Defined121

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
Local9
Adjacent20
Network118

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
Low65
None80

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
Required21
None126

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
≤20
≤30
≤411
≤523
≤632
≤727
≤832
≤916
≤106

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
≤413
≤526
≤633
≤731
≤822
≤918
≤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
≤416
≤527
≤641
≤721
≤833
≤92
≤106

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
≤69
≤77
≤816
≤914
≤1022

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
≤60
≤72
≤83
≤95
≤103

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
<2k25
<5k62
<10k17
<25k23
<50k2
<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

<1k123
<2k10
<5k5
<10k5
<25k4
<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 (46): Adobe git-server, Apache Maven, Apache maven-shared-utils, Apache Subversion, async-git, async-git Package, CODESYS Git, Cygwin Git, fs-git, get-git-data, Git, git, git-add-remote, git-annex, git-archive, git-big-picture, git-bug, git-clone, git-diff-apply, git-dummy-commit, git-fastclone, git-hub, Git-it, git-promise, git-pull-or-clone, git-tag-annotation-action, GIT Client, Git Changelog Plugin, Git Client Plugin, Git Credential Manager Core, Git for Windows, Git LFS, Git Parameter Plugin, Git Plugin, hosted-git-info, isomorphic-git, Jakub Chodounsky Bonobo Git Server, Joomprod Com Versioning, List Git Branches Parameter Plugin, Nanosleep trac-git, repo-git-downloader, Semantic Versioning Plugin, simple-git, tsMuxer, Wayfair git-parse, yarkeev git-interface

PublishedBaseTempVulnerabilityProductExpRemCTICVE
08/24/20225.05.0Git Plugin Build Log insufficiently protected credentialsGit PluginNot DefinedNot Defined0.08CVE-2022-38663
07/27/20224.84.8Git Plugin Webhook Endpoint information disclosureGit PluginNot DefinedNot Defined0.04CVE-2022-36884
07/27/20226.56.5Git Plugin Build cross-site request forgeryGit PluginNot DefinedNot Defined0.08CVE-2022-36882
07/27/20223.73.7Git Client Plugin SSH Host Key Verification key exchange without entity authenticationGit Client PluginNot DefinedNot Defined0.04CVE-2022-36881
07/27/20226.56.5Git Plugin Build authorizationGit PluginNot DefinedNot Defined0.25CVE-2022-36883
07/26/20226.26.2git-archive Exports command injectiongit-archiveNot DefinedNot Defined0.03CVE-2020-28422
07/13/20227.27.1Git for Windows Installer git.exe untrusted search pathGit for WindowsNot DefinedOfficial Fix0.04CVE-2022-31012
07/13/20227.06.9Git access controlGitNot DefinedOfficial Fix0.04CVE-2022-29187
07/02/20228.48.3git-clone command injectiongit-cloneNot DefinedNot Defined0.04CVE-2022-25900
06/27/20225.55.4repo-git-downloader Git Repository incorrect regexrepo-git-downloaderNot DefinedNot Defined0.00CVE-2021-40899
06/11/20225.95.8git-promise command injectiongit-promiseProof-of-ConceptUnavailable0.07CVE-2022-24376
05/23/20225.55.3Apache maven-shared-utils Quoted String Commandline command injectionmaven-shared-utilsNot DefinedOfficial Fix0.00CVE-2022-29599
05/18/20225.55.5Git Plugin SCM URL access controlGit PluginNot DefinedNot Defined0.04CVE-2022-30947
05/01/20228.58.4git-pull-or-clone spawn command injectiongit-pull-or-cloneNot DefinedOfficial Fix0.00CVE-2022-24437
04/22/20229.89.6yarkeev git-interface Command-Line Argument os command injectiongit-interfaceNot DefinedOfficial Fix0.04CVE-2022-1440
04/20/20228.58.4Git LFS exe CreateProcess untrusted search pathGit LFSNot DefinedOfficial Fix0.00CVE-2022-24826
04/19/20226.86.7git fetch argument injectiongitNot DefinedOfficial Fix0.07CVE-2022-25648
04/13/20223.53.5Git Parameter Plugin cross site scriptingGit Parameter PluginNot DefinedNot Defined0.04CVE-2022-29040
04/13/20225.55.5Apache Subversion mod_dav_svn use after freeSubversionNot DefinedNot Defined0.08CVE-2022-24070
04/12/20224.34.3Apache Subversion authz Rule improper authenticationSubversionNot DefinedNot Defined0.07CVE-2021-28544
04/02/20226.86.7simple-git Incomplete Fix CVE-2022-24433 command injectionsimple-gitNot DefinedOfficial Fix0.04CVE-2022-24066
03/17/20225.35.3git Git os command injectiongitNot DefinedNot Defined0.04CVE-2021-23632
03/16/20223.53.5List Git Branches Parameter Plugin cross site scriptingList Git Branches Parameter PluginNot DefinedNot Defined0.03CVE-2022-27212
03/16/20225.55.5Semantic Versioning Plugin Message protection mechanismSemantic Versioning PluginNot DefinedNot Defined0.04CVE-2022-27201
03/12/20226.86.7simple-git fetch argument injectionsimple-gitNot DefinedOfficial Fix0.05CVE-2022-24433

122 more entries are not shown

Interested in the pricing of exploits?

See the underground prices here!