Digium 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

Digium Asterisk144
Digium s800i2
Digium Certified Asterisk1
Digium Asterisk Open Source1
Digium Asterisk GUI1

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 Fix139
Temporary Fix0
Workaround0
Unavailable0
Not Defined11

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

High2
Functional0
Proof-of-Concept49
Unproven22
Not Defined77

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
Local3
Adjacent2
Network145

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
High1
Low38
None111

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
Required1
None149

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
≤41
≤516
≤659
≤727
≤838
≤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
≤30
≤47
≤538
≤643
≤739
≤815
≤98
≤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
≤31
≤43
≤516
≤665
≤720
≤837
≤95
≤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
≤30
≤40
≤50
≤66
≤73
≤811
≤93
≤101

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
≤51
≤60
≤70
≤82
≤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

<1k45
<2k34
<5k60
<10k2
<25k5
<50k4
<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

<1k150
<2k0
<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 (7): Addons Module (1), Asterisk (144), Asterisk GUI (1), Asterisk Open Source (1), Certified Asterisk (1), Zaptel (1), s800i (2)

Link to Vendor Website: https://www.digium.com/

PublishedBaseTempVulnerabilityProdExpRemEPSSCTICVE
12/15/20233.83.7Digium Asterisk path traversalCommunications SystemNot DefinedOfficial Fix0.001040.00CVE-2023-49294
12/15/20235.65.5Digium Asterisk DTLS unknown vulnerabilityCommunications SystemNot DefinedOfficial Fix0.005130.00CVE-2023-49786
12/15/20236.46.3Digium Asterisk buffer overflowCommunications SystemNot DefinedOfficial Fix0.001210.05CVE-2023-37457
04/15/20225.55.3Digium Asterisk STIR server-side request forgeryCommunications SystemNot DefinedOfficial Fix0.006870.00CVE-2022-26499
04/15/20226.36.0Digium Asterisk/Certified Asterisk func_odbc sql injectionCommunications SystemNot DefinedOfficial Fix0.008040.00CVE-2022-26651
04/15/20224.34.1Digium Asterisk STIR resource consumptionCommunications SystemNot DefinedOfficial Fix0.029400.00CVE-2022-26498
02/21/20214.34.3Digium Asterisk WebRTC Client res_rtp_asterisk.c stack-based overflowCommunications SystemNot DefinedOfficial Fix0.002630.00CVE-2021-26714
02/19/20215.15.1Digium Asterisk SDP Negotiation res_pjsip_session.c denial of serviceCommunications SystemNot DefinedOfficial Fix0.001930.00CVE-2021-26906
07/12/20194.24.2Digium Asterisk Open Source SDP chan_sip null pointer dereferenceCommunications SystemNot DefinedNot Defined0.004730.00CVE-2019-13161
07/12/20196.46.4Digium Asterisk res_pjsip_messaging memory corruptionCommunications SystemNot DefinedNot Defined0.047170.00CVE-2019-12827
11/14/20187.47.2Digium Asterisk DNS SRV/NAPTR Lookup memory corruptionCommunications SystemNot DefinedOfficial Fix0.004670.00CVE-2018-19278
12/22/20176.46.1Digium Asterisk PJSIP Channel Driver Contact Header input validationCommunications SystemNot DefinedOfficial Fix0.928680.03CVE-2017-17850
12/13/20174.84.7Digium Asterisk RTCP Stack memory corruptionCommunications SystemNot DefinedOfficial Fix0.928540.00CVE-2017-17664
12/02/20176.46.3Digium Asterisk chan_skinny Channel Driver chan_skinny.c resource managementCommunications SystemHighOfficial Fix0.693180.02CVE-2017-17090
11/09/20175.65.4Digium Asterisk pjsip Session Object memory corruptionCommunications SystemNot DefinedOfficial Fix0.020900.00CVE-2017-16672
11/09/20177.57.2Digium Asterisk CDR Handller memory corruptionCommunications SystemNot DefinedOfficial Fix0.017540.00CVE-2017-16671
10/10/20177.47.2Digium Asterisk RTCP Packet information disclosureCommunications SystemNot DefinedOfficial Fix0.001920.00CVE-2017-14603
09/26/20177.57.5Digium Asterisk GUI os command injectionCommunications SystemNot DefinedNot Defined0.001150.00CVE-2017-14001
09/02/20178.58.2Digium Asterisk command injectionCommunications SystemNot DefinedOfficial Fix0.961190.00CVE-2017-14100
09/02/20176.46.1Digium Asterisk res_rtp_asterisk.c information disclosureCommunications SystemNot DefinedOfficial Fix0.020560.00CVE-2017-14099
09/02/20176.46.1Digium Asterisk PJSIP Channel Driver input validationCommunications SystemNot DefinedOfficial Fix0.927180.00CVE-2017-14098
08/02/20175.25.1Digium Addons Module add-license-form.php cross site scriptingUnknownNot DefinedOfficial Fix0.001640.02CVE-2015-2690
06/02/20177.47.1Digium Asterisk PJSIP memory corruptionCommunications SystemNot DefinedOfficial Fix0.012080.06CVE-2017-9372
06/02/20176.46.1Digium Asterisk PJSIP out-of-boundsCommunications SystemNot DefinedOfficial Fix0.006600.00CVE-2017-9359
06/02/20176.46.1Digium Asterisk SCCP Packet infinite loopCommunications SystemNot DefinedOfficial Fix0.006940.05CVE-2017-9358

125 more entries are not shown

Do you need the next level of professionalism?

Upgrade your account now!