Beware bad passwords as attackers co-opt Linux servers into cybercrime
Did you prevent password-only logins on your SSH servers? On ALL of them? Are you sure about that?
Linux is an open-source operating system used across servers and devices, so kernel, distribution, and software vulnerabilities can affect deployed systems.
Search across headline titles and summaries.
Background for this topic.
Linux is an open-source operating-system kernel: privileged software that manages hardware, memory, processes, filesystems, and networking. Most deployments use it through a distribution that adds user-space tools, package managers, libraries, and an update policy. This distinction matters in security reporting: a kernel flaw, a distribution-package flaw, and a flaw in an application running on Linux may have different affected versions and fixes.
Material attack surfaces include kernel code, loadable modules and device drivers, network services, local privilege boundaries, and third-party packages. Vulnerabilities can enable denial of service, information disclosure, or escalation from an unprivileged account to root, depending on configuration and exploitability. Administrators should track upstream and distribution advisories, apply security updates, and reboot when a running kernel remains vulnerable. Mandatory access-control systems such as SELinux or AppArmor can restrict compromised processes; signed repositories, audit logs, and tested configuration baselines support package integrity and investigation. Open source does not itself guarantee security: exposure depends on code, configuration, maintenance, and the surrounding software stack.
Weekly headline count for the current query.
Did you prevent password-only logins on your SSH servers? On ALL of them? Are you sure about that?
Linux has never suffered from the infamous BSoD, short for blue screen of death, the name given to the dreaded “something went terribly wrong” message associated with a Windows system crash. Microsoft has tried many things over the years to shake that nickname “BSoD”, including changing the background colour used when crash messages appear, adding […]
It's serious, it's critical, and you could call it severe... but in HHGttG terminology, it's probably "mostly harmless".
What's better? Disclose early, patch fast? Or dig deep, disclose in full, patch more slowly?
Latest episode - listen now!
Even read-only files can be written to, leading to a dangerously general purpose elevation-of-privilege attack.
This bug is fiendishly hard to exploit - but if you patch, it won't be there to exploit at all.