CVE-2025-51055

8.6 HIGH

📋 TL;DR

Vedo Suite version 2024.17 stores sensitive credentials, secret keys, and database information in plain text within the /api_vedo/configuration/config.yml file. This allows attackers with file system access to read these credentials and potentially gain unauthorized access to systems. All deployments using this vulnerable version are affected.

💻 Affected Systems

Products:
  • Vedo Suite
Versions: 2024.17
Operating Systems: All platforms running Vedo Suite
Default Config Vulnerable: ⚠️ Yes
Notes: The vulnerability exists in the default configuration where credentials are stored in plain text in config.yml.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Full system compromise where attackers extract all stored credentials, gain administrative access to databases and connected systems, and potentially pivot to other network resources.

🟠

Likely Case

Credential theft leading to unauthorized access to the Vedo Suite application, connected databases, and any systems using the exposed secret keys.

🟢

If Mitigated

Limited impact if file permissions restrict access, but the plain-text storage remains a significant security weakness.

🌐 Internet-Facing: HIGH if the config.yml file is accessible via web server misconfiguration or directory traversal vulnerabilities.
🏢 Internal Only: HIGH as any user or process with file system access can read the sensitive credentials.

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Exploitation requires file system access to read the config.yml file. Public exploit code is available on GitHub.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: http://bottinelli.com

Restart Required: No

Instructions:

1. Check vendor advisory at http://bottinelli.com for official patch. 2. If patch available, apply following vendor instructions. 3. Remove or secure existing config.yml files with plain-text credentials.

🔧 Temporary Workarounds

Secure config.yml file permissions

linux

Restrict file permissions to prevent unauthorized access to the configuration file.

chmod 600 /path/to/api_vedo/configuration/config.yml
chown root:root /path/to/api_vedo/configuration/config.yml

Move credentials to environment variables

all

Replace plain-text credentials in config.yml with environment variable references.

export VEDO_DB_PASSWORD='secure_password'
Update config.yml to use ${VEDO_DB_PASSWORD} instead of plain text

🧯 If You Can't Patch

  • Implement strict file system access controls and monitor for unauthorized access to config.yml
  • Rotate all exposed credentials including database passwords, API keys, and secret keys immediately

🔍 How to Verify

Check if Vulnerable:

Check if /api_vedo/configuration/config.yml exists and contains plain-text credentials like passwords, secret keys, or database connection strings.

Check Version:

Check Vedo Suite version in application interface or configuration files for '2024.17'

Verify Fix Applied:

Verify config.yml no longer contains plain-text credentials and uses secure storage methods like environment variables or encrypted configuration.

📡 Detection & Monitoring

Log Indicators:

  • Unauthorized access attempts to config.yml file
  • Failed authentication attempts using credentials from config.yml

Network Indicators:

  • Unexpected database connections from new IP addresses
  • API calls using exposed secret keys

SIEM Query:

source="*config.yml*" AND (event="read" OR event="access") AND user!="authorized_user"

🔗 References

📤 Share & Export