Latest Linux Security News & Information

security advisorydenial of servicecritical

Ubuntu 16.04 & 18.04 Critical Kernel Advisory: Azure Systems Impacted

Canonical has fixed several recently identified critical Linux kernel vulnerabilities in July 2024. These vulnerabilities primarily affect Microsoft Azure cloud systems in Ubuntu 16.04 (Extended Security maintenance) and Ubuntu 1804 ESM. . If exploited, these vulnerabilities could result in downtime or unauthorized access to sensitive information, among other serious security risks for affected systems. In this article, I'll explore these Ubuntu vulnerabilities and their impact, how to identify which Ubuntu version you are running, and how to update your systems to protect against these flaws. I'll also discuss strategies for mitigating risk. Understanding These Vulnerabilities Canonical's updates address multiple vulnerabilities in the Linux kernel for Azure environments. Here are the critical vulnerabilities that were patched: CVE-2021-33631 (CVSS v3 Severity Score: 7.8 High): Description: The ext4 file system implementation was found to validate the data state on miswrite operations. Impact: An attacker could exploit this vulnerability by crafting a malicious ext4 file system image. Upon mounting, it could crash the system, resulting in a denial of service. CVE-2023-6270 (CVSS v3 Severity Score: 7.0 High): Description: A race condition in the ATA over Ethernet (AoE) driver was discovered, leading to a use-after-free vulnerability. Impact: This could be exploited to cause a denial of service or execute arbitrary code. CVE-2024-2201 : Description: Researchers found insufficiencies in mitigations for the initial Branch History Injection vulnerability ( CVE-2022-0001 ) in Intel processors. Impact: This could allow local attackers to expose sensitive information. CVE-2024-23307 (CVSS v3 Severity Score: 7.8 High): Description: A race condition in the software RAID driver leads to an integer overflow vulnerability. Impact: Privileged attackers could use this to cause a denial of service. CVE-2024-24861 (CVSS v3 Severity Score: 6.3 Medium): Description: A race condition in the Xceive XC4000 silicon tuner device driver led to an integer overflow vulnerability. Impact: This could potentially allow an attacker to cause a denial of service. Other patched vulnerabilities affect several subsystems, including the block layer subsystem, hardware random number generator core, GPU drivers, AFS file system, memory management, and Netfilter. Which Ubuntu Versions Are Impacted & What Is the Impact on Affected Systems? These vulnerabilities primarily impact Ubuntu 16.04 ESM and Ubuntu 18.04 ESM. Admins running these versions should immediately patch their systems to mitigate the risks associated with the identified vulnerabilities. The potential consequences of these vulnerabilities are severe: Denial of service (DoS) due to system crashes or resource exhaustion. Exposure of sensitive information through the exploitation of information disclosure vulnerabilities. Execution of arbitrary code could compromise the integrity and security of the system. How Can I Check My Ubuntu Version? System administrators can check their Ubuntu version to determine if they are at risk by executing: lsb_release -a Alternatively, they can use: cat /etc/lsb-release Both commands will provide detailed information about the Ubuntu distribution and release. How Can I Update My System? Follow the steps outlined below to update your Ubuntu system and apply the necessary patches. Update Package List: sudo apt update Upgrade Installed Packages: sudo apt upgrade Reboot System: sudo reboot Consistent updates ensure your system maintains optimal security by applying the latest patches. EOL Ubuntu Versions: Risks and Mitigation Strategies The risks of using End-of Life (EOL) Ubuntu versions such as Ubuntu 16.04 or 18.04, without Extended Security Maintenance are significant. These systems are not updated with security patches, makingthem vulnerable to known exploits. Practical mitigation strategies admins should implement to reduce risk include: Extended Security Maintenance (ESM): ESM is a type of security maintenance that can help reduce the risk of running EOL versions of Ubunto by providing extended support and security protection. Subscribe to Ubuntu Pro: This will provide ESM support and extend security updates past the five-year standard period. Extended Lifecycle Support: This cost-effective option for ESM offers security patches for Ubuntu 16.04 or 18.04 for five additional years after the end of life. Live Kernel Patching: Live patching solutions allow for live kernel patching. Security updates can be applied without requiring a restart. Monitor CVE Trackers Regularly: CVE trackers are a great way to stay current on the latest Linux vulnerabilities and patches. These best practices can help Linux administrators mitigate risk and maintain a robust security posture, even when Ubuntu versions are no longer supported. Our Final Thoughts on Mitigating These Threats Addressing these Linux kernel flaws in Ubuntu is essential, especially within Microsoft Azure Cloud environments. Administrators can protect their infrastructure from potential threats by taking proactive measures such as using ELS and ESM, patching the kernel, and subscribing to LinuxSecurity newsletters to stay informed of the latest threats to their systems. . Compromised weaknesses in essential operating systems may result in service interruptions or illicit retrieval of confidential data.. Linux Kernel Update, Ubuntu Security, Azure Vulnerabilities, Kernel Patching. . Brittany Day

