Submitty before v22.06.00 is vulnerable to Incorrect Access Control. An attacker can delete any post in the forum by modifying request parameter.

**Introduction**

Submitty before v22.06.00 is vulnerable to Incorrect Access Control. An attacker can delete any post in the forum by modifying request parameter.

**CVSS Score****Score**

*   **CVSS v3.1:** 5.4
*   **Vector:** AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

**Impact**

*   **Confidentiality:** This vulnerability has no direct impact on confidentiality.
*   **Integrity:** The attcker can delete any post in the forum.
*   **Availability:** The attcker can delete any post in the forum.

**Likelihood**

*   **Skill Required:** This attack requires basic knowledge of HTTP request.
*   **Conditions:** The attcker must be able to create a post and delete its own post.
*   **Discoverability:** This vulnerability is easy to find.

**Problem Details****Overview**

This report identifies an Incorrect Access Control vulnerability within Submitty, specifically within the post deletion functionality of the forum component. The vulnerability arises due to insufficient parameter validation. An attacker can exploit this flaw by modifying the request body.

The core issue lies in the inadequate validation of user privileges when a request is made to delete a forum post. In a typical scenario, a user should only be able to delete their own posts or, in the case of an administrator, any post. However, due to the lack of proper access control checks within the system, an unauthorized user can manipulate the HTTP request sent to the server. By altering parameters such as the post identifier within the request body, an attacker can bypass the standard permission model.

The most alarming consequence of this vulnerability is the ability of an attacker to delete any post on the forum, regardless of their permission level. This can lead to several significant issues:

1.  Important educational discussions or announcements can be removed, leading to a loss of valuable information for users.
2.  The vulnerability can be exploited to disrupt the normal operation of the forum, causing confusion and mistrust among users.

**Affected Area**

The forum component of Submitty.

**Root Cause**

The service used following code to check if an user can modify a post.

    $post_id = $_POST["post_id"] ?? $_POST["edit_post_id"];
    $post = $this->core->getQueries()->getPost($post_id);
    if (!$this->core->getAccess()->canI("forum.modify_post", ['post_author' => $post['author_user_id']])) {
        return $this->core->getOutput()->renderJsonFail('You do not have permissions to do that.');
    }
    

However, the service uses another parameter from POST request as delete parameter. The parameter thread_id is not validated by the previous check.

    $thread_id = $_POST["thread_id"];
    $thread_title = $this->core->getQueries()->getThread($thread_id)['title'];
    if ($this->core->getQueries()->setDeletePostStatus($post_id, $thread_id, 1)) {
        $type = "thread";
    }
    else {
        $type = "post";
    }
    

Therefore, an attacker can modify the request parameter in the post body and delete the post in another thread.

**Steps to Reproduce**

Following steps are required to reproduce the issue. An HTTP traffic interceptor is also required, such as Burp Suite.

1.  Create two accounts for Submitty.
2.  Access to the forum component of Submitty (any version before v22.06.00) with account A.
3.  Create a new post in a nre thread to the forum.
4.  Log in with account B, create another post in a new thread.
5.  Enable interceptor, click delete button to send a delete request.
6.  Modify the request body, change thread_id to the thread that created by account A.
7.  Foward the modified request, notice that the post created by account A has been deleted.

Verify all parameters at server side. Be aware of parameter mismatches.

**References**

The vulnerability has been fixed as a part of pull request 8032.

_Report prepared by: Fu Chai_ _Date: 10/31/2023_

CVE-2023-43194: CVE-2023-43194: Submitty Incorrect Access Control Vulnerability Report

Dromara Lamp-Cloud before v3.8.1 was discovered to use a hardcoded cryptographic key when creating and verifying a Json Web Token. This vulnerability allows attackers to authenticate to the application via a crafted JWT token.

*   *   Actions
        
        Automate any workflow
        
    *   Packages
        
        Host and manage packages
        
    *   Security
        
        Find and fix vulnerabilities
        
    *   Codespaces
        
        Instant dev environments
        
    *   Copilot
        
        Write better code with AI
        
    *   Code review
        
        Manage code changes
        
    *   Issues
        
        Plan and track work
        
    *   Discussions
        
        Collaborate outside of code
        
    

*   *   GitHub Sponsors
        
        Fund open source developers
        
    
    *   The ReadME Project
        
        GitHub community articles
        
    
*   Pricing

**Search code, repositories, users, issues, pull requests...**

**Provide feedback**

**Saved searches****Use saved searches to filter your results more quickly**

Sign up

CVE-2023-31579: JWTissues/lamp issue.md at main · xubowenW/JWTissues

The ongoing struggle between YouTube and ad blockers is turning ugly. Users are left with the choice between paying for Premium or watching ads.

The ongoing struggle between YouTube and ad blockers is turning users into the victims.

YouTube has gone all out in its fight against the use of add-ons, extensions and programs that prevent it from serving ads to viewers around the world. It started out as just a small experiment, but it looks like the company has opened the floodgates for most users now.

A spokesperson for YouTube told Engadget:

> “We’ve launched a global effort to urge viewers with ad blockers enabled to allow ads on YouTube or try YouTube Premium for an ad free experience. Ads support a diverse ecosystem of creators globally and allow billions to access their favorite content on YouTube.”

On a support page, YouTube says that if you use ad blockers, you’ll be asked to allow ads on YouTube or sign up for YouTube Premium. If you continue to use ad blockers, YouTube may block you from watching videos at all.

Now, users are flocking to places like Reddit to complain about YouTube’s hardened stance against ad blockers.

Privacy expert Alexander Hanff has filed a complaint with the Irish DPC (Data Protection Commission) about YouTube’s ad block blocking. Hanff says that YouTube needs permission to detect adblockers because by doing so it’s looking at something that is on the visitor’s system. In his complaint, Hanff demands that YouTube stop its anti-ad blocking policy, saying some experts call it “illegal”. 

The DPC is the Irish supervisory authority for the General Data Protection Regulation (GDPR), so any outcome of this complaint might only cause changes for EU residents. We have reported about plans to introduce ad free services by Meta, TikTok, and YouTube as a way to circumvent EU rules that require platforms to get users’ consent in order to show them targeted ads.

