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

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

Eclipse Jetty29
Eclipse Mosquitto18
Eclipse OpenJ911
Eclipse Theia7
Eclipse Vert.x6

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 Fix67
Temporary Fix0
Workaround0
Unavailable0
Not Defined72

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

High0
Functional0
Proof-of-Concept4
Unproven0
Not Defined135

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
Physical1
Local9
Adjacent25
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
High5
Low55
None79

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
Required24
None115

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
≤415
≤514
≤638
≤739
≤820
≤910
≤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
≤30
≤416
≤514
≤642
≤735
≤819
≤911
≤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
≤30
≤429
≤522
≤648
≤715
≤822
≤91
≤102

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
≤41
≤52
≤612
≤713
≤831
≤911
≤1020

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
≤33
≤42
≤52
≤64
≤79
≤88
≤91
≤102

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

<1k29
<2k87
<5k23
<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

<1k134
<2k5
<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 (46): BIRT (2), Buildship (1), Californium (3), Che (3), CycloneDDS (2), Cyclone DDS (2), Ditto (1), EDC (1), Equinox (1), Equinox p2 (1), GlassFish (1), Glassfish (1), Hawkbit (1), Hono (2), IDE (4), JGit (1), Jetty (29), Jetty Server (1), Keti (2), Kura (4), Leshan (1), Lyo (1), Memory Analyzer (3), Mojarra (3), Mosquito (1), Mosquitto (18), OMR (2), Open J9 (1), OpenJ9 (11), Openj9 (5), Paho MQTT C Client (1), Parsson (1), RAP (1), RDF4j (1), Sphinx (1), Target Management (1), Theia (7), ThreadX (3), TinyDTLS (1), Vert.0 (6), Vorto (1), Wakaama (2), Web Tools Platform (1), birt (1), hawkBit (1), tinydtls (1)

PublishedBaseTempVulnerabilityProdExpRemEPSSCTICVE
05/27/20244.94.8Eclipse Open J9 Concurrent Scavenge Garbage Collection Xgc:concurrentScavenge buffer access with incorrect length valueUnknownNot DefinedOfficial Fix0.000430.03CVE-2024-3933
05/23/20245.04.9Eclipse Ditto Explorer User Interface cross site scriptingUnknownNot DefinedOfficial Fix0.000440.05CVE-2024-5165
05/07/20245.35.3Eclipse EDC Connector Component insertion of sensitive information into sent dataUnknownNot DefinedOfficial Fix0.000450.03CVE-2024-4536
04/26/20249.89.6Eclipse Target Management os command injectionUnknownNot DefinedOfficial Fix0.000430.04CVE-2024-0740
04/09/20246.46.4Eclipse Kura LogServlet unknown vulnerabilityUnknownNot DefinedNot Defined0.000430.04CVE-2024-3046
03/26/20246.36.0Eclipse ThreadX tx_freertos.c xQueueCreateSet heap-based overflowUnknownProof-of-ConceptOfficial Fix0.000450.05CVE-2024-2212
03/26/20246.36.0Eclipse ThreadX __portable_aligned_alloc buffer overflowUnknownProof-of-ConceptOfficial Fix0.000450.04CVE-2024-2452
03/26/20246.05.7Eclipse ThreadX tx_clib_lock.c _Mtxinit array indexUnknownProof-of-ConceptOfficial Fix0.000450.05CVE-2024-2214
02/26/20246.46.3Eclipse Jetty HTTP/2 SSL resource consumptionUnknownNot DefinedOfficial Fix0.000450.00CVE-2024-22201
12/11/20234.74.7Eclipse Memory Analyzer Report Definition xml external entity referenceUnknownNot DefinedNot Defined0.000470.00CVE-2023-6194
11/15/20234.74.6Eclipse OpenJ9 JVM race conditionUnknownNot DefinedOfficial Fix0.000440.04CVE-2023-5676
11/09/20235.75.5Eclipse IDE xml external entity referenceUnknownNot DefinedOfficial Fix0.000460.04CVE-2023-4218
11/03/20235.75.7Eclipse Parsson JSON Parser denial of serviceUnknownNot DefinedOfficial Fix0.000440.04CVE-2023-4043
11/03/20237.87.7Eclipse Glassfish JDK input validationApplication Server SoftwareNot DefinedOfficial Fix0.001220.05CVE-2023-5763
10/18/20237.57.3Eclipse Mosquito Server iterationUnknownNot DefinedOfficial Fix0.000440.04CVE-2023-5632
10/10/20236.46.3Eclipse Jetty MetaDataBuilder.java MetaDataBuilder.checkSize integer underflowUnknownNot DefinedOfficial Fix0.004030.05CVE-2023-36478
09/21/20237.97.8Eclipse RAP FileUpload path traversalUnknownNot DefinedOfficial Fix0.002630.00CVE-2023-4760
09/15/20233.63.6Eclipse Jetty OpenId improper authenticationUnknownNot DefinedOfficial Fix0.000680.05CVE-2023-41900
09/14/20233.63.6Eclipse Jetty CGI Servlet quoting syntaxUnknownNot DefinedOfficial Fix0.000550.00CVE-2023-36479
09/14/20235.35.2Eclipse Jetty length parameterUnknownNot DefinedOfficial Fix0.000600.00CVE-2023-40167
09/12/20238.07.9Eclipse JGit case sensitivityUnknownNot DefinedOfficial Fix0.001280.07CVE-2023-4759
09/01/20235.95.8Eclipse Mosquitto QoS 2 Message memory leakUnknownNot DefinedOfficial Fix0.000980.00CVE-2023-28366
09/01/20237.37.2Eclipse Leshan DefaultDDFFileValidator xml external entity referenceUnknownNot DefinedOfficial Fix0.000630.05CVE-2023-41034
05/22/20236.96.8Eclipse Openj9 String buffer overflowUnknownNot DefinedOfficial Fix0.001300.00CVE-2023-2597
04/19/20234.03.9Eclipse Jetty Cookie Parser unknown vulnerabilityUnknownNot DefinedOfficial Fix0.000970.00CVE-2023-26049

114 more entries are not shown

Want to stay up to date on a daily basis?

Enable the mail alert feature now!