Jul 31, 2024 •

Brittany Day Security Vulnerabilities

security advisorydebianDoS

Ubuntu & Debian: Security Updates for Thunderbird and Firefox

Recent security updates for Ubuntu and Debian have been released to address vulnerabilities in Thunderbird, the popular open-source mail and newsgroup client, and Firefox, the widely used open-source web browser. The identified vulnerabilities could result in denial of service attacks, unauthorized access to sensitive information, and the execution of arbitrary code. . To help you protect your critical data and maintain system security and availability, let's examine these bugs, their impact, and the importance of applying the patches released by Thunderbird and Firefox to mitigate risk. What Bugs Have Been Found & Fixed in Thunderbird & Firefox? Vulnerabilities discovered and mitigated in Thunderbird and Firefox include the potential exploitation of users accessing maliciously crafted websites, which could lead to cross-site tracing, denial of service attacks, and unauthorized access to sensitive data ( CVE-2024-2609 , CVE-2024-3852 , CVE-2024-3864 ). Memory management flaws and the lack of limits in Thunderbird's handling of HTTP/2 CONTINUATION frames, which could cause out-of-bounds read exploits and denial of service attacks, have also been identified and fixed. ( CVE-2024-3854 , CVE-2024-3857 , CVE-2024-3859 , CVE-2024-3861 ). To address these issues, the Ubuntu security team has released patches for Ubuntu 23.10, Ubuntu 22.04 LTS, and Ubuntu 20.04 LTS, and the Debian security team has released patches for Debian 11 and Debian 12. What Are the Security Implications of These Flaws? The identified vulnerabilities in Thunderbird and Firefox have significant implications for the security of Ubuntu and Debian systems. Admins must update promptly to protect against potential threats posed by these bugs, including data theft and service disruption. However, the question arises: Were Ubuntu and Debian systems actively attacked before these vulnerabilities were patched? If so, what data could have been compromised? This situation raises concerns about proactive securitymeasures and the importance of continuously monitoring and updating systems. As opposed to applying patches manually as they are released, live kernel patching without system reboots can be beneficial in protecting against security bugs; however, it is important to consider its long-term consequences. By automating the patching process, there is a potential risk of blindly deploying security updates without proper testing, which could inadvertently introduce new vulnerabilities or system instabilities. System administrators must balance automation and thorough testing to ensure the integrity and stability of their systems. The impact of these vulnerabilities is significant for members of the Linux community. This discovery is another wake-up call to prioritize security updates and patch management. These vulnerabilities highlight the importance of user awareness and caution when accessing websites and handling email attachments. Admins can protect their systems and data by proactively addressing these issues and staying informed about emerging threats . Our Final Thoughts on These Recent Thunderbird & Firefox Bugs We hope to have shed light on recent Thunderbird and Firefox vulnerabilities and Ubuntu and Debian's actions to address them. This discovery underscores the need for Linux admins to remain proactive in their approach to system security. The implications of these vulnerabilities highlight the importance of continuous monitoring, regular patching, and user education. Security practitioners can effectively mitigate risks and protect their systems in the ever-evolving cybersecurity landscape by staying informed and taking the necessary precautions discussed in this article. . Recent Thunderbird and Firefox updates fix critical bugs to bolster security, patching issues like email handling flaws and memory safety, improving overall user protection. Thunderbird Security, Firefox Patching, Ubuntu Security, Debian Vulnerabilities, Information Disclosure. . Brittany Day

Jun 27, 2024 •

Brittany Day Security Vulnerabilities

Banner 2 1028x280 1708121730 1 1771599631

security advisorymedium severitykernel flaw

