Vedo Suite version 2024.17 is affected by an insecure data storage vulnerability that exposes sensitive credentials, posing a significant risk of unauthorized system access.

The application utilizes insecure storage practices by maintaining clear-text credentials and configuration secrets in a configuration file, which is accessible to unauthenticated attackers.

The exposure of clear-text credentials and database secrets allows an attacker to gain unauthorized access to backend systems and sensitive data stores. Given the CVSS score of 8.6, this vulnerability represents a high-severity risk that could lead to full compromise of the affected environment and severe reputational damage.

Immediate Action: Since no official patch is currently identified, administrators should restrict network and file system access to the /api_vedo/configuration/config.yml file immediately and rotate all credentials stored within it.

Proactive Monitoring: Monitor server access logs for unauthorized requests targeting the configuration directory or unusual patterns of authenticated activity following potential credential exposure.

Compensating Controls: Implement strict file system permissions to ensure the configuration file is readable only by the service account, and utilize a Web Application Firewall to block external access to the /api_vedo/configuration/ path.

Public Exploit Available: Yes — a published proof-of-concept exists as documented in the GitHub repository referenced by the CVE record.

This vulnerability presents a critical security risk due to the exposure of plain-text secrets. Organizations currently running Vedo Suite version 2024.17 must immediately restrict access to the affected configuration file and initiate a full rotation of all exposed secrets, as the existence of a public proof-of-concept significantly lowers the barrier for exploitation.