This vulnerability concerns the network driver 'enetc' where Virtual Functions (VFs) do not support the HWTSTAMP_TX_ONESTEP_SYNC feature. The issue is identified in version 2.0 of the affected software. No further technical details, impact, or exploit information is provided.
The Amazon.ApplicationLoadBalancer.Identity.AspNetCore repo https://github.com/awslabs/aws-alb-identity-aspnetcore#validatetokensignature contains Middleware that can be used in conjunction with the Application Load Balancer (ALB) OpenId Connect integration and can be used in any ASP.NET https://dotnet.microsoft.com/apps/aspnet Core deployment scenario, including Fargate, EKS, ECS, EC2, and Lambda. In the JWT handling code, it performs signature validation but fails to validate the JWT issuer and signer identity. The signer omission, if combined with a scenario where the infrastructure owner allows internet traffic to the ALB targets (not a recommended configuration), can allow for JWT signing by an untrusted entity and an actor may be able to mimic valid OIDC-federated sessions to the ALB targets.
The repository/package has been deprecated, is end of life, and is no longer supported. As a security best practice, ensure that your ELB targets (e.g. EC2 Instances, Fargate Tasks etc.) do not have public IP addresses. Ensure any forked or derivative code validate that the signer attribute in the JWT match the ARN of the Application Load Balancer that the service is configured to use.
Multiple security vulnerabilities were identified in the Linux kernel used in Microsoft Azure cloud environments, affecting subsystems including the Azure Network Adapter (MANA) driver, watchdog drivers, Netfilter, and network traffic control. These flaws could potentially allow an attacker to compromise the system. Fixes have been released in updated kernel versions requiring a system reboot and recompilation of third-party kernel modules due to ABI changes.
Multiple security vulnerabilities were discovered in the Linux kernel specifically affecting the Microsoft Azure Network Adapter (MANA) driver and network traffic control subsystems. These flaws could potentially allow an attacker to compromise the system. A security update addressing these issues has been released for the linux-azure kernel packages, requiring a system reboot and recompilation of third-party kernel modules due to ABI changes.
CVE-2024-38081 is an elevation of privilege vulnerability affecting .NET 6.0 applications running on versions 6.0.0 and earlier. The flaw allows an unprivileged user to manipulate the Visual Studio installation on Windows, potentially leading to elevated privileges. Microsoft has released patches in version 6.0.1 to address this issue. No mitigating factors have been identified, and users are advised to update to the fixed versions or later. Self-contained applications targeting affected versions must be recompiled and redeployed to mitigate the vulnerability.
CVE-2024-21412 is a high-severity security feature bypass vulnerability in Microsoft Windows Internet Shortcut Files. It allows attackers to bypass security features, potentially leading to high confidentiality and integrity impacts. The vulnerability has been exploited in the wild and is known to be used in ransomware campaigns. No specific affected versions or patch information is provided in the available data.
CVE-2023-35311 is a high-severity Time-of-check Time-of-use (TOCTOU) race condition vulnerability in Microsoft 365 Apps for Enterprise, specifically affecting Microsoft Outlook. This flaw allows an attacker to bypass security features, potentially leading to full compromise of confidentiality, integrity, and availability of affected systems. The vulnerability requires no privileges but does require user interaction, and it can be exploited remotely over the network. Although no known exploits are currently in the wild, the high CVSS score of 8.8 indicates a significant risk. European organizations using Microsoft 365 Apps for Enterprise version 16.0.1 are at risk, especially those with large deployments of Outlook. Mitigation involves applying patches once available, restricting user interaction with untrusted content, and monitoring for suspicious activity. Countries with high Microsoft 365 adoption and strategic targets, such as Germany, France, the UK, and the Netherlands, are most likely to be affected.