Linux Kernel: CVE-2023-6040 Medium Risk: Information Access Threat

Imagine your most sensitive and critical information being made accessible to threat actors without your permission or knowledge. This is exactly what a new information disclosure flaw discovered in the Linux kernel up to 5.17 could result in. As a Linux admin, staying up-to-date on vulnerabilities like this one is crucial to keeping your critical systems and confidential data secure. To help you understand and protect against this kernel bug, we'll explore its implications for security practitioners and the long-term consequences it may bring. We'll also explain how to secure your systems against this dangerous kernel flaw. . What Is This Vulnerability & How Does It Impact the Security of My Linux Systems? A security flaw in the Linux kernel, as reported by the Federal Office for Security in Information Technology (BSI). The vulnerability affects the Linux operating system, including the open-source Linux Kernel product. The severity of this flaw is assessed as "medium" based on the Common Vulnerability Scoring System (CVSS), with a base score of 7.8. The vulnerability, identified as CVE-2023-6040 , allows a local attacker to exploit the Linux kernel and gain unauthorized access to sensitive information. Next Steps: How Can I Mitigate This Flaw? To mitigate this vulnerability, it is critical to keep affected systems up to date and install security updates promptly . The implications of this vulnerability, particularly in the context of critical infrastructure and Internet-connected systems, are severe. Security practitioners must stay informed about vulnerabilities, their impact, and effective mitigation strategies by subscribing to industry newsletters like our Linux Advisory Watch . Stay safe out there, fellow Linux users! Continue Learning About Improving Your Security Posture Keep learning about improving your Linux security posture by exploring the following resources: Read our article on How To Secure the Linux Kernel. Explore our article on Top Tips forSecuring Your Linux System. . A serious kernel vulnerability, CVE-2023-XXXX, has emerged, raising alarms about unauthorized access, data leaks, and system control. Swift action is required.. Linux Kernel Security Flaw, Information Disclosure Mitigation, Security Practices. . Brittany Day

Feb 11, 2024 •

Brittany Day Security Vulnerabilities

security advisorypatch managementinformation disclosure

Ansible Security Alert: Critical Data Leak Vulnerability Under Attack

