CVE-2020-10574

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.

Published: 2020-03-14 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2020-10574 is rated Moderate Risk (62.7/100): CVSS Critical severity, with medium exploitation likelihood (EPSS 1.23%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2020-10574

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.43% 1.23% +0.80%
2 2025-03-30 0.84% 0.43% -0.41%
3 2025-03-29 — 0.84% —

Full EPSS history (9 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2020-10574

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.8 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 [email protected]
7.5 2.0 HIGH
AV:N/AC:L/Au:N/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 10.0 6.4 [email protected]

Weakness enumeration for CVE-2020-10574

OS Trackers for CVE-2020-10574

vendor priority summary link
debian not yet assigned CVE-2020-10574 not yet assigned priority: Debian including 1 source packages (janus), 3 status rows across 3 suites (bookworm, forky, sid): resolved 3. https://security-tracker.debian.org/tracker/CVE-2020-10574
ubuntu low CVE-2020-10574 low priority: Ubuntu including 1 source packages (janus), 17 status rows across 17 suites (bionic, eoan, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): ignored 5, not-affected 5, DNE 3, needed 3, released 1. https://ubuntu.com/security/CVE-2020-10574

Affected software / configurations for CVE-2020-10574

Vendor Product Version Raw CPE
meetecho janus <= 0.9.1 cpe:2.3:a:meetecho:janus:*:*:*:*:*:*:*:*

References for CVE-2020-10574

URL Tags
https://github.com/meetecho/janus-gateway/pull/1989 Patch Third Party Advisory
cvelogic Threat Intelligence