Github Vulnerabilities

Timeline

The analysis of the timeline helps to identify the required approach and handling of single items and item collections. This overview makes it possible to see less important slices and more severe hotspots at a glance. Prioritizing items becomes 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

GitHub Enterprise Server92
GitHub Community Edition12
GitHub Enterprise Edition12
GitHub Electron5
GitHub cmark-gfm2

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 Fix108
Temporary Fix0
Workaround0
Unavailable0
Not Defined14

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-Concept1
Unproven0
Not Defined120

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
Local7
Adjacent11
Network104

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
High36
Low59
None27

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
Required26
None96

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
≤33
≤49
≤531
≤631
≤716
≤822
≤910
≤100

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
≤33
≤410
≤532
≤631
≤718
≤825
≤93
≤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
≤20
≤310
≤419
≤532
≤623
≤726
≤812
≤90
≤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
≤21
≤31
≤41
≤510
≤69
≤717
≤86
≤916
≤109

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
≤34
≤43
≤512
≤67
≤710
≤812
≤95
≤107

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

<1k20
<2k76
<5k26
<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

<1k121
<2k1
<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 (16): Actions Runner (1), CodeQL Action (1), Community Edition (12), Desktop (1), Electron (5), Enterprise (1), Enterprise Edition (12), Enterprise Server (92), Gaug.es (1), GitHub Enterprise (1), Git LFS (1), cmark-gfm (2), codeql-action (1), codeql-cli-binaries (1), livehelperchat (1), paste-markdown (1)

PublishedBaseTempVulnerabilityProdExpRemEPSSCTICVE
01/29/20257.37.0GitHub Enterprise Server code injectionBug Tracking SoftwareNot DefinedOfficial Fix0.000450.02CVE-2024-10001
01/24/20254.34.1GitHub codeql-action log fileBug Tracking SoftwareNot DefinedOfficial Fix0.000440.02CVE-2025-24362
01/21/20255.04.8GitHub Enterprise Server signature verificationBug Tracking SoftwareNot DefinedOfficial Fix0.000450.07CVE-2025-23369
01/15/20256.05.9GitHub Desktop insufficiently protected credentialsBug Tracking SoftwareNot DefinedOfficial Fix0.000450.06CVE-2025-23040
11/08/20244.74.5GitHub Enterprise Server privileges managementBug Tracking SoftwareNot DefinedOfficial Fix0.000450.00CVE-2024-8810
11/08/20244.34.1GitHub Enterprise Server Personal Access Token authorizationBug Tracking SoftwareNot DefinedOfficial Fix0.000430.00CVE-2024-10824
11/07/20243.93.8GitHub Enterprise Server link followingBug Tracking SoftwareNot DefinedOfficial Fix0.000450.06CVE-2024-10007
10/11/20244.34.2GitHub Enterprise Server information disclosureBug Tracking SoftwareNot DefinedOfficial Fix0.000520.05CVE-2024-9539
10/11/20247.37.2GitHub Enterprise Server SAML SSO signature verificationBug Tracking SoftwareNot DefinedOfficial Fix0.008320.05CVE-2024-9487
09/24/20243.53.4GitHub Enterprise Server cross site scriptingBug Tracking SoftwareNot DefinedOfficial Fix0.000520.04CVE-2024-8770
09/24/20242.72.6GitHub Enterprise Server PAT privileges managementBug Tracking SoftwareNot DefinedOfficial Fix0.000590.04CVE-2024-8263
08/20/20244.84.7GitHub Enterprise Server authorizationBug Tracking SoftwareNot DefinedOfficial Fix0.000590.02CVE-2024-6337
08/20/20247.77.6GitHub Enterprise Server SAML Authentication signature verificationBug Tracking SoftwareNot DefinedOfficial Fix0.000680.00CVE-2024-6800
08/20/20245.35.2GitHub Enterprise Server authorizationBug Tracking SoftwareNot DefinedOfficial Fix0.000530.00CVE-2024-7711
07/17/20245.35.2GitHub Enterprise Server authorizationBug Tracking SoftwareNot DefinedOfficial Fix0.000580.00CVE-2024-5816
07/17/20245.45.3GitHub Enterprise Server cross-site request forgeryBug Tracking SoftwareNot DefinedOfficial Fix0.000540.00CVE-2024-5815
07/17/20244.84.7GitHub Enterprise Server information disclosureBug Tracking SoftwareNot DefinedOfficial Fix0.000520.00CVE-2024-6395
07/17/20245.45.3GitHub Enterprise Server authorizationBug Tracking SoftwareNot DefinedOfficial Fix0.000590.00CVE-2024-5817
07/17/20244.84.8GitHub Enterprise Server Personal Access Token privileges managementBug Tracking SoftwareNot DefinedOfficial Fix0.000590.00CVE-2024-5566
07/17/20244.84.7GitHub Enterprise Server Organization Member information disclosureBug Tracking SoftwareNot DefinedOfficial Fix0.000520.00CVE-2024-6336
07/17/20246.96.8GitHub Enterprise Server resource consumptionBug Tracking SoftwareNot DefinedOfficial Fix0.000560.03CVE-2024-5795
06/20/20245.75.6GitHub Enterprise Server server-side request forgeryBug Tracking SoftwareNot DefinedOfficial Fix0.000620.06CVE-2024-5746
05/21/20245.04.8GitHub Enterprise Server SAML Single Sign-on incorrect implementation of authentication algorithmBug Tracking SoftwareNot DefinedOfficial Fix0.000450.00CVE-2024-4985
04/19/20246.05.9GitHub Enterprise Server server-side request forgeryBug Tracking SoftwareNot DefinedOfficial Fix0.000450.00CVE-2024-3684
04/19/20244.84.7GitHub Enterprise Server GraphQL Mutation toctouBug Tracking SoftwareNot DefinedOfficial Fix0.000450.00CVE-2024-2440

97 more entries are not shown

Do you know our Splunk app?

Download it now for free!