Ansible is a widely used open-source configuration management and automation tool popular among Linux system administrators. A vulnerability recently disclosed in Ansible could allow attackers to access sensitive information on servers Ansible manages. This is a serious issue that Linux admins and IT teams need to take action on. . Though the vulnerability itself is not a critical remote code execution flaw, the implications are still far-reaching. Information disclosure bugs can often provide attackers the foothold they need to gain further access. Additionally, the popularity of Ansible means the number of servers at risk is quite high. This article will analyze the technical details of the vulnerability, discuss the potential consequences, and review mitigation strategies Linux administrators can take to protect servers. The disclosure highlights important lessons about supply chain security and keeping automation tools up-to-date. While Ansible has released a patch, companies using older versions may still be at risk. Summary of the Vulnerability Ansible, the popular open-source automation framework and orchestration engine, has discovered a serious vulnerability. The vulnerability allows an attacker to gain access to sensitive information through improper handling of variables. This issue affects Ansible users on all supported platforms using Ansible version 2.7 and newer. It has been classified as a high-severity vulnerability, with a CVSS score of 8.1 out of 10. The vulnerability arises because Ansible allows certain ‘unsafe’ variables to bleed across variable boundaries in YAML dictionaries and overwrites. Through clever manipulation, attackers can access sensitive data like passwords, tokens, and keys contained in group or host variables. Technical Details The vulnerability exists in certain Ansible Tower and Red Hat Ansible Automation Platform versions. Specifically, it allows privilege escalation via internal API misuse. The issue was tracked as Bugzilla CVE-2023-21769 . This API misuse vulnerability arises because Ansible fails to validate tower OAuth2 tokens properly for internal requests. As a result, an authenticated user with only read permissions could potentially obtain admin access and take over the Ansible environment. The vulnerability is present in the following versions of Ansible: Ansible Tower versions 3.8.0 and later prior to 3.8.5 Ansible Tower versions 4.0.0 to 4.1.0 Red Hat Ansible Automation Platform 2.3.0 to 2.3.1 So, in summary, this privilege escalation flaw allows lower privileged users to gain admin access by exploiting the internal API that lacks proper validation. Upgrading to Ansible versions 3.8.5, 4.2.0, or 2.3.2 will remediate the vulnerability. What Are the Implications for Linux Admins? This Ansible information disclosure vulnerability poses significant risks for Linux administrators relying on Ansible for automation and configuration management. The vulnerability allows attackers to access sensitive files and data on servers Ansible manages. This could expose credentials, passwords, private keys, and other confidential information. The biggest implication is that servers thought to be properly secured by Ansible may actually be misconfigured in ways that leave them vulnerable. If attackers find and exploit these misconfigurations, it can lead to server breaches, data theft, ransomware attacks , and more. For organizations using Ansible to automate and standardize server configurations at scale, this vulnerability highlights the inherent risks of any centralized configuration tool. A flaw in Ansible means all servers under its management are potentially impacted. Successful attacks via this vector could quickly compromise an entire fleet. Mitigating this issue will require rapid patching and an audit of existing Ansible practices to identify any misconfigurations. Organizations should also take time to review the principle of least privilege and consider limiting the breadth of access andcapabilities granted to Ansible across servers. Monitoring for suspicious activity reflecting exploitation of this vulnerability will also be critical. The Ansible disclosure offers a reminder about the diligence required to automate infrastructure at scale safely. Linux administrators should view this as an opportunity to lock down and enhance the security of their Ansible deployment and managed hosts. Careful configuration and restrictive privileges can help minimize risks when the next Ansible vulnerability emerges. Mitigation Strategies Linux admins can take several steps to detect and mitigate this Ansible vulnerability. Update Ansible - Make sure you have the latest Ansible version installed. Versions 2.9.27, 2.10.11, and 3.0.0 address this vulnerability with a fix. Running ansible --version will show your current version. Use SELinux - Enabling SELinux adds an extra layer of security that can help limit the impact of vulnerabilities. Set SELinux to enforcing mode on your Ansible controller and target hosts. Monitor Ansible Files - Closely watch Ansible files and directories, like /etc/ansible/ , for any unauthorized changes, to detect signs of exploitation. Tools like Tripwire or AIDE can automatically monitor and alert on file changes. Restrict Access - Limit access to your Ansible controller to only authorized users and restrict write permissions. Disable any unused Ansible plugins or modules to reduce the attack surface. Patch Underlying OS - Keep the operating systems on your Ansible controllers and managed hosts fully patched as additional hardening against potential threats. Rotate Credentials - Change any credentials used by Ansible on a regular basis per security best practices. This can limit access if any credentials are compromised. Check Playbook Outputs - Review Ansible playbook logs and standard output for any unexpected changes that could indicate foul play. By taking proactive stepsto secure Ansible and managed hosts, admins can reduce the chances of this vulnerability being successfully exploited in their environments. Carefully controlling Ansible access is key. Vendor Response Red Hat quickly responded to the vulnerability disclosure and released patched versions of Ansible. They acknowledged the vulnerability and worked diligently to mitigate the risks for their users. Red Hat released patched versions 2.9.27, 2.10.8, 4.10.0, 5.0.2 and 5.1.0 of Ansible to address the vulnerability. They recommended users upgrade to these versions as soon as possible to protect against the information disclosure risks. The vulnerability was addressed by restricting the Ansible JSON callback plugin to only displaying variables marked "safe." Sensitive values like passwords and keys that are not marked as safe will no longer be disclosed in Ansible output. Red Hat also updated the product documentation to discuss properly handling sensitive variables in Ansible playbooks. Users are advised to designate sensitive vars as "no_log" to avoid exposure. Proper categorization of vars will prevent accidental disclosure moving forward. Overall, Red Hat took the vulnerability disclosure seriously, quickly patched affected versions, and offered useful guidance to customers. Their proactive response mitigated risks for Ansible users and demonstrated their commitment to security. Long Term Consequences The disclosure of this Ansible vulnerability demonstrates the risks associated with supply chain attacks on open-source software. Even trusted, widely-used software like Ansible is vulnerable to potential exploits. Attackers are constantly probing popular open-source projects for weaknesses. Successful attacks allow adversaries to compromise thousands of downstream systems at once. This vulnerability serves as a wake-up call to the broader risks of supply chain attacks. Open source maintainers must remain vigilant about proactively auditing their codebases for security issues. Downstreamconsumers of open-source code must promptly patch vulnerabilities and diversify suppliers to mitigate risks. Multifactor authentication, principle of least privilege, network segmentation, and other security best practices provide additional protection. The cyber risk landscape is continually evolving. Widely used software and open-source projects are prime targets. This incident provides an opportunity to have broader conversations about software supply chain security. Organizations relying on open-source code must take steps to minimize risks associated with potential exploits. With collaboration across the industry, the security community can work to strengthen open-source ecosystems against supply chain threats. Key Takeaways for Linux Admins While this Ansible vulnerability is worrying, there are some important lessons Linux admins can take away: Stay vigilant about patching and updating software. When a patch is released, prioritize testing it and rolling it out. Software vulnerabilities are common, so staying on top of updates is critical. Conduct regular audits and scans. Don't just rely on vendor notifications. Proactively scan for vulnerabilities and misconfigurations in your environment using tools like Lynis or OpenSCAP. Enforce least privilege principles. Restrict access to sensitive information and resources. This lessens the impact if an account is compromised. Monitor closely for signs of intrusion. Watch for anomalies that could indicate malicious activity or compromised accounts. Have an incident response plan ready. Know how to isolate affected systems, reset credentials, collect forensic data, etc, if a breach occurs. Defense in depth. Use multiple layers of security rather than just one. For example, firewalls, intrusion prevention systems, strict permissions, etc. Learn from each incident. Figure out how the attack happened and what allowed it to succeed. Then strengthen those weaknesses. Regularly applying these practices can help Linux admins secure their systems and minimize the risk from vulnerabilities like this Ansible issue. Software will always have flaws, but the impact can be reduced with vigilance and preparedness. Looking Ahead The Ansible vulnerability demonstrates the importance of staying on top of security updates for all software used in an organization's IT infrastructure. Even widely used, trusted software like Ansible is susceptible to vulnerabilities that can potentially expose sensitive data. Looking ahead, Ansible must thoroughly review its codebase to identify and fix any additional vulnerabilities that could compromise its users. Organizations relying on Ansible must promptly install security patches as they become available to ensure their systems remain secure. This incident highlights the growing threat of software supply chain attacks. As enterprise IT ecosystems become more complex, with many interconnected applications and services, a vulnerability in any one component can create risk across the entire system. Organizations will need to take a holistic approach to IT security going forward, reviewing the security of all internal software rather than just isolated systems. Advanced persistent threat actors, including nation-state hacking groups, are apt to seize on vulnerabilities like this Ansible issue to gain access to high-value targets. The infosec community must continue working diligently to identify and rectify any weaknesses before they can be exploited. This may require software vendors to adopt new development practices such as "secure by design" methodologies. Looking further, automation tools like Ansible will play an increasingly central role in IT infrastructure and security workflows. It is imperative that they meet the highest standards for software assurance. Any weaknesses in these core solutions place the entire integrity of an organization's technology at risk. The Ansible team must take the hard lessons from this experienceand ensure they develop their products securely from the start. Our Final Thoughts on This Vulnerability The Ansible remote code execution vulnerability demonstrates the importance of staying vigilant about patching and updating systems. Even widely used, trusted software like Ansible can contain dangerous flaws. However, the quick response by Red Hat to issue a patch limited the damage from this bug. The implications of this vulnerability are a reminder that organizations must have an incident response plan ready for vulnerabilities in any software they rely on, even trusted open-source tools. Auditing different accounts' roles, software, and privileges are critical to limiting attack vectors. Multi-factor authentication provides another layer of protection. While this vulnerability was serious, it was averted due to the inherent openness and transparency of the open-source community. Having many eyes reviewing code enables bugs to be caught faster. This collaboration between Red Hat, security researchers, and the Ansible community protected users. Staying up-to-date on patches , having an incident response plan ready, and using defense-in-depth techniques will help secure systems from attacks exploiting vulnerabilities . The Ansible community's handling of this bug exemplifies the resilience and responsiveness of open-source security done right. . This Ansible flaw highlights threats for Linux system administrators, emphasizing rapid updates to prevent unauthorized access and system compromise.. Ansible Vulnerability, Linux Server Security, Automation Risks, Security Patch Management. . Brittany Day

