Overly broad permissions can turn one compromised account into a much larger security problem. Learn how to reduce unnecessary access, review privileges, and apply least privilege across modern Linux systems. Review Linux Privileges×

Alerts This Week
Warning Icon 1 514
Alerts This Week
Warning Icon 1 514

Stay Ahead With Linux Security News

Filter%20icon Refine news
X Clear Filters
X Clear Filters
View More

Get the latest News and Insights

Get the latest Linux and open source security news straight to your inbox.

Community Poll

Should Linux servers automatically install security updates?

No answer selected. Please try again.
Please select either existing option or enter your own, however not both.
Please select minimum {0} answer(s).
Please select maximum {0} answer(s).
/main-polls/157-should-linux-servers-automatically-install-security-updates?task=poll.vote&format=json
157
radio
0
[{"id":506,"title":"Yes \u2014 critical security patches should install automatically.","votes":0,"type":"x","order":1,"pct":0,"resources":[]},{"id":507,"title":"No \u2014 every update should be tested before deployment.","votes":0,"type":"x","order":2,"pct":0,"resources":[]},{"id":508,"title":"Only critical vulnerabilities should auto-install.","votes":0,"type":"x","order":3,"pct":0,"resources":[]},{"id":509,"title":"I patch when Reddit starts panicking.","votes":1,"type":"x","order":4,"pct":100,"resources":[]}] ["#ff5b00","#4ac0f2","#b80028","#eef66c","#60bb22","#b96a9a","#62c2cc"] ["rgba(255,91,0,0.7)","rgba(74,192,242,0.7)","rgba(184,0,40,0.7)","rgba(238,246,108,0.7)","rgba(96,187,34,0.7)","rgba(185,106,154,0.7)","rgba(98,194,204,0.7)"] 350
bottom 200
Loading...

Explore Latest Linux Security news

We found 4 articles for you...
210

RHEL and CentOS 7 Kernel Update: Security Fixes for Graphics Flaws

RHEL (Red Hat Enterprise Linux) and CentOS Linux 7 users have received a new Linux kernel security update fixing several vulnerabilities affecting the Intel graphics drivers. . The new Linux kernel security update comes exactly two months after the previous one and it’s here to fix three security vulnerabilities discovered by various security researchers in the Intel graphics drivers (i915), as well as three other security flaws. The three security vulnerabilities affecting the Intel graphics drivers are CVE-2020-12362 , an integer overflow that could allow a privileged user to escalate his/her privileges via local access, CVE-2020-12363 , an input validation flaw, and CVE-2020-12364 , a null pointer reference, both of which allowing a privileged user to initiate a denial-of-service (DoS) attack via local access The link for this article located at 9 to 5 Linux is no longer available. . The latest Linux kernel upgrade for RHEL and CentOS 7 addresses Intel graphics performance concerns, enhancing overall system security significantly.. kernel update, RHEL security, CentOS security, graphics flaw, local privilege escalation. . Brittany Day

Calendar%202 Jun 18, 2021 User Avatar Brittany Day Security Vulnerabilities
210

Intel: Two New Security Issues on Processors Related to Data Leakage

Intel last night made public two more data leakage disclosures, which tie back to Zombieload and November's TAA issue. . Here are the new disclosures: CVEID: CVE-2020-0548 Description: Cleanup errors in some Intel(R) Processors may allow an authenticated user to potentially enable information disclosure via local access. CVSS Base Score: 2.8 Low CVE-2020-0549 Description: Cleanup errors in some data cache evictions for some Intel(R) Processors may allow an authenticated user to potentially enable information disclosure via local access. CVSS Base Score: 6.5 Medium The link for this article located at Phoronix is no longer available. . Intel reveals two fresh security concerns tied to CPU termination flaws and access loopholes.. Data Leakage, Intel Processors, Information Disclosure. . Brittany Day

Calendar%202 Jan 28, 2020 User Avatar Brittany Day Security Vulnerabilities
77

Astaro Security Linux 2.016 Advisory Moderate Design Flaws