**Watch out for fakes**

With all this going on, users should be extra careful about downloading new ad blockers that claim to circumvent YouTube’s blocking. Oftentimes we’ll see miscreants trying to rip off users by launching non-functional products and promoting potentially unwanted programs (PUPs).

There are many examples of fake ad blocker extensions in the Chrome Web Store that we would advise against installing.

**Browser Guard**

As you may know, Malwarebytes Browser Guard has a built-in ad blocker. If you still need to access an important site but you’re being asked to disable your ad blocker, you can do this by clicking on the blue M logo in your browser taskbar and set the Ad/Trackers to be disabled for that site.

_Browser Guard blocks two entities on www.youtube.com_

**We don’t just report on threats—we remove them**

Cybersecurity risks should never spread beyond a headline. Keep threats off your devices by downloading Malwarebytes today.

 YouTube launches &#8220;global effort&#8221; to block ad blockers 

It’s very convenient to store your passwords in your browser. But is it a good idea?

At Malwarebytes we’ve been telling people for years not to reuse passwords, and that a password manager is a secure way of remembering all the passwords you need for your online accounts.

But we also know that a password manager can be overwhelming, especially when you’re just getting started. Once you’ve stored your tens or even hundreds of passwords, a password manager is relatively convenient to use and keep updated. But you have to get to that stage first and not everyone is at the same level of computer literacy.

So, you may have wondered if there’s another way. No doubt, you’ll have seen the pop ups in your browser asking if you’d like it to save your password for next time. In fact, many browsers refer to that as their password manager.

It’s very convenient, since your browser is usually the application that needs the password, but is it a good idea?

As usual, there are pros and cons.

**Encryption.** With a browser password manager, someone with access to your browser could see your passwords in clear text, although Windows can be set to ask for authentication (the same you use at startup of your device).

_The “Show password’ option_

To see the passwords in an actual password manager, an attacker would need to know the password for the password manager or the recovery phrase, which are usually a lot harder to find out than the Windows authentication (if set).

A word of warning here, some password managers have the option to keep you logged in for hours or even days. If there is any chance that anyone may acquire physical access, such settings defeat the added security of a password manager, since the attacker could open the password manager and look at your passwords in more or less the same way as they could in your browser.

**Lookalike phishing sites.** Both a standalone password manager and the one in your browser will protect you here. They will not fill out your password if the domain doesn’t match the one you saved the password for, which could indicate a phishing site. This can be very useful and this is where it beats writing down the password on a piece of paper or storing it in a text file. I should add that the domains that are worth setting up a fake site for are usually the ones that we would advise you add multi-factor-authentication (MFA) to.

**Syncing.** If you’ve stored your passwords in the browser and have chosen to synchronize your browser between devices, your passwords will port over as well. This is obviously very convenient, but it’s also a potential danger if someone gets access to one of your devices. A true password manager doesn’t rely on syncing between the same browser on different devices. Once you have the password manager installed on a device, you have it handy to use in any browser or other apps.

**Offline.** Many password managers cache your passwords locally, so you still have access when your connection is broken. Browser password storage doesn’t allow for this.

**Business devices.** It’s hard for the IT department to keep track of which user has which passwords saved in their browser. Password managers for businesses give them a better insight and make it easier to revoke passwords when needed.

**Password stealers.** There are types of malware that are capable of harvesting passwords from your device. They know exactly where browsers store their passwords and the encryption key, so they can steal and send the credentials to the attacker. Password managers are separate to the browser so they’re not at risk in the same way.

**Data breaches.** Several password managers will warn you if they find that your credentials are involved in a data breach, so you can change them. Browser storage doesn’t do this.

**Complex passwords.** Humans are bad at creating and remembering complex passwords. A password manager and some browsers can help you create a password that meets the required complexity and store it so you don’t have to remember it.

**Side channel attacks.** As we saw with a recent bug in Safari, attackers can use the autofill feature in a browser to harvest login credentials for a site. This only works if you have autofill enabled, so to make things a bit safer you can tell your browser to wait for your OK before it fills out the data. Here’s how…

**How to disabled autofill**

*   **Brave:** Settings > Autofill and passwords > Password Manager > Settings. Toggle off “Sign in automatically”

*   **Chrome:** Settings > Autofill and passwords > Google Password Manager > Settings. Toggle off “Sign in automatically.”

*   **Edge:** Settings > Profiles > Passwords > Settings. There you can toggle off autofill for passwords and for Personal data separately.

*   **Firefox:** Settings > Privacy & Security. Scroll down to Logins and Passwords and uncheck “Autofill logins and passwords.”

*   **Opera:** Settings > Advanced Settings > Autofill > Password Manager > Settings. Toggle off “Auto Sign-in.”

*   **Safari:** Safari (in the menu bar) > Settings > Autofill. Uncheck “Usernames and passwords” and “Credit cards”.

Your browser password manager gives you “ease of use” but that costs you some of your security. Of course, password managers aren’t foolproof either, so it’s important to decide for yourself where you store your passwords.

If you’re confident the website is safe and anyone that can access it under your account will not learn anything new, feel free to store the password in your browser, but disable autofill so you are the one that is in control.

Use MFA where possible. It enormously reduces the risk should someone get hold of your password. And refrain from using the browser password manager to store your credit card details or other sensitive personally identifiable information (e.g. medical information).

**We don’t just report on threats—we remove them**

Cybersecurity risks should never spread beyond a headline. Keep threats off your devices by downloading Malwarebytes today.

 Should you allow your browser to remember your passwords? 

One of the largest cybercrime services for laundering stolen merchandise was hacked recently, exposing its internal operations, finances and organizational structure. Here’s a closer look at the Russia-based SWAT USA Drop Service, which currently employs more than 1,200 people across the United States who are knowingly or unwittingly involved in reshipping expensive consumer goods purchased with stolen credit cards.

The login page for the criminal reshipping service SWAT USA Drop.