Jan 01, 2024 •

Brittany Day Security Vulnerabilities

security advisoryhigh severitydebian

Debian DSA-5526-1 High: Chromium DoS And Info Disclosure Risks

A severe, remotely exploitable Type Confusion vulnerability has been found in Chromium ( CVE-2023-5346 ). Due to its significant threat to the confidentiality, integrity, and availability of impacted systems, this bug has received a National Vulnerability Database base score of 8.8 out of 10 (“High” severity). . Several other important security vulnerabilities have also recently been found in Chromium, including inappropriate implementation in Custom Tabs, Prompts, Input, Custom Mobile Tabs, Autofill, Intents, Picture in Picture, and Interstitials, and insufficient policy enforcement in Downloads. These issues could result in the execution of arbitrary code, denial of service, or information disclosure. Essential Chromium security updates have been released to fix these dangerous bugs. As these flaws severely threaten the confidentiality, integrity, and availability of impacted systems, we urge all affected users to apply the updates released by Debian , Fedora , Gentoo , Mageia , and openSUSE immediately to protect their critical systems and sensitive data against attacks leading to downtime and compromise. To stay on top of essential updates released by the open-source programs and applications you use, register as a LinuxSecurity user , subscribe to our Linux Advisory Watch newsletter, and customize your advisories for your distro(s). This will enable you to stay up-to-date on the latest, most significant issues impacting the security of your systems. Follow @LS_Advisories on Twitter for real-time updates on advisories for your distro(s) . . Critical flaws discovered in Firefox present threats; patches required to safeguard machines from intrusions.. chromium vulnerabilities, DoS attacks, security fixes, information disclosure. . Brittany Day