Several serious theoretical and practical security vulnerabilities, alleged GPL license violations, and more were found in Astaro "secure" Linux. Joerg Luebbert writes, "Some of the vulnerabilities might be local and some might argue about that Astaro Security Linux is a Firewall and no server... but as it uses SSHD it could always be that the "loginuser" account might have been compromised and shell access granted.". . .. Several serious theoretical and practical security vulnerabilities, alleged GPL license violations, and more were found in Astaro "secure" Linux. Joerg Luebbert writes, "Some of the vulnerabilities might be local and some might argue about that Astaro Security Linux is a Firewall and no server... but as it uses SSHD it could always be that the "loginuser" account might have been compromised and shell access granted." Date: Sat, 02 Feb 2002 19:40:08 +0100 From: "[ISO-8859-1] Jörg Lübbert" To: bugtraq@ Subject: Vulnerabilities in Astaro Security Linux 2.016 Preamble: Product: Astaro Security Linux Version: 2.016 Vendor: Astaro AG Vendor URL: Vendor status and reply: Vendor has been contacted with posting of this message Description: Astaro develops and distributes the firewall solution Astaro Security Linux. Astaro Security Linux offers extensive protection for local networks against hackers, viruses and other risks of connecting to the Internet. Astaro Security Linux is distributed by a worldwide network of partners who offer local support regarding installation and maintenance. Introduction: Dear BugTraq readers. I've taken a short glimpse on Astaro Security Linux and found out some points of interest that are mostly design flaws. Please note that I am theorising (based on a 1 1/2 hour research only) about the impacts and have not proven their concepts on Astaro Security Linux yet even though most can be proved easily. Some of the vulnerabilities might be local and some might argue about that Astaro Security Linux is a Firewall and no server... butas it uses SSHD it could always be that the "loginuser" account might have been compromised and shell access granted. Vulnerabilities: Summary: 5 Design flaws 2 Completely theorised design flaws 1 Possible design flaw 1 Licensing violation 1 Software bug Category 1: Design flaw Problem 1: Astaro Security Linux chroots various daemons like snmpd and named in an insecure manner. The proc filesystem is mounted within their chroot jails. Furthermore the chroot jail entitled chroot-ipsec provides the proc file system, a bash, ls, cat and most notably mount. Impact 1: Arbitrary users could cause severe damage by breaking the named or snmpd remotely and by misusing the proc file system to reconfigure certain parts of the system configuration under proc/sys. Furthermore proc/kcore could be read to obtain information stored in memory which could lead to system administrator privileges. These could for instance be DES encrypted passwords which leads to another design flaw Exploit 1: None provided Category 2: Design flaw Problem 2: Astaro Security Linux uses the DES algorithm as standard hashing scheme. DES has turned very old and is known to be easily crackable with modern processing power. Impact 2: Arbitrary users who obtain encrypted passwords (see 1) could retreive a 6 letter clear-text password within just some hours using modern processing power and use it to compromise the system. Exploit 2: None provided Category 3: Design flaw Problem 3: Astaro Security Linux runs most of its daemons with UID 0 privileges. Affected daemons are: named or snmpd. These daemons run in a chroot jail. Impact 3: Arbitrary users could remotely crack one of the affected daemons and use UID 0 powers to compromise the whole file system even if these daemons run in a chroot jail. Additional note 3-1: The main design flaw lies within that these daemons run UID 0 within a chroot jail. The daemons itself are not the design flaw (even though BIND 8.2.3 can be considered old). Additional note3-2: Other daemons with UID 0 are syslogd, klogd, mdw_daemon.pl, cron, aua and sshd. VPN subsystem, SQUID and others haven't been checked by me. Exploit 3: None provided Category 4: Possible design flaw Problem 4: OpenSSL PRNG Internal State Disclosure Vulnerability Impact 4: Please see: Exploit 4: None provided Additional note 4: It was NOT tested if the version of OpenSSL (0.9.6) used in Astaro Security Linux is a security-patched version of OpenSSL 0.9.6 since no sources were provided (5) Category 5: Licensing violation Problem 5: Astaro AG releases software packages without providing their sources and modifications to them as required in §3 of the GNU GPL and neither seems to offer distribution of GPL sources for free within a 3 year period in a written form. Additional note 5: I have not checked every available documentation for a written form of an offer as described in GNU GPL §3 b but only their license (which should normally contain just that) and CD-ROM contents. Category 6: Design flaw Problem 6: Astaro Security Linux has a default limit for simultaneously processes of 8190 soft and 8912 hard and its default cpu-time is "unlimited". Impact 6: Arbitrary users with local access (loginuser) can easily launch fork bombs to consume 100% CPU power and stop the system from operating. Exploit 6: None provided Category 7: Completely theorised design flaw Problem 7: Astaro Security Linux uses a very old version of PAM (0.70 dated 09.10.1999) which maybe contains vulnerabilities. Category 8: Design flaw Problem 8: /proc/version indicates "Linux version 2.4.8-asl-0.010815.0", which indicates the 2.4.8 version of the Linux kernel that contains some security vulnerabilities. Additional information on possible vulnerabilities can be found here: Impact 8: Various, see above URLs. Exploit 8: None provided Additional note 8: Due to absence of source code it could not be proved if this kernel is patched against the security issues mentionedabove. Category 9: Completely theorised design flaw Problem 9: Astaro Security Linux seems to rely on an old version of glibc according to ls -l /lib/libc*. Output: -rwxr-xr-x 1 root root 1080268 Sep 15 2000 libc.so.6 If my assumption is correct and the version used was not patched, it could be possible that the system is vulnerable to a "glibc file globbing heap corruption vulnerability". For more information please see: Impact 9: See URL above Exploit 9: None provided Category 10: Software bug (OT for Bugtraq, still included;) Problem 10: During installation one can choose to install OpenSource software only or OpenSource software and the so called Astaro Security Enterprise Toolkit. When only "OpenSource" was chosen, the installer locks up after entry of the last password (I think this was for lilo). If my assumption is right (that a lilo password is asked for) then no lilo password will be set even though the Enterprise Toolkit was selected and the installation finished successfully. Additional note 10: System tested on was 800MHZ Duron, 128MB RAM, 20GB Maxtor HD, 52X CD-ROM, 3X RTL 8139. Final words: Conclusion, a final word to the Astaro AG: So much about a "Security Linux"... You may have done the firewalling and the configuration interface of your product real good... but you should also read some articles on what could be considered more internal security and work on your products some more. Disclaimer: None of the information provided are meant to aid any destructive purposes. I will furthermore take no responsibility for that anyone will use the information provided for his or her own malicious purposes. This information is intended to aid in improving the current state of Astaro Security Linux, warn companies and individuals who run Astaro Security Linux and should help other designers of Linux distributions to avoid flaws like the ones elaborated on above. Please also not that I am in no way affiliated with Astaro AG or any of their 3rd party affiliates or wantto harm Astaro AG and/or their customers. - Jörg Lübbert (aka Kaladis) -- Kaladix Linux - The Secure Linux Distribution URL: . Numerous practical security weaknesses and design flaws are highlighted in Astaro Security Linux, indicating critical issues.. Astaro Security Linux, design flaws, security weaknesses, GPL violations, access control. . LinuxSecurity.com Team

