Red Hat Quay up to 3.14.0 Proxy Cache insecure inherited permissions
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $5k-$25k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Red Hat Quay up to 3.14.0. Affected by this issue is some unknown functionality of the component Proxy Cache. This manipulation causes insecure inherited permissions. This vulnerability is handled as CVE-2025-4374. There is not any exploit available.
Details
A vulnerability has been found in Red Hat Quay up to 3.14.0 and classified as problematic. Affected by this vulnerability is some unknown functionality of the component Proxy Cache. The manipulation with an unknown input leads to a insecure inherited permissions vulnerability. The CWE definition for the vulnerability is CWE-277. A product defines a set of insecure permissions that are inherited by objects that are created by the program. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
A flaw was found in Quay. When an organization acts as a proxy cache, and a user or robot pulls an image that hasn't been mirrored yet, they are granted "Admin" permissions on the newly created repository.
The advisory is shared at bugzilla.redhat.com. This vulnerability is known as CVE-2025-4374 since 05/06/2025. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 08/01/2025). MITRE ATT&CK project uses the attack technique T1222 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-13599). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.redhat.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.0VulDB Meta Temp Score: 6.0
VulDB Base Score: 5.5
VulDB Temp Score: 5.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 6.5
CNA Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Insecure inherited permissionsCWE: CWE-277 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
05/06/2025 🔍05/06/2025 🔍
05/06/2025 🔍
08/01/2025 🔍
Sources
Vendor: redhat.comAdvisory: bugzilla.redhat.com
Status: Not defined
CVE: CVE-2025-4374 (🔍)
GCVE (CVE): GCVE-0-2025-4374
GCVE (VulDB): GCVE-100-307561
EUVD: 🔍
Entry
Created: 05/06/2025 07:25Updated: 08/01/2025 01:48
Changes: 05/06/2025 07:25 (51), 07/23/2025 23:49 (1), 08/01/2025 01:48 (13)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.