Oct 25, 2023 •

Brittany Day Security Vulnerabilities

security advisorycriticalremote code execution

Debian, Ubuntu, openSUSE: Critical Exim RCE and Info Disclosure Issues

Three critical security vulnerabilities have been discovered in the widely-used Exim open-source email transfer agent, including a NTLM challenge out-of-bounds read information disclosure bug ( CVE-2023-42114 ), a AUTH out-of-bounds write remote code execution (RCE) vulnerability ( CVE-2023-42115 ), and a SMTP challenge stack-based buffer overflow RCE flaw ( CVE-2023-42116 ). . These issues could result in malware execution, system compromise, and information disclosure on impacted systems. An essential update for Exim has been released to fix these critical issues. We strongly recommend that all affected users apply the updates released by Debian , Debian LTS , openSUSE , and Ubuntu now to protect their critical systems and sensitive data against attacks leading to compromise. To stay on top of essential updates released by the open-source programs and applications you use, register as a LinuxSecurity user , subscribe to our Linux Advisory Watch newsletter, and customize your advisories for your distro(s). This will enable you to stay up-to-date on the latest, most significant issues impacting the security of your systems. Follow @LS_Advisories on Twitter for real-time updates on advisories for your distro(s) . . Essential patches for Exim address RCE and information leak vulnerabilities, safeguarding systems from malicious code execution and potential breaches.. Exim Security Updates, Remote Code Execution, Information Disclosure, Open Source Email Vulnerabilities. . Brittany Day

Oct 08, 2023 •

Brittany Day Security Vulnerabilities

20.Lock AbstractDigital Circular Esm H240

security advisorycode executioncritical flaw

Ubuntu Security Advisory: Node.js Vulnerabilities Resolved for Exploitation

Several significant security issues were fixed in Node.js, including two critical vulnerabilities that have received a National Vulnerability Database base score of 9.8 out of 10. CVE-2019-15605 is an HTTP request smuggling bug in Node.js 10, 12, and 13 that causes malicious payload delivery when transfer-encoding is malformed, and CVE-2019-15606 is an authorization bypass issue in Nodejs 10, 12, and 13. . A remote attacker could possibly use these issues to obtain sensitive information or execute arbitrary code. Essential Node.js security updates have been released to fix these severe flaws. We urge all impacted users to apply the updates released by Ubuntu immediately to protect their critical systems and sensitive data against attacks leading to compromise. To stay on top of essential updates released by the open-source programs and applications you use, register as a LinuxSecurity user , subscribe to our Linux Advisory Watch newsletter, and customize your advisories for your distro(s). This will enable you to stay up-to-date on the latest, most significant issues impacting the security of your systems. Follow @LS_Advisories on Twitter for real-time updates on advisories for your distro(s) . . Crucial patches rolled out for Node.js addressing severe vulnerabilities. Safeguard your infrastructure and information from threats immediately.. Node.js Critical Issues, Ubuntu Security Fixes, Code Execution Vulnerabilities. . Brittany Day

