How severe is CVE-2020-14313?

CVE-2020-14313 has a CVSS 3.x base score of 4.3, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.

Is CVE-2020-14313 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (55th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2020-14313?

CVE-2020-14313 affects Redhat Quay. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2020-14313?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2020-14313 published?

CVE-2020-14313 was published on 2020-08-11 and last updated on 2026-06-17.

CVE-2020-14313

CVE-2020-14313 is a medium-severity vulnerability in Redhat Quay with a CVSS 3.x base score of 4.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Medium (CVSS 3.x base score 4.3)
CVSS v2: 4.0
EPSS exploit prediction: 1% (55th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Redhat Quay
Published: 2020-08-11
Last modified: 2026-06-17

Description

An information disclosure vulnerability was found in Red Hat Quay in versions before 3.3.1. This flaw allows an attacker who can create a build trigger in a repository, to disclose the names of robot accounts and the existence of private repositories within any namespace.

Frequently asked questions

What is CVE-2020-14313?: An information disclosure vulnerability was found in Red Hat Quay in versions before 3.3.1. This flaw allows an attacker who can create a build trigger in a repository, to disclose the names of robot accounts and the existence of private repositories within any namespace.
How severe is CVE-2020-14313?: CVE-2020-14313 has a CVSS 3.x base score of 4.3, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.
Is CVE-2020-14313 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (55th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2020-14313?: CVE-2020-14313 affects Redhat Quay. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2020-14313?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2020-14313 published?: CVE-2020-14313 was published on 2020-08-11 and last updated on 2026-06-17.

References

https://bugzilla.redhat.com/show_bug.cgi?id=1853026

Affected products (1)

cpe:2.3:a:redhat:quay:*:*:*:*:*:*:*:*

More vulnerabilities in Redhat Quay

CVE-2021-3762 — Critical (CVSS 9.8): A directory traversal vulnerability was found in the ClairCore engine of Clair. An attacker can exploit this by…
CVE-2020-27832 — Critical (CVSS 9.0): A flaw was found in Red Hat Quay, where it has a persistent Cross-site Scripting (XSS) vulnerability when displaying a…
CVE-2022-1227 — High (CVSS 8.8): A privilege escalation flaw was found in Podman. This flaw allows an attacker to publish a malicious image to a public…
CVE-2019-3864 — High (CVSS 8.8): A vulnerability was discovered in all quay-2 versions before quay-3.0.0, in the Quay web GUI where POST requests…
CVE-2023-44487 — High (CVSS 7.5): The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset…
CVE-2020-10735 — High (CVSS 7.5): A flaw was found in python. In algorithms with quadratic time complexity using non-binary bases, when using…

All CVEs affecting Redhat Quay →