154
Who killed MySQL? (lemmy.world)
submitted 1 year ago by [email protected] to c/[email protected]
top 9 comments
sorted by: hot top controversial new old
[-] [email protected] 25 points 1 year ago

My guess:

spoilerAn attacker exploited a SQL injection or buffer overflow flaw in Apache+PHP+MySQL (which they have no idea about), installed a Java based coin miner (gross, I know), and deleted /var/log to cover up their tracks. But it was Col. Kernel that killed MySQL for using up too much memory. Ruby is just there because of some obscure distro dependency nobody uses.

[-] [email protected] 8 points 1 year ago

Why is Apache running on root?

[-] [email protected] 6 points 1 year ago

Easier to push updates without all the red tape.

[-] [email protected] 5 points 1 year ago

In some setups where each vhost run as its own user, the main apache process has to run as root.

[-] [email protected] 8 points 1 year ago

Kernel did ... OoM

[-] [email protected] 6 points 1 year ago
[-] [email protected] 6 points 1 year ago

My money's on the sysop being guilty of ~~man~~processslaughter or at least gross negligence for not putting enough RAM in the box.

[-] [email protected] 2 points 1 year ago

The bundler did it.

[-] [email protected] 2 points 1 year ago

Injection attack submitted through apache, processed by an outdated PHP, forwarded to fat java who's running a ye olde ass library to do sql input sanitization (it failed lol), and passed onto MySQL via a ruby script, which had a stroke because the request was to write to /var/log because someone was screwing around in sqlmap

Oh and /var/log "accidentally" had 777 perms lmao

this post was submitted on 12 Jul 2023
154 points (97.0% liked)

Comic Strips

12040 readers
1831 users here now

Comic Strips is a community for those who love comic stories.

The rules are simple:

Web of links

founded 1 year ago
MODERATORS