Calendar%202 Jun 02, 2019 User Avatar LinuxSecurity.com Team Server Security
82

Swiss E-Voting System Advisory: Cryptographic Risk of Vote Tampering

Two separate teams of security researchers and academics from universities in Australia and Switzerland have revealed today vulnerabilities in the e-voting system that the Swiss voting commission plans to roll out for future elections. . Among the reported vulnerabilities there is one that security researchers said it could allow an attacker with local access to a voting machine --or the voting machine vendor itself-- to tamper with cast votes. The vulnerability resides in the cryptographic system that verifies that the cast votes are the same ones that are being reported, however, researchers say this cryptographic scheme is weak and allows someone to swap votes. The link for this article located at ZDNet is no longer available. . An in-depth examination of weaknesses present in Switzerland's electronic voting framework that could potentially enable manipulation of ballots.. Swiss E-Voting,Cryptographic Vulnerability,Vote Tampering,Security Research,Local Access. . Brittany Day

Calendar%202 Mar 13, 2019 User Avatar Brittany Day Government
83

Belkin N750 Router Critical: Local Access Risk Resolved

A serious vulnerability in a popular Belkin router could be exploited by a local, unauthenticated attacker to gain full control over affected devices.. The good news is that the bug has already been patched by Belkin. The bad news is that approximately nobody installs router firmware updates. The link for this article located at ThreatPost is no longer available. . The good news is that the bug has already been patched by Belkin. The bad news is that approximately. serious, vulnerability, popular, belkin, router, exploited, local, unauthenticated. . LinuxSecurity.com Team

Calendar%202 Nov 10, 2014 User Avatar LinuxSecurity.com Team Hacks/Cracks
77

FreeBSD 6.0-6.4: Local Root Access Risk in kqueue Notification Interface

A security researcher has uncovered a security bug in the FreeBSD operating system that allows users with limited privileges to take full control of underlying systems.. The bug in FreeBSD's kqueue notification interface makes it trivial for those with local access to a vulnerable system to gain full root privileges, Przemyslaw Frasunek, an independent security consultant in Poland, told The Register. It affects versions 6.0 through 6.4 of the operating system, the last two versions of which enjoy wide use and continue to be supported by the FreeBSD Foundation. Versions 7.1 and and beyond are not vulnerable. The link for this article located at The Register is no longer available. . A vulnerability in OpenBSD permits unauthorized users to escalate privileges through a flaw in the PF firewall subsystem.. FreeBSD Access Control Bug, Local Root Exploit, kqueue Notification Issue. . LinuxSecurity.com Team

Calendar%202 Sep 14, 2009 User Avatar LinuxSecurity.com Team Server Security
77

Sendmail Update: Critical Local Access Risk for Unix/Linux Admins