Oct 05, 2023 •

Brittany Day Security Vulnerabilities

security advisoryupdatedebian

Debian: DSA-5472-1 Critical: JOSE for C/C++ DoS and Info Exposure

It was discovered that JOSE for C/C++ AES GCM decryption routine incorrectly uses the Tag length from the actual Authentication Tag provided in the JWE ( CVE-2023-37464 ). This severe vulnerability is simple to exploit and threatens the integrity of impacted systems. . An attacker could use this to cause a denial of service (system crash) or to expose sensitive information. Updates for JOSE for C/C++ that mitigate this dangerous bug have been released. We strongly recommend that all impacted users apply the updates released by Debian , Debian LTS , Oracle , RedHat , Rocky Linux , and Ubuntu as soon as possible to safeguard their sensitive data and protect against potential security issues. To stay on top of essential updates released by the open-source programs and applications you use, register as a LinuxSecurity user , subscribe to our Linux Advisory Watch newsletter, and customize your advisories for your distro(s). This will enable you to stay up-to-date on the latest, most significant issues impacting the security of your systems. Follow @LS_Advisories on Twitter for real-time updates on advisories for your distro(s) . . Malicious users may exploit the JOSE vulnerability in C/C++ apps, risking denial of service and confidential data leaks. It's essential to apply updates promptly. DoS Cybersecurity, JOSE C/C++ Update, Info Disclosure Alert, System Integrity Risk. . Brittany Day

Sep 07, 2023 •

Brittany Day Security Vulnerabilities

Community Poll

More Polls

Should Linux servers automatically install security updates?

Yes — critical security patches should install automatically.
No — every update should be tested before deployment.
Only critical vulnerabilities should auto-install.
I patch when Reddit starts panicking.

Stay Ahead With Linux Security News

Refine news

Get the latest News and Insights

Community Poll

Should Linux servers automatically install security updates?

Trending News

Misuse of Cron Jobs for Long-Term Access in Linux Environments

Risks of GitHub Repo Breach on Linux Supply Chain Security

After Years of Supply Chain Attacks, npm Is Finally Closing the Door on Auto-Scripts

FFmpeg PixelSmash Vulnerability Exposes Linux Media Servers to Remote Code Execution Risk

Explore Latest Linux Security news

Ubuntu 16.04 & 18.04 Critical Kernel Advisory: Azure Systems Impacted

Ubuntu & Debian: Security Updates for Thunderbird and Firefox

Linux Kernel: CVE-2023-6040 Medium Risk: Information Access Threat

Ansible Security Alert: Critical Data Leak Vulnerability Under Attack

Debian DSA-5526-1 High: Chromium DoS And Info Disclosure Risks

Debian, Ubuntu, openSUSE: Critical Exim RCE and Info Disclosure Issues

Ubuntu Security Advisory: Node.js Vulnerabilities Resolved for Exploitation

Debian: DSA-5472-1 Critical: JOSE for C/C++ DoS and Info Exposure

Get the latest News and Insights

Community Poll

Should Linux servers automatically install security updates?

Trending News

Misuse of Cron Jobs for Long-Term Access in Linux Environments

Risks of GitHub Repo Breach on Linux Supply Chain Security

After Years of Supply Chain Attacks, npm Is Finally Closing the Door on Auto-Scripts

FFmpeg PixelSmash Vulnerability Exposes Linux Media Servers to Remote Code Execution Risk

Powered By

Linux Security - Your source for Top Linux News, Advisories, HOWTOs and Feature Releases

QUICK LINKS

subscribe to newsletters!

Stay Ahead With Linux Security News

Refine news

Topics

Category

Authors

Published Date

Get the latest News and Insights

Community Poll

Should Linux servers automatically install security updates?

Trending News

Explore Latest Linux Security news

Get the latest News and Insights

Community Poll

Should Linux servers automatically install security updates?

Trending News

Search Topics

Powered By

Linux Security - Your source for Top Linux News, Advisories, HOWTOs and Feature Releases

QUICK LINKS

subscribe to newsletters!