Urgent.News

What's breaking now, across thousands of outlets.

Tech

Dumping Every User's Plaintext Password Without Touching the Database

Exploiting a forgotten debug statement that logs plaintext passwords and a hidden SIEM dashboard with hardcoded credentials to retrieve a flag. Someone left a debug log in the login route that dumps passwords in plaintext. Those logs end up on a hidden SIEM dashboard protected by default credentials. We'll find it, log in, and read everyone's passwords. Lab setup From an empty directory: npx…

A forgotten debug statement in an online store app logged plaintext passwords in error logs. These logs ended up on a hidden SIEM dashboard with default login credentials. The app's URL is http://localhost:3000. A directory brute-forcer found the /monitoring/siem endpoint. Logging the email, password, and a flag in plaintext allowed retrieval of the flag OSS{pl41nt3xt_p4ssw0rd_1n_l0gs}.

Common vulnerabilities included logging sensitive request data, using plaintext logs, unlisted internal tools, and default credentials. To fix this, avoid logging sensitive data, use structured logging with field redaction, treat logs as sensitive, secure internal tools with strong credentials, and regularly review logs for sensitive information.

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

Read the original at dev.to →

More in Tech

How CIDS Should Handle Conflicting Security Signals.

A behavioral security system rarely receives perfectly consistent evidence. Imagine one session produces: Network Signal → unusual request pattern Identity Signal → authenticated legitimate user Host…

  • Security signals are evidence, not verdicts
  • CIDS treats conflicts as part of reasoning process
  • Risk: Elevated, Confidence: Moderate, Reason: Behavioral evidence strong but telemetry inconsistent

More from Saturday 19 September →