One of the largest cybercrime services for laundering stolen merchandise was hacked recently, exposing its internal operations, finances and organizational structure. Here’s a closer look at the Russia-based **SWAT USA Drop Service**, which currently employs more than 1,200 people across the United States who are knowingly or unwittingly involved in reshipping expensive consumer goods purchased with stolen credit cards.

Among the most common ways that thieves extract cash from stolen credit card accounts is through purchasing pricey consumer goods online and reselling them on the black market. Most online retailers grew wise to these scams years ago and stopped shipping to regions of the world most frequently associated with credit card fraud, including Eastern Europe, North Africa, and Russia.

But such restrictions have created a burgeoning underground market for reshipping scams, which rely on willing or unwitting residents in the United States and Europe to receive stolen goods and relay them to crooks living in the embargoed areas.

Services like SWAT are known as “Drops for stuff” on cybercrime forums. The “**drops**” are people who have responded to work-at-home package reshipping jobs advertised on craigslist.com and job search sites. Most reshipping scams promise employees a monthly salary and even cash bonuses. In reality, the crooks in charge almost always stop communicating with drops just before the first payday, usually about a month after the drop ships their first package.

The packages arrive with prepaid shipping labels that are paid for with stolen credit card numbers, or with hijacked online accounts at FedEx and the US Postal Service. Drops are responsible for inspecting and verifying the contents of shipments, attaching the correct shipping label to each package, and sending them off via the appropriate shipping company.

SWAT takes a percentage cut (up to 50 percent) where “**stuffers**” — thieves armed with stolen credit card numbers — pay a portion of each product’s retail value to SWAT as the reshipping fee. The stuffers use stolen cards to purchase high-value products from merchants and have the merchants ship the items to the drops’ address. Once the drops receive and successfully reship the stolen packages, the stuffers then sell the products on the local black market.

The SWAT drop service has been around in various names and under different ownership for almost a decade. But in early October 2023, SWAT’s current co-owner — a Russian-speaking individual who uses the handle “**Fearlless**” — took to his favorite cybercrime forum to lodge a formal complaint against the owner of a competing reshipping service, alleging his rival had hacked SWAT and was trying to poach his stuffers and reshippers by emailing them directly.

Milwaukee-based security firm Hold Security shared recent screenshots of a working SWAT stuffer’s user panel, and those images show that SWAT currently lists more than 1,200 drops in the United States that are available for stuffers to rent. The contact information for **Kareem**, a young man from Maryland, was listed as an active drop. Contacted by KrebsOnSecurity, Kareem agreed to speak on condition that his full name not be used in this story.

A SWAT panel for stuffers/customers. This page lists the rules of the service, which do not reimburse stuffers for “acts of god,” i.e. authorities seizing stolen goods or arresting the drop.

Kareem said he’d been hired via an online job board to reship packages on behalf of a company calling itself **CTSI**, and that he’s been receiving and reshipping iPads and Apple watches for several weeks now. Kareem was less than thrilled to learn he would probably not be getting his salary on the promised payday, which was coming up in a few days.

Kareem said he was instructed to create an account at a website called **portal-ctsi\[.\]com**, where each day he was expected to log in and check for new messages about pending shipments. Anyone can sign up at this website as a potential reshipping mule, although doing so requires applicants to share a great deal of personal and financial information, as well as copies of an ID or passport matching the supplied name.

A SWAT panel for stuffers/customers, listing hundreds of drops in the United States by their status. “Going to die” are those who are about to be let go without promised payment, or who have quit on their own.

On a suspicion that the login page for portal-ctsi\[.\]com might be a custom coding job, KrebsOnSecurity selected “view source” from the homepage to expose the site’s HTML code. Grabbing a snippet of that code (e.g., “smarty/default/jui/js/jquery-ui-1.9.2.min.js”) and searching on it at **publicwww.com** reveals more than four dozen other websites running the same login panel. And all of those appear to be geared toward either stuffers or drops.

In fact, more than half of the domains that use this same login panel actually include the word “stuffer” in the login URL, according to publicwww. Each of the domains below that end in “/user/login.php” are sites for active and prospective drops, and each corresponds to a unique fake company that is responsible for managing its own stable of drops:

lvlup-store\[.\]com/stuffer/login.php  
personalsp\[.\]com/user/login.php  
destaf\[.\]com/stuffer/login.php  
jaderaplus\[.\]com/stuffer/login.php  
33cow\[.\]com/stuffer/login.php  
panelka\[.\]net/stuffer/login.php  
aaservice\[.\]net/stuffer/login.php  
re-shipping\[.\]ru/stuffer/login.php  
bashar\[.\]cc/stuffer/login.php  
marketingyoursmall\[.\]biz/stuffer/login.php  
hovard\[.\]xyz/stuffer/login.php  
pullback\[.\]xyz/stuffer/login.php  
telollevoexpress\[.\]com/stuffer/login.php  
postme\[.\]today/stuffer/login.php  
wint-job\[.\]com/stuffer/login.php  
squadup\[.\]club/stuffer/login.php  
mmmpack\[.\]pro/stuffer/login.php  
yoursmartpanel\[.\]com/user/login.php  
opt257\[.\]org/user/login.php  
touchpad\[.\]online/stuffer/login.php  
peresyloff\[.\]top/stuffer/login.php  
ruzke\[.\]vodka/stuffer/login.php  
staf-manager\[.\]net/stuffer/login.php  
data-job\[.\]club/stuffer/login.php  
logistics-services\[.\]org/user/login.php  
swatship\[.\]club/stuffer/login.php  
logistikmanager\[.\]online/user/login.php  
endorphine\[.\]world/stuffer/login.php  
burbon\[.\]club/stuffer/login.php  
bigdropproject\[.\]com/stuffer/login.php  
jobspaket\[.\]net/user/login.php  
yourcontrolboard\[.\]com/stuffer/login.php  
packmania\[.\]online/stuffer/login.php  
shopping-bro\[.\]com/stuffer/login.php  
dash-redtag\[.\]com/user/login.php  
mnger\[.\]net/stuffer/login.php  
begg\[.\]work/stuffer/login.php  
dashboard-lime\[.\]com/user/login.php  
control-logistic\[.\]xyz/user/login.php  
povetru\[.\]biz/stuffer/login.php  
dash-nitrologistics\[.\]com/user/login.php  
cbpanel\[.\]top/stuffer/login.php  
hrparidise\[.\]pro/stuffer/login.php  
d-cctv\[.\]top/user/login.php  
versandproject\[.\]com/user/login.php  
packitdash\[.\]com/user/login.php  
avissanti-dash\[.\]com/user/login.php  
e-host\[.\]life/user/login.php  
pacmania\[.\]club/stuffer/login.php

