janus-gateway up to 0.10.0 janus.c janus_process_incoming_request Request initialization of resource

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.9$0-$5k0.00

Summaryinfo

A vulnerability was found in janus-gateway up to 0.10.0. It has been classified as problematic. Affected by this vulnerability is the function janus_process_incoming_request of the file janus.c. The manipulation as part of Request leads to initialization of resource. This vulnerability is uniquely identified as CVE-2020-13899. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability was found in janus-gateway up to 0.10.0 and classified as problematic. This issue affects the function janus_process_incoming_request of the file janus.c. The manipulation as part of a Request leads to a initialization of resource vulnerability. Using CWE to declare the problem leads to CWE-909. The product does not initialize a critical resource. Impacted is confidentiality. The summary by CVE is:

An issue was discovered in janus-gateway (aka Janus WebRTC Server) through 0.10.0. janus_process_incoming_request in janus.c discloses information from uninitialized stack memory.

The weakness was disclosed 06/10/2020 (GitHub Repository). The advisory is shared at github.com. The identification of this vulnerability is CVE-2020-13899 since 06/07/2020. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The entries VDB-156496, VDB-156498 and VDB-156499 are pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.4
VulDB Meta Temp Score: 6.2

VulDB Base Score: 5.3
VulDB Temp Score: 4.9
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.5
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Initialization of resource
CWE: CWE-909 / CWE-908
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

06/07/2020 🔍
06/10/2020 +3 days 🔍
06/11/2020 +1 days 🔍
10/23/2020 +134 days 🔍

Sourcesinfo

Advisory: github.com
Status: Not defined
Confirmation: 🔍

CVE: CVE-2020-13899 (🔍)
GCVE (CVE): GCVE-0-2020-13899
GCVE (VulDB): GCVE-100-156497
See also: 🔍

Entryinfo

Created: 06/11/2020 10:31
Updated: 10/23/2020 20:51
Changes: 06/11/2020 10:31 (39), 06/11/2020 10:36 (17), 10/23/2020 20:51 (1)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Interested in the pricing of exploits?

See the underground prices here!