CVE-2024-3625: Mirror-registry: redis password stored in plain-text

Published Apr 10, 2024
·
Updated

A flaw was found in Quay, where Quay's database is stored in plain text in mirror-registry on Jinja's config.yaml file. This issue leaves the possibility of a malicious actor with access to this file to gain access to Quay's Redis instance.

Other sources

The Quay's database is stored in plain-text in mirror-registry on the jinja's config.yaml file, leaving the possibility of an malicious actor with permissions to access this file to gain access to Quay's Redis instance.

Red Hat

Affected Software

1 affected component
Red Hat Quay

Event History

Apr 10, 2024
Data Sourced
via Red Hat·08:53 PM
DescriptionSeverityAffected Software
Apr 25, 2024
CVE Published
via MITRE·05:46 PM
Data Sourced
via MITRE·05:46 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:15 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

What is the severity of CVE-2024-3625?

CVE-2024-3625 has a high severity due to the exposure of sensitive database information in plain text.

2

How do I fix CVE-2024-3625?

To fix CVE-2024-3625, secure the Jinja's config.yaml file by encrypting the database credentials and restricting access to authorized users.

3

What software is affected by CVE-2024-3625?

The affected software for CVE-2024-3625 is Red Hat Quay.

4

What are the potential risks of CVE-2024-3625?

The risks of CVE-2024-3625 include unauthorized access to Quay's Redis instance and potential data breaches.

5

How can I verify if my system is vulnerable to CVE-2024-3625?

You can verify if your system is vulnerable to CVE-2024-3625 by checking if the database credentials are stored in plain text within the Jinja's config.yaml file.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203