Security experts and vendors of Linux and other Unix-like operating systems are urging network administrators to replace some versions of popular e-mail server software known as Sendmail, because the most recent open-source versions can provide a doorway for local hackers.. . .. Security experts and vendors of Linux and other Unix-like operating systems are urging network administrators to replace some versions of popular e-mail server software known as Sendmail, because the most recent open-source versions can provide a doorway for local hackers. Since malicious individuals would need to gain command-line access to a server in order to exploit the vulnerability, the problem is greatest for organizations such as Internet service providers or universities that regularly provide shell access to users. Cade Cairns, a member of the Security Focus Threat Analysis Team, reported late last week that hackers with access to run Sendmail from the command line of vulnerable systems could possibly gain administrator access to the server by supplying specially crafted commands. The link for this article located at Newsbytes is no longer available. . Specialists strongly recommend that system administrators enhance their Sendmail versions to mitigate the possibility of unauthorized local access by hackers.. Sendmail Security Update, Unix-Like Systems, Mail Server Vulnerability. . LinuxSecurity.com Team

Calendar%202 Aug 24, 2001 User Avatar LinuxSecurity.com Team Server Security
83

SuSE Kernel Update: Clarifying Misconceptions On Backdoors And Security

Roman Drahtmüller send this message to the suse-security-announce mailing list in regards to an April Fools joke that some people are taking a little bit too seriously. . .. Roman Drahtmüller send this message to the suse-security-announce mailing list in regards to an April Fools joke that some people are taking a little bit too seriously : Date: Thu, 29 Mar 2001 15:48:18 +0200 (MEST) From: Roman Drahtmueller To: This email address is being protected from spambots. You need JavaScript enabled to view it. Subject: [suse-security-announce] Kernel Backdoor (April Fool's joke) To those involved in Linux security: The latest release of "Linux-Magazin", a monthly German magazine that focuses on Linux, contains an article by Mirko Dölle about security problems in the Linux kernel. In particular, the article argues that IP packets could be forwarded to the address 208.47.125.33 (there is a PTR record at gary7.nsa.gov, which has an A record back to the same address). Many German Linux users have been calling SuSE support to learn details on how to deal with this problem, not willing to believe that the article is an April Fool's joke on security. None of the claims are correct, which makes a kernel update unnecessary for this particular problem. Now, as inclined readers of security mailing lists may have noticed, there are indeed security problems in the Linux kernel. These problems are no backdoors of any kind, and they are not related to the article mentioned above. In addition, the known kernel security issues are not remotely exploitable, which means that local shell access is needed to take advantage of the weaknesses. The weaknesses allow for a local attacker to gain superuser access to the system. SuSE will provide update packages for the supported distributions 6.3, 6.4, 7.0 and 7.1 shortly that eliminate the known problems. The SuSE kernels are standard kernels, equipped with a set of patches that introduce drivers and many other enhancements to the standard Linux kernel. The update packages are currently being tested and will be available and announced assoon as possible. As an information for those who compile and install their own kernels: The freshly released Linux kernel version 2.2.19 fixes the known issues in the kernel. It should run smoothly on all 6.x SuSE Linux distributions, but please note that 2.2.19 requires update packages for the lvm and/or the raidtools (formerly mdutils) package if lvm (logical volume manager) or the software raid facility of the Linux kernel are used. The lvm package is available for download from our ftp server ftp.suse.com, the raidtools package will follow soon. Regards, Roman Drahtmüller, SuSE Security . Digital hoax regarding hidden system vulnerabilities sparks unease among users about Ubuntu safety. Red Hat clarifies the situation promptly.. Linux Kernel, SuSE Security, Kernel Problems, Security Messaging. . LinuxSecurity.com Team

Calendar%202 Mar 29, 2001 User Avatar LinuxSecurity.com Team Hacks/Cracks
News Add Esm H340

Get the latest News and Insights

Get the latest Linux and open source security news straight to your inbox.

Community Poll

Should Linux servers automatically install security updates?

No answer selected. Please try again.
Please select either existing option or enter your own, however not both.
Please select minimum {0} answer(s).
Please select maximum {0} answer(s).
/main-polls/157-should-linux-servers-automatically-install-security-updates?task=poll.vote&format=json
157
radio
0
[{"id":506,"title":"Yes \u2014 critical security patches should install automatically.","votes":0,"type":"x","order":1,"pct":0,"resources":[]},{"id":507,"title":"No \u2014 every update should be tested before deployment.","votes":0,"type":"x","order":2,"pct":0,"resources":[]},{"id":508,"title":"Only critical vulnerabilities should auto-install.","votes":0,"type":"x","order":3,"pct":0,"resources":[]},{"id":509,"title":"I patch when Reddit starts panicking.","votes":1,"type":"x","order":4,"pct":100,"resources":[]}] ["#ff5b00","#4ac0f2","#b80028","#eef66c","#60bb22","#b96a9a","#62c2cc"] ["rgba(255,91,0,0.7)","rgba(74,192,242,0.7)","rgba(184,0,40,0.7)","rgba(238,246,108,0.7)","rgba(96,187,34,0.7)","rgba(185,106,154,0.7)","rgba(98,194,204,0.7)"] 350
bottom 200