Why so many websites? In practice, all drops are cut loose within approximately 30 days of their first shipment — just before the promised paycheck is due. Because of this constant churn, each stuff shop operator must be constantly recruiting new drops. Also, with this distributed setup, even if one reshipping operation gets shut down (or exposed online), the rest can keep on pumping out dozens of packages a day.

A 2015 academic study (PDF) on criminal reshipping services found the average financial hit from a reshipping scheme per cardholder was $1,156.93. That study looked into the financial operations of several reshipping schemes, and estimated that approximately 1.6 million credit and debit cards are used to commit at least $1.8 billion in reshipping fraud each year.

It’s not hard to see how reshipping can be a profitable enterprise for card crooks. For example, a stuffer buys a stolen payment card off the black market for $10, and uses that card to purchase more than $1,100 worth of goods. After the reshipping service takes its cut (~$550), and the stuffer pays for his reshipping label (~$100), the stuffer receives the stolen goods and sells them on the black market in Russia for $1,400. He has just turned a $10 investment into more than $700. Rinse, wash, and repeat.

The breach at SWAT exposed not only the nicknames and contact information for all of its stuffers and drops, but also the group’s monthly earnings and payouts. SWAT apparently kept its books in a publicly accessible Google Sheets document, and that document reveals Fearlless and his business partner each routinely made more than $100,000 every month operating their various reshipping businesses.

The exposed SWAT financial records show this crime group has tens of thousands of dollars worth of expenses each month, including payments for the following recurring costs:

\-advertising the service on crime forums and via spam;  
\-people hired to re-route packages, usually by voice over the phone;  
\-third-party services that sell hacked/stolen USPS/Fedex labels;  
\-“drops test” services, contractors who will test the honesty of drops by sending them fake jewelry;  
\-“documents,” e.g. sending drops to physically pick up legal documents for new phony front companies.

The spreadsheet also included the cryptocurrency account numbers that were to be credited each month with SWAT’s earnings. Unsurprisingly, a review of the blockchain activity tied to the bitcoin addresses listed in that document shows that many of them have a deep association with cybercrime, including ransomware activity and transactions at darknet sites that peddle stolen credit cards and residential proxy services.

The information leaked from SWAT also has exposed the real-life identity and financial dealings of its principal owner — Fearlless, a.k.a. “SwatVerified.” We’ll hear more about Fearlless in Part II of this story. Stay tuned.

Russian Reshipping Service ‘SWAT USA Drop’ Exposed

NVIDIA GPU Display Driver for Windows contains a vulnerability that allows Windows users with low levels of privilege to escalate privileges when an administrator is updating GPU drivers, which may lead to escalation of privileges.

**Details**

This section provides a summary of potential vulnerabilities that this security update addresses and their impact. Descriptions use CWE™, and base scores and vectors use CVSS v3.1 standards.

**NVIDIA GPU Display Driver**

**CVE ID**

**Description**

**Base Score**

**CWE and Vector**

CVE‑2023‑31027

NVIDIA GPU Display Driver for Windows contains a vulnerability that allows Windows users with low levels of privilege to escalate privileges when an administrator is updating GPU drivers, which may lead to escalation of privileges.

8.2

CWE-427  
AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H

CVE‑2023‑31019

NVIDIA GPU Display Driver for Windows contains a vulnerability in wksServicePlugin.dll, where the driver implementation does not restrict or incorrectly restricts access from the named pipe server to a connecting client, which may lead to potential impersonation to the client's secure context.

7.8

CWE-284  
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CVE‑2023‑31017

NVIDIA GPU Display Driver for Windows contains a vulnerability where an attacker may be able to write arbitrary data to privileged locations by using reparse points. A successful exploit of this vulnerability may lead to code execution, denial of service, escalation of privileges, information disclosure, or data tampering.

7.8

CWE: 552  
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CVE‑2023‑31016

NVIDIA GPU Display Driver for Windows contains a vulnerability where an uncontrolled search path element may allow an attacker to execute arbitrary code, which may lead to code execution, denial of service, escalation of privileges, information disclosure, or data tampering.

7.3

CWE-427  
AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

CVE‑2023‑31020

NVIDIA GPU Display Driver for Windows contains a vulnerability in the kernel mode layer, where an unprivileged regular user can cause improper access control, which may lead to denial of service or data tampering.

6.1

CWE-284  
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H

CVE‑2023‑31022

NVIDIA GPU Display Driver for Windows and Linux contains a vulnerability in the kernel mode layer, where a NULL-pointer dereference may lead to denial of service.

5.5

CWE: 476  
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CVE‑2023‑31023

NVIDIA Display Driver for Windows contains a vulnerability where an attacker may cause a pointer dereference of an untrusted value, which may lead to denial of service.

5.5

CWE: 822  
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

**NVIDIA vGPU Software**

**CVE ID**

**Description**

**Base Score**

**CWE and Vector**

CVE‑2023‑31018

NVIDIA GPU Driver for Windows and Linux contains a vulnerability in the kernel mode layer, where an unprivileged regular user can cause a NULL-pointer dereference, which may lead to denial of service.

6.5

CWE: 476  
AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H

CVE‑2023‑31026

NVIDIA vGPU software for Windows and Linux contains a vulnerability in the Virtual GPU Manager (vGPU plugin), where a NULL-pointer dereference may lead to denial of service.

6.0

CWE: 476  
AV:L/AC:L/PR:H/UI:N/S:C/C:N/I:N/A:H

