Security Test: Exposed MySQL Config¶

Description¶

Default Severity: high

When the MySQL configuration file is accidentally made public, anyone can view sensitive details like usernames, passwords, and connection info. This exposure can let attackers break into your database, steal data, or find other ways to compromise your system. It usually happens when developers leave these files with loose permissions or mistakenly keep them in public folders during setup or debugging. The risks include unauthorized access and potential data breaches, so it's crucial to properly secure these files to avoid giving attackers an easy entry point.

Configuration¶

Identifier: information_disclosure/exposed_mysql_config

Examples¶

All configuration available:

checks:
  information_disclosure/exposed_mysql_config:
    skip: false # default

Compliance and Standards¶