Type Communications System

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 »

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 »

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 »

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 »

The approach a vulnerability it becomes important to use the expected access vector. This is typically via the network, local, or physically even.

Authentication »

To exploit a vulnerability a certail level of authentication might be required. Vulnerabilities without such a requirement are much more popular.

User Interaction »

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 »

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 »

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 »

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 »

The National Vulnerability Database (NVD) is also defining CVSS vectors and scores. These are usually not complete and might differ from VulDB scores.

Vendor »

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 »

There are sometimes also security researcher which provide their own CVSS vectors and scores for vulnerabilities they have found and published.

Exploit 0-day »

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 »

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 (21): Asterisk, Asterisk-Addons, Asterisk2Billing, Asterisk Open Source, Asterisk PBX, Asterisk s800i, Asterisk Zaptel, Asterisk@Home, AXON PBX, Brekeke pbx, Digium Asterisk, Digium Asterisk GUI, Digium Asterisk Open Source, Free PBX Phone System, Incredible PBX 11, innovaphone innovaphone PBX, NCH Axon Virtual PBX, Sangoma Asterisk, Sangoma Certified Asterisk, SIPhone Enterprise PBX, Tomasz Rekawek Yet Another Asterisk Panel

PublishedBaseTempVulnerabilityProdExpRemCTICVE
11/07/20204.34.1Asterisk PBX SIP Invite res_pjsip_session denial of servicePBXNot DefinedOfficial Fix0.00CVE-2020-28327
11/06/20205.35.1Asterisk PBX INVITE infinite loopPBXNot DefinedOfficial Fix0.00CVE-2020-28242
11/22/20196.46.4Sangoma Asterisk/Certified Asterisk res_pjsip_t38.c null pointer dereferenceAsterisk/Certified AsteriskNot DefinedNot Defined0.00CVE-2019-18976
11/22/20196.96.9Sangoma Asterisk/Certified Asterisk chan_sip.c authorizationAsterisk/Certified AsteriskNot DefinedNot Defined0.00CVE-2019-18790
11/22/20197.57.5Sangoma Asterisk/Certified Asterisk Asterisk Manager Interface manager.c authorizationAsterisk/Certified AsteriskNot DefinedNot Defined0.00CVE-2019-18610
10/29/20197.47.4Asterisk PBX Call authorizationPBXNot DefinedNot Defined0.07CVE-2009-3723
09/09/20195.45.4Sangoma Asterisk Invite res_pjsip_t38 null pointer dereferenceAsteriskNot DefinedNot Defined0.07CVE-2019-15297
09/09/20196.46.4Sangoma Asterisk RTP Packet translate.c input validationAsteriskNot DefinedNot Defined0.03CVE-2019-15639
07/12/20194.24.2Digium Asterisk Open Source SDP chan_sip null pointer dereferenceAsterisk Open SourceNot DefinedNot Defined0.00CVE-2019-13161
07/12/20196.46.4Digium Asterisk res_pjsip_messaging memory corruptionAsteriskNot DefinedNot Defined0.00CVE-2019-12827
05/23/20196.46.4Asterisk null pointer dereferenceAsteriskNot DefinedNot Defined0.00CVE-2016-7550
02/28/20195.45.1Asterisk Open Source integer overflowOpen SourceNot DefinedOfficial Fix0.06CVE-2019-7251
11/14/20187.47.1Digium Asterisk DNS SRV/NAPTR Lookup memory corruptionAsteriskNot DefinedOfficial Fix0.00CVE-2018-19278
09/24/20186.46.1Asterisk PBX res_http_websocket.so resource managementPBXNot DefinedOfficial Fix0.03CVE-2018-17281
06/12/20185.45.1Asterisk Open Source TCP TLS improper authenticationOpen SourceNot DefinedOfficial Fix0.05CVE-2018-12228
06/12/20185.35.1Asterisk PBX ACL information disclosurePBXNot DefinedOfficial Fix0.00CVE-2018-12227
06/01/20185.75.7AXON PBX Reflected cross site scriptingPBXNot DefinedNot Defined0.00CVE-2018-11552
06/01/20187.57.5AXON PBX DLL Loader pbxsetup.exe untrusted search pathPBXNot DefinedNot Defined0.03CVE-2018-11551
02/22/20184.84.6Asterisk HTTP Server res_http_websocket.c data processingAsteriskNot DefinedOfficial Fix0.05CVE-2018-7287
02/22/20185.44.9Asterisk Connection data processingAsteriskProof-of-ConceptOfficial Fix0.00CVE-2018-7286
02/22/20186.46.1Asterisk RTP null pointer dereferenceAsteriskNot DefinedOfficial Fix0.00CVE-2018-7285
02/22/20187.46.6Asterisk memory corruptionAsteriskProof-of-ConceptOfficial Fix0.00CVE-2018-7284
12/22/20176.46.1Digium Asterisk PJSIP Channel Driver Contact Header input validationAsteriskNot DefinedOfficial Fix0.00CVE-2017-17850
12/13/20174.84.6Digium Asterisk RTCP Stack memory corruptionAsteriskNot DefinedOfficial Fix0.07CVE-2017-17664
12/02/20176.46.1Digium Asterisk chan_skinny Channel Driver chan_skinny.c resource managementAsteriskHighOfficial Fix0.04CVE-2017-17090

Do you need the next level of professionalism?

Upgrade your account now!