Continuous Integration 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

Jenkins166
CloudBees Jenkins67
jenkins-reviewbot Plugin2
Jenkins-ci Monitoring plugin2
Jenkins vRealize Orchestrator Plugin1

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 Fix130
Temporary Fix0
Workaround1
Unavailable0
Not Defined124

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

High3
Functional0
Proof-of-Concept4
Unproven0
Not Defined248

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
Local6
Adjacent33
Network216

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
High6
Low129
None120

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
Required108
None147

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
≤31
≤413
≤586
≤684
≤739
≤823
≤96
≤103

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
≤31
≤413
≤587
≤693
≤738
≤816
≤95
≤102

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
≤33
≤449
≤565
≤669
≤737
≤825
≤94
≤103

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
≤31
≤42
≤536
≤654
≤733
≤817
≤924
≤107

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
≤70
≤80
≤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

<1k85
<2k103
<5k66
<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

<1k237
<2k18
<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 (22): Apache Continuum, CloudBees Jenkins, CloudBees Jenkins Operations Center, Jenkins, Jenkins-ci Exclusion, Jenkins-ci Monitoring plugin, Jenkins-ci Subversion-plugin, jenkins-cloudformation-plugin Plugin, jenkins-email-ext, jenkins-mailer-plugin, jenkins-reviewbot Plugin, jenkins-ssh-slaves-plugin, Jenkins AWS Global Configuration Plugin, Jenkins OWASP Dependency-Track Plugin, Jenkins Promoted Builds Plugin, Jenkins Sonar Quality Gates Plugin, Jenkins SQLPlus Script Runner Plugin, Jenkins Subversion Plugin, Jenkins Support Core Plugin, Jenkins Team Foundation Server Plugin, Jenkins TestComplete Support Plugin, Jenkins vRealize Orchestrator Plugin

PublishedBaseTempVulnerabilityProductExpRemCTICVE
09/22/20224.44.4Jenkins Tooltip cross site scriptingJenkinsNot DefinedNot Defined0.03CVE-2022-41224
06/24/20225.45.4Jenkins vRealize Orchestrator Plugin HTTP POST Request cross-site request forgeryvRealize Orchestrator PluginNot DefinedNot Defined0.05CVE-2022-34211
06/24/20224.84.8Jenkins Build Button cross site scriptingJenkinsNot DefinedNot Defined0.04CVE-2022-34173
06/24/20224.84.8Jenkins Symbol-based Icons cross site scriptingJenkinsNot DefinedNot Defined0.06CVE-2022-34172
06/24/20224.84.8Jenkins SVG Icon cross site scriptingJenkinsNot DefinedNot Defined0.03CVE-2022-34171
06/24/20224.84.8Jenkins Help Icon cross site scriptingJenkinsNot DefinedNot Defined0.03CVE-2022-34170
06/24/20223.53.5Jenkins Fragment protection mechanismJenkinsNot DefinedNot Defined0.03CVE-2022-34175
06/23/20223.13.1Jenkins Login Form timing discrepancyJenkinsNot DefinedNot Defined0.17CVE-2022-34174
02/09/20225.95.9Jenkins XStream Converter protection mechanismJenkinsNot DefinedNot Defined0.06CVE-2022-0538
01/13/20224.34.3Jenkins Parameter cross-site request forgeryJenkinsNot DefinedNot Defined0.03CVE-2022-20612
11/04/20215.55.5Jenkins Subversion Plugin Subversion Key File path traversalSubversion PluginNot DefinedNot Defined0.03CVE-2021-21698
11/04/20215.55.5Jenkins incomplete blacklistJenkinsNot DefinedNot Defined0.00CVE-2021-21697
11/04/20215.55.5Jenkins Symbolic Links authorizationJenkinsNot DefinedNot Defined0.05CVE-2021-21695
11/04/20215.55.5Jenkins authorizationJenkinsNot DefinedNot Defined0.06CVE-2021-21694
11/04/20215.55.5Jenkins Agent-to-Controller improper authorizationJenkinsNot DefinedNot Defined0.03CVE-2021-21693
11/04/20215.55.5Jenkins Agent-to-Controller authorizationJenkinsNot DefinedNot Defined0.03CVE-2021-21691
11/04/20215.55.5Jenkins Agent-to-Controller authorizationJenkinsNot DefinedNot Defined0.03CVE-2021-21689
11/04/20215.55.5Jenkins Agent-to-Controller authorizationJenkinsNot DefinedNot Defined0.05CVE-2021-21687
11/04/20215.55.5Jenkins Agent-to-Controller authorizationJenkinsNot DefinedNot Defined0.03CVE-2021-21685
11/04/20215.55.5Jenkins Agent-to-Controller authorizationJenkinsNot DefinedNot Defined0.03CVE-2021-21692
11/04/20215.55.5Jenkins Agent File protection mechanismJenkinsNot DefinedNot Defined0.04CVE-2021-21690
11/04/20216.56.5Jenkins Agent-to-Controller Security Check authorizationJenkinsNot DefinedNot Defined0.03CVE-2021-21688
11/04/20215.55.5Jenkins Agent-to-Controller Security Subsystem path traversalJenkinsNot DefinedNot Defined0.00CVE-2021-21686
11/04/20215.55.5Jenkins FilePath API protection mechanismJenkinsNot DefinedNot Defined0.03CVE-2021-21696
10/07/20215.55.5Jenkins File Browser path traversalJenkinsNot DefinedNot Defined0.05CVE-2021-21683

230 more entries are not shown

Interested in the pricing of exploits?

See the underground prices here!