CVE‑2023‑31021

NVIDIA vGPU software for Windows and Linux contains a vulnerability in the Virtual GPU Manager (vGPU plugin), where a malicious user in the guest VM can cause a NULL-pointer dereference, which may lead to denial of service.

5.5

CWE: 476  
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

The NVIDIA risk assessment is based on an average of risk across a diverse set of installed systems and may not represent the true risk to your local installation. NVIDIA recommends consulting a security or IT professional to evaluate the risk to your specific configuration.

**Security Updates for NVIDIA GPU Display Driver****CVE IDs Addressed in Each Windows Driver Branch**

The following table lists the CVE IDs addressed by the update in each Windows driver branch.

**Windows Driver Branch**

**CVE IDs Addressed**

R545, R535, R525

CVE‑2023‑31016, CVE‑2023‑31017, CVE‑2023‑31019, CVE‑2023‑31020, CVE‑2023‑31022, CVE‑2023‑31023, CVE‑2023‑31027

R470

CVE‑2023‑31017, CVE‑2023‑31019, CVE‑2023‑31020, CVE‑2023‑31022, CVE‑2023‑31023, CVE‑2023‑31027

**Security Updates for NVIDIA GPU Windows Display Driver**

The following table lists the NVIDIA software products affected, Windows driver versions affected, and the updated version available from nvidia.com that includes this security update. Download the updates from the NVIDIA Driver Downloads page.

**Software Product**

**Operating System**

**Driver Branch**

**Affected Driver Versions**

**Updated Driver Version**

GeForce

Windows

R545

All driver versions prior to 546.01

546.01

Windows 10 and 11

R470

All driver versions prior to 474.64 for support of GeForce Kepler desktop

474.64

Windows 7 and 8._x_

R470

All driver versions prior to 474.64

474.64

Studio

Windows

R545

All driver versions prior to 546.01

546.01

NVIDIA RTX,  
Quadro,  
NVS

Windows

R545

All driver versions prior to 546.01

546.01

R535

All driver versions prior to 537.70

537.70

R525

All driver versions prior to 529.19

529.19

R470

All driver versions prior to 474.64

474.64

Tesla

Windows

R535

All driver versions prior to 537.70

537.70

R525

All driver versions prior to 529.19

529.19

R470

All driver versions prior to 474.64

474.64

**CVE IDs Addressed in Each Linux Driver Branch**

The following table lists the CVE IDs addressed by the update in each Linux driver branch.

**Linux Driver Branch**

**CVE IDs Addressed**

R545, R535, R525, R470

CVE‑2023‑31022

**Security Updates for NVIDIA GPU Linux Display Driver**

The following table lists the NVIDIA software products affected, Linux driver versions affected, and the updated version available from nvidia.com that includes this security update. Download the updates from the NVIDIA Driver Downloads page.

**Software Product**

**Operating System**

**Driver Branch**

**Affected Driver Versions**

**Updated Driver Version**

GeForce

Linux

R545

All driver versions prior to 545.29.02

545.29.02

R535

All driver versions prior to 535.129.03

535.129.03

R525

All driver versions prior to 525.147.05

525.147.05

R470

All driver versions prior to 470.223.02

470.223.02

NVIDIA RTX, Quadro, NVS

Linux

R545

All driver versions prior to 545.29.02

545.29.02

R535

All driver versions prior to 535.129.03

535.129.03

R525

All driver versions prior to 525.147.05

525.147.05

R470

All driver versions prior to 470.223.02

470.223.02

Tesla

Linux

R535

All driver versions prior to 535.129.03

535.129.03

R525

All driver versions prior to 525.147.05

525.147.05

R470

All driver versions prior to 470.223.02

470.223.02

**Notes**

*   Your computer hardware vendor may provide you with Windows GPU display driver versions including 545.91, 537.70, 529.19 and 474.64, which also contain the security updates.
*   The tables above may not be a comprehensive list of all affected supported versions or branch releases and may be updated as more information becomes available.
*   Earlier software branch releases that support these products may also be affected. If you are using an earlier branch release for which an update version is not listed above, we recommend upgrading to the latest branch release.

**Security Updates for NVIDIA vGPU Software****CVE IDs Addressed in Each Windows vGPU Driver Branch**

The following table lists the CVE IDs addressed by the update in each Windows vGPU driver branch.

**Windows Driver Branch**

**CVE IDs Addressed**

R535

CVE‑2023‑31016, CVE‑2023‑31017, CVE‑2023‑31018, CVE‑2023‑31019, CVE‑2023‑31020, CVE‑2023‑31021, CVE‑2023‑31022, CVE‑2023‑31023, CVE‑2023‑31027

R525

CVE‑2023‑31016, CVE‑2023‑31017, CVE‑2023‑31018, CVE‑2023‑31019, CVE‑2023‑31020, CVE‑2023‑31022, CVE‑2023‑31023, CVE‑2023‑31027

R470

CVE‑2023‑31017, CVE‑2023‑31018, CVE‑2023‑31019, CVE‑2023‑31020, CVE‑2023‑31022, CVE‑2023‑31023, CVE‑2023‑31027

**CVE IDs Addressed in Each Linux vGPU Driver Branch**

The following table lists the CVE IDs addressed by the update in each Linux vGPU driver branch.

**Linux Driver Branch**

**CVE IDs Addressed**

R535, R525, R470

CVE‑2023‑31018, CVE‑2023‑31022

**CVE IDs Addressed in Each vGPU Manager Driver Branch**

The following table lists the CVE IDs addressed by the update in each vGPU Manager driver branch.

**vGPU Manager Driver Branch**

**CVE IDs Addressed**

R535

CVE‑2023‑31018, CVE‑2023‑31021, CVE‑2023‑31022, CVE‑2023‑31026

R525

CVE‑2023‑31018, CVE‑2023‑31022, CVE‑2023‑31026

R470

CVE‑2023‑31018, CVE‑2023‑31022

**Affected Components, Affected Versions, and Updated Versions**

