Janus up to 0.9.1 Admin API janus.c API Request name resolution

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.
9.8$0-$5k0.00

Summaryinfo

A vulnerability described as very critical has been identified in Janus up to 0.9.1. Impacted is an unknown function of the file janus.c of the component Admin API. Executing a manipulation as part of API Request can lead to name resolution. This vulnerability appears as CVE-2020-10574. The attack may be performed from remote. There is no available exploit.

Detailsinfo

A vulnerability has been found in Janus up to 0.9.1 and classified as very critical. This vulnerability affects an unknown code block of the file janus.c of the component Admin API. The manipulation as part of a API Request leads to a name resolution vulnerability. The CWE definition for the vulnerability is CWE-706. The product uses a name or reference to access a resource, but the name/reference resolves to a resource that is outside of the intended control sphere. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

An issue was discovered in Janus through 0.9.1. janus.c tries to use a string that doesn't actually exist during a "query_logger" Admin API request, because of a typo in the JSON validation.

The weakness was presented 03/14/2020. This vulnerability was named CVE-2020-10574 since 03/14/2020. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 03/15/2020).

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

See VDB-151621, VDB-151620, VDB-151619 and VDB-151617 for similar entries. If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 9.8
VulDB Meta Temp Score: 9.8

VulDB Base Score: 9.8
VulDB Temp Score: 9.8
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 9.8
NVD Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Name resolution
CWE: CWE-706
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: 🔍

Patch: github.com

Timelineinfo

03/14/2020 🔍
03/14/2020 +0 days 🔍
03/15/2020 +1 days 🔍
04/16/2024 +1493 days 🔍

Sourcesinfo

Advisory: github.com
Status: Not defined

CVE: CVE-2020-10574 (🔍)
GCVE (CVE): GCVE-0-2020-10574
GCVE (VulDB): GCVE-100-151618
See also: 🔍

Entryinfo

Created: 03/15/2020 10:35
Updated: 04/16/2024 12:23
Changes: 03/15/2020 10:35 (36), 03/15/2020 10:40 (17), 04/16/2024 12:23 (18)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!