Isc 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

ISC BIND187
ISC DHCP21
ISC INN14
ISC DHCPD6
ISC dhcp4

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 Fix209
Temporary Fix0
Workaround4
Unavailable1
Not Defined24

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

High6
Functional4
Proof-of-Concept48
Unproven13
Not Defined167

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
Local16
Adjacent7
Network215

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
Low19
None214

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
Required0
None238

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
≤49
≤57
≤681
≤750
≤866
≤99
≤1016

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
≤523
≤672
≤776
≤837
≤911
≤1010

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
≤414
≤515
≤699
≤720
≤864
≤910
≤1016

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
≤54
≤613
≤711
≤834
≤94
≤100

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
≤618
≤74
≤833
≤91
≤101

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
≤52
≤68
≤71
≤89
≤91
≤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

<1k0
<2k1
<5k13
<10k83
<25k120
<50k20
<100k0
≥100k1

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

<1k212
<2k8
<5k7
<10k10
<25k1
<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 (9): BIND (187), DHCP (21), DHCP Client (2), DHCPD (6), INN (14), Kea (1), Lynx (2), Stork (1), dhcp (4)

Link to Vendor Website: https://www.isc.org/

PublishedBaseTempVulnerabilityProdExpRemEPSSCTICVE
07/23/20247.57.3ISC BIND Client Query assertionDomain Name SoftwareNot DefinedOfficial Fix0.000450.04CVE-2024-4076
07/23/20247.57.3ISC BIND RR resource consumptionDomain Name SoftwareNot DefinedOfficial Fix0.000520.00CVE-2024-1737
07/23/20247.57.3ISC BIND DNS Messages over TCP resource consumptionDomain Name SoftwareNot DefinedOfficial Fix0.000490.06CVE-2024-0760
07/23/20247.57.3ISC BIND Key Resource Record resource consumptionDomain Name SoftwareNot DefinedOfficial Fix0.000490.03CVE-2024-1975
07/11/20247.57.5ISC Stork TLS Certificate Validation certificate validationUnknownNot DefinedNot Defined0.000910.03CVE-2024-28872
02/13/20245.35.2ISC BIND ECS-Enabled Cache resource consumptionDomain Name SoftwareNot DefinedOfficial Fix0.000460.05CVE-2023-5680
02/13/20247.57.3ISC BIND DNS64 assertionDomain Name SoftwareNot DefinedOfficial Fix0.001020.04CVE-2023-5679
02/13/20247.57.3ISC BIND RFC 1918 Reverse Zone Query assertionDomain Name SoftwareNot DefinedOfficial Fix0.001020.03CVE-2023-5517
02/13/20247.57.3ISC BIND DNS Message Parser resource consumptionDomain Name SoftwareNot DefinedOfficial Fix0.001020.04CVE-2023-4408
02/13/20247.57.3ISC BIND named allocation of resourcesDomain Name SoftwareNot DefinedOfficial Fix0.001080.00CVE-2023-6516
09/20/20236.46.3ISC BIND DNS-over-TLS Query assertionDomain Name SoftwareNot DefinedOfficial Fix0.001200.03CVE-2023-4236
09/20/20237.57.3ISC BIND Control Channel Message recursionDomain Name SoftwareNot DefinedOfficial Fix0.002080.04CVE-2023-3341
06/22/20237.47.2ISC BIND Recursive-clients Quota stack-based overflowDomain Name SoftwareNot DefinedOfficial Fix0.001590.03CVE-2023-2911
06/22/20236.46.3ISC BIND NSEC Record denial of serviceDomain Name SoftwareNot DefinedOfficial Fix0.000850.03CVE-2023-2829
06/22/20237.57.3ISC BIND Cache resource consumptionDomain Name SoftwareNot DefinedOfficial Fix0.001680.06CVE-2023-2828
01/27/20236.46.3ISC BIND ECS Option denial of serviceDomain Name SoftwareNot DefinedOfficial Fix0.001320.00CVE-2022-3488
01/27/20236.46.3ISC BIND UPDATE Message resource consumptionDomain Name SoftwareNot DefinedOfficial Fix0.000930.03CVE-2022-3094
01/27/20236.46.3ISC BIND named denial of serviceDomain Name SoftwareNot DefinedOfficial Fix0.000930.00CVE-2022-3736
01/27/20235.65.5ISC BIND named recursionDomain Name SoftwareNot DefinedOfficial Fix0.000930.04CVE-2022-3924
10/07/20225.45.3ISC DHCP fqdn Label resource consumptionNetwork Management SoftwareNot DefinedOfficial Fix0.000990.00CVE-2022-2929
10/07/20226.16.0ISC DHCPD Server Response option_code_hash_lookup integer overflowNetwork Management SoftwareNot DefinedOfficial Fix0.001070.00CVE-2022-2928
09/21/20226.86.7ISC BIND Resolver denial of serviceDomain Name SoftwareNot DefinedOfficial Fix0.003740.04CVE-2022-3080
09/21/20226.16.1ISC BIND Statistics Channel buffer overflowDomain Name SoftwareNot DefinedOfficial Fix0.001260.00CVE-2022-2881
09/21/20226.06.0ISC BIND DNS Resolution Service denial of serviceDomain Name SoftwareNot DefinedOfficial Fix0.001860.00CVE-2022-2795
09/21/20226.46.3ISC BIND memory leakDomain Name SoftwareNot DefinedOfficial Fix0.004510.04CVE-2022-38178

213 more entries are not shown

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!