The following table lists NVIDIA vGPU software components affected, versions affected, and the updated version that includes this security update.

**CVE IDs Addressed**

**vGPU Software Component**

**Operating System**

**Affected Versions**

**Updated Version**

**vGPU Software**

**Driver**

**vGPU Software**

**Driver**

CVE‑2023‑31016  
CVE‑2023‑31017  
CVE‑2023‑31018  
CVE‑2023‑31019  
CVE‑2023‑31020  
CVE‑2023‑31022  
CVE‑2023‑31023  
CVE‑2023‑31027

Guest driver

Windows

All versions prior to and including 16.1

537.13

16.2

537.70

All versions prior to and including 15.3

529.11

15.4

529.19

All versions prior to and including 13.8

474.44

13.9

474.64

CVE‑2023‑31018  
CVE‑2023‑31022

Guest driver

Linux

All versions prior to and including 16.1

535.104.05

16.2

535.109.03

All versions prior to and including 15.3

525.125.06

15.4

525.147.05

All versions prior to and including 13.8

470.199.02

13.9

470.223.02

CVE‑2023‑31018  
CVE‑2023‑31021  
CVE‑2023‑31022  
CVE‑2023‑31026

Virtual GPU Manager

Citrix Hypervisor,  
VMware vSphere,

Red Hat Enterprise Linux KVM,

Ubuntu

All versions prior to and including 16.1

535.104.06

16.2

535.109.03

All versions prior to and including 15.3

525.125.03

15.4

525.147.01

All versions prior to and including 13.8

470.199.03

13.9

470.223.02

CVE‑2023‑31018  
CVE‑2023‑31021  
CVE‑2023‑31022

Virtual GPU Manager

Azure Stack HCI

All versions prior to and including 16.1

537.13

16.2

537.70

All versions prior to and including 15.3

529.06

15.4

529.19

**Notes**

*   The table above may not be a comprehensive list of all affected supported versions or branch releases and may be updated as more information becomes available.
*   Earlier software branch releases that support these products may also be affected. If you are using an earlier branch release for which an update version is not listed above, we recommend upgrading to the latest branch release.

**Security Updates for NVIDIA Cloud Gaming****CVE IDs Addressed in Each Windows Cloud Gaming Driver Branch**

The following table lists the CVE IDs addressed by the update in each Windows Cloud Gaming driver branch.

**Windows Driver Branch**

**CVE IDs Addressed**

R545, R535

CVE‑2023‑31016, CVE‑2023‑31017, CVE‑2023‑31018, CVE‑2023‑31019, CVE‑2023‑31020, CVE‑2023‑31021, CVE‑2023‑31022, CVE‑2023‑31023, CVE‑2023‑31027

R525

CVE‑2023‑31016, CVE‑2023‑31017, CVE‑2023‑31018, CVE‑2023‑31019, CVE‑2023‑31020, CVE‑2023‑31022, CVE‑2023‑31023, CVE‑2023‑31027

R470

CVE‑2023‑31017, CVE‑2023‑31018, CVE‑2023‑31019, CVE‑2023‑31020, CVE‑2023‑31022, CVE‑2023‑31023, CVE‑2023‑31027

**CVE IDs Addressed in Each Linux Cloud Gaming Driver Branch**

The following table lists the CVE IDs addressed by the update in each Linux Cloud Gaming driver branch

**Linux Driver Branch**

**CVE IDs Addressed**

R545, R535, R525, R470

CVE‑2023‑31018, CVE‑2023‑31022

**CVE IDs Addressed in Each Cloud Gaming Manager Driver Branch**

The following table lists the CVE IDs addressed by the update in each Cloud Gaming Manager driver branch

**Gaming Manager Driver Branch**

**CVE IDs Addressed**

R545, R535

CVE‑2023‑31018, CVE‑2023‑31021, CVE‑2023‑31022, CVE‑2023‑31026

R525

CVE‑2023‑31018, CVE‑2023‑31022, CVE‑2023‑31026

R470

CVE‑2023‑31018, CVE‑2023‑31022

**Affected Components, Affected Versions, and Updated Versions**

The following table lists the NVIDIA software products affected, versions affected, and the updated version that includes this security update.

**CVE IDs Addressed**

**Cloud Gaming Component**

**Operating System**

**Affected Versions**

**Updated Version**

**Cloud Gaming Software**

**Driver**

**Cloud Gaming Software**

**Driver**

CVE‑2023‑31016  
CVE‑2023‑31017  
CVE‑2023‑31018  
CVE‑2023‑31019  
CVE‑2023‑31020  
CVE‑2023‑31022  
CVE‑2023‑31023  
CVE‑2023‑31027

Guest driver

Windows

All versions prior to and including September 2023 release

537.42

October 2023 release

546.01

CVE‑2023‑31018  
CVE‑2023‑31022

Guest driver

Linux

All versions prior to and including September 2023 release

535.113.01

October 2023 release

545.29.02

CVE‑2023‑31018  
CVE‑2023‑31021  
CVE‑2023‑31022  
CVE‑2023‑31026

Virtual GPU Manager

Red Hat Enterprise Linux KVM,

VMware vSphere

All versions prior to and including September 2023 release

535.113.01

October 2023 release

545.29.02

**Acknowledgements**

NVIDIA thanks the following people for reporting the issues to us:

CVE‑2023‑31027: Patryk Nowakowski

CVE‑2023‑31017: Lockheed Martin Red Team

**Get the Most Up to Date Product Security Information**

Visit the NVIDIA Product Security page to

*   Subscribe to security bulletin notifications
*   See the current list of NVIDIA security bulletins
*   Report a potential security issue in any NVIDIA supported product
*   Learn more about the vulnerability management process followed by the NVIDIA Product Security Incident Response Team (PSIRT)

**Revision History**

  

**Revision**

**Date**

**Description**

1.1

November 1, 2023

Updated Windows Studio Display Driver version to 546.01

1.0

October 31, 2023

Initial release

**Support**

If you have any questions about this security bulletin, contact NVIDIA Support.

**Frequently Asked Questions (FAQs)**

