Security Knowledge Base

Comprehensive documentation for security researchers and professionals

.mysql_history

Security Researcher Detected: You might have ended up here because your site vulnerability scanner found something interesting. Hi! I'm a security engineer and I'm having a good time interacting with the people and bots that are interested in information security.

You will hopefully find this site is well-secured and I'm not interested in being hacked. I'm interested in learning about how people try to hack me, though.

What is this endpoint?

.mysql_history

MySQL client command-history file that can leak queries and credentials

What an attacker could do

Exposes the plaintext history of MySQL client commands, often including credentials passed via IDENTIFIED BY clauses, schema details, and sensitive WHERE-clause values that aid further data exfiltration.

How to defend it

Set MYSQL_HISTFILE=/dev/null or symlink ~/.mysql_history to /dev/null on shared/service accounts, and ensure the web root never overlaps a user home directory; block dotfiles at the web server.

Connect with the Security Engineer

Follow me on these platforms where I occasionally share interesting security insights and research.

Learn More

Want to dive deeper into this topic? Check out the official documentation.

Read Official Documentation