Urgent.News

What's breaking now, across thousands of outlets.

Tech

Admin dropped the F-bomb in a password to show hackers who was really 1337

Cursing in login credentials can help keep the bad guys out, but not when the rest of your security is BS

Admin dropped the F-bomb in a password to show hackers who was really 1337

In this week's PWNED report, security researcher Dahvid Schloss of Suzu Labs shares an incident involving a factory with outdated Windows 7 servers connected to CNC milling machines. Despite the company having experienced a security breach six months prior, Schloss was tasked with ensuring the servers were secure. He initially struggled to gain access due to the servers not being connected to the domain, but eventually found a vulnerable server connected to the network.

Upon further investigation, Schloss discovered a password for an admin account written in leet speak as "heyhackergof***yourself." Initially believing it was a joke, Schloss kept the credentials hidden for a week. During a follow-up, he revealed the password to the IT team, who recognized it as the admin account he had set up. The password, while strong, was an embarrassing choice and exposed the factory to further vulnerabilities.

Written by urgent.news from The Register Science's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

This story

This is one outlet's version. Read the fullest account.

Read the original at theregister.com →

More in Tech

BOLA, the #1 API Vulnerability: a One-Line Fix and an A-B Test in Go and PHP

An invoicing application exposes an API : web addresses, or URLs, that other programs call to read or change invoices. Bob is logged in with his account.

  • BOLA (Broken Object Level Authorization) ranks as top API vulnerability in 2023
  • Fix involves single line of code checking user ownership of invoice
  • Test requires two accounts: one to create invoice, another to access it expecting 404

Activate WP_DEBUG and read debug.log without breaking the site in production

A site that crashes without saying anything is a site that is hiding the answer from you. WordPress knows about it, it simply refuses to display it, and this is intentional: showing a PHP trace to…

  • Activate WPDEBUG and set WPDEBUGLOG to true in wp-config.php
  • Disable WPDEBUGDISPLAY to prevent errors from showing to visitors
  • Check debug.log for Fatal, Warning, and Notice messages to diagnose issues

More from Thursday 29 October →