How do I determine which NVIDIA display driver version is currently installed on my PC?

**Disclaimer**

ALL NVIDIA INFORMATION, DESIGN SPECIFICATIONS, REFERENCE BOARDS, FILES, DRAWINGS, DIAGNOSTICS, LISTS, AND OTHER DOCUMENTS (TOGETHER AND SEPARATELY, “MATERIALS”) ARE BEING PROVIDED “AS IS.” NVIDIA MAKES NO WARRANTIES, EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE WITH RESPECT TO THE MATERIALS, AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OR CONDITION OF TITLE, MERCHANTABILITY, SATISFACTORY QUALITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT, ARE HEREBY EXCLUDED TO THE MAXIMUM EXTENT PERMITTED BY LAW.

Information is believed to be accurate and reliable at the time it is furnished. However, NVIDIA Corporation assumes no responsibility for the consequences of use of such information or for any infringement of patents or other rights of third parties that may result from its use. No license is granted by implication or otherwise under any patent or patent rights of NVIDIA Corporation. Specifications mentioned in this publication are subject to change without notice. This publication supersedes and replaces all information previously supplied. NVIDIA Corporation products are not authorized for use as critical components in life support devices or systems without express written approval of NVIDIA Corporation.

CVE-2023-31027: NVIDIA Support


Franklin Fueling System TS-550 versions prior to 1.9.23.8960 are vulnerable to attackers decoding admin credentials, resulting in unauthenticated access to the device.






CVE-2023-5846

A vulnerability has been identified in PT-G503 Series firmware versions prior to v5.2, where the Secure attribute for sensitive cookies in HTTPS sessions is not set, which could cause the cookie to be transmitted in plaintext over an HTTP session. The vulnerability may lead to security risks, potentially exposing user session data to unauthorized access and manipulation.



As of June 15, 2022, this site no longer supports Internet Explorer. Please use another browser for the best experience on our site.

**Please sign in**

**SUMMARY**

**PT-G503 Series Multiple Vulnerabilities**

*   Security Advisory ID: MPSA-230203
*   Version: V1.0
*   Release Date: Nov 02, 2023
*   Reference:
    

PT-G503 Series firmware version v5.2 and prior are affected by multiple vulnerabilities in the old version of jQuery, weak cipher suites, and unsecure web cookies. Using the older jQuery version and weak cipher suites and not setting session cookie attributes properly caused these vulnerabilities. These vulnerabilities could put your security at risk in many ways, such as Cross-site Scripting (XSS) attacks, prototype pollution, data leaks, unauthorized access to user sessions, etc. 

  
The identified vulnerability types and potential impacts are shown below:

Item

Vulnerability Type

Impact

1

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (CWE-79) 

CVE-2015-9251, CVE-2020-11022, CVE-2020-11023 (jQuery) 

An attacker located remotely can insert HTML or JavaScript into the system via a web interface. 

2

Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') (CWE-1321) 

CVE-2019-11358 (jQuery) 

An attacker can inject attributes that are used in other components. 

3

Inadequate Encryption Strength (CWE-326) 

CVE-2005-4900 (cipher) 

An attacker may be able to decrypt the data using spoofing attacks. 

4

Sensitive Cookie Without 'HttpOnly' Flag (CWE-1004) 

CVE-2023-4217 (Cookie) 

This vulnerability could cause security risks and allow unauthorized access to user session data. 

5

Sensitive Cookie in HTTPS Session Without 'Secure' Attribute (CWE-614) 

CVE-2023-5035 (Cookie) 

This vulnerability could cause the cookie to be transmitted in plaintext over an HTTP session. 

**Vulnerability Scoring Details**

ID

CVSS V3.1

VECTOR

REMOTE EXPLOIT WITHOUT AUTH?

CVE-2005-4900 

5.9 

AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N 

Yes

CVE-2015-9251 

6.1 

AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N 

Yes

CVE-2019-11358 

6.1 

AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N 

Yes

CVE-2020-11022 

6.9 

AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:L/A:N 

Yes

CVE-2020-11023 

6.9 

AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:L/A:N 

Yes

CVE-2023-4217 

3.1 

AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N 

Yes

CVE-2023-5035 

3.1 

AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N 

Yes

**AFFECTED PRODUCTS AND SOLUTIONS**

**Affected Products:**

The affected products and firmware versions are shown below.

Product Series

Affected Versions

PT-G503 Series 

Firmware version 5.2 and prior. 

**Solutions:**

For CVE-2005-4900, CVE-2015-9251, CVE-2019-11358, CVE-2020-11022, and CVE-2020-11023, Moxa has developed appropriate solutions to address the vulnerabilities by updating the jQuery version and removing weak cipher suites. The solutions for affected products are shown below. 

****Mitigation****

The risk levels of CVE-2023-4217 and CVE-2023-5035 are low, and it’s hard to forbidden HTTP connections because HTTP is still required in certain legacy application scenarios. To mitigate these vulnerabilities, users should carefully use HTTP if necessary, and could try to replace HTTP by HTTPS when using the web service. Additionally, refer to the following mitigation measures to deploy the product in an appropriate product security context. 

Moxa recommends users follow CISA recommendations.  

*   Reduce network exposure by ensuring that all control system devices and systems are not accessible from the Internet. 
    
*   Place control system networks and remote devices behind firewalls, isolating them from business networks. 
    
*   When remote access is necessary, employ secure methods such as Virtual Private Networks (VPNs). It is important to note that VPNs may have vulnerabilities and should be kept up to date with the latest available version. Remember that the security of a VPN depends on the security of its connected devices. 
    

**Revision History:**

VERSION

DESCRIPTION

RELEASE DATE

1.0

First Release

Nov 2, 2023 

**Relevant Products**

PT-G503 Series ·

*     Print this page
    
*   You can manage and share your saved list in My Moxa
    

**Let’s get that fixed**

If you are concerned about a potential cybersecurity vulnerability, please contact us and one of technical support staff will get in touch with you.

Report a Vulnerability

CVE-2023-5035: PT-G503 Series Multiple Vulnerabilities

Following a string of serious security incidents, Microsoft says it has a plan to deal with escalating threats from cybercriminals and state-backed hackers.

Today, in a blog post and email to employees, Microsoft is announcing a broad vision for tackling the cybersecurity challenges that have increasingly plagued the company and its customers in recent years. Known as the Secure Future Initiative, the plan leans heavily on artificial intelligence tools as a “game changer” and also includes a call for international cyberspace norms, an expansion of the company's 2017 Digital Geneva Convention.

The most tangible and immediately applicable component of the strategy, though, relates to improvements in Microsoft's software development and engineering approach. In Thursday's email, executive vice president for Microsoft security Charlie Bell and colleagues Scott Guthrie and Rajesh Jha lay out a plan to further safeguard identity management systems in Microsoft products, improve security software development, and shorten response and patch release times for addressing vulnerabilities, specifically those in the cloud.

The announcement comes as Microsoft has faced scrutiny over situations where vulnerabilities in its products have enabled attackers—both financially-motivated cybercriminals and state-backed hackers—to rampage through the company's own systems and those of customers. And the climate around accountability is evolving as regulators and law enforcement look for new paths to deterring, but also preventing, damaging hacks. On Monday, for example, the United States Securities and Exchange Commission (SEC) announced charges against the IT management company SolarWinds and its chief information security officer over “cybersecurity risks and vulnerabilities” that the SEC alleges were known and should have been addressed.

Microsoft said on Thursday that its Secure Future Initiative comes in response to wildly escalating threats from attackers. “In recent months, we’ve concluded within Microsoft that the increasing speed, scale, and sophistication of cyberattacks call for a new response," company vice chair and president Brad Smith wrote.

In an interview with WIRED, Microsoft's Bell emphasized that both cybercriminal and state-backed actors are professionalizing and homing in on phishing and creative approaches to credential theft as the most direct and effective method for infiltrating organizations of all sorts. He noted that while it is difficult to get an accurate accounting of total global economic losses due to cybercrime and cyberattacks, Microsoft believes that total losses have been greater than $6 trillion and could close in on $10 trillion by 2025.

“The threat is growing,” he tells WIRED. “It's a huge drag on the world. So when you look at all of this going on and you say well what can we do? Microsoft is in the center of much of the ability to defend. It caused us to step back.”

Speeding vulnerability response times by 50 percent and moving toward mandating secure default settings for customers are two aggressive steps Microsoft says it plans to take to make a tangible impact on customer security. Bell says that multi-factor authentication adoption among Microsoft customers is at roughly 34 percent, but “it should be 100 percent.”

The changes come as other giants across the industry, including Google, are acknowledging the need to push secure defaults, particularly around authentication. The software development platform GitHub, which Microsoft owns, has been working on rolling out mandatory two-factor for months. Apple has long mandated two-factor for most accounts, and Google has been publicly working toward the goal for years.

On many components of the Secure Future Initiative, Microsoft is not exactly late to the party on hardline changes, but is noticeably behind the early advocates. And in general, concepts of engineering software to be secure by design or building system architecture to be zero trust were prominent features of the past decade. Yet, between cloud services and all of the legacy Windows systems around the world, Microsoft is at the very heart of IT infrastructure, and in many ways, global cybersecurity moves at Microsoft’s pace.

“It’s an absolutely terrible world if we don’t get ahead of it,” Bell says. “We have all the data right now that the threat actors—they’re poking from the outside, they see a little bit. We know everything because we’re on the inside. If we’re gonna tackle the security problem we’ve got to be real about the fact that you’re not going to flip a light switch and everybody’s running in the cloud. There’s a lot of operational ground to cover between here and there. And Microsoft is the company that supports that world, that critical infrastructure that’s out there.”

Microsoft Does Damage Control With Its New 'Secure Future Initiative'

GLPI is a free asset and IT management software package. Starting in version 10.0.7 and prior to version 10.0.10, an unverified object instantiation allows one to upload malicious PHP files to unwanted directories. Depending on web server configuration and available system libraries, malicious PHP files can then be executed through a web server request. Version 10.0.10 fixes this issue. As a workaround, remove write access on `/ajax` and `/front` files to the web server.

**This is a security release, upgrading is recommended**

This release fixes a security issue that has been recently discovered. Update is **recommended!**

You can download the **GLPI 10.0.10 archive** on GitHub.

You will find below security issues fixed in this bugfixes version:

*   \[SECURITY - Critical\] Unallowed PHP script execution (CVE-2023-42802).
*   \[SECURITY - High\] Account takeover via SQL Injection in UI layout preferences (CVE-2023-41320).
*   \[SECURITY - High\] Account takeover via Kanban feature (CVE-2023-41326).
*   \[SECURITY - High\] Account takeover through API (CVE-2023-41324).
*   \[SECURITY - High\] File deletion through document upload process (CVE-2023-42462).
*   \[SECURITY - Moderate\] Sensitive fields enumeration through API (CVE-2023-41321).
*   \[SECURITY - Moderate\] Privilege Escalation from technician to super-admin (CVE-2023-41322).
*   \[SECURITY - Moderate\] Users login enumeration by unauthenticated user (CVE-2023-41323).
*   \[SECURITY - Moderate\] Phishing through a login page malicious URL (CVE-2023-41888).
*   \[SECURITY - Moderate\] SQL injection in ITIL actors (CVE-2023-42461).

Also, here is a short list of main changes done in this version:

*   \[FEATURE\] PHP 8.3 and MySQL 8.1 support.
*   \[FEATURE\] Enable usage of images in rich text of followups/tasks/solution templates.
*   \[PERFORMANCES\] Improve ticket timeline rendering performances.
*   \[FIX\] Fix issues with usage of LDAP bind options.
*   \[FIX\] Fix some issues on SLA/OLA escalation levels computation.
*   \[FIX\] Fix some issues on search on numeric and dates fields.
*   Several minor fixes

The **full changelog is available** for more details.

We would like to thank all people who contributed to this new version and all those who contributes regularly to the GLPI project!

Regards.

Tag

#auth