assign static ip ubuntu 18 04

How to Configure Static IP Address on Ubuntu 18.04

Updated on Mar 9, 2020

In this tutorial, we’ll explain how to set up a static IP address on Ubuntu 18.04.

Generally, IP addresses are assigned dynamically by your router DHCP server. Setting a static IP address on your Ubuntu machine may be required in different situations, such as configuring port forwarding or running a media server on your network.

Configuring Static IP address using DHCP #

The easiest and the recommended way to assign a static IP address to a device on your LAN is by setting up a Static DHCP on your router. Static DHCP or DHCP reservation is a feature found on most routers which makes the DHCP server to automatically assign the same IP address to a specific network device, every time the device requests an address from the DHCP server. This works by assigning a static IP to the device’s unique MAC address. The steps for configuring a DHCP reservation vary from router to router, and it’s advisable to consult the vendor’s documentation.

Starting with 17.10 release, Netplan is the default network management tool on Ubuntu, replacing the configuration file /etc/network/interfaces that had previously been used to configure the network on Ubuntu.

Netplan uses configuration files in YAML syntax. To configure a network interface with Netplan, you need to create a YAML description for that interface, and Netplan will generate the required configuration files for your chosen renderer tool.

Netplan currently supports two renderers NetworkManager and Systemd-networkd. NetworkManager is mostly used on Desktop machines while the Systemd-networkd is used on servers without a GUI.

Configuring Static IP address on Ubuntu Server #

The newer versions of Ubuntu uses ‘Predictable Network Interface Names’ that, by default, start with en[letter][number] .

The first step is to identify the name of the ethernet interface you want to configure. To do so use the ip link command, as shown below:

The command will print a list of all the available network interfaces. In this case, the name of the interface is ens3 :

Netplan configuration files are stored in the /etc/netplan directory and have the extension .yaml . You’ll probably find one or two YAML files in this directory. The file may differ from setup to setup. Usually, the file is named either 01-netcfg.yaml , 50-cloud-init.yaml , or NN_interfaceName.yaml , but in your system it may be different.

Open the YAML configuration file with your text editor :

Before changing the configuration, let’s explain the code in a short.

Each Netplan Yaml file starts with the network key that has at least two required elements. The first required element is the version of the network configuration format, and the second one is the device type. The device type can be ethernets , bonds , bridges , or vlans .

The configuration above also includes the renderer type. Out of the box, if you installed Ubuntu in server mode, the renderer is configured to use networkd as the back end.

Under the device’s type (in this case ethernets ), you can specify one or more network interfaces. In this example, we have only one interface ens3 that is configured to obtain IP addressing from a DHCP server dhcp4: yes .

To assign a static IP address to ens3 interface, edit the file as follows:

Set DHCP to dhcp4: no .
Specify the static IP address 192.168.121.199/24 . Under addresses: you can add one or more IPv4 or IPv6 IP addresses that will be assigned to the network interface.
Specify the gateway gateway4: 192.168.121.1
Under nameservers , set the IP addresses of the nameservers addresses: [8.8.8.8, 1.1.1.1]

When editing Yaml files, make sure you follow the YAML code indent standards. If there are syntax errors in the configuration, the changes will not ne applied.

Once done save and close the file and apply the changes with:

Verify the changes by typing:

That’s it! You have assigned a static IP to your Ubuntu server.

Configuring Static IP address on Ubuntu Desktop #

Setting up a static IP address on Ubuntu Desktop computers requires no technical knowledge.

In the Activities screen, search for “network” and click on the Network icon. This will open the GNOME Network configuration settings. Click on the cog icon.

The Network interface settings dialog box will be opened:

In “IPV4” Method" section, select “Manual” and enter your static IP address, Netmask and Gateway. Once done, click on the “Apply” button.

Now that you have set up a static IP Address, open your terminal either by using the Ctrl+Alt+T keyboard shortcut or by clicking on the terminal icon and verify the changes by typing:

The output will show the interface IP address:

Conclusion #

You have learned how to assign a static IP address on your Ubuntu 18.04 machine.

If you have any questions, please leave a comment below.

How to Configure Static IP Address on Ubuntu 20.04

How to install python 3.8 on ubuntu 18.04, how to install odoo 13 on ubuntu 18.04.

How to Change Root Password in Ubuntu Linux
How to Uninstall Software Packages on Ubuntu
How To Add Apt Repository In Ubuntu
How to Add User to Sudoers in Ubuntu

If you like our content, please consider buying us a coffee. Thank you for your support!

We’ll never share your email address or spam you.

Sep 15, 2020

Nov 5, 2019

Oct 19, 2019

TechRepublic

Account information.

Share with Your Friends

How to configure a static IP address in Ubuntu Server 18.04

Your email has been sent

From the office of, “If it’s not broken don’t fix it” comes this: In Ubuntu Server , there’s a brand new method of setting IP addresses. Gone are the days of manually editing the flat text /etc/network/interfaces file. In its place is netplan. That’s right, Ubuntu fans, the method you’ve known for years is now a thing of the past. Instead of a very simple text file, Ubuntu Server requires editing a .yaml file (complete with proper adherence to correct code indent for each line of the block), in order to configure your IP addressing.

Before you panic, it’s not all that challenging. In fact, it’s really just a matter of understanding the layout of these .yaml files and how networking is now restarted. I’m going to show you just that, such that you can configure a static IP address in Ubuntu Server 18.04 as easily as you could in 16.04.

The new method

Open up a terminal window on your Ubuntu 18.04 server (or log in via secure shell). Change into the /etc/netplan directory with the command cd /etc/netplan . Issue the command ls and you should see a file named 50-cloud-init.yaml . If you don’t also see a file named 01-netcfg.yaml , create it with the command sudo touch 01-netcfg.yaml . Before we edit that file, we need to know the name of our networking interface. Issue the command ip a and you should see your system network interface listed by name ( Figure A ).

Now we’re going to create a new netplan configuration file. If you don’t see the 01-netcfg.yaml file, create one with the command sudo nano 01-netcfg.yaml . Our file is going to look like that which you see in Figure B .

What’s crucial about the layout of this file is not using the exact same spacing as my example, but that you’re consistent. If you’re not consistent with your indents, the file will not work. What you see in that sample file is all you need to configure that static IP address. Do notice, you aren’t setting the address is the same fashion as you did with Ubuntu 16.04. With the old method, you set IP address and netmask like so:

address = 192.168.1.206 netmask = 255.255.255.0

With netplan, these are set with a single line:

addresses : [192.168.1.206/24]

Restarting/testing networking

With the new method, you must restart networking using netplan. So once you’ve configured your interface, issue the command:

sudo netplan apply

The above command will restart networking and apply the new configuration. You shouldn’t see any output. If networking fails to function properly, you can issue the command:

sudo netplan --debug apply

The output of the command ( Figure C ) should give you some indication as to what’s going wrong.

That’s all there is to it

There ya go. That’s all there is to configuring a static IP address in Ubuntu Server 18.04. Remember, you’ll have to do this for each interface you have on your server. Make sure to name the files something like 01-netcfg.yaml and 02-netcfg-yaml. It’s not terribly difficult, once you’re used to not working with that old-school interfaces file.

Subscribe to the Developer Insider Newsletter

From the hottest programming languages to commentary on the Linux OS, get the developer and open source news and tips you need to know. Delivered Tuesdays and Thursdays

How to install Ubuntu Server 18.04
How to enable remote desktop connections in Ubuntu 18.04
How to enable an automatic purge of temp files in Ubuntu 18.04
How to connect Ubuntu 18.04 to your Google account
Ubuntu 18.04 LTS: The Linux for AI, clouds, and containers

Create a TechRepublic Account

Get the web's best business technology news, tutorials, reviews, trends, and analysis—in your inbox. Let's start with the basics.

* - indicates required fields

Sign in to TechRepublic

Lost your password? Request a new password

Reset Password

Please enter your email adress. You will receive an email message with instructions on how to reset your password.

Check your email for a password reset link. If you didn't receive an email don't forgot to check your spam folder, otherwise contact support .

Welcome. Tell us a little bit about you.

This will help us provide you with customized content.

Want to receive more TechRepublic news?

You're all set.

Thanks for signing up! Keep an eye out for a confirmation email from our team. To ensure any newsletters you subscribed to hit your inbox, make sure to add [email protected] to your contacts list.

Set static IP in Ubuntu using Terminal

Everything you need to know about setting static IP on an Ubuntu machine using the command line.

Dec 5, 2022 — Pratham Patel

Normally, the router's DHCP server handles assigning the IP address to every device on the network, including your computer.

The DHCP server may also give you a new IP address occasionally. This could cause a problem if you have a home lab or server setup that works on a fixed IP address.

You need to set a static IP address on your Ubuntu system to avoid problems.

Step 1: Identify the correct network interface

The first step is always to know the name of your network interface.

"But why?" you might ask. That is because since Ubuntu 20.04, the network interfaces are named using predictable network interface names . This means your one and only ethernet interface will not be named 'eth0'.

Ubuntu Server and Ubuntu Desktop use different renderers for 'netplan', they are 'systemd-networkd' and 'NetworkManager', respectively. So let's go over their differences.

Ubuntu Server

To see available network interfaces on Ubuntu Server, run the following command:

Doing so will show a similar result:

The output enumerates network interfaces with numbers.

From this, I can see that the ethernet interface is 'enp1s0'.

Ubuntu Desktop

The advantage (at least in my opinion) of having Ubuntu Desktop is having NetworkManager as the renderer for netplan .

It has a pretty CLI output :)

Run the following command to view the available network interfaces:

That will give you the device name, type, state and connection status.

Here is what it looks like on my computer:

This is more readable at first glance. I can make out that my ethernet interface is named 'enp1s0'.

Step 2: See current IP address

Now that you know which interface needs to be addressed, let us edit a file .

Before I change my IP address/set a static one, let us first see what my current IP address is .

Nice! But let's change it to '192.168.122.128' for demonstration purposes.

Step 3: See the gateway

A gateway is a device that connects different networks (basically what your all-in-one router is). To know the address of your gateway, run the following command:

The gateway address will be on the line that begins with "default via".

Below is the output of running the ip command on my computer:

On the line that starts with "default via", I can see that my gateway address '192.168.122.1'

Make a note of your gateway address.

Step 4: Set static IP address

Now that you have detail like interface name and gateway address, it is time to edit a config file.

Step 4-A: Disable cloud-init if present

The easiest way to know if cloud-init is present or not is to check if there is a package with that name.

Run the following command to check:

If you get an outupt, you have 'cloud-init' installed.

Now, to disable could-init, create a new file inside the /etc/cloud/cloud.cfg.d directory. The name does not matter, so I will call it '99-disable-cloud-init.cfg'.

Add the following line to it:

Please reboot your Ubuntu system now so that cloud-init does not interfere when we set our static IP address in the next step. :)

Back to Step 4

Once the 'cloud-init' related configuration is complete, we must now edit the netplan configuration to add our static IP address.

Go to the /etc/netplan directory. It is better if there is one file (easier to know which one to edit), but in some cases, there might also be more than one file with the extension '.yml' or '.yaml'.

When in doubt, grep for the name of your network interface. Use the following command if you are not comfortable with grep:

Since the name of network interface for my ethernet is 'enp1s0', I will run the following command:

running this command shows that the file I am looking for is '00-installer-config.yaml'. So let us take a look at it.

You might have noticed a line that says 'ethernet' and our network interface name under that. Under this is where we configure our 'enp1s0' network interface.

Since we do not want DHCP assigned IP address, let us change that field from true to no .

Add a field called addresses . Write the IP address you wish to assign your computer along with the network prefix. So I will write 192.168.122.128/24 in the addresses field.

Finally, we also need to specify DNS nameservers. For that, create a new field called nameservers and under that, create a field called addresses which contains the IP address for your DNS servers . I used Cloudflare's DNS servers but you can use whatever you want.

This is what my '00-installer-config.yaml' file looks like after editing it to my liking.

To apply the settings, run the following command:

This will take only a few seconds, and the IP address will be updated once it is done.

You can check the IP address using the hostname -I command.

Perfect! The IP address has now changed successfully.

I know that it feels complicated but this is the proper procedure when you are trying to assign static IP via the command line in Ubuntu.

Let me know if you are stuck at some point or encounter any technical issues.

Fell in love with Ubuntu the first time I tried it. Been distro-hopping since 2016.

Ubuntu Static IP configuration

In this tutorial, you will learn all about Ubuntu static IP address configuration. We will provide the reader with a step by step procedure on how to set static IP address on Ubuntu Server via netplan and Ubuntu Desktop using NetworkManager . Static IP address is recommended for servers as the static address does not change as oppose to a dynamic IP address assignment via DHCP server. This tutorial will work for all recent versions of Ubuntu, including the latest LTS release, Ubuntu 22.04 Jammy Jellyfish. Ubuntu offers us a GUI method and command line method to set a static IP address, and both methods are covered below.

In this tutorial you will learn how to:

Set static IP address on Ubuntu Desktop using a NetworkManager
Configure static IP address on Ubuntu server via networkd daemon

Software Requirements and Conventions Used

Software Requirements and Linux Command Line Conventions
Category	Requirements, Conventions or Software Version Used
System	Installed or Ubuntu Server/Desktop
	N/A
Other	Privileged access to your Linux system as root or via the command.
Conventions	– requires given to be executed with root privileges either directly as a root user or by use of command – requires given to be executed as a regular non-privileged user

Ubuntu Static IP configuration step by step

Ubuntu desktop.

The simplest approach on how to configure a static IP address on Ubuntu Desktop is via GNOME graphical user interface:

Ubuntu Server

To configure a static IP address on your Ubuntu server you need to modify a relevant netplan network configuration file within /etc/netplan/ directory.

For example, you might find there a default netplan configuration file called 50-cloud-init.yaml or 01-network-manager-all.yaml with a following content using the networkd deamon to configure your network interface via DHCP:

Default dynamic IP address settings on Ubuntu Server

To set your network interface enp0s3 to static IP address 192.168.1.233 with gateway 192.168.1.1 and DNS server as 8.8.8.8 and 8.8.4.4 replace the above configuration with the one below.

Ubuntu server configured with static IP address.

Once ready apply changes with:

In case you run into some issues execute:

Closing Thoughts

In this tutorial, we saw how to configure a static IP address on an Ubuntu Linux system. This ensures that our private internal IP address will not change again, unless we manually do so at a later time. This has some advantages over DHCP since it means that our system can always be found at the same network address.

How to Assign Static IP Address on Ubuntu Linux

Brief: In this tutorial, you’ll learn how to assign static IP address on Ubuntu and other Linux distributions. Both command line and GUI methods have been discussed.

IP addresses on Linux Systems in most cases are assigned by Dynamic Host Configuration Protocol (DHCP) servers. IP addresses assigned this way are dynamic which means that the IP address might change when you restart your Ubuntu system . It’s not necessary but it may happen.

Dynamic IP is not an issue for normal desktop Linux users in most cases . It could become an issue if you have employed some special kind of networking between your computers.

For example, you can share your keyboard and mouse between Ubuntu and Raspberry Pi . The configuration uses IP addresses of both system. If the IP address changes dynamically, then your setup won’t work.

Another use case is with servers or remotely administered desktops. It is easier to set static addresses on those systems for connection stability and consistency between the users and applications.

In this tutorial, I’ll show you how to set up static IP address on Ubuntu based Linux distributions. Let me show you the command line way first and then I’ll show the graphical way of doing it on desktop.

Method 1: Assign static IP in Ubuntu using command line

Note for desktop users : Use static IP only when you need it. Automatic IP saves you a lot of headache in handling network configuration.

Step 1: Get the name of network interface and the default gateway

The first thing you need to know is the name of the network interface for which you have to set up the static IP.

You can either use ip command or the network manager CLI like this:

In my case, it shows my Ethernet (wired) network is called enp0s25:

Next, you should note the default gateway IP using the Linux command ip route :

As you can guess, the default gateway is 192.168.31.1 for me.

Step 2: Locate Netplan configuration

Ubuntu 18.04 LTS and later versions use Netplan for managing the network configuration. Netplan configuration are driven by .yaml files located in /etc/netplan directory.

By default, you should see a .yaml file named something like 01-network-manager-all.yaml, 50-cloud-init.yaml, 01-netcfg.yaml.

Whatever maybe the name, its content should look like this:

You need to edit this file for using static IP.

Step 3: Edit Netplan configuration for assigning static IP

Just for the sake of it, make a backup of your yaml file.

Please make sure to use the correct yaml file name in the commands from here onward.

Use nano editor with sudo to open the yaml file like this:

Please note that yaml files use spaces for indentation . If you use tab or incorrect indention, your changes won’t be saved.

You should edit the file and make it look like this by providing the actual details of your IP address, gateway, interface name etc.

In the above file, I have set the static IP to 192.168.31.16.

Save the file and apply the changes with this command:

You can verify it by displaying your ip address in the terminal with ‘ip a’ command.

If you don’t want to use the static IP address anymore, you can revert easily.

If you have backed up the original yaml file, you can delete the new one and use the backup one.

Otherwise, you can change the yaml file again and make it look like this:

Method 2: Switch to static IP address in Ubuntu graphically

If you are on desktop, using the graphical method is easier and faster.

Go to the settings and look for network settings. Click the gear symbol adjacent to your network connection.

Assign Static IP address in Ubuntu Linux

Next, you should go to the IPv4 tab. Under the IPv4 Method section, click on Manual.

In the Addresses section, enter the IP static IP address you want, netmask is usually 24 and you already know your gateway IP with the ip route command.

You may also change the DNS server if you want. You can keep Routes section to Automatic.

Once everything is done, click on Apply button. See, how easy it is to set a static IP address graphically.

If you haven’t read my previous article on how to change MAC Address , you may want to read in conjunction with this one.

More networking related articles will be rolling out, let me know your thoughts at the comments below and stay connected to our social media.

Dimitrios is an MSc Mechanical Engineer but a Linux enthusiast in heart. His machines are powered by Arch Linux but curiosity drives him to constantly test other distros. Challenge is part of his per

Exploring the Default Tiling Windows Feature in Ubuntu 24.04 (and Enhancing it)

Fixing applications icon missing from the launcher in ubuntu, reset forgotten root password in ubuntu, install multiple python versions on ubuntu with pyenv, 5 tiny tweaks that help me a great deal with ubuntu 24.04 on my laptop, become a better linux user.

With the FOSS Weekly Newsletter, you learn useful Linux tips, discover applications, explore new distros and stay updated with the latest from Linux world

Great! You’ve successfully signed up.

Welcome back! You've successfully signed in.

You've successfully subscribed to It's FOSS.

Your link has expired.

Success! Check your email for magic link to sign-in.

Success! Your billing info has been updated.

Your billing was not updated.

Instructions

How to configure static IP address on Ubuntu 18.04

Main idea of this article

The most often case of infrastructure organization today is automated settings assign via DHCP server cause no more needed on client side. But if you don't have DHCP - no panic. You may set IP address manually after this material reading.

Firstly, you should define the network interface which settings you are want to change. To see all network cards with theirs settings just run command below:

List All Active Network Interfaces on Ubuntu

In this output we've seen that our computer has three ethernet adapters. One of them is assigned to docker, other is loopback interface. So, our aim is ens33 network adapter. Let's go.

Since version 17.10 Ubuntu uses netplan tool to manage connectivity settings. This utility based on YAML synopsis rules. All settings are stored in /etc/netplan/*.yaml files.

So we should list all files in /etc/netplan/ directory:

NOTE: If there are no files found you can re-build it to default system config:

As we see, only 50-cloud-init.yaml file is present. To change connectivity settings we will edit it via text editor.

Let's find our adapter's name inside. By default, Ubuntu 18.04 is trying to get network settings from dedicated DHCP-node. Directive below is responsible for this:

Some explains:

ens33 – interface name dhcp4, dhcp6 – this sections are respective to the dhcp-properties for 4th and 6th IP-protocol versions. addresses – static addresses "pointed" to the interface. (in CIDR format) gateway4 – IPv4 address for default hope. nameservers – IP addresses for servers which resolves DNS-queries.

NOTE: You must use spaces only, no tabs.

To apply changes just run this command:

As we see, no error messages, everything is OK.

And finally, just see system settings again:

Congratulations! IP addresses config is fully consistent with YAML-file we modified.

After this instruction reading you may assign static IP addresses to your Ubuntu server.

Thanks! Please indicate the reason for the low rating so that we can improve the article

Cloud servers
VMware cloud
Block storage
Object storage
Private network
Direct connect
Edge Gateways
Developer tools
Serverspace GPT API
Marketplace
Application Hosting
Web Hosting
WordPress Hosting
Cloud for startups
Cloud for E-commerce
Big Data computing
Referral program
About Serverspace
Press center
Terms of service
Privacy Policy
Use of Cookies
Infrastructure
Data centers
Control panel
Customer stories

Create account

By signing up you agree to the Terms of Service .

How-To Geek

How to set a static ip address in ubuntu.

Your changes have been saved

Email Is sent

Please verify your email address.

You’ve reached your account maximum for followed topics.

Quick Links

What is a static ip address, setting a static ip in ubuntu, set a static ip in ubuntu with the gui, connection convenience, key takeaways.

After gathering your connection name, subnet mask, and default gateway, you can set a static IP address in the terminal using the nmcli command. Or, in the GNOME desktop, open your connection settings and click the + icon, then enter the info for your static IP address there.

Your home network relies on IP addresses to route data between devices, and sometimes on reconnecting to the network a device's address can change. Here's how to give an Ubuntu Linux computer a permanent IP address that survives reboots.

Everything on your network home network, whether it's using a wired connection or Wi-Fi, has an IP address . IP stands for Internet Protocol. An IP address is a sequence of four numbers separated by three dots. Each IP address that is unique within that network.

IP addresses act as numeric labels. Your router uses these labels to send data between the correct devices. Usually, your router assigns IP addresses. It knows which IP addresses are in use and which are free. When a new device connects to the network, it requests an IP address and the router allocates one of the unused IP addresses. This is called DHCP, or dynamic host configuration protocol .

When a device is restarted or powered off and on, it may receive its old IP address once more, or it might be allocated a new IP address. This is normal for DHCP and it doesn't affect the normal running of your network. But if you have a server or some other computer that you need to be able to reach by its IP address, you'll run into problems if its IP address doesn't survive power downs or reboots.

Pinning a specific IP address to a computer is called allocating a static IP address . A static IP address, as its name suggests, isn't dynamic and it doesn't change even if the computer is power-cycled .

Nmcli is the command-line network manager tool , and can be used to change your IP address, configure network devices, and --- relevant to our purposes --- set up a static IP in Ubuntu.

We're demonstrating this technique on Ubuntu 22.04 LTS, but it ought to work on any Linux distribution, including Ubuntu 23.04. The nmcli tool was released in 2004, so it should be present on just about any standard distribution.

Let's take a look at the network connections that already exist on the computer. We're using the connection command with the show argument.

nmcli connection show

This displays some information about each connection. We only have a single connection configured.

The details of a single network connection displayed by nmcli

The output is wider than the terminal window. This is the information that we're shown.

Name	UUID	TYPE	DEVICE
netplan-enp0s3	1eef7e45-3b9d-3043-bee3-fc5925c90273	ethernet	enp0s3

Name : Our network connection is called "netplan-enp0s3."
UUID : The universally unique identifier Linux uses to reference this connection internally.
Type : This is an ethernet connection.
Device : This connection is using the "enp0s3" network interface. It's the only network card in this computer.

We can use the ip command to discover the IP address this computer is using.

The output of the ip addr command showing the ip address of the computer

In the output we can see the "enp0s3" entry, and its current IP address, 192.168.86.117. The "/24" is a shorthand way of saying that this network uses a 255.255.255.0 subnet mask . Take a note of this number, we'll need to use it later.

We need to choose the IP address we're going to set as our static IP address. Obviously, you can't use an IP address that is already in use by another device. One safe way to proceed is to use the current IP address assigned to the Ubuntu system. We know for certain that nothing else is using that IP address.

If we want to use a different IP address, try pinging it. We're going to test whether IP address 192.168.86.128 is in use. If everything else on your network uses DHCP and you get no response to the ping command, it should be safe to use.

ping 192.168.86.128

Using ping to determine if an IP address is in use

Even if another device had previously used that IP address, it'll be given a new IP address when it next boots up. Nothing responds to the ping requests, so we're clear to go ahead and configure 192.168.86.128 as our new static IP.

We also need to know the IP address of your default gateway , which will usually be your broadband router. We can find this using the ip command and the route option, which we can abbreviate to "r."

Using the ip command to find the IP address of the default gateway

The entry that starts with "default" is the route to the default gateway. Its IP address is 192.168.86.1. Now we can start to issue commands to set up our static IP address.

The first command is a long one.

sudo nmcli con add con-name "static-ip" ifname enp0s3 type ethernet ip4 192.168.86.128/24 gw4 192.168.86.1

Creating a new connection with the nmcli command

Taken in small chunks, it's not as bad as it looks. We're using sudo . The nmcli arguments are:

con : Short for "connection."
add : We're going to add a connection.
con-name "static-ip" : The name of our new connection will be "static-ip."
ifname enp0s3 : The connection will use network interface "enp0s3."
type ethernet : We're creating an ethernet connection.
ip4 192.168.86.128/24 : The IP address and subnet mask in classless inter-domain routing notation . This is where you need to use the number you took note of earlier.
gw4 192.168.86.1 : The IP address of the gateway we want this connection to use.

To make our connection a functioning connection, we need to provide a few more details. Our connection exists now, so we're not adding anything, we're modifying settings, so we use the mod argument. The setting we're changing is the IPv4 DNS settings. 8.8.8.8 is the IP address of Google's primary public DNS server , and 8.8.4.4 is Google's fallback DNS server.

Note that there is a "v" in "ipv4." In the previous command the syntax was "ip4" without a "v." The "v" needs to be used when you're modifying settings, but not when adding connections.

nmcli con mod "static-ip" ipv4.dns "8.8.8.8,8.8.4.4"

Using the nmcli command to set the DNS servers for a connection

To make our IP address static, we need to change the method which the IP address obtains its value. The default is "auto" which is the setting for DHCP. We need to set it to "manual."

nmcli con mod "static-ip" ipv4.method manual

Using the nmcli command to set an IP address to static

And now we can start or "bring up" our new connection.

nmcli con up "static-ip" ifname enp0s3

Using the nmcli command to start a network connection

We didn't get any error messages which is great. Lets use nmcli to look at our connections once more.

nmcli con show

The details of two network connections displayed by nmcli

Here's the output:

NAME	UUID	TYPE	DEVICE
static-ip	da681e18-ce9c-4456-967b-63a59c493374	ethernet	enp0s3
netplan-enp0s3	1eef7e45-3b9d-3043-bee3-fc5925c90273	ethernet	--

Our static-ip connection is active and using device "enp0s3." The existing connection "netplan-enp0s3" is no longer associated with a physical network interface because we've pinched "enp0s3" from it.

Click the icons at the far-right end of the system bar to show the system menu, then click on the "Wired Connected" menu option. If you're using a wireless connection, instead click the name of your Wi-Fi network.

The available connections are displayed. A dot indicates which is in use. Click the "Wired Settings" or "Wi-Fi Settings" menu option. The details of the active connection are displayed.

If you followed our previous instructions the new connection will be the active connection. We can see our new "static-ip" connection has the IP address, default gateway, and DNS servers that we set for it.

The system menu with the "Wired Connected" pane expanded

To create a new connection using the "Settings" application, click the " + " icon on the "Networks" page, above the list of wired connections.

The wired connection section in the Network tab of the Settings app

A dialog appears. We need to provide a name for our new static IP connection.

We're calling our new connection "static-2." Click the "IPv4" tab.

Select the "Manual" radio button, and complete the "Address", "Netmask", and "Gateway" fields. Also complete the DNS field, and then click the green "Apply" button. Note the comma between the DNS entries.

Our new connection is listed in the "Wired" connections pane.

A newly-added connection in the wired connection section of the Network tab of the Settings app

You can swap between the available connections by clicking directly on their names.

If you want to modify a connection after you create it, click the cog icon. In this case, we'll enter the settings for the "static-ip" connection.

A dialog box opens. Click on the "IPv4" tab.

The IPv4 tab of the connection settings dialog

Because we set our new IP address to be static, the "Manual" radio button is selected. You could change this back to DHCP by selecting the "Automatic (DHCP)" radio button, and clicking the green "Apply" button.

Using the nmcli command or the GNOME desktop and apps, you can hop between network connections very easily and very quickly.

It's more convenient to have a selection of connection profiles and move between them as you need to, rather than to have one that you keep editing. If something goes horribly wrong with the connection you're editing or adding, you can always fall back on one of the existing connections.

How to Configure static IP address in Ubuntu Server 18.04 LTS

When you install Ubuntu Server 18.04, it will grab a dynamically assigned IP address from your DHCP server, But you cannot run a server with dynamic IP addresses. So it's important to assign a permanent static IP address in place right away.

When it comes to Ubuntu network interface configuration, the way in which you set a static IP has completely changed. The previous LTS version Ubuntu 16.04 used /etc/network/interfaces file to configure static IP addresses, but Ubuntu 18.04 use new method known as netplan.

In this tutorial we will learn how to configure network interfaces in Ubuntu server 18.04 Bionic Beaver with netplan. We will look at how to set static IP addresses, default gateway and DNS name servers.

Identify available network interface with ip command.
Netplan and YAML format interface configuration file.
Assigning static IP addresses (IPv4).
Configure static IPv6 Addresses on Ubuntu Server.
Assign multiple IP addresses to a single network interface.
Configure Multiple network interfaces.

Identify available network interface with ip command

Before configure static IP address, you need to identify the available network interfaces on your Ubuntu server 18.04 and what is the device ID assigned to a particular network interface.

If you run ip link show command it will list all available network interfaces on your server.

Identify available network interface with ip command

To view current IP configuration, run the ip addr command:

The output will display the currently assign IP configuration for all network interfaces.

Netplan and YAML format interface configuration file

the way in which you set a static IP has completely changed. Ubuntu 18.04 uses a new method called netplan. In netplan the interface configuration file resides in the /etc/netplan directory and configuration file have .yaml extension. YAML syntax is very easy to understand and you don't need to be an expert on yaml format to edit the interface file. You only need to know what is needed for the network configuration.

If you list the content of the /etc/netplan directory, you will see the interface configuration file with yaml extension.

In netplan the interface configuration file resides in the /etc/netplan directory and configuration file have .yaml extension

In my Ubuntu server name of the file is 50-cloud-init.yaml, but it could be saved with a different name depends on the Install Type.

Install Type	Interface file name
Ubuntu server Live ISO/Cloud	50-cloud-init.yaml
Ubuntu Server ISO (Alternative Ubuntu Server installer)	01-netcfg.yaml
Ubuntu Desktop ISO	01-network-manager-all.yaml

On my Ubuntu server content of the file looks like following:

By just looking at the last line: "dhcp4: yes", we can say that the ethernet interface enp0s3 has been configured to lease IP address from the DHCP Server. So this the configuration you need to have if you are planning to assign dynamic IP addresses from a DHCP server.

Assigning static IP addresses (IPv4)

Here is the sample netplan configuration file with static IP Assignment (IPV4), In this configuration, interface enp0s3 has been configured with IP 192.168.1.100 and the default gateway of 192.168.1.1.

In order to apply the configuration, run the netplan command:

Then, run the ip add command to make sure that the changes being applied:

How it works..

In the above example, we configured enp0s3 ethernet interface to use static the IP address 192.168.1.100.

The first line:"version: 2" indicate this configuration block use netplan version 2 format.

The next line: "renderer: networkd" tells that this interface is managed by the systemd-networkd service.

An alternative option to networkd is NetworkManager, if the interface is managed by the NetworkManager. If you looked at the netplan config file of the Ubuntu 18.04 desktop, the renderer option is set to NetworkManager, because in a graphical desktop environment interfaces are managed by the NetworkManager.

Next, we start the interface configuration:

Here, enp0s3 is the name of the interface, you can run ip link show command to list network interfaces on your Ubuntu server.

Next, we set the static IP to 192.168.1.100 with the netmask of 24:

The address option can be also defined in following format:

Next, we set the default gateway to 192.168.1.1:

We used the option gateway4 because this is IPv4 gateway, For IPv6 gateway we need to use gateway6 option.

Next, we set the DNS servers to 8.8.8.8 and 4.4.4.4.

To apply new interface configurations, we run the netplan command :

The command will Apply current netplan config to running system. We no longer need to do network restart to apply changes.

Configure static IPv6 Addresses on Ubuntu Server

The same netplan format use to assign IPv6 address, only difference is , we need to use the gateway6 option instead of gateway4 .

Assign multiple IP addresses to a single network interface

It is very common to have a single network interface configured with more that one IP address. Following is the sample Ubuntu netplan config file with two IPv4 address assigned to one network interface.

The address option can be also written in following format:

A single network interface can be configured with both IPv4 and IPv6 addresses as shown in the following netplan file:

Configure Multiple network interfaces

It is very common to install more that one network interface on a single server. Here's an example netplan file, configured with static addresses for two network cards:

Note that only the primary interface has been configured with a default gateway, In this case it is enp0s3. It is not practical to have more than one default gateway, the default gateway is the address you send traffic when you have no other route for it.

Let's look at another netplan example where both static and DHCP addresses being used:

In the preceding example, the wifi interface wlp3s0 has been configured to lease IP address from the DHCP server.

In this tutorial we learned how to configure static IP address on Ubuntu 18.04 Bionic Beaver, where the old /etc/network/interfaces file is no longer in used. Ubuntu 18 now uses the new method called netplan to manage networking.

With Netplan, configuration files for the network interfaces reside in the /etc/netplan directory, in YAML data format, while the netplan command uses to restart networking after configuration changes.

Setting a Static IP in Ubuntu – Linux IP Address Tutorial

In most network configurations, the router DHCP server assigns the IP address dynamically by default. If you want to ensure that your system IP stays the same every time, you can force it to use a static IP.

That's what we will learn in this article. We will explore two ways to set a static IP in Ubuntu.

Static IP addresses find their use in the following situations:

Configuring port forwarding.
Configuring your system as a server such as an FTP server, web server, or a media server.

Pre-requisites:

To follow this tutorial you will need the following:

Ubuntu installation, preferably with a GUI.
sudo rights as we will be modifying system configuration files.

How to Set a Static IP Using the Command Line

In this section, we will explore all the steps in detail needed to configure a static IP.

Step 1: Launch the terminal

You can launch the terminal using the shortcut Ctrl+ Shift+t .

Step 2: Note information about the current network

We will need our current network details such as the current assigned IP, subnet mask, and the network adapter name so that we can apply the necessary changes in the configurations.

Use the command below to find details of the available adapters and the respective IP information.

The output will look something like this:

For my network, the current adapter is eth0 . It could be different for your system

Note the current network adapter name

As my current adapter is eth0 , the below details are relevant.

It is worth noting that the current IP 172.23.199.129 is dynamically assigned. It has 20 bits reserved for the netmask. The broadcast address is 172.23.207.255 .

Note the subnet

We can find the subnet mask details using the command below:

Select the output against your adapter and read it carefully.

Based on the class and subnet mask, the usable host IP range for my network is: 172.23.192.1 - 172.23.207.254 .

Subnetting is a vast topic. For more info on subnetting and your usable IP ranges, check out this article .

Step 3: Make configuration changes

Netplan is the default network management tool for the latest Ubuntu versions. Configuration files for Netplan are written using YAML and end with the extension .yaml .

Note: Be careful about spaces in the configuration file as they are part of the syntax. Without proper indentation, the file won't be read properly.

Go to the netplan directory located at /etc/netplan .

ls into the /etc/netplan directory.

If you do not see any files, you can create one. The name could be anything, but by convention, it should start with a number like 01- and end with .yaml . The number sets the priority if you have more than one configuration file.

I'll create a file named 01-network-manager-all.yaml .

Let's add these lines to the file. We'll build the file step by step.

The top-level node in a Netplan configuration file is a network: mapping that contains version: 2 (means that it is using network definition version 2).

Next, we'll add a renderer, that controls the overall network. The renderer is systemd-networkd by default, but we'll set it to NetworkManager .

Now, our file looks like this:

Next, we'll add ethernets and refer to the network adapter name we looked for earlier in step#2. Other device types supported are modems: , wifis: , or bridges: .

As we are setting a static IP and we do not want to dynamically assign an IP to this network adapter, we'll set dhcp4 to no .

Now we'll specify the specific static IP we noted in step #2 depending on our subnet and the usable IP range. It was 172.23.207.254 .

Next, we'll specify the gateway, which is the router or network device that assigns the IP addresses. Mine is on 192.168.1.1 .

Next, we'll define nameservers . This is where you define a DNS server or a second DNS server. Here the first value is 8.8.8.8 which is Google's primary DNS server and the second value is 8.8.8.4 which is Google's secondary DNS server. These values can vary depending on your requirements.

Step 4: Apply and test the changes

We can test the changes first before permanently applying them using this command:

If there are no errors, it will ask if you want to apply these settings.

Now, finally, test the changes with the command ip a and you'll see that the static IP has been applied.

How to Set a Static IP Using the GUI

It is very easy to set a static IP through the Ubuntu GUI/ Desktop. Here are the steps:

Search for settings .
Click on either Network or Wi-Fi tab, depending on the interface you would like to modify.
To open the interface settings, click on the gear icon next to the interface name.
Select “Manual” in the IPV4 tab and enter your static IP address, Netmask and Gateway.
Click on the Apply button.

Verify by using the command ip a

In this article, we covered two methods to set the static IP in Ubuntu. I hope you found the article useful.

What’s your favorite thing you learned from this tutorial? Let me know on Twitter !

You can read my other posts here .

I am a DevOps Consultant and writer at FreeCodeCamp. I aim to provide easy and to-the-point content for Techies!

If you read this far, thank the author to show them you care. Say Thanks

Learn to code for free. freeCodeCamp's open source curriculum has helped more than 40,000 people get jobs as developers. Get started

Configure Static IP Address on Ubuntu 22.04|20.04|18.04

In today’s guide, we are going to see how to configure a static IP address on Ubuntu server 22.04|20.04|18.04. After installing Ubuntu 22.04|20.04|18.04 Server or Desktop, the default setting it to obtain an IP address automatically via DHCP server. This means that you will have to configure a Static IP address Manually.

Method 1: Manually edit Network Configuration files

In this example, we’ll use vim editor and configure our server to use the IP address of 10.10.1.5 , netmask 255.255.255.0 , dns server 8.8.8.8 and default gateway being 10.10.1.1.

Open /etc/network/interfaces

Then add the following lines replacing with your IP information.

For the changes to take effect, restart your network daemon by

Don’t forget to replace eth0 with your network card name.

Check that you have an ip address on eth0 interface by typing

Method 2: Use Netplan YAML network configuration

On Ubuntu 22.04|20.04|18.04, you can use Netplan which is a YAML network configuration tool to set static IP address.

This configuration assumes your network interface is called eth0 . This may vary depending on your working environment.

Then configure like below.

When done making the changes, save the configuration file and apply your network settings.

To confirm your network settings, use the command:

If you don’t need IPv6, it’s possible to disable it like follows.

YOU CAN SUPPORT OUR WORK WITH A CUP OF COFFEE

As we continue to grow, we would wish to reach and impact more people who visit and take advantage of the guides we have on our blog. This is a big task for us and we are so far extremely grateful for the kind people who have shown amazing support for our work over the time we have been online.

Setting a Static IP Address in Ubuntu 18.04

This guide will show you the simple steps of setting a static IP address on Ubuntu 18.04.

When your device first connects to your router, the DHCP (Dynamic Host Configuration Protocol) of your router will assign it an IP address.

Typically this IP address will be automatically be assigned to your device from a pool.

While some routers try to hand the same IP to the same device every restart, it is something that is never guaranteed.

There are two primary ways to work around the dynamic IP allocation behavior of your router.

Reserving a static ip address using dhcp, requesting a static ip address, identifying the network interface name, using netplan to define a static ip address, setting a static ip address using the desktop interface.

The first way of assigning a static IP address is to make use of something called DHCP reservation.

DHCP reservation is typically the best way of setting a static IP address for your Ubuntu 18.04 device.

It is not specific to your OS and will guarantee that the router doesn’t give the IP to a different device.

When your device connects to your router, it will ask for an IP address while exposing your network interface’s MAC address.

The router will then check to see if an IP has been reserved for that MAC address. If it has been reserved, the router will give that IP to your device.

Assigning an IP address to Ubuntu 18.04 using DHCP Reservation Diagram

To configure DHCP reservation, you will need to utilize your router settings.

As the configuration for this will differ significantly between routers, we recommend consulting your model’s documentation.

You should note that your Wi-Fi and Ethernet connections are assigned two different MAC addresses. To retain the reserved IP address, you will need only to use one network interface.

The alternative way is to adjust your device to request a specific IP address from your router’s DHCP server.

When the device connects to the router, it will say that it wants to utilize a specific IP address.

If that IP address is available from the pool, it will be assigned to your Ubuntu 18.04 device.

Ubuntu 18,04 Requesting a Static IP Address

The biggest drawback of this method is that the IP address is never guaranteed to be available. The router can easily assign the IP to another device as it isn’t reserved.

If the assignment fails, then the device will fail to connect to the network.

It will not fall back to retrieve an IP address from the router’s pool

In the next few sections, we will show how to set Ubuntu 18.04 to request a specific IP address from the router.

Setting a Static IP Address on Ubuntu Server 18.04

This section is going to show you how to set a static IP address on Ubuntu server 18.04.

Since the Ubuntu server operating system has no desktop interface, we will need to handle all of this using its terminal interface.

Ubuntu 18.04 makes use of something called “ Predictable Network Interfaces Name ” by default.

Predictable interface names were designed to make it easier to know what name a network device would be assigned.

For example, we know that an ethernet interface will always start with en .

Likewise, a wireless network interface would have a name that starts with the text wl .

1. To get a list of our network interfaces on Ubuntu Server 18.04, we need to use the ip command.

Please run the following command on your device to list all of its currently active network interfaces.

2. Using the ip link command, you should end up seeing something like we have below.

From our example you can see we have two network devices.

The first device identified by the name “ lo ” is the loopback device, which you can ignore safely.

Our second device is the one we are after and has the name “ enp0s3 “. This device is our computer’s ethernet network interface.

3. Before proceeding, make sure that you make a note of your network interface’s name.

In our case, this will be “ enp0s3 “, but yours will likely be different.

To set a static IP address on Ubuntu server 18.04, we will need this network interface name.

Ubuntu Server 18.04 makes use of a network management tool called Netplan .

We will need to modify settings for Netplan so that it attempts to utilize the IP we set when it connects to the router.

1. Our first task will be to see what config files came with our installation of Ubuntu server 18.04.

Use the following ls command to list the files that sit in the “ /etc/netplan/ ” directory.

From this list, identify the configuration file containing your network interface’s settings.

In our case, this file was called “ 01-netcfg.yaml “, but there is a chance that it has a different name, such as “ 50-cloud-init.yaml “.

If no files exist within this directory, continue this tutorial as is. By the end, you should have a basic configuration setup.

2. To edit the Netplan configuration, we will make use of the nano text editor .

Make sure you swap out the filename we are using with the one you identified in the previous step.

3. Within this file, you should see something similar to what we have below.

This bit of text is what tells Netplan how it should be handling the connection.

Let us give you a quick rundown so that you get an idea of how these settings work.

network: – To configure network devices, the file must start with the network: block.

All of the configuration details for our network will be placed under this block.

version: – We can use “ version: ” to tell Netplan what configuration markup we are using.

In our case, this value will be 2 , which is the current standard at the time of publishing.

renderer: – Using this option, you can define what backend will handle the connection.

There are only two possible settings for this, the default, which is networkd and NetworkManager .

ethernets: – Underneath this block is where you will define all of the settings for your ethernet interfaces.

If you are utilizing a wireless connection, you might see the text “ wifis ” instead of “ ethernets “.

enp0s3: – Using our network interface name defines a new block where we can set options specific to that device.

Remember that this device might be called something different and will not exactly match what we have specified.

dhcp4: – Using this option, we can turn on or off our network interface automatically fetching an IP address from the router.

At the moment, you can see this option is set to yes . W will disable this option to make Ubuntu 18.04 utilize a static IP address.

Please note that if you are using IPv6 , this will be referenced as dhcp6 instead.

4. We now need to modify this configuration file so that Ubuntu 18.04 will fetch a static IP address.

When editing this file, remember that indentation is important. Something that resides within a block needs to have an additional two spaces from the previous block.

For example, the “ ethernets: block is spaced two spaces in from the start of the “ network: ” block.

a. First, we need to disable our network interface from interacting with the DHCP server.

To disable the DHCP functionality, you need to change the “ dhcp4: ” value from “ yes ” to “ no “.

b. Next, we can define the static IP address for your Ubuntu 18.04 computer.

To do this, we need to add a new “ addresses: ” option.

Next to this option, we need to specify each of the IPs you want to assign to your device.

These IP addresses need to be wrapped in square brackets ( [ ] ), with each separate IP separated by a comma ( , ).

In our example below, we are going to be assigning our network interface the IP 192.168.0.123 .

c. As we have disabled the DHCP functionality, we will need to use the “ gateway4: ” option to define the gateway address.

Typically the gateway address will be the internal IP address of the router your device is connected to.

If you are using IPv6, you will need to use the option “ gateway6: ” as well.

For our example, our router is accessible from the 192.168.1.1 address.

d. The last thing we need to define the nameservers that we want to use for the server.

As “ nameservers ” is its own block, we need to add the following line before defining the DNS IPs.

e. Within this block, we need to define the nameservers that we want to connect to by using the “ addresses: ” option.

As this option sits within the “ nameservers: ” block, it needs an additional two spaces.

Like with IP addresses, these need to be wrapped in square brackets ( [ ] ) with each nameserver separated by a comma ( , ).

For our example, we will be using Google’s DNS servers, those two IP addresses being “ 8.8.8.8 ” and “ 8.8.4.4 “.

5. By the end of this section, your configuration should end up looking a bit like what we have below.

Once you have finished editing the config file, you can save it by pressing CTRL + X , followed by Y , then the ENTER key.

6. Since we made changes to the configuration file, we will need to get Netplan to apply them.

To apply the changes, we need to run the following command.

7. You can verify that the Ubuntu 18.04 operating system uses your static IP address using the ip command.

Using the ip command, we can list all of the addresses that have been assigned to our network interface.

From this command, you should end up finding a result for your ethernet device.

Above, you can see that our value for inet is now the static IP address that we set within the configuration file.

This section will show you how to set a static IP address while using the desktop version of Ubuntu 18.04.

This process is more straightforward than the one needed for the server edition of Ubuntu, as it’s done purely through the settings interface.

1. Before we can set a static IP address, we need to get to the settings screen.

While using the desktop interface, click the right side of the taskbar where the sound, power, and network icons are.

Finding the Desktop Settings Dropdown Box

2. In the drop-down box that appears, you should see an icon with a wrench and spanner.

You need to click this icon to open up the settings page.

3. Now that we have the settings page opened, we need to change to the networking tab.

Find and click the “ Networking ” option in the left-hand sidebar.

4. On this screen, you should see a list of your network interfaces.

Identify the one you are using for your internet connection and click the cog next to it.

5. Next, we need to change to the IPv4 tab.

Find IPv4 in the menu bar of the current window and click it.

Please note that if you are using IPv6, you should change to that tab instead.

6. Finally, we are in the right menu on Ubuntu 18.04 to set a static IP address.

There are several things you will need to do on this screen.

First, you need to change the DHCP mode from automatic to manual ( 1. ).

Once in manual mode, you will need to define the address ( 2. ), netmask ( 3. ), and gateway ( 4. ).

Address – This is the IP address you want to be assigned when your computer connects to the network.

Netmask – The netmask is used to divide an IP address into subnets. In our case, we will be using the netmask “ 255.255.255.0 ” to put us in the last subnet.

Gateway – You need to set the gateway to the local IP address where your router sits. The gateway is where your device connects through to reach the rest of the network.

Once you have set all three of these values, click the “ Apply ” button ( 5. ) in the window’s top right corner.

Setting a Static IP address with Ubuntu Desktop 18.04

7. To ensure everything is working as it should be, restart your device.

Once it has restarted you can verify the IP address that it has been assigned by opening up the terminal.

The easiest way to open up the terminal when running Ubuntu 18.04 is to use CTRL + ALT + T .

8. Within the terminal, run the following command to show the status of all of your configured network devices.

If everything has worked correctly you should see your IP address listed as inet YOURSTATICIPADDRESS .

Hopefully, you now will have set up your Ubuntu 18.04 installation with a static IP address.

If you have had any issues with getting your installation to utilize a static IP address, please leave a comment below.

Be sure to check out some of our other Linux or Ubuntu tutorials .

Receive our Raspberry Pi projects, coding tutorials, Linux guides and more!

Thank you for subscribing

Netplan – How To Configure Static IP Address in Ubuntu 18.04 using Netplan

The first task for anyone after the installation of Ubuntu will be setting up an IP address to a system. In some cases, these tasks are taken care using DHCP (Dynamic Network Configuration Protocol) which handles assigning IP Address to Desktop and Servers.

But, if you look at the bigger infrastructure, they use static IP to avoid network problems due non-availability of DHCP server .

READ : How to configure DHCP server on CentOS 7 / Ubuntu 18.04 / 16.04 / Debian 9

Here, we will see how to configure static IP Address in Ubuntu 18.04 with netplan – new network configuration tool .

Also, at later of the article, we will take a look at how to use ifupdown ( /etc/network/interfaces / Network Manager ) for assigning static IP Address in Ubuntu 18.04 .

Prerequisites

Switch to the root user.

Find the available network cards on your system

You can run any one of the below commands in the terminal to get a list of network interfaces available on your system.

Choose the desired network interface

The output of the ifconfig command:

inet 192.168.1.6 netmask 255.255.255.0 broadcast 192.168.1.255

At this time, the system interface ( enp0s3) takes IP Address from DHCP server.

My laptop WiFi interface has not been connected to WiFi router. Hence, there is no IP address assigned to it.

For this demo, we will configure a static IP for enp0s3 / wlx7c8bca0d69b6 .

IP Address = 192.168.1.100 Netmask = 255.255.255.0 GATEWAY=192.168.1.1 DNS Server 1 = 192.168.1.1 DNS Server 2 = 8.8.8.8 Domain Name = itzgeek.local

Configure Static IP Address using Netplan

Netplan is a new network configuration utility that was introduced in Ubuntu 17.10 that reads the YAML file and generates all the confirguration for renderer tool ( NetworkManager or networkd ).

Netplan reads network configuration from /etc/netplan/*.yaml .

First, remove the ifupdown package so that we can use netplan to configure network interfaces.

In Ubuntu 18.04 server, cloud-init manages the network configuration. So, you would need to disable it by editing the below file.

Put the below line into the configuration file.

Move any files present in /etc/netplan directory to other location.

Now, we will create a netplan configuration for the network interface. I recommend you to use vim apt install vim editor for auto syntax.

Use the below configuration file.

To use NetworkManager, you would need to install the Network Manager sudo apt install network-manager and then use renderer: NetworkManager in the netplan configuration file.

wlx7c8bca0d69b6 – Wifi interface device name Raj – My Wifi SSID MyPass – Wifi Password

Generate the required configuration for the renderers.

Apply all configuration and restart renderers.

Verify Static IP Address

Verify the static IP using the below commands.

Also, verify the DNS servers entries.

Configure Static IP Address using ifupdown / Network Manager

Install the below packages using apt command to support the old method of configuring static IP address to systems.

Edit the interfaces file.

Update the file with below information.

# Interface Name #

# IP Address #

# Netmask #

# Gateway #

# DNS Servers #

Restart the networking using the following command.

For assigning an IP address to Wifi interface, use the Gnome Network Manager.

Click on your Wifi router name and then enter the router’s password to connect. On successful connection, your laptop would automatically receive an IP address from Wifi router which has built-in DHCP service.

If you want to assign static, click on the gear icon in WiFi settings page.

Go to IPv4 tab and enter the IP address details shown like below. Finally, click Apply .

That’s All.

How To Install MySQL 8.0 on Ubuntu 18.04 LTS (Bionic Beaver)

How To Install And Set Up KVM On Ubuntu 18.04 LTS / Ubuntu 17.10

How to Set a Static IP Address On Ubuntu 22.04

How To Install PHP 8.1 on Ubuntu 20.04 / Ubuntu 18.04

How To Install Nvidia Drivers On Ubuntu 20.04 / Ubuntu 18.04

Install Zoom Client On Ubuntu 20.04/18.04 & Linux Mint 20/19

How To Install Jenkins on Ubuntu 20.04 / Ubuntu 18.04

How To Backup and Restore Ubuntu & Linux Mint With Timeshift

CentOS 8 / RHEL 8
CentOS 7 / RHEL 7
CentOS 6 / RHEL 6
LinuxMint 20
Linux Mint 19
Linux Mint 18
Rocky Linux 8
Ubuntu 22.04
Ubuntu 20.04
Ubuntu 18.04
MySQL / MariaDB
Other Tools

Stack Exchange Network

Stack Exchange network consists of 183 Q&A communities including Stack Overflow , the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

How to setup a static IP on Ubuntu Server 18.04

I've seen some people saying the file to set static ip is still /etc/network/interfaces

And I've seen other people saying that in 18.04 it's now on /etc/netplan (which people seem unhappy about)

I've tried putting this:

In my /etc/netplan/50-cloud-init.yaml and doing sudo netplan apply but that just kills the servers connection to the internet.

1 Is it a desktop or a server? – user68186 Commented Apr 29, 2018 at 5:10
1 Is this a fresh 18.04 install or upgrade from another version? – WinEunuuchs2Unix Commented Apr 29, 2018 at 5:16
Sorry I should've said this in the text, its a fresh install of 18.04 server. – final20 Commented Apr 29, 2018 at 5:25
The most simple solution for me was, to specify a static IPv4 address right during installation (together with subnet, gateway, etc.). Simply fill out some wizard fields, no messing with configuration files. – Uwe Keim Commented Oct 9, 2018 at 10:01
You can also do this on routers. Steps are self-explanatory in the router config. – EODCraft Staff Commented Jan 12, 2019 at 10:25

11 Answers 11

All the answers telling you to directly edit /etc/netplan/50-cloud-init.yaml are wrong since CloudInit is used and will generate that file. In Ubuntu 18.04.2 it is clearly written inside the file :

So you should not edit that file but the one under /etc/cloud/cloud.cfg.d/ if you still want to use CloudInit.

Another way is to completely disable CloudInit first by creating an empty file /etc/cloud/cloud-init.disabled (see https://cloudinit.readthedocs.io/en/latest/topics/boot.html ) and then the other answers are OK. Under Ubuntu 18.04.2 I had to use dpkg-reconfigure cloud-init to let it take into account the file /etc/cloud/cloud-init.disabled . I think this is a little bit weird.

I suggest you to rename the file (not the right name since 50-cloud-init.yaml let us think it still uses CloudInit).

Then you may end up with a file name /etc/netplan/01-netcfg.yaml which contains the configuration below. Note the use of the networkd renderer instead of NetworkManager because the configuration is on a server.

4 It works great. This should be the best answer. 50-cloud-init.yaml as stated shouldn't be modified. – Relic Commented Jun 26, 2019 at 13:11
3 If still using CloudInit, you need to do a sudo cloud-init clean -r to get the change to take, as per veperr's answer (at least for me on Ubuntu Server 18.04.3). – Stuart Rossiter Commented Aug 8, 2019 at 11:59
1 ...plus the renderer line is no longer valid it seems (and is missing in the base version of the file that you edit). – Stuart Rossiter Commented Aug 27, 2019 at 10:26
Simply adding a custom file under /etc/netplan/##-*.yaml works as well. Such as: "/etc/netplan/99-custom-network.yaml". This also follows the netplan.io/examples instructions. In "conf.d" type config areas you should always opt for a custom/new file if possible instead of editing installed package files. It's why we have these "numbered file" areas. These default #'ed files can frequently get overwritten. And YES: If you have a "50-cloud-init.yaml", it should NOT be used. It is system generated as noted in comments. Why people keep posting this as an answer is anyone's guess? – B. Shea Commented Dec 13, 2021 at 15:59
1 Yep. But, you can add it directly to /etc/netplan . Any new files under this area will persist through reboots. I gave you +1 for 1: saying not to edit cloud-init, and 2: Creating a new file in a numbered area (& not editing ANY preexisting/system ones). Note: You do not even necessarily need to disable anything so long as you are updating the same network interface. A higher numbered yaml will override all previous repeated directives (or should). So "50-" will be read in AFTER "01-". If you renamed your file "99-" you wouldn't have to disable "50-" - if that makes sense. See my answer – B. Shea Commented Dec 13, 2021 at 16:34

This is set a static IP instruction in Ubuntu-Server 18.04 and 20.04

Then replace your configuration, for example, the following lines:, apply changes:.

In case you run into some issues execute:

/24 is equivalent with 255.255.255.0
ens160 is your ethernet name, you can get it using $ ifconfig
Ubuntu 16.04 and 14.04 network-interface configuration have a different method.
The file is in YAML format : Use spaces, no tabs.

not able to ping after assigning static IP address – gjois Commented Mar 3, 2019 at 14:55
OK....I'm able to ping after doing service networking restart – gjois Commented Mar 3, 2019 at 15:42
7 I wouldn't do that since that file is generated by CloudInit – Ludovic Kuty Commented Mar 13, 2019 at 7:48
only works if your ethernet is "ens160", check your ethernet "ls /sys/class/net/" and replace "ens160" with it. – sailfish009 Commented Mar 17, 2020 at 3:40
@sailfish009 I mentioned it before in the NOTE section in my answer. – Benyamin Jafari Commented Mar 17, 2020 at 6:11

I've found another way using cloud-init.

Edit the file /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg - the contents seem to be the same as they would be in /etc/netplan.

clean, reboot and re-initialize cloud-init with this command:

That's it! Your system will reboot, cloud-init will re-initialize and pickup the change in /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg and apply them to /etc/netplan/50-cloud-init.yaml and all will be well. Verify with ifconfig .

1 2 things. -> 1. Better to create your own "99-myconfig.cfg" file under /etc/cloud/cloud.cfg.d/ so it's read in last and will overwrite any previous configs and will not be overwritten by possible system updates. 2. ifconfig is defunct . Use ip command now. For example ip addr will show same thing as ifconfig use to. – B. Shea Commented Dec 7, 2021 at 16:11

Ubuntu 18.04 uses now Netplan to configure the network interfaces, so the configuration must be done in the file /etc/netplan/50-cloud-init.yaml , the documentation advises not to mess anymore with the old file /etc/network/interfaces . I have used this configuration with my Ubuntu Server virtual machine and it works so far, just make sure the info is correct; the optional: true setting supposedly speeds up the booting time by not verifying if the interface is connected or not, this is default, also there is no need to declare values not used, for example DHCP, if they are absent they are taken as disabled, also the default renderer in Ubuntu Server is networkd so there is no need to declare it. Taking the information from your post, it should be like this:

Once you save the file, run sudo netplan --debug apply the debug flag will output more info and can help to detect any errors. Check the ethernet cable, if in virtual review the VM configuration. If using a WLAN I have read that it is a bit more tricky to setup but I haven't yet set up a machine connected to WiFi with this server version.

If you want more info about Netplan there is a website, it has some basic configuration examples.

https://netplan.io/

1 Wrong. DO NOT EDIT 50-cloud-init.yaml , or any existing system generated files! – B. Shea Commented Dec 13, 2021 at 16:40

Config file is in YAML format : Don't use TAB when configuring the file. It only works with SPACE .

Writing a new answer as so many are just wrong.

Do not edit 50-cloud-init.yaml , 00-installer-config.yaml or ANY system generated files/package files.

From https://netplan.io/examples/ :

"To configure netplan, save configuration files under /etc/netplan/ with a .yaml extension (e.g. /etc/netplan/config.yaml) .."

The installer/ system did that. Now you need to override it.

Also consult man netplan-generate for the rules governing how the network configurations are read from /etc/netplan/*.yaml (and elsewhere).

To correctly update the netplan area to use a static IP over the default DHCP:

Edit/Create a new file (the prepended number+dash and .yaml extension are important):

sudo nano /etc/netplan/99-custom-network.yaml

Add your properly formatted YAML to this file. A static IP example:

(Note: My network device is ens160 - not eth0 - adjust as needed.) Save. Then do a sudo netplan apply . Make sure your network interface looks right and is working ( ip ad / ping ). Then do a reboot. Retest.

This follows the netplan.io instructions as well as the general rule of not editing any existing/installed files when possible. In /etc/netplan/ and similar conf.d/ type config areas you should always opt for a high numbered custom/new file (if possible) instead of editing any installed package files.

It's why they have numbered files in these configuration areas (in /etc/netplan/ and others). The higher the number on the file equates to when it is read in.

Therefore, something with "99-" prepended on it will generally be read in last and OVERRIDE anything that repeated before it. Therefore, if a network interface is set to DHCP in "00-installer-config.yaml", and/or "50-cloud.init.yaml", the settings for the same interface in a "99-*.yaml" file will override everything else read in previously.

Generally these installed YAML files will NOT get overwritten, but that isn't valid logic to not follow the conf.d "standard" of using custom files to override and avoid editing any installed files. It doesn't take any extra time. Drop a file in netplan. Done. So, there's no excuse as I have witnessed in comments of "well, it's worked so far..".

So, editing the default netplan *.yaml(s) will technically (usually) "work", but you should avoid using them when possible.

Network configuration in 18.04 is managed via netplan and configured with cloud-init. To change your network configuration edit the 50-curtin-networking.cfg file in /etc/cloud/cloud.cfg.d/ . If this file does not exist then create it.

Find your interface name

Edit / create the cloud-init network configuration file

To set a static IP address, use the addresses key, which takes a list of (IPv4 or IPv6), addresses along with the subnet prefix length (e.g. /24). Gateway and DNS information can be provided as well:

You can find more configuration options at https://netplan.io/examples

Reload the cloud-init configuration. This will reboot your server.

This is the setting what make it work.

restart the server

change eth0 to your adapter, find out your adapter using ifconfig.

1 Wrong. DO NOT EDIT 50-cloud-init.yaml, or any existing system generated files! – B. Shea Commented Dec 13, 2021 at 16:41

To find available ethernet interfaces use ip link show

Then edit the 50-cloud-init.yaml file using $sudo nano /etc/netplan/50-cloud-init.yaml

Add the configuration for available interfaces like eth0: and eth1:

Then use command $sudo netplan apply to apply the changes.

Then edit the 50-cloud-init.yaml file using $sudo vim /etc/netplan/50-cloud-init.yaml

$ sudo netplan apply

1 I wouldn't do that since that file is generated by CloudInit. – Ludovic Kuty Commented Mar 13, 2019 at 7:47
1 Why oh why is every guide to setting a static IP on 18.04 telling me to edit a yaml file that says it is a dynamically created file that will not persist? Another cruel joke from the Ubuntu developers that think it is ok to just break things by default... – Bigtexun Commented Mar 20, 2019 at 18:13
1 Wrong. DO NOT EDIT 50-cloud-init.yaml, or any existing system generated files! – B. Shea Commented Dec 13, 2021 at 16:42
@B.Shea I have 20+ servers running for 4 years with regular upgrades and maintenance. Never once, 50-cloud-init.yaml has been reset or overwritten. For what I have noticed, cloud-init (as the name says) is run once, at server creation and then it won't be automatically reissued again. – Dario Fumagalli Commented Mar 2, 2022 at 3:34
1 @DarioFumagalli Only 4 years? You're using broken logic: Just because nothing "broke" doesn't mean you are doing it the proper way. You should NEVER edit system installed config files if there is a way to avoid it. And there is clearly a way to avoid it in this case.. – B. Shea Commented Mar 2, 2022 at 13:07

This worked for me:

[172.23.4.2/24, ] is the additional thing I did on the yaml file.

Reference: https://serverspace.io/support/help/how-to-configure-static-ip-address-on-ubuntu-18-04/

You must log in to answer this question.

Not the answer you're looking for browse other questions tagged networking server ip 18.04 ..

The Overflow Blog
Community Products Roadmap Update, July 2024
Featured on Meta
We spent a sprint addressing your requests — here’s how it went
Upcoming initiatives on Stack Overflow and across the Stack Exchange network...

Hot Network Questions

Can a country refuse to deliver a person accused of attempted murder?
Lengths of generators of surface group
What is the correct translation of the ending of 2 Peter 3:17?
What spells can I cast while swallowed?
When selling a machine with proprietary software that links against an LGPLv3 library, do I need to give the customer root access?
Weather on a Flat, Infinite Sea
Dual citizenship with USA & South Africa and exited South Africa on wrong passport (USA). What passport do I use to reenter SA?
ForeignFunctionLoad / RawMemoryAllocate and c-struct that includes an array
How can I power both sides of breaker box with two 120 volt battery backups?
When can まで mean "only"?
How to solve the intersection truncation problem of multiple \draw[thick, color=xxx] commands by color？
Changing equation into elliptic curve
Struggling w/ Jesus and Jewish law
Would this telescope be capable to detect Middle Ages Civilization?
Does installing Ubuntu Deskto on Xubuntu LTS adopt the longer Ubuntu support period
How do we define addition?
Has the Supreme Court given any examples where presumptive immunity would be overcome?
Is "necesse est tibi esse placidus" valid classical Latin?
Using 50 Ω coax cable instead of passive probe
Why did the general choose this as the exact time of attack?
firefox returns odd results for file:/// or file:///tmp
Improve spacing around equality = and other math relation symbols
I'm not sure what I damaged in crash. Derailleur? gears?
How to write a module that provides an 'unpublish comment' shortcut link on each comment

Configure Ubuntu Server 18.04 to use a static IP address

Since Ubuntu 17.10 Artful, Netplan has been introduced as the new network configuration utility. This tutorial will show you how to change the IP address from DHCP to static using Netplan.

Table of Contents

Introduction

There will be a file placed in the /etc/netplan folder that’s used to configure the network. You might come across two different filenames depending on what installation media you’ve used. These are:

Ubuntu Server 18.04 server ISO

Ubuntu Server 18.04 cloud image

As you can see by the name above, the cloud image uses cloud-init to configure the network, so we can’t just edit this file because changes might be overwritten. We’ll have to disable network configuration by cloud-init .

How to disable network configuration by cloud-init

Create a new file called:

Add the following to the file:

Rename the netplan config file to the same as the one in the server ISO.

How to change the IP address from DHCP to static on Ubuntu Server 18.04

Open the netplan config file:

You should see a file that looks similar to this:Advertisements

It’s the ethernets section of the file we want to change below the name of your ethernet adapter. On my system it’s enp0s3 . First we want to change dhcp4 to false and then add the static IP config below this. Here’s an example below:

Now apply the config with the following command:

That’s it

Now the server will keep the assigned IP address whenever it’s restarted.

David Miller is a seasoned tech aficionado with a profound expertise in NGINX and Ubuntu. With a career spanning over a decade, David has honed his skills in optimizing web servers and enhancing server performance to perfection. His deep-rooted passion for open-source technologies has led him to become a go-to resource in the field. Whether it’s crafting intricate NGINX configurations or troubleshooting complex Ubuntu server issues, David’s problem-solving prowess shines through.

Customer Login

Windows VPS

Forex VPS Hosting

Dedicated Hosting

Web Hosting

WordPress Hosting

Windows Hosting

Web Hosting For Agencies

Hosting Solutions

Dedicated Servers

Server Deals

Cloud Backup

Servers For Agencies & Reseller

Rent-A-Server

Data Center Designer

Customer References

Cloud Solutions

Compute Engine (IaaS)

Managed Kubernetes

Our Strengths

Data Backup & Disaster Recovery

Digitalization for SMEs

On-Premise vs Cloud Computing

Domain Names

Domain Transfer

SSL Certificate

Data Centers

Personal Consultant

Website Checker

Favicon Generator

SEO Checker

Whois Lookup

SSL Checker

IP Address Checker

Domain Check

Partner Programs

Partner Program

Affiliate Program

Partner Network

Referral Program

Mondoze Knowledge Base

Search our articles or browse by category below.

How to Configure Static IP Address on Ubuntu 18.04
Ubuntu 18.04
1. In this tutorial, we'll explain how to set up a static IP address on Ubuntu 18.04.
2. Configuring Static IP address using DHCP
4. Configuring Static IP address on Ubuntu Server
5. Let's explain the code in a short time before changing the configuration.
6. To assign a static IP address to ens3 interface edit the file as follows:
7. Configuring Static IP address on Ubuntu Desktop
8. Conclusion

In this tutorial, we'll explain how to set up a static IP address on Ubuntu 18.04.

IP addresses are assigned dynamically by your router DHCP server. In different situations such as configuring port forwarding or running a media server on your network, it may be necessary to set a static IP address on your Ubuntu computer.

Configuring Static IP address using DHCP

The easiest and the recommended way to assign a static IP address to a device on your LAN is by setting up a Static DHCP on your router. Static DHCP or DHCP reservation is a feature found on most routers which makes the DHCP server to automatically assign the same IP address to a specific network device, every time the device requests an address from the DHCP server. This works by assigning a static IP to the device unique MAC address. The steps for configuring a DHCP reservation varies from router to router and it’s advisable to consult the vendor’s documentation.

Netplan uses configuration files with YAML syntax. To configure a network interface with Netplan you simply create a YAML description for that interface and Netplan generates the required configuration files for your chosen renderer tool.

Netplan currently supports two renderers NetworkManager and Systemd-networkd. NetworkManager is mostly used on desktop machines, while System-network is used without a GUI on servers.

Configuring Static IP address on Ubuntu Server

The newer versions of Ubuntu uses ‘Predictable Network Interface Names’ that start with en[letter][number] . by default. The first step is to identify the name of the ethernet interface you want to configure. You can use the ip link command as shown below:

The command will print a list of all the available network interfaces. In this case, the name of the interface is ens3 :

Netplan configuration files are stored in the /etc/netplan directory and have the extension .yaml . You’ll probably find one or two YAML files in this directory. The file may differ from setup to setup. Usually, the file is named either 01-netcfg.yaml , 50-cloud-init.yaml or NN_interfaceName.yaml , but in your system it may be different.

Open the YAML configuration file with your text editor:

Let's explain the code in a short time before changing the configuration.

Each Netplan Yaml file starts with the network key that has at least two required elements. The first required element is the version of network configuration format and the second one is the device type. Device types values can be ethernets , bonds , bridges , and vlans .

The configuration above also includes the renderer type. Out of the box, if you installed Ubuntu in server mode the renderer is configured to use networkd as the back end.

Under the device’s type ( in this case ethernets ) we can specify one or more network interfaces. In this example we have only one interface ens3 that is configured to obtain IP addressing from a DHCP server dhcp4: yes .

To assign a static IP address to ens3 interface edit the file as follows:

Set DHCP to no dhcp4: yes
Specify the static IP address 192.168.121.199/24 . Under addresses: you can add one or more IPv4 or IPv6 IP addresses that will be assigned to the network interface.
Specify the gateway gateway4: 192.168.121.1
Under nameservers , specify the nameservers addresses: [8.8.8.8, 1.1.1.1]

Make sure you follow the YAML code indent requirements when editing Yaml files as it may not work if the configuration includes a syntax error.

Once the file is saved and closed and the changes are applied with:

Verify the changes by typing:

That’s it! You have assigned a static IP to your Ubuntu server.

Configuring Static IP address on Ubuntu Desktop

Setting up a static IP address on Ubuntu Desktop computers requires no technical knowledge.

1.In the Activities screen, search for “network” and click on the Network icon. This will open the GNOME Network configuration settings. Click on the cog icon.

ubuntu Network interface settings dialog box

The output will show the interface IP address:

You have learned how to assign a static IP address on your Ubuntu 18.04 machine. If you have any questions, please leave a comment below.

The following article will guide you on How to assign additional Static IP on Windows Server 2016 .

Knowledge Base
Customer Login

Dedicated Servers

Robust, secure and industrial-grade dedicated servers.

Storage Dedicated Servers

Affordable, customizable, reliable

High Performance Servers

High availability hosting utilizing high grade servers.

Secure, single-tenant and agile virtualized environment.

Co-location

Safe home for your servers in our high-class data centre.

Backup and Restore

Reliable, cost effective, backup and disaster recovery.

DDos Protection

7 layer DDoS mitigation system that protects your network.

Managed Services

Outsource your IT tasks to our skilled technical team.

Find a good domain for your business.

Powerful email hosting platform at your fingertips.

Web Hosting

Reliable and scalable web hosting solution.

It’s not about what we say, it’s about what we do. Learn more about Casbay’s background and confidently join our growing community.

Our vision, history and photo gallery.

Our Data Centre

Tier III certified data centre.

Our Clients

Explore our existing client base.

Our partners that grow with us in our journey.

The latest news and media releases.

Casbay Knowledge Base

Search our articles or browse by category below.

How to Configure Static IP Address on Ubuntu 18.04

In this tutorial, we’ll explain how to set up a static IP address on Ubuntu 18.04.

Do you know that:

Your router DHCP server would assign the IP addresses dynamically? In different situations such as configuring port forwarding or running a media server on your network, it may be necessary to set a static IP address on your Ubuntu computer.

Configuring Static IP address using DHCP

The easiest way to assign a static IP address to a device on your LAN is by setting up a Static DHCP on your router. Static DHCP or DHCP reservation is a feature that we find on most routers which makes the DHCP server automatically assign the same IP address to a specific network device, every time the device requests an address from the DHCP server. This works by assigning a static IP to the device’s unique MAC address. However, the steps for configuring a DHCP reservation vary from router to router and it’s advisable to consult the vendor’s documentation.

Starting with the 17.10 release, Netplan is the default network management tool on Ubuntu, replacing the configuration file /etc/network/interfaces that had previously been used to configure the network on Ubuntu.

Moreover, Netplan currently supports two renderers NetworkManager and Systemd-networkd. We use NetworkManager mostly on desktop machines. For System-network, we use it when a GUI is absent on servers.

Configuring Static IP address on Ubuntu Server

To configure a static IP address, you will need a VPS or Dedicated Server that runs on Ubuntu. The newer versions of Ubuntu uses ‘Predictable Network Interface Names’ that start with en[letter][number] . by default. The first step is to identify the name of the ethernet interface you want to configure. You can use the following IP link command:

The command will print a list of all the available network interfaces. In this case, the name of the interface is ens3 :

The location of the Netplan configuration files is in the /etc/netplan directory and have the extension .yaml . You’ll probably find one or two YAML files in this directory. The file may differ from setup to setup. Usually, the file is named either 01-netcfg.yaml , 50-cloud-init.yaml or NN_interfaceName.yaml , but in your system, it may be different.

Next, open the YAML configuration file with your text editor:

Before changing the configuration

Let’s explain the code in a short time before changing the configuration.

Furthermore, the configuration above also includes the renderer type. Out of the box, if you installed Ubuntu in server mode the renderer is configured to use networkd as the back end.

Under the device’s type ( in this case ethernets ) we can specify one or more network interfaces. In this example, we have only one interface ens3 that is configured to obtain IP addressing from a DHCP server dhcp4: yes .

To assign a static IP address to ens3 the interface edit the file as follows:

Set DHCP to no dhcp4: yes
Specify the static IP address 192.168.121.199/24 . Under addresses: you can add one or more IPv4 or IPv6 IP addresses that will be assigned to the network interface.
Specify the gateway gateway4: 192.168.121.1
Under nameservers , specify the nameservers addresses: [8.8.8.8, 1.1.1.1]

Make sure you follow the YAML code indent requirements when editing Yaml files as it may not work if the c onfiguration includes a syntax error.

Once you save and closed the file, and the changes are applied with:

Then verify the changes by typing:

That’s it! You have assigned a static IP to your Ubuntu server.

Configuring Static IP address on Ubuntu Desktop

Setting up a static IP address on Ubuntu Desktop computers requires no technical knowledge.

1.In the Activities screen, search for “network” and click on the Network icon. This will open the GNOME Network configuration settings. Click on the cog icon.

3. In “IPV4” Method” section select “Manual”, and enter your static IP address, Netmask and Gateway. Click on the “Apply” button once completed.

Now that you have set up a static IP Address, open your terminal either by using the Ctrl+Alt+T keyboard shortcut or by clicking on the terminal icon and verify the changes by typing:

The output will show the interface IP address:

You have learned how to assign a static IP address on your Ubuntu 18.04 machine.

If you have any questions, please leave a comment below.

Looking for more guide articles on Ubuntu? Kindly visit our Knowledge Base .

[email protected]
Cloud Server
VPS Hosting
Windows VPS
Dedicated Server
Cloud calculator
Encryption Project
Data Center
Terms of Service
Acceptance Use Policy
Privacy Policy
Money Back Guarantee
Payment Info
Support Ticket
Knowledgebase

How to Configure Network Static IP Address in Ubuntu 18.04

Netplan is a new command-line network configuration utility introduced in Ubuntu 17.10 to manage and configure network settings easily in Ubuntu systems. It allows you to configure a network interface using YAML abstraction. It works in conjunction with the NetworkManager and systemd-networkd networking daemons (referred to as renderers , you can choose which one of these to use) as interfaces to the kernel.

It reads network configuration described in /etc/netplan/*.yaml and you can store configurations for all your network interfaces in these files.

In this article, we will explain how to configure a network static or dynamic IP address for a network interface in Ubuntu 18.04 using Netplan utility.

List All Active Network Interfaces on Ubuntu

First, you need to identify the network interface you are going to configure. You can list all attached network interfaces on your system using the ifconfig command as shown.

From the output of the above command, we have 3 interfaces attached to the Ubuntu system: 2 ethernet interfaces and the loop back interface . However, the enp0s8 ethernet interface has not been configured and has no static IP address.

Set Static IP Address in Ubuntu 18.04

In this example, we will configure a static IP for the enp0s8 ethernet network interface. Open the netplan configuration file using your text editor as shown.

Important : In case a YAML file is not created by the distribution installer, you can generate the required configuration for the renderers with this command.

In addition, auto generated files may have different filenames on desktop, servers, cloud instantiations etc (for example 01-network-manager-all.yaml or 01-netcfg.yaml ), but all files under /etc/netplan/*.yaml will be read by netplan.

Then add the following configuration under the ethernet section.

dhcp4 and dhcp6 – dhcp properties of an interface for IPv4 and IPv6 receptively.
addresses – sequence of static addresses to the interface.
gateway4 – IPv4 address for default gateway.
nameservers – sequence of IP addresses for nameserver.

Once you have added, your configuration file should now have the following content, as shown in the following screenshot. The first interface enp0s3 is configured to use DHCP and enp0s8 will use a static IP address.

The addresses property of an interface expects a sequence entry for example [192.168.14.2/24, “2001:1::1/64”] or [192.168.56.110/24, ] (see netplan man page for more information).

Save the file and exit. Then apply the recent network changes using following netplan command.

Now verify all the available network interfaces once more time, the enp0s8 ethernet interface should now be connected to the local network, and have an IP addresses as shown in the following screenshot.

Set Dynamic DHCP IP Address in Ubuntu

To configure the enp0s8 ethernet interface to receive an IP address dynamically through DHCP, simply use the following configuration.

Save the file and exit. Then apply the recent network changes and verify the IP address using following commands.

From now on your system will get an IP address dynamically from a router.

You can find more information and configuration options by consulting the netplan man page.

Congratulations! You’ve successfully configured a network static IP addresses to your Ubuntu servers. If you have any queries, share them with us via the comment form below.

Hey TecMint readers ,

Exciting news! Every month, our top blog commenters will have the chance to win fantastic rewards, like free Linux eBooks such as RHCE , RHCSA , LFCS , Learn Linux , and Awk , each worth $20 !

Learn more about the contest and stand a chance to win by sharing your thoughts below !

Each tutorial at TecMint is created by a team of experienced Linux system administrators so that it meets our high-quality standards.

How to Install Cinnamon Desktop On Ubuntu 24.04

How to Install CockroachDB Cluster on Ubuntu 24.04

How to Install CakePHP on Ubuntu 24.04

How to Reset Forgotten Root Password in Ubuntu

zzUpate Upgrade Ubuntu System With Single Command

zzUpdate – Fully Upgrade Ubuntu to Latest Newer Release

How to Install Apache Pinot in Linux

26 Comments

There is a .yaml file for configuration. The syntax of it is horrible! I didn’t understand at all – HOW can I write wireless networks, WHERE, and HOW MUCH spices can be there.

yaml language is very structured. Notice that each indent is two spaces. In order to use your wireless network, you need to discover what the OS thinks the name of the device is. For most OSs, you can simply type: ip a – That should return a list of all available adapters in your system.

From there you have a working example from the article above. Just plug in your wireless device name instead of eth0. Also, you haven’t stated if your wireless is acting in AP mode or as a client. Good luck!

sudo apt update not working anymore.

Ubuntu loves play with us, its like when we was kids and played the touch and go :)

First it changes /etc/network/interfaces to /etc/netplan/50-cloud-init.yaml as you can see when do:

# ifupdown has been replaced by netplan(5) on this system. See # /etc/netplan for current configuration. # To re-enable ifupdown on this system, you can run: # sudo apt install ifupdown

Second it changes /etc/netplan/50-cloud-init.yaml to /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg as you can see when do:

Then even after running [ cloud-init clean -r ] sometimes changes in /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg arent applied

Thanks! you save my day! Really well explained

This is great! Many thanks for the feedback.

Hello I’m trying to set up my computer with GPU to be accessed from my laptop and from my friends laptop through putty, for this the solution i thought it would work was set up a static IP and open port 22 so that we can access the GPU machine through putty from other laptop.

After i set up the static IP my internet connection in Gpu machine is not working also i don’t have an idea how to proceed further in port forwarding .

1. My questions are is my solution to set up static IP and open port 22 will work for my above requirement. 2. Any suggestions to solve my internet connectivity issue.

@Dwarakanath,

First check your static IP is reachable from other laptop by doing a ping request to IP. Secondly, make sure the opened port 22 is listening on the system using netstat command .

@Ravi save thanks for replying ping from my laptop to connect my static ip machine gets timeout, I see that you ask me to check the port 22 is listening using netstat to make it more clear I am yet to open port 22 for which any help will be highly appreciated

Your static IP must be reachable from your laptop, and to open port 22 on ufw firewall, run:

I think you have a mistake with regards to what “ netplan generate ” does, you have a notice saying “Important: In case a YAML file is not created by the distribution installer, you can generate the required configuration for the renderers with this command.”, this is incorrect. On the man page ( http://manpages.ubuntu.com/manpages/cosmic/man8/netplan-generate.8.html ) it says “netplan-generate – generate backend configuration from netplan YAML files”

“netplan generate” *reads* the YAML files it can’t create the yaml file for you, ie it won’t touch any of the yaml files in the “ /etc/netplan/ ” directory.

I have noticed when I run “ netplan generate ” it creates the configuration files in “ /run/systemd/network/ ” on Ubuntu 18.04

The man page also says: “You will not normally need to run this directly as it is run by netplan apply, netplan try, or at boot.”

So I think you should remove the reference to “netplan generate ” as it’s just a red herring. If there is nothing in “ /etc/netplan ” then that command isn’t going to help you out.

Many thanks for the heads up, we will look into this.

Those linux devs who made this decision are absolutely bunch of very strong and bad words. You have no idea what did you do to a mindset of administrator who expect that nobody, really nobody mess with sys admin networking stuff.

Specially developers. Do you have ANY idea what did you just do by switching to this netplan? This is unbelievable stupid. Unbelievable. Sys Admin really have other things to do besides watching which developer had some stupid inspiration and decide to change stable thing that work flawlessly.

Unbelievable. Have no nice word for this move. You should really go and destroy your head with hammer.

Many thanks for sharing your thoughts with us.

Interesting tutorial but at the netplan part you are going to fast for me. I don’t have that file, i do have a 50cloudminitmyaml does this mean i need to add my ipaddress in the 5-cloud file?

You can generate a file for you system, using this command:

Read it in your article, but was afraid because I got a different file by default.

After adding ens7 to

and checking with:

all seemed well, but I can no longer ssh into my box now. Why?

Can you try this >>

that should tell you if open or available, also change the yes and no to true and false.

How is it, that in 2018 the configuration of your networks is decades behind Redhat 6?? Since when have we been reduced to config file editing, when the old classic blue and red config menu’s were fantastic. I dunno, even Raspberry Pi has better tools out of the box…..

Looking to set up a static IP address in preparation for setting up a personal VPN via raspberry Pi

Cannot find not generate a netplan file at all

Configuration of ethernet looks as follows:

Just a “Rank-Pensioner” amateur who can copy & past but does not understand much about Linux!

Cheers, Ton

If there is no default netplan config file, try to generate one as shown in the article, then put your config in there. For more information, read the netplan man page.

dhcp4: yes dhcp6: yes

dhcp4: no dhcp6: no

has to be changed to dhcp4: true dhcp6: true

dhcp4: false dhcp6: false

Yes, this is correct but yes or no values also work. After i installed Ubuntu 18.04, one of the default interfaces using dhcp4 had a value of yes(see the screenshot in article).

I didn’t work for me :(

Had to go to the man page and other examples and change it to true false, it it works for you and others then all gravy, just sharing the heads up

Practically, the best option would be to use true or false.

Got Something to Say? Join the Discussion... Cancel reply

Thank you for taking the time to share your thoughts with us. We appreciate your decision to leave a comment and value your contribution to the discussion. It's important to note that we moderate all comments in accordance with our comment policy to ensure a respectful and constructive conversation.

Rest assured that your email address will remain private and will not be published or shared with anyone. We prioritize the privacy and security of our users.

Save my name, email, and website in this browser for the next time I comment.

How to configure static IP on ubuntu 18.04 server ?

Static ip configuration on ubuntu 18.04 server.

We know the configuration of IP on Ubuntu 18.04 is different from other. Ubuntu versions like Ubuntu 14, Ubuntu 16 etc. The manner by which Ubuntu oversees organize interfaces has totally changed. We use NetPlan as the new network configuration tool to manage network settings in Ubuntu 18. NetPlan replaces the static interfaces “/etc/network/interfaces” document that had already been utilized to design Ubuntu organize interfaces.

In Ubuntu 18.04 we use,

/etc/netplan/*.yaml to configure interfaces instead of /etc/network/interfaces.

The new interfaces setup record can be found under the /etc/netplan directory. There are two renderers for this tool that is NetworkManager and networkd. NetworkManager renderer is generally utilized on personal computers and networkd on servers.

Configuring Static IP Addresses with Networkd

To Identify Active Network Interfaces on Ubuntu, Initially, we need to identify the network interface which we are going to set up. We can list all attached network interfaces on the server using the “ifconfig” or “ip a” command.

Note: In case a YAML file is not created by the distribution installer, we can generate the required configuration for the renderers with the following command,

” #netplan generate”

Even though auto-generated files have different file names, all files under /etc/netplan/*.yaml will be read by netplan.

To Set Static IP Address in Ubuntu 18.04

For this example, we consider interface “eth0” as the interface in which IP has to be configured.

Open the file under /etc/netplan by Vim or nano,

” #vim /etc/netplan/01-netcfg.yaml”

Then add the below configuration in the ethernet section that is under eth0.

eth0: dhcp4: no dhcp6: no addresses: [192.***.**.8/29 ] gateway4: 192.***.**.7 nameservers: addresses: [8.8.8.8, 8.8.4.4]

Save the file and exit. Using netplan command, apply the recent network changes.

#netplan apply

To verify IP configuration.

The eth0 ethernet interface will now connect to the local network and will be responding to ping.

#ifconfig -a #ping 8.8.8.8

Your Email (required)

Your Message

Share This Story, Choose Your Platform!

About the author: justin varghese.

10 Common Technical Issues That Your Web Hosting Support Team Can Help You With

Game Server Issues: ‘Connection to Server Lost’ is Fixed

How to Fix WordPress White Screen of Death?

Node.js in Plesk: How To Host Node.JS Application in Plesk

How to Configure Static IP Address on Ubuntu 18.04 (Desktop)

Question – How To Change IP Address on Ubuntu 18.04 Desktop? Steps to set the static IP address on your Ubuntu Desktop system

Ubuntu 18.04 systems are using netplan instead of older static interfaces. The desktop provides an attractive GUI for working with it. You can easily change or set a static IP address on your Ubuntu system.

For the server edition, you can follow this tutorial to configure IP address on Ubuntu using the command line.

Step 1 – Open Network Settings

Login to your Ubuntu Desktop system. After that open settings windows on your Ubuntu Desktop machine as showing in the below screen.

In the left sidebar click on the Network tab. After that click icon to open setting for your systems network interface as shown in the below screen.

This window will show you the current IP address configured on your system. Now select the IPv4 tab.

Step 2 – Setup Static IP on Ubuntu 18.04

Under the IPv4 Method select the “Manual” option.

Now go to the Addresses section and set your IP Address, Netmask, and Gateway.

You can also set remote DNS IP addresses. If you don’t know what to set here use 8.8.8.8 and 8.8.4.4 as shown in below screenshot.

Step 3 – View Current IPs

Press CTRL + ALT + T to launch the terminal on your Ubuntu system. Now type following IP command to view all IP addresses configured on your system.

How to easily find the ip address of a docker container, how to configure static ip address on ubuntu 24.04.

So what file is the Static IP saved in? It used to be /etc/network/interfaces then recently it is usually saved to /etc/netplan/50-cloud-init.yaml?

Save my name, email, and website in this browser for the next time I comment.

Type above and press Enter to search. Press Esc to cancel.

Trending Articles on Technical and Non Technical topics

Selected Reading
UPSC IAS Exams Notes
Developer's Best Practices
Questions and Answers
Effective Resume Writing
HR Interview Questions
Computer Glossary

How to Configure Network Static IP Address in Ubuntu 18.04?

Introduction.

The Internet Protocol (IP) address is a crucial component of computer networking as it uniquely identifies each device connected to a network. By default, most network interfaces are configured to obtain an IP address dynamically from a router or DHCP server. However, in some cases, it is necessary to configure a static IP address.

A static IP address is an IP address that is manually assigned to a device and does not change over time unless manually reconfigured. In this article, we will discuss how to configure a static IP address on Ubuntu 18.04 and why it's important in some situations.

What Is Static IP Address And Why It's Important?

When you connect your computer or other devices like printers and servers to a network, they are assigned dynamic IPs by default using DHCP (Dynamic Host Configuration Protocol). However, there are several reasons why you may want or need your devices to have static IPs instead of dynamic IPs.

One of the primary reasons for having a static IP is stability- when you have a device with dynamic IPs constantly changing its addresses it can be challenging for other computers on the network to keep track of where that machine is located correctly. This problem can cause issues such as disrupted connections and broken services.

With a static IP address, you specify an address that devices will always be able to find your machine at no matter what else changes on the network around it over time. Another reason for having a static IP is security – assigning fixed addresses can help security measures track traffic patterns from known locations more efficiently than if addresses constantly change; this helps them distinguish between legitimate traffic from known hosts versus potentially malicious traffic from unknown sources.

Understanding Network Configuration in Ubuntu 18.04

Overview of network configuration files and their locations.

Before proceeding with setting up a static IP address, it is important to have a basic understanding of network configuration files in Ubuntu 18.04. There are two primary configuration files for network settings in Ubuntu 18.04: /etc/network/interfaces and /etc/netplan/*.yaml.

The /etc/network/interfaces file is used by the ifupdown package, which is the traditional method of configuring networking on Ubuntu systems. The file contains interface configurations such as IP address, netmask, gateway, and DNS servers.

The /etc/netplan/*.yaml file is used by the Netplan utility for configuring networking in Ubuntu 18.04. This YAML-based configuration file provides a simple and flexible way to configure network interfaces.

Explanation of the importance of understanding network configuration before proceeding with configuring a static IP address

Having an understanding of how network configurations work in Ubuntu 18.04 is essential when configuring static IP addresses. Static IP addresses are manually assigned, unlike dynamic IPs that are automatically assigned by DHCP (Dynamic Host Configuration Protocol). Assigning an incorrect static IP address or modifying other critical settings can lead to loss of connectivity to the network and internet.

Therefore, before proceeding with setting up a static IP address on your system, it is important to have some knowledge about how networking works in Ubuntu 18.04 operating system so that you can avoid making mistakes that might cause problems later on during the process or cause your system to be inaccessible over your local area network or even over public networks like the internet. In short, having this knowledge will help you troubleshoot any problem or issue that may arise during the process correctly because you will understand what is happening and why.

Identifying Network Interface Name and Current IP Address

As we proceed towards configuring a static IP address in Ubuntu 18.04, the first step is to identify the network interface name. In Ubuntu 18.04, network interfaces are named differently from previous versions, so it is important to understand how to find the correct interface name.

One way to identify the name of the network interface is by using command-line tools such as ifconfig or ip addr show. To use ifconfig, open a terminal window and type "ifconfig" at the prompt.

A list of all available network interfaces will be displayed with their respective names. To check the current dynamic IP address assigned to the interface, look for an entry labeled "inet addr" under each interface’s details in ifconfig output.

The inet addr value represents the dynamic IP address assigned by DHCP server. Another tool that can be used to obtain information about network interfaces in Ubuntu 18.04 is ip command line utility.

By running “ip addr show” command on terminal you can get a detailed list of all available interfaces with their IPv4, IPv6 addresses and other important information. Knowing how to find both this information will be useful while configuring static IP addresses in Ubuntu 18.04 since you need this information while editing netplan YAML file in order configure a static IP address correctly

Configuring Static IP Address using Netplan

Overview of netplan yaml file structure.

Netplan is a configuration utility that allows users to easily configure network settings in Ubuntu 18.04. The main configuration file for Netplan is located at "/etc/netplan/", and it uses YAML syntax for its configuration files. The syntax of the file is strict, so even a small error can cause issues with network connectivity.

The top-level elements in the Netplan YAML file specify the behavior of each network interface defined in the configuration file. These elements contain basic information about the network interface, such as its name, IP address, gateway, DNS server(s), and any custom routes.

Step-by-step guide on how to edit and configure Netplan YAML file for static IP addressing.

Here are the steps involved in configuring a static IP address using Netplan −

Open your Terminal application by pressing `Ctrl+Alt+T` or searching for "Terminal" on the Ubuntu applications menu.

Navigate to "/etc/netplan/" by running this command: `cd /etc/netplan/`

Open the default NetPlan YAML configuration file called "50-cloud-init.yaml" by running this command: `sudo nano 50-cloud-init.yaml`

Locate your network interface name from Section II earlier (e.g., enp0s25) and add these lines under it−

Replace "YOUR_STATIC_IP_ADDRESS/MASK", "YOUR_GATEWAY_IP_ADDRESS", and "YOUR_DNS_SERVER_IP_ADDRESSES" with your own values.

Save your changes by pressing `Ctrl+X`, then press Y when prompted to save, and press Enter to confirm the file name.

Test your configuration by running the following command: `sudo netplan apply`

Explanation on how to apply changes made on Netplan YAML file.

To apply changes made in the Netplan YAML file, you need to run the "netplan apply" command in the Terminal. This command applies your changes immediately without requiring a system reboot.

If you don't run this command, any changes you make will not be applied until a system reboot or until you manually run this command. Additionally, if there are any syntax errors in your NetPlan YAML configuration file, running "netplan apply" will fail and an error message will be displayed in your Terminal output.

Overall, configuring static IP addresses using NetPlan can be a great way to ensure stable network connectivity for Ubuntu 18.04 users. The process may seem complex at first glance but once you follow these steps carefully it'll become much simpler.

In this article, we discussed the importance of having a static IP address in Ubuntu 18.04. A static IP address ensures that your device can always be reached at the same network address, making it easier to manage and keep track of devices on your network. This is particularly important for servers and other devices that need to be accessible from outside your local network.

How to Configure Network Static IP Address on RHEL/CentOS 8?
How to Install and Configure an NFS Server on Ubuntu 18.04?
Difference between Static IP Address and Dynamic IP Address
How to Change Hostname on Ubuntu 18.04?
3 Ways to Set a Static IP Address in RHEL 8
How to Install Anaconda on Ubuntu 18.04 and 20.04?
How to Enable/Disable UFW Firewall on Ubuntu 18.04 & 20.04?
How to hide an IP address
How to identify server IP address in PHP?
How to get the ip address in C#?
How to Pad IP Address With Zero in Excel?
How to Install and Configure FTP Server in Ubuntu?
Validate IP Address in C++
Validate IP Address in Python
Validate IP Address in C#

Kickstart Your Career

Get certified by completing the course

How to assign static IP address on Ubuntu Linux

Here are the steps to assign an IP address to an Ubuntu Server using the Settings app and Terminal commands.

On Ubuntu (version 22.04, 21.04, or older releases), it’s possible to assign a static IP address through the Settings interface or the Terminal using commands, and in this guide, you will learn how.

Once you complete the installation of the Ubuntu Server (or client version), the device will receive a network configuration assigned automatically by the Dynamic Host Configuration Protocol (DHCP) server available in the local network. Although this configuration is enough to access the network and internet, it’s a good idea to assign a static network configuration as you probably are setting up the system to serve different services, such as file and print sharing and others.

The reason is that a dynamic configuration can change at any time, and a static network configuration is permanent, meaning that devices in the network will be able to always reach the server with the address.

This guide will teach you the steps to configure a static IP address for your Ubuntu Server installation. You can also use these instructions for the client version of the Linux distro.

Set static IP address configuration on Ubuntu Linux (GUI)

Set static ip address configuration on ubuntu linux (command).

To assign a static IP address on Ubuntu (server or client) through the Settings app, use these steps:

Open Settings .

Click on Network .

Click the Settings button for the “Wired” network interface.

Click the IPv4 tab.

Select the Manual option for the “IPv4 Method” setting.

Under the “Addresses” section, confirm the static IP address in the “Address” setting — for example, 10.1.4.201.

Confirm the subnet mask in the “Netmask” settings — for example, 255.255.255.0.

Confirm the gateway address (usually the router’s IP) in the “Gateway” setting.

Turn off the Automatic toggle switch for the “DNS” setting.

Confirm the DNS address(es) for this static configuration — for example, the router IP address or your preferred DNS address, such as the ones from Google Public DNS, 8.8.8.8, 8.8.4.4 .

(Optional) Click the IPv6 tab.

Select the Disable option in the “IPv6 Method” setting.

Click the Apply button.

(Optional) Turn off and on the Wired toggle switch on the “Network” page if the configuration isn’t working.

Once you complete the steps, the Linux distro will start using the new static network configuration.

To assign a static IP address on Ubuntu Linux (server or client), use these steps:

Open Terminal

Type the following command to determine the network interface name and press Enter :

Type the following command to open the configuration file and press Enter :

Copy and paste the following configuration (changing the TCP/IP settings with your settings):

In the command, change “ens33” for the name of your server network adapter name and “10.1.4.201/24” for the static IP address and subnet mask after the forward slash (/) you want to assign to the Ubuntu Server. For example, the “/24” assigns the “255.255.255.0” address. Also, change “8.8.4.4, 8.8.8.8” for static DNS addresses. The comma (,) is only required when setting up multiple addresses. And change “10.1.4.1” for the default gateway of your network (usually the router IP address).

Press “Ctrl + O,” “Enter,” and “Ctrl + X” to save the changes and exit the text editor.

Type the following command to apply the new static IP address configuration and press Enter :

(Optional) Type the following command to confirm the static network configuration and press Enter :

In the command, change “ens33” to the name of the adapter.

After you complete the steps, the static IP address configuration will apply to the network adapter on Ubuntu (server or client).

How to backup config file on TrueNAS
How to create Windows Server bootable USB media

Errors or typos? Topics missing? Hard to read? Let us know or open an issue on GitHub .

Multipass is a flexible and powerful tool that can be used for many purposes. In its simplest form, it can be used to quickly create and destroy Ubuntu VMs (instances) on any host machine. When used maximally, Multipass is a local mini-cloud on your laptop, ensuring that you can test and develop multi-instance or container-based cloud applications.

This tutorial will help you understand how Multipass works, and the skills you need to use its main features.

Install Multipass

Multipass is available for Linux, macOS and Windows. To install it on the OS of your choice, please follow the instructions provided in How to install Multipass .

Create and use a basic instance

Start Multipass from the application launcher. In Ubuntu, press the super key and type “Multipass”, or find Multipass in the Applications panel on the lower left of the desktop.

After launching the application, you should see the Multipass tray icon on the upper right section of the screen.

Click on the Multipass icon and select Open Shell .

Clicking this button does many things in the background. First, it creates a new virtual machine (instance) named “primary”, with 1GB of RAM, 5GB of disk, and 1 CPU. Second, it installs the most recent Ubuntu LTS release on that instance. Third, it mounts your $HOME directory in the instance. Last, it opens a shell to the instance, announced by the command prompt ubuntu@primary .

You can see elements of this in the printout below:

Let’s test it out. As you’ve just learnt, the previous step automatically mounted your $HOME directory in the instance. Use this to share data with your instance. More concretely, create a new folder called Multipass_Files in your $HOME directory.

As you can see, a README.md file has been added to the shared folder. Check for the folder and read the file from your new instance:

Start Multipass from the application launcher. In macOS, open the application launcher, type “Multipass”, and launch the application.

After launching the application, you should see the Multipass tray icon in the upper right section of the screen.

Start Multipass from the application launcher. Press the Windows key and type “Multipass”, then launch the application.

After launching the application, you should see the Multipass tray icon in the lower right section of the screen (you may need to click on the small arrow located there).

Let’s test it out. As you’ve just learnt, the previous step automatically mounted your $HOME directory in the instance. Try out a few Linux commands to see what you’re working with.

Congratulations, you’ve got your first instance!

This instance is great for when you just need a quick Ubuntu VM, but let’s say you want a more customised instance, how can you do that? Multipass has you covered there too.

Exercise 1: When you select Open Shell, what happens in the background is the equivalent of the CLI commands multipass launch –name primary followed by multipass shell . Open a terminal and try multipass shell (if you didn’t follow the steps above, you will have to run the launch command first).

Exercise 2: In Multipass, an instance with the name “primary” is privileged. That is, it serves as the default argument of multipass shell among other capabilities. In different terminal instances, check multipass shell primary and multipass shell . Both commands should give the same result.

Create a customised instance

Multipass has a great feature to help you get started with creating customised instances. Open a terminal and run the multipass find command. The result shows a list of all images you can currently launch through Multipass.

Launch an instance running Ubuntu 22.10 (“Kinetic Kudu”) by typing the multipass launch kinetic command.

Now, you have an instance running and it has been named randomly by Multipass. In this case, it has been named “coherent-trumpetfish”.

You can check some basic info about your new instance by running the following command:

multipass exec coherent-trumpetfish -- lsb_release -a

This tells multipass to execute the command lsb_release -a on the “coherent-trumpetfish” instance.

Perhaps after using this instance for a while, you decide that what you really need is the latest LTS version of Ubuntu, with a more informative name and a little more memory and disk. You can delete the “coherent-trumpetfish” instance by running the following command:

multipass delete coherent-trumpetfish

You can now launch the type of instance you need by running this command:

multipass launch lts --name ltsInstance --memory 2G --disk 10G --cpus 2

Now, you have an instance running and it has been named randomly by Multipass. In this case, it has been named “breezy-liger”.

multipass exec breezy-liger -- lsb_release -a

This tells Multipass to execute the command lsb_release -a on the “breezy-liger” instance.

Perhaps after using this instance for a while, you decide that what you really need is the latest LTS version of Ubuntu, with a more informative name and a little more memory and disk. You can delete the “breezy-liger” instance by running the following command:

multipass delete breezy-liger

Now, you have an instance running and it has been named randomly by Multipass. In this case, it has been named “decorous-skate”.

multipass exec decorous-skate -- lsb_release -a

This tells Multipass to execute the command lsb_release -a on the “decorous-skate” instance.

Perhaps after using this instance for a while, you decide that what you really need is the latest LTS version of Ubuntu, with a more informative name and a little more memory and disk. You can delete the “decorous-skate” instance by running the following command:

multipass delete decorous-skate

Manage instances

You can confirm that the new instance has the specs you need by running multipass info ltsInstance .

You’ve created and deleted quite a few instances. It is time to run multipass list to see the instances you currently have.

The result shows that you have two instances running, the “primary” instance and the LTS machine with customised specs. The “coherent-trumpetfish” instance is still listed, but its state is “Deleted”. You can recover this instance by running multipass recover coherent-trumpetfish . But for now, delete the instance permanently by running multipass purge . Then run multipass list again to confirm that the instance has been permanently deleted.

The result shows that you have two instances running, the “primary” instance and the LTS machine with customised specs. The “breezy-liger” instance is still listed, but its state is “Deleted”. You can recover this instance by running multipass recover breezy-liger . But for now, delete the instance permanently by running multipass purge . Then run multipass list again to confirm that the instance has been permanently deleted.

The result shows that you have two instances running, the “primary” instance and the LTS machine with customised specs. The “decorous-skate” instance is still listed, but its state is “Deleted”. You can recover this instance by running multipass recover decorous-skate . But for now, delete the instance permanently by running multipass purge . Then run multipass list again to confirm that the instance has been permanently deleted.

You’ve now seen a few ways to create, customise, and delete an instance. It is time to put those instances to work!

Put your instances to use

Let’s see some practical examples of what you can do with your Multipass instances:

Run a simple web server

Launch from a blueprint to run docker containers.

One way to put a Multipass instance to use is by running a local web server in it.

Return to your customised LTS instance. Take note of its IP address, which was revealed when you ran multipass list . Then run multipass shell ltsInstance to open a shell in the instance.

From the shell, you can run:

Open a browser and type in the IP address of your instance into the address bar. You should now see the default Apache homepage.

Just like that, you’ve got a web server running in a Multipass instance!

You can use this web server locally for any kind of local development or testing. However, if you want to access this web server from the internet (for instance, a different computer), you need an instance that is exposed to the external network.

Some environments require a lot of configuration and setup. Multipass Blueprints are instances with a deep level of customization. For example, the Docker Blueprint is a pre-configured Docker environment with a Portainer container already running.

You can launch an instance using the Docker Blueprint by running multipass launch docker --name docker-dev .

Once that’s done, run multipass info docker-dev to note down the IP of the new instance.

Copy the IP address starting with “10” and paste it into your browser, then add a colon and the portainer default port, 9000. It should look like this: 10.115.5.235:9000. This will take you to the Portainer login page where you can set a username and password.

From there, select Local to manage a local Docker environment.

Inside the newly selected local Docker environment, locate the sidebar menu on the page and click on app templates , then select NGINX .

From the Portainer dashboard, you can see the ports available on nginx. To verify that you have nginx running in a Docker container inside Multipass, open a new web page and paste the IP address of your instance followed by one of the port numbers.

Congratulations! You can now use Multipass proficiently.

There’s more to learn about Multipass and its capabilities. Check out our how-to guides for ideas and help with your project. Our reference pages contain definitions of key concepts, a complete CLI command reference, settings options and more.

Join the discussion on the Multipass forum and let us know what you are doing with your instances!

Let us know how this worked for you and what you’d like to see next!

Contributors: @nhart , @saviq , @townsend , @andreitoterman , @tmihoc , @luisp , @ricab , @sharder996 , @georgeliaojia , @mscho7969 , @itecompro , @mr-cal , @sally-makin , @gzanchi , @bagustris , @pitifulpete

I am new to multipass and am trying to configure things such that my personal machine on my LAN can directly access the VMs created in multipass. I have an Ubuntu Linux server where I am able to run multipass and launch VM, but given the VMs are on a private 10.x.x.x network and my machine is 192.168.1.x, I cannot connect directly to the VMs.

I have gone through the documentation and am clearly missing how things can be setup to make this work. I have seen references to creating a static route on my localmachine to the 10 network, but it seems there should be a better way to do this. I have also found a reference to using network-manager that results in the VMs getting an IP from the local LAN, but have not been able to get network-manager to load / make this work.

Really hoping somebody can assist me in getting the network configuration set such that I can access the VMs directly from my LAN.

Thank you! Bob

Hey @boursawb , you need to bridge your VMs to the outside. You can achieve that using the --network option to launch , e.g.: multipass launch --network eth0 . multipass networks displays available network interfaces. However, on Linux this is only supported with the LXD driver.

Have a look at this how-to for more.

Thank you, @ricab !

I went through the tutorial, and after a few more changes (getting NetworkManager loaded, service running, etc.), I was able to launch an instance that was bridged and I could access it as expected from my multipass host as well as my local machine on the LAN - Perfect!

I assumed this information would be retained in the configuration such that if I stop and start the VM that the bridged network would remain, but this does not seem to be the case.

Is that expected behavior, or should I be able to stop/start the VMs after the initial launch and have the bridged network remain?

Is it preferred to start a VM via a cloud-init script which calls on a specific netplan each time you want to stand up a VM?

Is it not intended to remain the VMs for a period of time and start/stop them as required?

I’ve looked at several of the docs/tutorials on cloud init scripts for multipass, but there seems to be chunks of info assumed/missing and I’m struggling to put this all together.

Any info you could throw my way to help me get this sorted out/better understand how this all works and what the requirements are would be awesome!

Thank you for your time. Bob

An instance launched with a bridged network should definitely retain it. Once generated, Multipass keeps it alone. That includes the network interface inside the instance, the cloud-init config under the hood, and the generated bridge on the host.

If this is not what you’re seeing, something is going wrong. What exactly do you observe? Missing IP? No connectivity? Did you perhaps enable a firewall in the meantime, which could be blocking DHCP?

Otherwise, would you mind filing an issue with all relevant info, so that we can better follow up? Thanks.

An official website of the United States government

Here’s how you know

Official websites use .gov A .gov website belongs to an official government organization in the United States.

Secure .gov websites use HTTPS A lock ( Lock A locked padlock ) or https:// means you’ve safely connected to the .gov website. Share sensitive information only on official, secure websites.

Free Cyber Services #protect2024 Secure Our World Shields Up Report A Cyber Issue

Vulnerability Summary for the Week of June 24, 2024

The CISA Vulnerability Bulletin provides a summary of new vulnerabilities that have been recorded by the National Institute of Standards and Technology (NIST) National Vulnerability Database (NVD) in the past week. NVD is sponsored by CISA. In some cases, the vulnerabilities in the bulletin may not yet have assigned CVSS scores. Please visit NVD for updated vulnerability entries, which include CVSS scores once they are available.

Vulnerabilities are based on the Common Vulnerabilities and Exposures (CVE) vulnerability naming standard and are organized according to severity, determined by the Common Vulnerability Scoring System (CVSS) standard. The division of high, medium, and low severities correspond to the following scores:

High : vulnerabilities with a CVSS base score of 7.0–10.0
Medium : vulnerabilities with a CVSS base score of 4.0–6.9
Low : vulnerabilities with a CVSS base score of 0.0–3.9

Entries may include additional information provided by organizations and efforts sponsored by CISA. This information may include identifying information, values, definitions, and related links. Patch information is provided when available. Please note that some of the information in the bulletin is compiled from external, open-source reports and is not a direct result of CISA analysis.

High Vulnerabilities

Primary Vendor -- Product	Description	Published
access_management_specialist_project -- access_management_specialist	An issue in Shenzhen Weitillage Industrial Co., Ltd the access management specialist V6.62.51215 allows a remote attacker to obtain sensitive information.	2024-06-24
aimeos--ai-client-html	ai-client-html is an Aimeos e-commerce HTML client component. Debug information revealed sensitive information from environment variables in error log. This issue has been patched in versions 2024.04.7, 2023.10.15, 2022.10.13 and 2021.10.22.	2024-06-25
amazon -- freertos-plus-tcp	FreeRTOS-Plus-TCP is a lightweight TCP/IP stack for FreeRTOS. FreeRTOS-Plus-TCP versions 4.0.0 through 4.1.0 contain a buffer over-read issue in the DNS Response Parser when parsing domain names in a DNS response. A carefully crafted DNS response with domain name length value greater than the actual domain name length, could cause the parser to read beyond the DNS response buffer. This issue affects applications using DNS functionality of the FreeRTOS-Plus-TCP stack. Applications that do not use DNS functionality are not affected, even when the DNS functionality is enabled. This vulnerability has been patched in version 4.1.1.	2024-06-24
Arista Networks--Arista Wireless Access Points	This Advisory describes an issue that impacts Arista Wireless Access Points. Any entity with the ability to authenticate via SSH to an affected AP as the "config" user is able to cause a privilege escalation via spawning a bash shell. The SSH CLI session does not require high permissions to exploit this vulnerability, but the config password is required to establish the session. The spawned shell is able to obtain root privileges.	2024-06-27
auto-featured-image_project -- auto-featured-image	The Auto Featured Image plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the 'create_post_attachment_from_url' function in all versions up to, and including, 1.2. This makes it possible for authenticated attackers, with contributor-level and above permissions, to upload arbitrary files on the affected site's server which may make remote code execution possible.	2024-06-27
Avaya--IP Office	An improper input validation vulnerability was discovered in Avaya IP Office that could allow remote command or code execution via a specially crafted web request to the Web Control component. Affected versions include all versions prior to 11.1.3.1.	2024-06-25
Avaya--IP Office	An unrestricted file upload vulnerability in Avaya IP Office was discovered that could allow remote command or code execution via the One-X component. Affected versions include all versions prior to 11.1.3.1.	2024-06-25
ays-pro--Quiz Maker	The Quiz Maker plugin for WordPress is vulnerable to time-based SQL Injection via the 'ays_questions' parameter in all versions up to, and including, 6.5.8.3 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.	2024-06-25
Baicells--Snap Router	Use of Hard-coded Credentials vulnerability in Baicells Snap Router BaiCE_BMI on EP3011 (User Passwords modules) allows unauthorized access to the device.	2024-06-25
BC Security--Empire	BC Security Empire before 5.9.3 is vulnerable to a path traversal issue that can lead to remote code execution. A remote, unauthenticated attacker can exploit this vulnerability over HTTP by acting as a normal agent, completing all cryptographic handshakes, and then triggering an upload of payload data containing a malicious path.	2024-06-27
Brocade--Fabric OS	A vulnerability in the default configuration of the Simple Network Management Protocol (SNMP) feature of Brocade Fabric OS versions before v9.0.0 could allow an authenticated, remote attacker to read data from an affected device via SNMP. The vulnerability is due to hard-coded, default community string in the configuration file for the SNMP daemon. An attacker could exploit this vulnerability by using the static community string in SNMP version 1 queries to an affected device.	2024-06-26
ChatGPTNextWeb--ChatGPT-Next-Web	NextChat is a cross-platform ChatGPT/Gemini UI. There is a Server-Side Request Forgery (SSRF) vulnerability due to a lack of validation of the `endpoint` GET parameter on the WebDav API endpoint. This SSRF can be used to perform arbitrary HTTPS request from the vulnerable instance (MKCOL, PUT and GET methods supported), or to target NextChat users and make them execute arbitrary JavaScript code in their browser. This vulnerability has been patched in version 2.12.4.	2024-06-28
CycloneDX--cyclonedx-core-java	The CycloneDX core module provides a model representation of the SBOM along with utilities to assist in creating, validating, and parsing SBOMs. Before deserializing CycloneDX Bill of Materials in XML format, _cyclonedx-core-java_ leverages XPath expressions to determine the schema version of the BOM. The `DocumentBuilderFactory` used to evaluate XPath expressions was not configured securely, making the library vulnerable to XML External Entity (XXE) injection. This vulnerability has been fixed in cyclonedx-core-java version 9.0.4.	2024-06-28
DataDog--dd-trace-cpp	dd-trace-cpp is the Datadog distributed tracing for C++. When the library fails to extract trace context due to malformed unicode, it logs the list of audited headers and their values using the `nlohmann` JSON library. However, due to the way the JSON library is invoked, it throws an uncaught exception, which results in a crash. This vulnerability has been patched in version 0.2.2.	2024-06-28
Dell--Integrated Dell Remote Access Controller 9	iDRAC9, versions prior to 7.00.00.172 for 14th Generation and 7.10.50.00 for 15th and 16th Generations, contains a session hijacking vulnerability in IPMI. A remote attacker could potentially exploit this vulnerability, leading to arbitrary code execution on the vulnerable application.	2024-06-29
Dell--PowerProtect DD	Dell PowerProtect DD, versions prior to 8.0, LTS 7.13.1.0, LTS 7.10.1.30, LTS 7.7.5.40 contain a buffer overflow vulnerability. A remote low privileged attacker could potentially exploit this vulnerability, leading to an application crash or execution of arbitrary code on the vulnerable application's underlying operating system with privileges of the vulnerable application.	2024-06-26
Dell--PowerProtect DD	Dell PowerProtect DD, versions prior to 8.0, LTS 7.13.1.0, LTS 7.10.1.30, LTS 7.7.5.40 contain an OS command injection vulnerability in an admin operation. A remote low privileged attacker could potentially exploit this vulnerability, leading to the execution of arbitrary OS commands on the system application's underlying OS with the privileges of the vulnerable application. Exploitation may lead to a system take over by an attacker.	2024-06-26
Elastic--Elastic Cloud Enterprise	It was identified that under certain specific preconditions, an API key that was originally created with a specific privileges could be subsequently used to create new API keys that have elevated privileges.	2024-06-28
flippercode--WP Maps Display Google Maps Perfectly with Ease	The WordPress Plugin for Google Maps - WP MAPS plugin for WordPress is vulnerable to SQL Injection via the 'id' parameter of the 'put_wpgm' shortcode in all versions up to, and including, 4.6.1 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with contributor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.	2024-06-29
Fortra--FileCatalyst Workflow	A SQL Injection vulnerability in Fortra FileCatalyst Workflow allows an attacker to modify application data. Likely impacts include creation of administrative users and deletion or modification of data in the application database. Data exfiltration via SQL injection is not possible using this vulnerability. Successful unauthenticated exploitation requires a Workflow system with anonymous access enabled, otherwise an authenticated user is required. This issue affects all versions of FileCatalyst Workflow from 5.1.6 Build 135 and earlier.	2024-06-25
gitlab -- gitlab	An issue was discovered in GitLab CE/EE affecting all versions starting from 15.8 prior to 16.11.5, starting from 17.0 prior to 17.0.3, and starting from 17.1 prior to 17.1.1, which allows an attacker to trigger a pipeline as another user under certain circumstances.	2024-06-27
gitlab -- gitlab	Improper authorization in global search in GitLab EE affecting all versions from 16.11 prior to 16.11.5 and 17.0 prior to 17.0.3 and 17.1 prior to 17.1.1 allows an attacker leak content of a private repository in a public project.	2024-06-27
goauthentik--authentik	authentik is an open-source Identity Provider that emphasizes flexibility and versatility. Authentik API-Access-Token mechanism can be exploited to gain admin user privileges. A successful exploit of the issue will result in a user gaining full admin access to the Authentik application, including resetting user passwords and more. This issue has been patched in version(s) 2024.2.4, 2024.4.2 and 2024.6.0.	2024-06-28
goauthentik--authentik	authentik is an open-source Identity Provider. Access restrictions assigned to an application were not checked when using the OAuth2 Device code flow. This could potentially allow users without the correct authorization to get OAuth tokens for an application and access it. This issue has been patched in version(s) 2024.6.0, 2024.2.4 and 2024.4.3.	2024-06-28
HashiCorp--Shared library	HashiCorp's go-getter library can be coerced into executing Git update on an existing maliciously modified Git Configuration, potentially leading to arbitrary code execution.	2024-06-25
Hewlett Packard Enterprise (HPE)--HPE Athonet Mobile Core	A security vulnerability has been identified in HPE Athonet Mobile Core software. The core application contains a code injection vulnerability where a threat actor could execute arbitrary commands with the privilege of the underlying container leading to complete takeover of the target system.	2024-06-25
Hitachi Vantara--Pentaho Business Analytics Server	Hitachi Vantara Pentaho Business Analytics Server prior to versions 10.1.0.0 and 9.3.0.7, including 8.3.x allow a malicious URL to inject content into the Analyzer plugin interface.	2024-06-26
Hitachi Vantara--Pentaho Business Analytics Server	Hitachi Vantara Pentaho Business Analytics Server prior to versions 10.1.0.0 and 9.3.0.7, including 8.3.x allow a malicious URL to inject content into the Analyzer plugin interface.	2024-06-26
Hitachi Vantara--Pentaho Business Analytics Server	Hitachi Vantara Pentaho Business Analytics Server versions before 10.1.0.0 and 9.3.0.7, including 8.3.x do not correctly protect the ACL service endpoint of the Pentaho User Console against XML External Entity Reference.	2024-06-26
IBM--MQ	IBM MQ 9.3 LTS and 9.3 CD could allow an authenticated user to escalate their privileges under certain configurations due to incorrect privilege assignment. IBM X-Force ID: 289894.	2024-06-28
IBM--OpenBMC	IBM OpenBMC FW1050.00 through FW1050.10 BMCWeb HTTPS server component could disclose sensitive URI content to an unauthorized actor that bypasses authentication channels. IBM X-ForceID: 290026.	2024-06-27
IBM--Security Access Manager Docker	IBM Security Access Manager Docker 10.0.0.0 through 10.0.7.1 could allow a local user to obtain root access due to improper access controls. IBM X-Force ID: 254638.	2024-06-27
IBM--Security Access Manager Docker	IBM Security Access Manager Docker 10.0.0.0 through 10.0.7.1 could allow a local user to obtain root access due to improper access controls. IBM X-Force ID: 254649.	2024-06-27
IBM--Security Access Manager Docker	IBM Security Access Manager Docker 10.0.0.0 through 10.0.7.1, under certain configurations, could allow a user on the network to install malicious packages. IBM X-Force ID: 261197.	2024-06-27
Icegram--Email Subscribers & Newsletters	Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Icegram Email Subscribers & Newsletters allows SQL Injection.This issue affects Email Subscribers & Newsletters: from n/a through 5.7.25.	2024-06-26
InstaWP Team--InstaWP Connect	Improper Control of Generation of Code ('Code Injection') vulnerability in InstaWP Team InstaWP Connect allows Code Injection.This issue affects InstaWP Connect: from n/a through 0.1.0.38.	2024-06-24
Intrado--911 Emergency Gateway (EGW)	Intrado 911 Emergency Gateway login form is vulnerable to an unauthenticated blind time-based SQL injection, which may allow an unauthenticated remote attacker to execute malicious code, exfiltrate data, or manipulate the database.	2024-06-26
itsourcecode--Online Food Ordering System	A vulnerability has been found in itsourcecode Online Food Ordering System up to 1.0 and classified as critical. This vulnerability affects unknown code of the file /addproduct.php. The manipulation of the argument photo leads to unrestricted upload. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. VDB-269806 is the identifier assigned to this vulnerability.	2024-06-27
itsourcecode--Pool of Bethesda Online Reservation System	A vulnerability, which was classified as critical, has been found in itsourcecode Pool of Bethesda Online Reservation System 1.0. Affected by this issue is some unknown functionality of the file controller.php. The manipulation of the argument rmtype_id leads to sql injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-269804.	2024-06-27
itsourcecode--Simple Online Hotel Reservation System	A vulnerability was found in itsourcecode Simple Online Hotel Reservation System 1.0. It has been declared as critical. This vulnerability affects unknown code of the file index.php. The manipulation of the argument username leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-269620.	2024-06-25
j11g -- cruddiy	The CRUDDIY project is vulnerable to shell command injection via sending a crafted POST request to the application server. The exploitation risk is limited since CRUDDIY is meant to be launched locally. Nevertheless, a user with the project running on their computer might visit a website which would send such a malicious request to the locally launched server.	2024-06-24
Juniper Networks--Session Smart Router	An Authentication Bypass Using an Alternate Path or Channel vulnerability in Juniper Networks Session Smart Router or conductor running with a redundant peer allows a network based attacker to bypass authentication and take full control of the device. Only routers or conductors that are running in high-availability redundant configurations are affected by this vulnerability. No other Juniper Networks products or platforms are affected by this issue. This issue affects: Session Smart Router: * All versions before 5.6.15, * from 6.0 before 6.1.9-lts, * from 6.2 before 6.2.5-sts. Session Smart Conductor: * All versions before 5.6.15, * from 6.0 before 6.1.9-lts, * from 6.2 before 6.2.5-sts. WAN Assurance Router: * 6.0 versions before 6.1.9-lts, * 6.2 versions before 6.2.5-sts.	2024-06-27
linux -- linux_kernel	In the Linux kernel, the following vulnerability has been resolved: drm: zynqmp_dpsub: Always register bridge We must always register the DRM bridge, since zynqmp_dp_hpd_work_func calls drm_bridge_hpd_notify, which in turn expects hpd_mutex to be initialized. We do this before zynqmp_dpsub_drm_init since that calls drm_bridge_attach. This fixes the following lockdep warning: [ 19.217084] ------------[ cut here ]------------ [ 19.227530] DEBUG_LOCKS_WARN_ON(lock->magic != lock) [ 19.227768] WARNING: CPU: 0 PID: 140 at kernel/locking/mutex.c:582 __mutex_lock+0x4bc/0x550 [ 19.241696] Modules linked in: [ 19.244937] CPU: 0 PID: 140 Comm: kworker/0:4 Not tainted 6.6.20+ #96 [ 19.252046] Hardware name: xlnx,zynqmp (DT) [ 19.256421] Workqueue: events zynqmp_dp_hpd_work_func [ 19.261795] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 19.269104] pc : __mutex_lock+0x4bc/0x550 [ 19.273364] lr : __mutex_lock+0x4bc/0x550 [ 19.277592] sp : ffffffc085c5bbe0 [ 19.281066] x29: ffffffc085c5bbe0 x28: 0000000000000000 x27: ffffff88009417f8 [ 19.288624] x26: ffffff8800941788 x25: ffffff8800020008 x24: ffffffc082aa3000 [ 19.296227] x23: ffffffc080d90e3c x22: 0000000000000002 x21: 0000000000000000 [ 19.303744] x20: 0000000000000000 x19: ffffff88002f5210 x18: 0000000000000000 [ 19.311295] x17: 6c707369642e3030 x16: 3030613464662072 x15: 0720072007200720 [ 19.318922] x14: 0000000000000000 x13: 284e4f5f4e524157 x12: 0000000000000001 [ 19.326442] x11: 0001ffc085c5b940 x10: 0001ff88003f388b x9 : 0001ff88003f3888 [ 19.334003] x8 : 0001ff88003f3888 x7 : 0000000000000000 x6 : 0000000000000000 [ 19.341537] x5 : 0000000000000000 x4 : 0000000000001668 x3 : 0000000000000000 [ 19.349054] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffffff88003f3880 [ 19.356581] Call trace: [ 19.359160] __mutex_lock+0x4bc/0x550 [ 19.363032] mutex_lock_nested+0x24/0x30 [ 19.367187] drm_bridge_hpd_notify+0x2c/0x6c [ 19.371698] zynqmp_dp_hpd_work_func+0x44/0x54 [ 19.376364] process_one_work+0x3ac/0x988 [ 19.380660] worker_thread+0x398/0x694 [ 19.384736] kthread+0x1bc/0x1c0 [ 19.388241] ret_from_fork+0x10/0x20 [ 19.392031] irq event stamp: 183 [ 19.395450] hardirqs last enabled at (183): [<ffffffc0800b9278>] finish_task_switch.isra.0+0xa8/0x2d4 [ 19.405140] hardirqs last disabled at (182): [<ffffffc081ad3754>] __schedule+0x714/0xd04 [ 19.413612] softirqs last enabled at (114): [<ffffffc080133de8>] srcu_invoke_callbacks+0x158/0x23c [ 19.423128] softirqs last disabled at (110): [<ffffffc080133de8>] srcu_invoke_callbacks+0x158/0x23c [ 19.432614] ---[ end trace 0000000000000000 ]--- (cherry picked from commit 61ba791c4a7a09a370c45b70a81b8c7d4cf6b2ae)	2024-06-24
linux -- linux_kernel	In the Linux kernel, the following vulnerability has been resolved: riscv: prevent pt_regs corruption for secondary idle threads Top of the kernel thread stack should be reserved for pt_regs. However this is not the case for the idle threads of the secondary boot harts. Their stacks overlap with their pt_regs, so both may get corrupted. Similar issue has been fixed for the primary hart, see c7cdd96eca28 ("riscv: prevent stack corruption by reserving task_pt_regs(p) early"). However that fix was not propagated to the secondary harts. The problem has been noticed in some CPU hotplug tests with V enabled. The function smp_callin stored several registers on stack, corrupting top of pt_regs structure including status field. As a result, kernel attempted to save or restore inexistent V context.	2024-06-24
linux -- linux_kernel	In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Fix buffer size in gfx_v9_4_3_init_ cp_compute_microcode() and rlc_microcode() The function gfx_v9_4_3_init_microcode in gfx_v9_4_3.c was generating about potential truncation of output when using the snprintf function. The issue was due to the size of the buffer 'ucode_prefix' being too small to accommodate the maximum possible length of the string being written into it. The string being written is "amdgpu/%s_mec.bin" or "amdgpu/%s_rlc.bin", where %s is replaced by the value of 'chip_name'. The length of this string without the %s is 16 characters. The warning message indicated that 'chip_name' could be up to 29 characters long, resulting in a total of 45 characters, which exceeds the buffer size of 30 characters. To resolve this issue, the size of the 'ucode_prefix' buffer has been reduced from 30 to 15. This ensures that the maximum possible length of the string being written into the buffer will not exceed its size, thus preventing potential buffer overflow and truncation issues. Fixes the below with gcc W=1: drivers/gpu/drm/amd/amdgpu/gfx_v9_4_3.c: In function 'gfx_v9_4_3_early_init': drivers/gpu/drm/amd/amdgpu/gfx_v9_4_3.c:379:52: warning: '%s' directive output may be truncated writing up to 29 bytes into a region of size 23 [-Wformat-truncation=] 379 \| snprintf(fw_name, sizeof(fw_name), "amdgpu/%s_rlc.bin", chip_name); \| ^~ ...... 439 \| r = gfx_v9_4_3_init_rlc_microcode(adev, ucode_prefix); \| ~~~~~~~~~~~~ drivers/gpu/drm/amd/amdgpu/gfx_v9_4_3.c:379:9: note: 'snprintf' output between 16 and 45 bytes into a destination of size 30 379 \| snprintf(fw_name, sizeof(fw_name), "amdgpu/%s_rlc.bin", chip_name); \| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ drivers/gpu/drm/amd/amdgpu/gfx_v9_4_3.c:413:52: warning: '%s' directive output may be truncated writing up to 29 bytes into a region of size 23 [-Wformat-truncation=] 413 \| snprintf(fw_name, sizeof(fw_name), "amdgpu/%s_mec.bin", chip_name); \| ^~ ...... 443 \| r = gfx_v9_4_3_init_cp_compute_microcode(adev, ucode_prefix); \| ~~~~~~~~~~~~ drivers/gpu/drm/amd/amdgpu/gfx_v9_4_3.c:413:9: note: 'snprintf' output between 16 and 45 bytes into a destination of size 30 413 \| snprintf(fw_name, sizeof(fw_name), "amdgpu/%s_mec.bin", chip_name); \| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~	2024-06-24
Magarsus Consultancy--SSO (Single Sign On)	Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection'), CWE - 200 - Exposure of Sensitive Information to an Unauthorized Actor, CWE - 522 - Insufficiently Protected Credentials vulnerability in Magarsus Consultancy SSO (Single Sign On) allows SQL Injection.This issue affects SSO (Single Sign On): from 1.0 before 1.1.	2024-06-26
Membership Software--WishList Member X	Improper Control of Generation of Code ('Code Injection') vulnerability in Membership Software WishList Member X allows Code Injection.This issue affects WishList Member X: from n/a before 3.26.7.	2024-06-24
Membership Software--WishList Member X	Improper Privilege Management vulnerability in Membership Software WishList Member X allows Privilege Escalation.This issue affects WishList Member X: from n/a before 3.26.7.	2024-06-24
Membership Software--WishList Member X	Missing Authorization vulnerability in Membership Software WishList Member X.This issue affects WishList Member X: from n/a before 3.26.7.	2024-06-24
Mia Technology Inc.--Mia-Med Health Aplication	Improper Restriction of Excessive Authentication Attempts vulnerability in Mia Technology Inc. Mia-Med Health Aplication allows Interface Manipulation.This issue affects Mia-Med Health Aplication: before 1.0.14.	2024-06-24
Microsoft--Microsoft Power Platform	An authenticated attacker can exploit an Untrusted Search Path vulnerability in Microsoft Dataverse to execute code over a network.	2024-06-27
mitmproxy--pdoc	pdoc provides API Documentation for Python Projects. Documentation generated with `pdoc --math` linked to JavaScript files from polyfill.io. The polyfill.io CDN has been sold and now serves malicious code. This issue has been fixed in pdoc 14.5.1.	2024-06-26
modalweb--Advanced File Manager	The Advanced File Manager plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 5.2.4 via the 'fma_local_file_system' function. This makes it possible for unauthenticated attackers to extract sensitive data including backups or other sensitive information if the files have been moved to the built-in Trash folder.	2024-06-29
Moxa--OnCell G3150A-LTE Series	OnCell G3470A-LTE Series firmware versions v1.7.7 and prior have been identified as vulnerable due to a lack of neutralized inputs in IPSec configuration. An attacker could modify the intended commands sent to target functions, which could cause malicious users to execute unauthorized commands.	2024-06-25
Moxa--OnCell G3150A-LTE Series	OnCell G3470A-LTE Series firmware versions v1.7.7 and prior have been identified as vulnerable due to missing bounds checking on buffer operations. An attacker could write past the boundaries of allocated buffer regions in memory, causing a program crash.	2024-06-25
Moxa--OnCell G3470A-LTE Series	OnCell G3470A-LTE Series firmware versions v1.7.7 and prior have been identified as vulnerable due to a lack of neutralized inputs in the web key upload function. An attacker could modify the intended commands sent to target functions, which could cause malicious users to execute unauthorized commands.	2024-06-25
n/a--n/a	An issue was discovered in the Agent in Delinea Privilege Manager (formerly Thycotic Privilege Manager) before 12.0.1096 on Windows. Sometimes, a non-administrator user can copy a crafted DLL file to a temporary directory (used by .NET Shadow Copies) such that privilege escalation can occur if the core agent service loads that file.	2024-06-28
Next4Biz CRM & BPM Software--Business Process Manangement (BPM)	Improper Control of Generation of Code ('Code Injection') vulnerability in Next4Biz CRM & BPM Software Business Process Manangement (BPM) allows Remote Code Inclusion.This issue affects Business Process Manangement (BPM): from 6.6.4.4 before 6.6.4.5.	2024-06-24
omron -- nj101-1000_firmware	Insufficient verification of data authenticity issue exists in NJ Series CPU Unit all versions and NX Series CPU Unit all versions. If a user program in the affected product is altered, the product may not be able to detect the alteration.	2024-06-24
pendulum-project--ntpd-rs	nptd-rs is a tool for synchronizing your computer's clock, implementing the NTP and NTS protocols. There is a missing limit for accepted NTS-KE connections. This allows an unauthenticated remote attacker to crash ntpd-rs when an NTS-KE server is configured. Non NTS-KE server configurations, such as the default ntpd-rs configuration, are unaffected. This vulnerability has been patched in version 1.1.3.	2024-06-28
pgadmin.org--pgAdmin 4	pgAdmin <= 8.8 has an installation Directory permission issue. Because of this issue, attackers can gain unauthorised access to the installation directory on the Debian or RHEL 8 platforms.	2024-06-25
Progress Software Corporation--WhatsUp Gold	In WhatsUp Gold versions released before 2023.1.3, a Remote Code Execution issue exists in Progress WhatsUp Gold. This vulnerability allows an unauthenticated attacker to achieve the RCE as a service account through NmApi.exe.	2024-06-25
Progress Software Corporation--WhatsUp Gold	In WhatsUp Gold versions released before 2023.1.3, an unauthenticated Remote Code Execution vulnerability in Progress WhatsUpGold. The Apm.UI.Areas.APM.Controllers.CommunityController allows execution of commands with iisapppool\nmconsole privileges.	2024-06-25
Progress Software Corporation--WhatsUp Gold	In WhatsUp Gold versions released before 2023.1.3, an unauthenticated Remote Code Execution vulnerability in Progress WhatsUpGold. The WhatsUp.ExportUtilities.Export.GetFileWithoutZip allows execution of commands with iisapppool\nmconsole privileges.	2024-06-25
Progress Software Corporation--WhatsUp Gold	In WhatsUp Gold versions released before 2023.1.3, an authenticated user with certain permissions can upload an arbitrary file and obtain RCE using Apm.UI.Areas.APM.Controllers.Api.Applications.AppProfileImportController.	2024-06-25
Progress Software Corporation--WhatsUp Gold	In WhatsUp Gold versions released before 2023.1.3, an Improper Access Control vulnerability in Wug.UI.Controllers.InstallController.SetAdminPassword allows local attackers to modify admin's password.	2024-06-25
Progress Software Corporation--WhatsUp Gold	In WhatsUp Gold versions released before 2023.1.3, there is a missing authentication vulnerability in WUGDataAccess.Credentials. This vulnerability allows unauthenticated attackers to disclose Windows Credentials stored in the product Credential Library.	2024-06-25
Progress Software Corporation--WhatsUp Gold	In WhatsUp Gold versions released before 2023.1.3, a vulnerability exists in the TestController functionality. A specially crafted unauthenticated HTTP request can lead to a disclosure of sensitive information.	2024-06-25
Progress Software Corporation--WhatsUp Gold	In WhatsUp Gold versions released before 2023.1.3, an uncontrolled resource consumption vulnerability exists. A specially crafted unauthenticated HTTP request to the TestController Chart functionality can lead to denial of service.	2024-06-25
Progress Software Corporation--WhatsUp Gold	In WhatsUp Gold versions released before 2023.1.3, an unauthenticated Denial of Service vulnerability was identified. An unauthenticated attacker can put the application into the SetAdminPassword installation step, which renders the application non-accessible.	2024-06-25
Progress Software Corporation--WhatsUp Gold	In WhatsUp Gold versions released before 2023.1.3, a Server Side Request Forgery vulnerability exists in the GetASPReport feature. This allows any authenticated user to retrieve ASP reports from an HTML form.	2024-06-25
Progress Software Corporation--WhatsUp Gold	In WhatsUp Gold versions released before 2023.1.3, an authenticated SSRF vulnerability in Wug.UI.Areas.Wug.Controllers.SessionControler.Update allows a low privileged user to chain this SSRF with an Improper Access Control vulnerability. This can be used to escalate privileges to Admin.	2024-06-25
Progress Software Corporation--WhatsUp Gold	In WhatsUp Gold versions released before 2023.1.3, Distributed Edition installations can be exploited by using a deserialization tool to achieve a Remote Code Execution as SYSTEM. The vulnerability exists in the main message processing routines NmDistributed.DistributedServiceBehavior.OnMessage for server and NmDistributed.DistributedClient.OnMessage for clients.	2024-06-25
Progress--MOVEit Gateway	Improper Authentication vulnerability in Progress MOVEit Gateway (SFTP modules) allows Authentication Bypass.This issue affects MOVEit Gateway: 2024.0.0.	2024-06-25
Progress--MOVEit Transfer	Improper Authentication vulnerability in Progress MOVEit Transfer (SFTP module) can lead to Authentication Bypass.This issue affects MOVEit Transfer: from 2023.0.0 before 2023.0.11, from 2023.1.0 before 2023.1.6, from 2024.0.0 before 2024.0.2.	2024-06-25
PTC--Creo Elements/Direct License	PTC Creo Elements/Direct License Server exposes a web interface which can be used by unauthenticated remote attackers to execute arbitrary OS commands on the server.	2024-06-27
renesas -- rcar_gen3	Incorrect Calculation vulnerability in Renesas arm-trusted-firmware allows Local Execution of Code. When checking whether a new image invades/overlaps with a previously loaded image the code neglects to consider a few cases. that could An attacker to bypass memory range restriction and overwrite an already loaded image partly or completely, which could result in code execution and bypass of secure boot.	2024-06-24
Salon Booking System--Salon booking system	Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Salon Booking System Salon booking system allows File Manipulation.This issue affects Salon booking system: from n/a through 9.9.	2024-06-24
scidsg--hushline	Hush Line is a free and open-source, anonymous-tip-line-as-a-service for organizations or individuals. There is a stored XSS in the Inbox. The input is displayed using the `safe` Jinja2 attribute, and thus not sanitized upon display. This issue has been patched in version 0.1.0.	2024-06-28
scidsg--hushline	Hush Line is a free and open-source, anonymous-tip-line-as-a-service for organizations or individuals. The TOTP authentication flow has multiple issues that weakens its one-time nature. Specifically, the lack of 2FA for changing security settings allows attacker with CSRF or XSS primitives to change such settings without user interaction and credentials are required. This vulnerability has been patched in version 0.10.	2024-06-27
silabs.com--Ember ZNet SDK	An unauthenticated IEEE 802.15.4 'co-ordinator realignment' packet can be used to force Zigbee nodes to change their network identifier (pan ID), leading to a denial of service. This packet type is not useful in production and should be used only for PHY qualification.	2024-06-27
SoftEtherVPN--SoftEtherVPN	SoftEtherVPN is a an open-source cross-platform multi-protocol VPN Program. When SoftEtherVPN is deployed with L2TP enabled on a device, it introduces the possibility of the host being used for amplification/reflection traffic generation because it will respond to every packet with two response packets that are larger than the request packet size. These sorts of techniques are used by external actors who generate spoofed source IPs to target a destination on the internet. This vulnerability has been patched in version 5.02.5185.	2024-06-26
Spotfire--Spotfire Analyst	Vulnerability in Spotfire Spotfire Analyst, Spotfire Spotfire Server, Spotfire Spotfire for AWS Marketplace allows In the case of the installed Windows client: Successful execution of this vulnerability will result in an attacker being able to run arbitrary code.This requires human interaction from a person other than the attacker., In the case of the Web player (Business Author): Successful execution of this vulnerability via the Web Player, will result in the attacker being able to run arbitrary code as the account running the Web player process, In the case of Automation Services: Successful execution of this vulnerability will result in an attacker being able to run arbitrary code via Automation Services..This issue affects Spotfire Analyst: from 12.0.9 through 12.5.0, from 14.0 through 14.0.2; Spotfire Server: from 12.0.10 through 12.5.0, from 14.0 through 14.0.3, from 14.2.0 through 14.3.0; Spotfire for AWS Marketplace: from 14.0 before 14.3.0.	2024-06-27
stiofansisland--UsersWP Front-end login form, User Registration, User Profile & Members Directory plugin for WordPress	The UsersWP - Front-end login form, User Registration, User Profile & Members Directory plugin for WordPress plugin for WordPress is vulnerable to time-based SQL Injection via the 'uwp_sort_by' parameter in all versions up to, and including, 1.2.10 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.	2024-06-29
StylemixThemes--Consulting Elementor Widgets	Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in StylemixThemes Consulting Elementor Widgets allows PHP Local File Inclusion.This issue affects Consulting Elementor Widgets: from n/a through 1.3.0.	2024-06-24
StylemixThemes--Consulting Elementor Widgets	Improper Neutralization of Special Elements used in a Command ('Command Injection') vulnerability in StylemixThemes Consulting Elementor Widgets allows OS Command Injection.This issue affects Consulting Elementor Widgets: from n/a through 1.3.0.	2024-06-24
StylemixThemes--Consulting Elementor Widgets	Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in StylemixThemes Consulting Elementor Widgets allows PHP Local File Inclusion.This issue affects Consulting Elementor Widgets: from n/a through 1.3.0.	2024-06-24
Synology--Camera Firmware	A vulnerability regarding buffer copy without checking size of input ('Classic Buffer Overflow') is found in the libjansson component and it does not affect the upstream library. This allows remote attackers to execute arbitrary code via unspecified vectors. The following models with Synology Camera Firmware versions before 1.0.7-0298 may be affected: BC500 and TC500.	2024-06-28
Synology--Camera Firmware	A vulnerability regarding improper neutralization of special elements used in an OS command ('OS Command Injection') is found in the IP block functionality. This allows remote authenticated users with administrator privileges to execute arbitrary commands via unspecified vectors. The following models with Synology Camera Firmware versions before 1.0.7-0298 may be affected: BC500 and TC500.	2024-06-28
Synology--Camera Firmware	A vulnerability regarding authentication bypass by spoofing is found in the RTSP functionality. This allows man-in-the-middle attackers to obtain privileges without consent via unspecified vectors. The following models with Synology Camera Firmware versions before 1.0.7-0298 may be affected: BC500 and TC500.	2024-06-28
Synology--Camera Firmware	A vulnerability regarding improper neutralization of special elements used in an OS command ('OS Command Injection') is found in the NTP configuration. This allows remote authenticated users with administrator privileges to execute arbitrary commands via unspecified vectors. The following models with Synology Camera Firmware versions before 1.0.7-0298 may be affected: BC500 and TC500.	2024-06-28
Synology--Synology Router Manager (SRM)	Download of code without integrity check vulnerability in AirPrint functionality in Synology Router Manager (SRM) before 1.2.5-8227-11 and 1.3.1-9346-8 allows man-in-the-middle attackers to execute arbitrary code via unspecified vectors.	2024-06-28
Talya Informatics--Elektraweb	Reliance on Cookies without Validation and Integrity Checking vulnerability in Talya Informatics Elektraweb allows Session Credential Falsification through Manipulation, Accessing/Intercepting/Modifying HTTP Cookies, Manipulating Opaque Client-based Data Tokens.This issue affects Elektraweb: before v17.0.68.	2024-06-27
Talya Informatics--Elektraweb	Improper Access Control, Missing Authorization, Incorrect Authorization, Incorrect Permission Assignment for Critical Resource, Missing Authentication, Weak Authentication, Improper Restriction of Communication Channel to Intended Endpoints vulnerability in Talya Informatics Elektraweb allows Exploiting Incorrectly Configured Access Control Security Levels, Manipulating Web Input to File System Calls, Embedding Scripts within Scripts, Malicious Logic Insertion, Modification of Windows Service Configuration, Malicious Root Certificate, Intent Spoof, WebView Exposure, Data Injected During Configuration, Incomplete Data Deletion in a Multi-Tenant Environment, Install New Service, Modify Existing Service, Install Rootkit, Replace File Extension Handlers, Replace Trusted Executable, Modify Shared File, Add Malicious File to Shared Webroot, Run Software at Logon, Disable Security Software.This issue affects Elektraweb: before v17.0.68.	2024-06-27
Talya Informatics--Travel APPS	Authorization Bypass Through User-Controlled Key vulnerability in Talya Informatics Travel APPS allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Travel APPS: before v17.0.68.	2024-06-27
The Conduit Contributors--Conduit	Missing authorization in Client-Server API in Conduit <=0.7.0, allowing for any alias to be removed and added to another room, which can be used for privilege escalation by moving the #admins alias to a room which they control, allowing them to run commands resetting passwords, siging json with the server's key, deactivating users, and more	2024-06-25
The Conduit Contributors--Conduit	Lack of privilege checking when processing a redaction in Conduit versions v0.6.0 and lower, allowing a local user to redact any message from users on the same server, given that they are able to send redaction events.	2024-06-25
themewinter--WPCafe Online Food Ordering, Restaurant Menu, Delivery, and Reservations for WooCommerce	The WPCafe - Online Food Ordering, Restaurant Menu, Delivery, and Reservations for WooCommerce plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 2.2.25 via the reservation_extra_field shortcode parameter. This makes it possible for authenticated attackers, with Contributor-level access and above, to include remote files on the server, potentially resulting in code execution	2024-06-25
Tp-Link--ER7206 Omada Gigabit VPN Router	A leftover debug code vulnerability exists in the cli_server debug functionality of Tp-Link ER7206 Omada Gigabit VPN Router 1.4.1 Build 20240117 Rel.57421. A specially crafted series of network requests can lead to arbitrary command execution. An attacker can send a sequence of requests to trigger this vulnerability.	2024-06-25
tpm2-software--tpm2-tools	tpm2 is the source repository for the Trusted Platform Module (TPM2.0) tools. This vulnerability allows attackers to manipulate tpm2_checkquote outputs by altering the TPML_PCR_SELECTION in the PCR input file. As a result, digest values are incorrectly mapped to PCR slots and banks, providing a misleading picture of the TPM state. This issue has been patched in version 5.7.	2024-06-28
usbarmory--mxs-dcp	The NXP Data Co-Processor (DCP) is a built-in hardware module for specific NXP SoCsÂ¹ that implements a dedicated AES cryptographic engine for encryption/decryption operations. The dcp_tool reference implementation included in the repository selected the test key, regardless of its `-t` argument. This issue has been patched in commit 26a7.	2024-06-28
virtosoftware -- sharepoint_bulk_file_download	An issue was discovered in VirtoSoftware Virto Bulk File Download 5.5.44 for SharePoint 2019. The Virto.SharePoint.FileDownloader/Api/Download.ashx isCompleted method allows arbitrary file download and deletion via absolute path traversal in the path parameter.	2024-06-24
VMware--Salt Project	A specially crafted url can be created which leads to a directory traversal in the salt file server. A malicious user can read an arbitrary file from a Salt master's filesystem.	2024-06-27
warfareplugins--Social Sharing Plugin Social Warfare	Several plugins for WordPress hosted on WordPress.org have been compromised and injected with malicious PHP scripts. A malicious threat actor compromised the source code of various plugins and injected code that exfiltrates database credentials and is used to create new, malicious, administrator users and send that data back to a server. Currently, not all plugins have been patched and we strongly recommend uninstalling the plugins for the time being and running a complete malware scan.	2024-06-25
wpeka-club--Cookie Consent for WP Cookie Consent, Consent Log, Cookie Scanner, Script Blocker (for GDPR, CCPA & ePrivacy)	The WP Cookie Consent ( for GDPR, CCPA & ePrivacy ) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'Client-IP' header in all versions up to, and including, 3.2.0 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.	2024-06-26

Medium Vulnerabilities

Primary Vendor -- Product	Description	Published
Adobe--Adobe Experience Manager	Adobe Experience Manager versions 6.5.20 and earlier are affected by a stored Cross-Site Scripting (XSS) vulnerability that could be abused by a low-privileged attacker to inject malicious scripts into vulnerable form fields. Malicious JavaScript may be executed in a victim's browser when they browse to the page containing the vulnerable field.	2024-06-25
Adobe--Adobe Experience Manager	Adobe Experience Manager versions 6.5.20 and earlier are affected by a stored Cross-Site Scripting (XSS) vulnerability that could be abused by a low-privileged attacker to inject malicious scripts into vulnerable form fields. Malicious JavaScript may be executed in a victim's browser when they browse to the page containing the vulnerable field.	2024-06-25
amans2k--Funnel Builder for WordPress by FunnelKit Customize WooCommerce Checkout Pages, Create Sales Funnels, Order Bumps & One Click Upsells	The Funnel Builder for WordPress by FunnelKit - Customize WooCommerce Checkout Pages, Create Sales Funnels, Order Bumps & One Click Upsells plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'mimes' parameter in all versions up to, and including, 3.3.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.	2024-06-29
anchorcms -- anchor_cms	Cross Site Scripting vulnerability in Anchor CMS v.0.12.7 allows a remote attacker to execute arbitrary code via a crafted .pdf file.	2024-06-24
Automattic--WordPress	Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Automattic WordPress allows Stored XSS.This issue affects WordPress: from 6.5 through 6.5.4, from 6.4 through 6.4.4, from 6.3 through 6.3.4, from 6.2 through 6.2.5, from 6.1 through 6.1.6, from 6.0 through 6.0.8, from 5.9 through 5.9.9.	2024-06-25
Automattic--WordPress	Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Automattic WordPress allows Relative Path Traversal.This issue affects WordPress: from 6.5 through 6.5.4, from 6.4 through 6.4.4, from 6.3 through 6.3.4, from 6.2 through 6.2.5, from 6.1 through 6.1.6, from 6.0 through 6.0.8, from 5.9 through 5.9.9, from 5.8 through 5.8.9, from 5.7 through 5.7.11, from 5.6 through 5.6.13, from 5.5 through 5.5.14, from 5.4 through 5.4.15, from 5.3 through 5.3.17, from 5.2 through 5.2.20, from 5.1 through 5.1.18, from 5.0 through 5.0.21, from 4.9 through 4.9.25, from 4.8 through 4.8.24, from 4.7 through 4.7.28, from 4.6 through 4.6.28, from 4.5 through 4.5.31, from 4.4 through 4.4.32, from 4.3 through 4.3.33, from 4.2 through 4.2.37, from 4.1 through 4.1.40.	2024-06-25
awordpresslife--Portfolio Gallery Image Gallery Plugin	The Portfolio Gallery - Image Gallery Plugin plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'PFG' shortcode in all versions up to, and including, 1.6.4 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.	2024-06-27
bdthemes--Ultimate Post Kit Addons For Elementor (Post Grid, Post Carousel, Post Slider, Category List, Post Tabs, Timeline, Post Ticker, Tag Cloud)	The Ultimate Post Kit Addons For Elementor - (Post Grid, Post Carousel, Post Slider, Category List, Post Tabs, Timeline, Post Ticker, Tag Cloud) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'url' parameter within the Social Count (Static) widget in all versions up to, and including, 3.11.7 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.	2024-06-28
berriai--berriai/litellm	berriai/litellm version 1.34.34 is vulnerable to improper access control in its team management functionality. This vulnerability allows attackers to perform unauthorized actions such as creating, updating, viewing, deleting, blocking, and unblocking any teams, as well as adding or deleting any member to or from any teams. The vulnerability stems from insufficient access control checks in various team management endpoints, enabling attackers to exploit these functionalities without proper authorization.	2024-06-27
bfintal--Stackable Page Builder Gutenberg Blocks	The Stackable - Page Builder Gutenberg Blocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'data-caption' parameter in all versions up to, and including, 3.13.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.	2024-06-28
bhagirath25--Floating Social Buttons	The Floating Social Buttons plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.5. This is due to missing or incorrect nonce validation on the floating_social_buttons_option() function. This makes it possible for unauthenticated attackers to update the plugins settings and inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.	2024-06-29
bigbluebutton--bigbluebutton	BigBlueButton is an open-source virtual classroom designed to help teachers teach and learners learn. An attacker with a valid join link to a meeting can trick BigBlueButton into generating a signed join link with additional parameters. One of those parameters may be "role=moderator", allowing an attacker to join a meeting as moderator using a join link that was originally created for viewer access. This vulnerability has been patched in version(s) 2.6.18, 2.7.8 and 3.0.0-alpha.7.	2024-06-28
Blossom Themes--BlossomThemes Email Newsletter	Server-Side Request Forgery (SSRF) vulnerability in Blossom Themes BlossomThemes Email Newsletter.This issue affects BlossomThemes Email Newsletter: from n/a through 2.2.6.	2024-06-26
brechtvds--Easy Affiliate Links	The Easy Affiliate Links plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the eafl_reset_settings AJAX action in all versions up to, and including, 3.7.3. This makes it possible for authenticated attackers, with Subscriber-level access and above, to reset the plugin's settings.	2024-06-28
brechtvds--Easy Image Collage	The Easy Image Collage plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the ajax_image_collage() function in all versions up to, and including, 1.13.5. This makes it possible for authenticated attackers, with Contributor-level access and above, to erase all of the content in arbitrary posts.	2024-06-28
britner--Gutenberg Blocks with AI by Kadence WP Page Builder Features	The Gutenberg Blocks with AI by Kadence WP - Page Builder Features plugin for WordPress is vulnerable to DOM-based Stored Cross-Site Scripting via HTML data attributes in all versions up to, and including, 3.2.45 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.	2024-06-29
Brocade--Fabric OS	A vulnerability in a password management API in Brocade Fabric OS versions before v9.2.1, v9.2.0b, v9.1.1d, and v8.2.3e prints sensitive information in log files. This could allow an authenticated user to view the server passwords for protocols such as scp and sftp. Detail. When the firmwaredownload command is incorrectly entered or points to an erroneous file, the firmware download log captures the failed command, including any password entered in the command line.	2024-06-26
Brocade--Fabric OS	A vulnerability in the web interface in Brocade Fabric OS before v9.2.1, v9.2.0b, and v9.1.1d prints encoded session passwords on session storage for Virtual Fabric platforms. This could allow an authenticated user to view other users' session encoded passwords.	2024-06-26
Canonical Ltd.--Ubuntu Advantage Desktop Pro	Marco Trevisan discovered that the Ubuntu Advantage Desktop Daemon, before version 1.12, leaks the Pro token to unprivileged users by passing the token as an argument in plaintext.	2024-06-27
carlosfazenda--Page and Post Clone	The Page and Post Clone plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 6.0 via the 'content_clone' function due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Author-level access and above, to clone and read private posts.	2024-06-29
Checkmk GmbH--Checkmk	Stored XSS in some confirmation pop-ups in Checkmk before versions 2.3.0p7 and 2.2.0p28 allows Checkmk users to execute arbitrary scripts by injecting HTML elements into some user input fields that are shown in a confirmation pop-up.	2024-06-25
Checkmk GmbH--Checkmk	Stored XSS in the Crash Report page in Checkmk before versions 2.3.0p7, 2.2.0p28, 2.1.0p45, and 2.0.0 (EOL) allows users with permission to change Global Settings to execute arbitrary scripts by injecting HTML elements into the Crash Report URL in the Global Settings.	2024-06-25
CryoutCreations--Anima	Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in CryoutCreations Anima allows Stored XSS.This issue affects Anima: from n/a through 1.4.1.	2024-06-26
Dell--PowerEdge Platform	Dell PowerEdge Server BIOS contains an TOCTOU race condition vulnerability. A local low privileged attacker could potentially exploit this vulnerability to gain access to otherwise unauthorized resources.	2024-06-25
Dell--PowerProtect DD	Dell PowerProtect DD, versions prior to 8.0, LTS 7.13.1.0, LTS 7.10.1.30, LTS 7.7.5.40 contain a Server-Side Request Forgery (SSRF) vulnerability. A remote high privileged attacker could potentially exploit this vulnerability, leading to disclosure of information on the application or remote client.	2024-06-26
Dell--PowerProtect DD	Dell PowerProtect DD, versions prior to 8.0, LTS 7.13.1.0, LTS 7.10.1.30, LTS 7.7.5.40 contain an Improper Control of a Resource Through its Lifetime vulnerability in an admin operation. A remote low privileged attacker could potentially exploit this vulnerability, leading to temporary resource constraint of system application. Exploitation may lead to denial of service of the application.	2024-06-26
Dell--PowerProtect DD	Dell PowerProtect DD, versions prior to 8.0, LTS 7.13.1.0, LTS 7.10.1.30, LTS 7.7.5.40 contain a Stored Cross-Site Scripting Vulnerability. A remote high privileged attacker could potentially exploit this vulnerability, leading to the storage of malicious HTML or JavaScript codes in a trusted application data store. When a high privileged victim user accesses the data store through their browsers, the malicious code gets executed by the web browser in the context of the vulnerable web application. Exploitation may lead to information disclosure, session theft, or client-side request forgery	2024-06-26
Dell--PowerProtect DD	Dell PowerProtect Data Domain, versions prior to 7.13.0.0, LTS 7.7.5.40, LTS 7.10.1.30 contain an weak cryptographic algorithm vulnerability. A remote unauthenticated attacker could potentially exploit this vulnerability, leading to man-in-the-middle attack that exposes sensitive session information.	2024-06-26
Dell--PowerProtect DD	Dell Data Domain, versions prior to 7.13.0.0, LTS 7.7.5.30, LTS 7.10.1.20 contain an SQL Injection vulnerability. A local low privileged attacker could potentially exploit this vulnerability, leading to the execution of certain SQL commands on the application's backend database causing unauthorized access to application data.	2024-06-26
Dell--PowerProtect DD	Dell PowerProtect DD, versions prior to 8.0, LTS 7.13.1.0, LTS 7.10.1.30, LTS 7.7.5.40 on DDMC contain a relative path traversal vulnerability. A remote high privileged attacker could potentially exploit this vulnerability, leading to the application sending over an unauthorized file to the managed system.	2024-06-26
detheme -- dethemekit_for_elementor	The DethemeKit For Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the URL parameter of the De Gallery widget in all versions up to and including 2.1.5 due to insufficient input sanitization and output escaping on user-supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user clicks on the injected link.	2024-06-27
devitemsllc--HT Mega Absolute Addons For Elementor	The HT Mega - Absolute Addons For Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Video player widget settings in all versions up to, and including, 2.5.5 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.	2024-06-26
devitemsllc--HT Mega Absolute Addons For Elementor	The HT Mega - Absolute Addons For Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via multiple widgets in all versions up to, and including, 2.5.5 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.	2024-06-26
Dream-Theme--The7 Website and eCommerce Builder for WordPress	The The7 - Website and eCommerce Builder for WordPress theme for WordPress is vulnerable to Stored Cross-Site Scripting via the 'url' attribute within the plugin's Icon and Heading widgets in all versions up to, and including, 11.13.0 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.	2024-06-25
Enalean--tuleap	Tuleap is an Open Source Suite to improve management of software developments and collaboration. Users are able to see backlog items that they should not see. This issue has been patched in Tuleap Community Edition version 15.9.99.97.	2024-06-25
ericsson -- codechecker	CodeChecker is an analyzer tooling, defect database and viewer extension for the Clang Static Analyzer and Clang Tidy. Zip files uploaded to the server endpoint of `CodeChecker store` are not properly sanitized. An attacker, using a path traversal attack, can load and display files on the machine of `CodeChecker server`. The vulnerable endpoint is `/Default/v6.53/CodeCheckerService@massStoreRun`. The path traversal vulnerability allows reading data on the machine of the `CodeChecker server`, with the same permission level as the `CodeChecker server`. The attack requires a user account on the `CodeChecker server`, with permission to store to a server, and view the stored report. This vulnerability has been patched in version 6.23.	2024-06-24
everthemess--Goya	The Goya theme for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'attra-color', 'attra-size', and 'product-cata' parameters in versions up to, and including, 1.0.8.7 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.	2024-06-29
fastly--js-compute-runtime	@fastly/js-compute is a JavaScript SDK and runtime for building Fastly Compute applications. The implementation of several functions were determined to include a use-after-free bug. This bug could allow for unintended data loss if the result of the preceding functions were sent anywhere else, and often results in a guest trap causing services to return a 500. This bug has been fixed in version 3.16.0 of the `@fastly/js-compute` package.	2024-06-26
finesoft_project -- finesoft	Cross Site Scripting vulnerability in Hangzhou Meisoft Information Technology Co., Ltd. Finesoft v.8.0 and before allows a remote attacker to execute arbitrary code via a crafted script to the login.jsp parameter.	2024-06-24
finesoft_project -- finesoft	Hangzhou Meisoft Information Technology Co., Ltd. FineSoft <=8.0 is affected by Cross Site Scripting (XSS) which allows remote attackers to execute arbitrary code. Enter any account and password, click Login, the page will report an error, and a controllable parameter will appear at the URL:weburl.	2024-06-24
gallerycreator--Gallery Blocks with Lightbox. Image Gallery, (HTML5 video , YouTube, Vimeo) Video Gallery and Lightbox for native gallery	The Gallery Blocks with Lightbox. Image Gallery, (HTML5 video , YouTube, Vimeo) Video Gallery and Lightbox for native gallery plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'galleryID' and 'className' parameters in all versions up to, and including, 3.2.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.	2024-06-28
Genexis--Tilgin Fiber Home Gateway HG1522	A vulnerability was found in Genexis Tilgin Fiber Home Gateway HG1522 CSx000-01_09_01_12. It has been declared as problematic. Affected by this vulnerability is an unknown functionality of the file /status/product_info/. The manipulation of the argument product_info leads to cross site scripting. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-269755. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.	2024-06-26
gitlab -- gitlab	An issue was discovered in GitLab CE/EE affecting all versions starting from 9.2 prior to 16.11.5, starting from 17.0 prior to 17.0.3, and starting from 17.1 prior to 17.1.1, with the processing logic for generating link in dependency files can lead to a regular expression DoS attack on the server	2024-06-27
gitlab -- gitlab	An issue was discovered in GitLab CE/EE affecting all versions starting from 16.7 prior to 16.11.5, starting from 17.0 prior to 17.0.3, and starting from 17.1 prior to 17.1.1, which allows private job artifacts can be accessed by any user.	2024-06-27
gitlab -- gitlab	Multiple Denial of Service (DoS) conditions has been discovered in GitLab CE/EE affecting all versions starting from 1.0 prior to 16.11.5, starting from 17.0 prior to 17.0.3, and starting from 17.1 prior to 17.1.1 which allowed an attacker to cause resource exhaustion via banzai pipeline.	2024-06-27
gitlab -- gitlab	An issue was discovered in GitLab CE/EE affecting all versions starting from 12.0 prior to 16.11.5, starting from 17.0 prior to 17.0.3, and starting from 17.1 prior to 17.1.1, which allows for an attacker to cause a denial of service using a crafted OpenAPI file.	2024-06-27
gitlab -- gitlab	An issue was discovered in GitLab CE/EE affecting all versions starting from 16.9 prior to 16.11.5, starting from 17.0 prior to 17.0.3, and starting from 17.1 prior to 17.1.1, which allows merge request title to be visible publicly despite being set as project members only.	2024-06-27
gitlab -- gitlab	An issue was discovered in GitLab CE/EE affecting all versions starting from 16.9 prior to 16.11.5, starting from 17.0 prior to 17.0.3, and starting from 17.1 prior to 17.1.1, where a stored XSS vulnerability could be imported from a project with malicious commit notes.	2024-06-27
gitlab -- gitlab	An issue was discovered in GitLab EE affecting all versions starting from 16.0 prior to 16.11.5, starting from 17.0 prior to 17.0.3, and starting from 17.1 prior to 17.1.1, which allows an attacker to access issues and epics without having an SSO session using Duo Chat.	2024-06-27
gitlab -- gitlab	An issue was discovered in GitLab CE/EE affecting all versions starting from 16.1 prior to 16.11.5, starting from 17.0 prior to 17.0.3, and starting from 17.1 prior to 17.1.1, which allows non-project member to promote key results to objectives.	2024-06-27
gitlab -- gitlab	An issue was discovered in GitLab CE/EE affecting all versions starting from 16.10 prior to 16.11.5, starting from 17.0 prior to 17.0.3, and starting from 17.1 prior to 17.1.1, which allows a project maintainer can delete the merge request approval policy via graphQL.	2024-06-27
h5p -- h5p	The Interactive Content WordPress plugin before 1.15.8 does not validate uploads which could allow a Contributors and above to update malicious SVG files, leading to Stored Cross-Site Scripting issues	2024-06-27
hashicorp -- retryablehttp	go-retryablehttp prior to 0.7.7 did not sanitize urls when writing them to its log file. This could lead to go-retryablehttp writing sensitive HTTP basic auth credentials to its log file. This vulnerability, CVE-2024-6104, was fixed in go-retryablehttp 0.7.7.	2024-06-24
HCL Software--Connections	HCL Connections is vulnerable to a cross-site scripting attack where an attacker may leverage this issue to execute arbitrary script code in the browser of an unsuspecting user which leads to executing malicious script code. This may let the attacker steal cookie-based authentication credentials and comprise user's account then launch other attacks.	2024-06-25
Hitachi--Hitachi Storage Provider for VMware vCenter	Incorrect Default Permissions vulnerability in Hitachi Storage Provider for VMware vCenter allows local users to read and write specific files.This issue affects Hitachi Storage Provider for VMware vCenter: from 3.1.0 before 3.7.4.	2024-06-25
IBM--Cloud Pak for Security	IBM Cloud Pak for Security (CP4S) 1.10.0.0 through 1.10.11.0 and IBM QRadar Software Suite 1.10.12.0 through 1.10.21.0 allows web pages to be stored locally which can be read by another user on the system. IBM X-Force ID: 233673.	2024-06-28
IBM--Cognos Analytics	IBM Cognos Analytics 11.2.0, 11.2.1, 11.2.2, 11.2.3, 11.2.4, 12.0.0, 12.0.1, and 12.0.2 is potentially vulnerable to cross site scripting (XSS). A remote attacker could execute malicious commands due to improper validation of column headings in Cognos Assistant. IBM X-Force ID: 282780.	2024-06-28
IBM--Cognos Analytics	IBM Cognos Analytics 11.2.0, 11.2.1, 11.2.2, 11.2.3, 11.2.4, 12.0.0, 12.0.1, and 12.0.2 is vulnerable to improper certificate validation when using the IBM Planning Analytics Data Source Connection. This could allow an attacker to spoof a trusted entity by interfering in the communication path between IBM Planning Analytics server and IBM Cognos Analytics server. IBM X-Force ID: 283364.	2024-06-28
IBM--MQ	IBM MQ Console 9.3 LTS and 9.3 CD could disclose could allow a remote attacker to obtain sensitive information when a detailed technical error message is returned in the browser. This information could be used in further attacks against the system. IBM X-Force ID: 292765.	2024-06-28
IBM--MQ	IBM MQ 9.3 LTS and 9.3 CD could allow a remote attacker to obtain sensitive information when a detailed technical error message is returned in the browser. This information could be used in further attacks against the system. IBM X-Force ID: 292766.	2024-06-28
IBM--MQ	IBM MQ 9.0 LTS, 9.1 LTS, 9.2 LTS, 9.3 LTS and 9.3 CD, in certain configurations, is vulnerable to a denial of service attack caused by an error processing messages when an API Exit using MQBUFMH is used. IBM X-Force ID: 290259.	2024-06-28
IBM--MQ	IBM MQ 9.0 LTS, 9.1 LTS, 9.2 LTS, 9.3 LTS, and 9.3 CD is vulnerable to a denial of service attack caused by an error applying configuration changes. IBM X-Force ID: 290335.	2024-06-28
IBM--Security Access Manager Docker	IBM Security Access Manager Docker 10.0.0.0 through 10.0.7.1 could disclose sensitive information to a local user to do improper permission controls. IBM X-Force ID: 261195.	2024-06-27
IBM--Security Access Manager Docker	IBM Security Access Manager Docker 10.0.0.0 through 10.0.7.1 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information. IBM X-Force ID: 261198.	2024-06-27
IBM--Security Verify Access Docker	IBM Security Access Manager Docker 10.0.0.0 through 10.0.7.1 could allow a local user to possibly elevate their privileges due to sensitive configuration information being exposed. IBM X-Force ID: 292413.	2024-06-28
IBM--Security Verify Access Docker	IBM Security Access Manager Docker 10.0.0.0 through 10.0.7.1 could allow a local user to obtain sensitive information from the container due to incorrect default permissions. IBM X-Force ID: 292415.	2024-06-28
IBM--Security Verify Access	IBM Security Verify Access 10.0.0 through 10.0.7.1 could allow a local user to obtain sensitive information from trace logs. IBM X-Force ID: 252183.	2024-06-27
IBM--Security Verify Access	IBM Security Verify Access 10.0.0.0 through 10.0.7.1, under certain configurations, could allow an unauthenticated attacker to cause a denial of service due to asymmetric resource consumption. IBM X-Force ID: 287615.	2024-06-27
IBM--Sterling B2B Integrator Standard Edition	IBM Sterling B2B Integrator Standard Edition 6.0.0.0 through 6.2.0.2 is vulnerable to cross-site scripting. This vulnerability allows an authenticated user to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session. IBM X-Force ID: 265511.	2024-06-27
IBM--Sterling B2B Integrator Standard Edition	IBM Sterling B2B Integrator Standard Edition 6.1 and 6.2 does not restrict or incorrectly restricts frame objects or UI layers that belong to another application or domain, which can lead to user confusion about which interface the user is interacting with. IBM X-Force ID: 265508.	2024-06-27
IBM--Storage Defender - Resiliency Service	IBM Storage Defender - Resiliency Service 2.0.0 through 2.0.4 uses an inadequate account lockout setting that could allow an attacker on the network to brute force account credentials. IBM X-Force ID: 281678.	2024-06-28
IBM--Storage Defender - Resiliency Service	IBM Storage Defender - Resiliency Service 2.0.0 through 2.0.4 agent username and password error response discrepancy exposes product to brute force enumeration. IBM X-Force ID: 294869.	2024-06-28
IBM--WebSphere Application Server	IBM WebSphere Application Server 8.5 and 9.0 is vulnerable to cross-site scripting. This vulnerability allows a privileged user to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session. IBM X-Force ID: 292640.	2024-06-27
itsourcecode--Tailoring Management System	A vulnerability, which was classified as critical, was found in itsourcecode Tailoring Management System 1.0. This affects an unknown part of the file customeradd.php. The manipulation of the argument fullname/address/phonenumber/sex/email/city/comment leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-269805 was assigned to this vulnerability.	2024-06-27
kadencewp -- gutenberg_blocks_with_ai	The Gutenberg Blocks with AI by Kadence WP - Page Builder Features plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Google Maps widget parameters in all versions up to, and including, 3.2.42 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.	2024-06-27
kadencewp -- kadence_blocks_pro	The kadence-blocks-pro WordPress plugin before 2.3.8 does not prevent users with at least the contributor role using some of its shortcode's functionalities to leak arbitrary options from the database.	2024-06-27
lahirudanushka--School Management System	A vulnerability was found in lahirudanushka School Management System 1.0.0/1.0.1 and classified as critical. Affected by this issue is some unknown functionality of the file examresults-par.php of the component Exam Results Page. The manipulation of the argument sid leads to sql injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-269492.	2024-06-24
lahirudanushka--School Management System	A vulnerability classified as critical has been found in lahirudanushka School Management System 1.0.0/1.0.1. This affects an unknown part of the file /attendancelist.php of the component Attendance Report Page. The manipulation of the argument aid leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-269487.	2024-06-24
lahirudanushka--School Management System	A vulnerability classified as critical was found in lahirudanushka School Management System 1.0.0/1.0.1. This vulnerability affects unknown code of the file parent.php of the component Parent Page. The manipulation of the argument update leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-269488.	2024-06-24
lahirudanushka--School Management System	A vulnerability, which was classified as critical, has been found in lahirudanushka School Management System 1.0.0/1.0.1. This issue affects some unknown processing of the file teacher.php of the component Teacher Page. The manipulation of the argument update leads to sql injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-269489 was assigned to this vulnerability.	2024-06-24
lahirudanushka--School Management System	A vulnerability, which was classified as critical, was found in lahirudanushka School Management System 1.0.0/1.0.1. Affected is an unknown function of the file student.php of the component Student Page. The manipulation of the argument update leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. VDB-269490 is the identifier assigned to this vulnerability.	2024-06-24
lahirudanushka--School Management System	A vulnerability has been found in lahirudanushka School Management System 1.0.0/1.0.1 and classified as critical. Affected by this vulnerability is an unknown functionality of the file subject.php of the component Subject Page. The manipulation of the argument update leads to sql injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-269491.	2024-06-24
linux -- linux_kernel	In the Linux kernel, the following vulnerability has been resolved: um: Add winch to winch_handlers before registering winch IRQ Registering a winch IRQ is racy, an interrupt may occur before the winch is added to the winch_handlers list. If that happens, register_winch_irq() adds to that list a winch that is scheduled to be (or has already been) freed, causing a panic later in winch_cleanup(). Avoid the race by adding the winch to the winch_handlers list before registering the IRQ, and rolling back if um_request_irq() fails.	2024-06-24
looswebstudio--SEO SIMPLE PACK	The SEO SIMPLE PACK plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 3.2.1 via META description. This makes it possible for unauthenticated attackers to extract limited information about password protected posts.	2024-06-28
Magarsus Consultancy--SSO (Single Sign On)	URL Redirection to Untrusted Site ('Open Redirect') vulnerability in Magarsus Consultancy SSO (Single Sign On) allows Manipulating Hidden Fields.This issue affects SSO (Single Sign On): from 1.0 before 1.1.	2024-06-26
ManageEngine--OpManager	Zoho ManageEngine ITOM products versions from 128234 to 128248 are affected by the stored cross-site scripting vulnerability in the proxy server option.	2024-06-24
matter-labs--era-compiler-vyper	ZKsync Era is a layer 2 rollup that uses zero-knowledge proofs to scale Ethereum. There is possible invalid stack access due to the addresses used to access the stack not properly being converted to cells. This issue has been patched in version 1.5.0.	2024-06-28
mediavine -- create	The Create by Mediavine plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's Schema Meta shortcode in all versions up to, and including, 1.9.7 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.	2024-06-27
mermaid-js--zenuml-core	ZenUML is JavaScript-based diagramming tool that requires no server, using Markdown-inspired text definitions and a renderer to create and modify sequence diagrams. Markdown-based comments in the ZenUML diagram syntax are susceptible to Cross-site Scripting (XSS). The comment feature allows the user to attach small notes for reference. This feature allows the user to enter in their comment in markdown comment, allowing them to use common markdown features, such as `**` for bolded text. However, the markdown text is currently not sanitized before rendering, allowing an attacker to enter a malicious payload for the comment which leads to XSS. This puts existing applications that use ZenUML unsandboxed at risk of arbitrary JavaScript execution when rendering user-controlled diagrams. This vulnerability was patched in version 3.23.25,	2024-06-26
Mia Technology Inc.--Mia-Med Health Aplication	Use of a Broken or Risky Cryptographic Algorithm vulnerability in Mia Technology Inc. Mia-Med Health Aplication allows Signature Spoofing by Improper Validation.This issue affects Mia-Med Health Aplication: before 1.0.14.	2024-06-24
Moxa--OnCell G3150A-LTE Series	OnCell G3470A-LTE Series firmware versions v1.7.7 and prior have been identified as vulnerable due to accepting a format string from an external source as an argument. An attacker could modify an externally controlled format string to cause a memory leak and denial of service.	2024-06-25
n/a--djangorestframework	Versions of the package djangorestframework before 3.15.2 are vulnerable to Cross-site Scripting (XSS) via the break_long_headers template filter due to improper input sanitization before splitting and joining with <br> tags.	2024-06-26
n/a--ESXi	VMware ESXi contains an out-of-bounds read vulnerability. A malicious actor with local administrative privileges on a virtual machine with an existing snapshot may trigger an out-of-bounds read leading to a denial-of-service condition of the host.	2024-06-25
n/a--vCenter Server	The vCenter Server contains a denial-of-service vulnerability. A malicious actor with network access to vCenter Server may create a denial-of-service condition.	2024-06-25
N/A--VMware Cloud Director Object Storage Extension	VMware Cloud Director Object Storage Extension contains an Insertion of Sensitive Information vulnerability. A malicious actor with adjacent access to web/proxy server logging may be able to obtain sensitive information from URLs that are logged.	2024-06-27
N/A--VMware Cloud Director	VMware Cloud Director contains an Improper Privilege Management vulnerability. An authenticated tenant administrator for a given organization within VMware Cloud Director may be able to accidentally disable their organization leading to a Denial of Service for active sessions within their own organization's scope.	2024-06-27
n/a--VMware ESXi	VMware ESXi contains an authentication bypass vulnerability. A malicious actor with sufficient Active Directory (AD) permissions can gain full access to an ESXi host that was previously configured to use AD for user management https://blogs.vmware.com/vsphere/2012/09/joining-vsphere-hosts-to-active-directory.html by re-creating the configured AD group ('ESXi Admins' by default) after it was deleted from AD.	2024-06-25
N/A--VMware Workspace One UEM	VMware Workspace One UEM update addresses an information exposure vulnerability. A malicious actor with network access to the Workspace One UEM may be able to perform an attack resulting in an information exposure.	2024-06-27
nattywp--Silesia	The Silesia theme for WordPress is vulnerable to Stored Cross-Site Scripting via the 'link' attribute within the theme's Button shortcode in all versions up to, and including, 1.0.6 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.	2024-06-28
netweblogic--Events Manager Calendar, Bookings, Tickets, and more!	The Events Manager - Calendar, Bookings, Tickets, and more! plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'country' parameter in all versions up to, and including, 6.4.8 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.	2024-06-29
Next4Biz CRM & BPM Software--Business Process Manangement (BPM)	Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Next4Biz CRM & BPM Software Business Process Manangement (BPM) allows Stored XSS.This issue affects Business Process Manangement (BPM): from 6.6.4.4 before 6.6.4.5.	2024-06-24
ninjateam -- wp_chat_app	The WP Chat App WordPress plugin before 3.6.5 does not sanitise and escape some of its settings, which could allow high privilege users such as admins to perform Cross-Site Scripting attacks even when unfiltered_html is disallowed.	2024-06-27
petesheppard84--Extensions for Elementor	The Extensions for Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'url' parameter within the EE Button widget in all versions up to, and including, 2.0.30 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.	2024-06-29
Play.ht--Play.ht	Improper Authentication vulnerability in Play.Ht allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Play.Ht: from n/a through 3.6.4.	2024-06-24
posimyththemes--The Plus Addons for Elementor Elementor Addons, Page Templates, Widgets, Mega Menu, WooCommerce	The The Plus Addons for Elementor - Elementor Addons, Page Templates, Widgets, Mega Menu, WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'video_color' parameter in all versions up to, and including, 5.6.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.	2024-06-27
Progress Software Corporation--WhatsUp Gold	In WhatsUp Gold versions released before 2023.1.3, a path traversal vulnerability exists. A specially crafted unauthenticated HTTP request to AppProfileImport can lead can lead to information disclosure.	2024-06-25
Progress Software Corporation--WhatsUp Gold	In WhatsUp Gold versions released before 2023.1.3, an unauthenticated Path Traversal vulnerability exists Wug.UI.Areas.Wug.Controllers.SessionController.LoadNMScript. This allows allows reading of any file from the applications web-root directory .	2024-06-25
Progress Software Corporation--WhatsUp Gold	In WhatsUp Gold versions released before 2023.1.3, an unauthenticated Arbitrary File Read issue exists in Wug.UI.Areas.Wug.Controllers.SessionController.CachedCSS. This vulnerability allows reading of any file with iisapppool\NmConsole privileges.	2024-06-25
ravichandra--Infinite	The Infinite theme for WordPress is vulnerable to Stored Cross-Site Scripting via the 'project_url' parameter in all versions up to, and including, 1.1.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.	2024-06-28
renesas -- rcar_gen3	Integer Underflow (Wrap or Wraparound) vulnerability in Renesas arm-trusted-firmware. An integer underflow in image range check calculations could lead to bypassing address restrictions and loading of images to unallowed addresses.	2024-06-24
rocklobster -- contact_form_7	The Contact Form 7 WordPress plugin before 5.9.5 has an open redirect that allows an attacker to utilize a false URL and redirect to the URL of their choosing.	2024-06-27
scidsg--hushline	Hush Line is a free and open-source, anonymous-tip-line-as-a-service for organizations or individuals. The CSP policy applied on the `tips.hushline.app` website and bundled by default in this repository is trivial to bypass. This vulnerability has been patched in version 0.1.0.	2024-06-28
silabs.com--SiSDK	In a Silicon Labs multi-protocol gateway, a corrupt pointer to buffered data on a multi-protocol radio co-processor (RCP) causes the OpenThread Border Router(OTBR) application task running on the host platform to crash, allowing an attacker to cause a temporary denial-of-service.	2024-06-27
SourceCodester--Simple Online Bidding System	A vulnerability was found in SourceCodester Simple Online Bidding System 1.0. It has been classified as critical. This affects an unknown part of the file /admin/ajax.php?action=save_settings. The manipulation of the argument img leads to unrestricted upload. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-269493 was assigned to this vulnerability.	2024-06-24
Spotfire--Spotfire Enterprise Runtime for R - Server Edition	Vulnerability in Spotfire Spotfire Enterprise Runtime for R - Server Edition, Spotfire Spotfire Statistics Services, Spotfire Spotfire Analyst, Spotfire Spotfire Desktop, Spotfire Spotfire Server allows The impact of this vulnerability depends on the privileges of the user running the affected software..This issue affects Spotfire Enterprise Runtime for R - Server Edition: from 1.12.7 through 1.20.0; Spotfire Statistics Services: from 12.0.7 through 12.3.1, from 14.0.0 through 14.3.0; Spotfire Analyst: from 12.0.9 through 12.5.0, from 14.0.0 through 14.3.0; Spotfire Desktop: from 14.0 through 14.3.0; Spotfire Server: from 12.0.10 through 12.5.0, from 14.0.0 through 14.3.0.	2024-06-27
squid-cache--squid	Squid is a caching proxy for the Web supporting HTTP, HTTPS, FTP, and more. Due to an Out-of-bounds Write error when assigning ESI variables, Squid is susceptible to a Memory Corruption error. This error can lead to a Denial of Service attack.	2024-06-25
Synology--Camera Firmware	A vulnerability regarding improper limitation of a pathname to a restricted directory ('Path Traversal') is found in the Language Settings functionality. This allows remote attackers to read specific files containing non-sensitive information via unspecified vectors. The following models with Synology Camera Firmware versions before 1.0.7-0298 may be affected: BC500 and TC500.	2024-06-28
Synology--Camera Firmware	A vulnerability regarding incorrect authorization is found in the firmware upgrade functionality. This allows remote authenticated users with administrator privileges to bypass firmware integrity check via unspecified vectors. The following models with Synology Camera Firmware versions before 1.0.7-0298 may be affected: BC500 and TC500.	2024-06-28
Synology--Synology Router Manager (SRM)	Incorrect default permissions vulnerability in firewall functionality in Synology Router Manager (SRM) before 1.2.5-8227-11 and 1.3.1-9346-8 allows man-in-the-middle attackers to access highly sensitive intranet resources via unspecified vectors.	2024-06-28
Talya Informatics--Travel APPS	Improper Access Control vulnerability in Talya Informatics Travel APPS allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Travel APPS: before v17.0.68.	2024-06-27
tatvic--Conversios Google Analytics 4 (GA4), Google Ads, Meta Pixel & more for WooCommerce	The Conversios - Google Analytics 4 (GA4), Meta Pixel & more Via Google Tag Manager For WooCommerce plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'tiktok_user_id' parameter in all versions up to, and including, 7.0.12 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.	2024-06-28
Tenda--A301	A vulnerability classified as critical was found in Tenda A301 15.13.08.12. Affected by this vulnerability is the function fromSetWirelessRepeat of the file /goform/SetOnlineDevName. The manipulation of the argument devName leads to stack-based buffer overflow. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-269947. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.	2024-06-28
Tenda--A301	A vulnerability, which was classified as critical, has been found in Tenda A301 15.13.08.12. Affected by this issue is the function formWifiBasicSet of the file /goform/SetOnlineDevName. The manipulation of the argument devName leads to stack-based buffer overflow. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-269948. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.	2024-06-28
The Conduit Contributors--Conduit	Lack of validation of origin in federation API in Conduit, allowing any remote server to impersonate any user from any server in most EDUs	2024-06-25
The Conduit Contributors--Conduit	Lack of consideration of key expiry when validating signatures in Conduit, allowing an attacker which has compromised an expired key to forge requests as the remote server, as well as PDUs with timestamps past the expiry date	2024-06-25
thehappymonster--Happy Addons for Elementor	The Happy Addons for Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'url' attribute within the plugin's Gradient Heading widget in all versions up to, and including, 3.11.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.	2024-06-29
timstrifler--Exclusive Addons for Elementor	The Exclusive Addons for Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's Card widget in all versions up to, and including, 2.6.9.8 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.	2024-06-26
tislam100--Scylla lite	The Scylla lite theme for WordPress is vulnerable to Stored Cross-Site Scripting via the 'url' parameter within the theme's Button shortcode in all versions up to, and including, 1.8.3 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.	2024-06-28
tislam100--Theron Lite	The Theron Lite theme for WordPress is vulnerable to Stored Cross-Site Scripting via the 'url' parameter within the theme's Button shortcode in all versions up to, and including, 2.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.	2024-06-28
tpm2-software--tpm2-tools	tpm2-tools is the source repository for the Trusted Platform Module (TPM2.0) tools. A malicious attacker can generate arbitrary quote data which is not detected by `tpm2 checkquote`. This issue was patched in version 5.7.	2024-06-28
tpm2-software--tpm2-tss	This repository hosts source code implementing the Trusted Computing Group's (TCG) TPM2 Software Stack (TSS). The JSON Quote Info returned by Fapi_Quote has to be deserialized by Fapi_VerifyQuote to the TPM Structure `TPMS_ATTEST`. For the field `TPM2_GENERATED magic` of this structure any number can be used in the JSON structure. The verifier can receive a state which does not represent the actual, possibly malicious state of the device under test. The malicious device might get access to data it shouldn't, or can use services it shouldn't be able to. This issue has been patched in version 4.1.0.	2024-06-28
trudesk_project -- trudesk	TruDesk Help Desk/Ticketing Solution v1.1.11 is vulnerable to a Cross-Site Request Forgery (CSRF) attack which would allow an attacker to restart the server, causing a DoS attack. The attacker must craft a webpage that would perform a GET request to the /api/v1/admin/restart endpoint, then the victim (who has sufficient privileges), would visit the page and the server restart would begin. The attacker must know the full URL that TruDesk is on in order to craft the webpage.	2024-06-24
twinpictures, baden03--jQuery T(-) Countdown Widget	Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in twinpictures, baden03 jQuery T(-) Countdown Widget allows Stored XSS.This issue affects jQuery T(-) Countdown Widget: from n/a through 2.3.25.	2024-06-26
urkekg--Stock Ticker	The Stock Ticker plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's stock_ticker shortcode in all versions up to, and including, 3.24.4 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.	2024-06-29
virtosoftware -- sharepoint_bulk_file_download	An issue was discovered in VirtoSoftware Virto Bulk File Download 5.5.44 for SharePoint 2019. It discloses full pathnames via Virto.SharePoint.FileDownloader/Api/Download.ashx?action=archive.	2024-06-24
virtosoftware -- sharepoint_bulk_file_download	An issue was discovered in VirtoSoftware Virto Bulk File Download 5.5.44 for SharePoint 2019. The Virto.SharePoint.FileDownloader/Api/Download.ashx isCompleted method allows an NTLMv2 hash leak via a UNC share pathname in the path parameter.	2024-06-24
VMware--Salt Project	Syndic cache directory creation is vulnerable to a directory traversal attack in salt project which can lead a malicious attacker to create an arbitrary directory on a Salt master.	2024-06-27
webtechstreet -- elementor_addon_elements	The Elementor Addon Elements plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'url' parameter in versions up to, and including, 1.13.5 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.	2024-06-27
webtechstreet -- elementor_addon_elements	The Elementor Addon Elements plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'url' parameter in versions up to, and including, 1.13.5 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.	2024-06-27
WordPress Foundation--WordPress	WordPress Core is vulnerable to Stored Cross-Site Scripting via the HTML API in various versions prior to 6.5.5 due to insufficient input sanitization and output escaping on URLs. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.	2024-06-25
wpzita--Zita Elementor Site Library	The Zita Elementor Site Library plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the import_xml_data, xml_data_import, import_option_data, import_widgets, and import_customizer_settings functions in all versions up to, and including, 1.6.2. This makes it possible for authenticated attackers, with subscriber-level access and above, to create pages, update certain options, including WooCommerce page titles and Elementor settings, import widgets, and update the plugin's customizer settings and the WordPress custom CSS. NOTE: This vulnerability was partially fixed in version 1.6.2.	2024-06-25
xwiki -- xwiki	XWiki Platform is a generic wiki platform offering runtime services for applications built on top of it. The content of a document included using `{{include reference="targetdocument"/}}` is executed with the right of the includer and not with the right of its author. This means that any user able to modify the target document can impersonate the author of the content which used the `include` macro. This vulnerability has been patched in XWiki 15.0 RC1 by making the default behavior safe.	2024-06-24
Yokogawa Electric Corporation--FAST/TOOLS	A vulnerability has been found in FAST/TOOLS and CI Server. The affected product's WEB HMI server's function to process HTTP requests has a security flaw (Reflected XSS) that allows the execution of malicious scripts. Therefore, if a client PC with inadequate security measures accesses a product URL containing a malicious request, the malicious script may be executed on the client PC. The affected products and versions are as follows: FAST/TOOLS (Packages: RVSVRN, UNSVRN, HMIWEB, FTEES, HMIMOB) R9.01 to R10.04 CI Server R1.01.00 to R1.03.00	2024-06-26
Yokogawa Electric Corporation--FAST/TOOLS	A vulnerability has been found in FAST/TOOLS and CI Server. The affected products have built-in accounts with no passwords set. Therefore, if the product is operated without a password set by default, an attacker can break into the affected product. The affected products and versions are as follows: FAST/TOOLS (Packages: RVSVRN, UNSVRN, HMIWEB, FTEES, HMIMOB) R9.01 to R10.04 CI Server R1.01.00 to R1.03.00	2024-06-26

Low Vulnerabilities

Primary Vendor -- Product	Description	Published
bigbluebutton--bigbluebutton	BigBlueButton is an open-source virtual classroom designed to help teachers teach and learners learn. An attacker may be able to exploit the overly elevated file permissions in the `/usr/local/bigbluebutton/core/vendor/bundle/ruby/2.7.0/gems/resque-2.6.0` directory with the goal of privilege escalation, potentially exposing sensitive information on the server. This issue has been patched in version(s) 2.6.18, 2.7.8 and 3.0.0-alpha.7.	2024-06-28
Checkmk GmbH--Checkmk	Insertion of Sensitive Information into Log File in Checkmk GmbH's Checkmk versions <2.3.0p7, <2.2.0p28, <2.1.0p45 and <=2.0.0p39 (EOL) causes automation user secrets to be written to audit log files accessible to administrators.	2024-06-26
Dell--CloudLink	Dell Key Trust Platform, v3.0.6 and prior, contains Use of a Cryptographic Primitive with a Risky Implementation vulnerability. A local privileged attacker could potentially exploit this vulnerability, leading to privileged information disclosure.	2024-06-28
Dell--CPG BIOS	Dell Client Platform BIOS contains an Out-of-bounds Write vulnerability in an externally developed component. A high privileged attacker with local access could potentially exploit this vulnerability, leading to Information tampering.	2024-06-25
Dell--PowerProtect DD	Dell PowerProtect DD, versions prior to 8.0, LTS 7.13.1.0, LTS 7.10.1.30, LTS 7.7.5.40 contain an open redirect vulnerability. A remote low privileged attacker could potentially exploit this vulnerability, leading to information disclosure.	2024-06-26
Dell--PowerProtect DD	Dell PowerProtect DD, versions prior to 8.0, LTS 7.13.1.0, LTS 7.10.1.30, LTS 7.7.5.40 contain a disclosure of temporary sensitive information vulnerability. A remote high privileged attacker could potentially exploit this vulnerability, leading to the reuse of disclosed information to gain unauthorized access to the application report.	2024-06-26
DSpace--DSpace	DSpace is an open source software is a turnkey repository application used by more than 2,000 organizations and institutions worldwide to provide durable access to digital resources. In DSpace 7.0 through 7.6.1, when an HTML, XML or JavaScript Bitstream is downloaded, the user's browser may execute any embedded JavaScript. If that embedded JavaScript is malicious, there is a risk of an XSS attack. This vulnerability has been patched in version 7.6.2.	2024-06-26
HCL Software--Connections	HCL Connections contains a broken access control vulnerability that may allow unauthorized user to update data in certain scenarios.	2024-06-25
HCL Software--DRYiCE AEX	HCL DRYiCE AEX is impacted by a lack of clickjacking protection in the AEX web application. An attacker can use multiple transparent or opaque layers to trick a user into clicking on a button or link on another page than the one intended.	2024-06-28
HCL Software--DRYiCE AEX	HCL DRYiCE AEX product is impacted by lack of input validation vulnerability in a particular web application. A malicious script can be injected into a system which can cause the system to behave in unexpected ways.	2024-06-28
HCL Software--DRYiCE AEX	HCL DRYiCE AEX product is impacted by Missing Root Detection vulnerability in the mobile application. The mobile app can be installed in the rooted device due to which malicious users can gain unauthorized access to the rooted devices, compromising security and potentially leading to data breaches or other malicious activities.	2024-06-28
HCL Software--DRYiCE AEX	HCL DRYiCE AEX is potentially impacted by disclosure of sensitive information in the mobile application when a snapshot is taken.	2024-06-28
Kareadita--Kavita	Kavita is a cross platform reading server. Opening an ebook with malicious scripts inside leads to code execution inside the browsing context. Kavita doesn't sanitize or sandbox the contents of epubs, allowing scripts inside ebooks to execute. This vulnerability was patched in version 0.8.1.	2024-06-28
LabVantage--LIMS	A vulnerability was found in LabVantage LIMS 2017. It has been declared as problematic. This vulnerability affects unknown code of the file /labvantage/rc?command=file&file=WEB-CORE/elements/files/filesembedded.jsp of the component POST Request Handler. The manipulation of the argument sdcid/keyid1/keyid2/keyid3 leads to cross site scripting. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-269800. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.	2024-06-27
LabVantage--LIMS	A vulnerability was found in LabVantage LIMS 2017. It has been rated as problematic. This issue affects some unknown processing of the file /labvantage/rc?command=page of the component POST Request Handler. The manipulation of the argument param1 leads to cross site scripting. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-269801 was assigned to this vulnerability. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.	2024-06-27
LabVantage--LIMS	A vulnerability classified as problematic has been found in LabVantage LIMS 2017. Affected is an unknown function of the file /labvantage/rc?command=page&sdcid=LV_ReagentLot of the component POST Request Handler. The manipulation of the argument mode leads to cross site scripting. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. VDB-269802 is the identifier assigned to this vulnerability.	2024-06-27
LabVantage--LIMS	A vulnerability classified as problematic was found in LabVantage LIMS 2017. Affected by this vulnerability is an unknown functionality of the file /labvantage/rc?command=file&file=WEB-OPAL/pagetypes/bulletins/sendbulletin.jsp of the component POST Request Handler. The manipulation of the argument bulletinbody leads to cross site scripting. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-269803.	2024-06-27
lahirudanushka--School Management System	A vulnerability was found in lahirudanushka School Management System 1.0.0/1.0.1 and classified as problematic. This issue affects some unknown processing of the file /subject.php of the component Subject Page. The manipulation of the argument Subject Title/Sybillus Details leads to cross site scripting. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-269807.	2024-06-27
NixOS--nix	Nix is a package manager for Linux and other Unix systems that makes package management reliable and reproducible. A build process has access to and can change the permissions of the build directory. After creating a setuid binary in a globally accessible location, a malicious local user can assume the permissions of a Nix daemon worker and hijack all future builds. This issue was patched in version(s) 2.23.1, 2.22.2, 2.21.3, 2.20.7, 2.19.5 and 2.18.4.	2024-06-28
octobercms--october	October is a self-hosted CMS platform based on the Laravel PHP Framework. This issue affects authenticated administrators who may be redirected to an untrusted URL using the PageFinder schema. The resolver for the page finder link schema (`october://`) allowed external links, therefore allowing an open redirect outside the scope of the active host. This vulnerability has been patched in version 3.5.15.	2024-06-26
octobercms--october	October is a self-hosted CMS platform based on the Laravel PHP Framework. The X-October-Request-Handler Header does not sanitize the AJAX handler name and allows unescaped HTML to be reflected back. There is no impact since this vulnerability cannot be exploited through normal browser interactions. This unescaped value is only detectable when using a proxy interception tool. This issue has been patched in version 3.5.15.	2024-06-26
The Conduit Contributors--Conduit	Incomplete cleanup when performing redactions in Conduit, allowing an attacker to check whether certain strings were present in the PDU before redaction	2024-06-25
udn--udn News App	udn News Android APP stores the user session in logcat file when user log into the APP. A malicious APP or an attacker with physical access to the Android device can retrieve this session and use it to log into the news APP and other services provided by udn.	2024-06-25
udn--udn News App	udn News Android APP stores the unencrypted user session in the local database when user log into the application. A malicious APP or an attacker with physical access to the Android device can retrieve this session and use it to log into the news APP and other services provided by udn.	2024-06-25
ZKTeco--ZKBio CVSecurity V5000	A vulnerability, which was classified as problematic, was found in ZKTeco ZKBio CVSecurity V5000 4.1.0. This affects an unknown part of the component Push Configuration Section. The manipulation of the argument Configuration Name leads to cross site scripting. It is possible to initiate the attack remotely. The identifier VDB-269733 was assigned to this vulnerability. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.	2024-06-26

Severity Not Yet Assigned

Primary Vendor -- Product	Description	Published	CVSS Score
Adminer--Adminer	Adminer and AdminerEvo are vulnerable to SSRF via database connection fields. This could allow an unauthenticated remote attacker to enumerate or access systems the attacker would not otherwise have access to. Adminer is no longer supported, but this issue was fixed in AdminerEvo version 4.8.4.	2024-06-24	not yet calculated
Adminer--Adminer	Adminer and AdminerEvo allow an unauthenticated remote attacker to cause a denial of service by connecting to an attacker-controlled service that responds with HTTP redirects. The denial of service is subject to PHP configuration limits. Adminer is no longer supported, but this issue was fixed in AdminerEvo version 4.8.4.	2024-06-24	not yet calculated
Apache Software Foundation--Apache JSPWiki	XSS in Upload page in Apache JSPWiki 2.12.1 and priors allows the attacker to execute javascript in the victim's browser and get some sensitive information about the victim. Apache JSPWiki users should upgrade to 2.12.2 or later.	2024-06-24	not yet calculated
Apache Software Foundation--Apache StreamPipes	Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) vulnerability in Apache StreamPipes user self-registration and password recovery mechanism. This allows an attacker to guess the recovery token in a reasonable time and thereby to take over the attacked user's account. This issue affects Apache StreamPipes: from 0.69.0 through 0.93.0. Users are recommended to upgrade to version 0.95.0, which fixes the issue.	2024-06-24	not yet calculated
Apple--AirPods Firmware Update A, AirPods Firmware Update F, and Beats Firmware Update F	An authentication issue was addressed with improved state management. This issue is fixed in AirPods Firmware Update 6A326, AirPods Firmware Update 6F8, and Beats Firmware Update 6F8. When your headphones are seeking a connection request to one of your previously paired devices, an attacker in Bluetooth range might be able to spoof the intended source device and gain access to your headphones.	2024-06-26	not yet calculated
Autodesk--AutoCAD, Advance Steel and Civil 3D	A maliciously crafted CATPART file, when parsed in CC5Dll.dll and ASMBASE228A.dll through Autodesk applications, can force an Out-of-Bound Write. A malicious actor can leverage this vulnerability to cause a crash, read sensitive data, or execute arbitrary code in the context of the current process.	2024-06-25	not yet calculated
Autodesk--AutoCAD, Advance Steel and Civil 3D	A maliciously crafted PRT file, when parsed in opennurbs.dll through Autodesk applications, can force an Out-of-Bound Read. A malicious actor can leverage this vulnerability to cause a crash, read sensitive data, or execute arbitrary code in the context of the current process.	2024-06-25	not yet calculated
Autodesk--AutoCAD, Advance Steel and Civil 3D	A maliciously crafted X_B and X_T file, when parsed in pskernel.DLL through Autodesk applications, can force an Out-of-Bound Write. A malicious actor can leverage this vulnerability to cause a crash, read sensitive data, or execute arbitrary code in the context of the current process.	2024-06-25	not yet calculated
Autodesk--AutoCAD, Advance Steel and Civil 3D	A maliciously crafted CATPART, X_B and STEP, when parsed in ASMKERN228A.dll and ASMKERN229A.dll through Autodesk applications, can lead to a memory corruption vulnerability by write access violation. This vulnerability, in conjunction with other vulnerabilities, can lead to code execution in the context of the current process.	2024-06-25	not yet calculated
Autodesk--AutoCAD, Advance Steel and Civil 3D	A maliciously crafted CATPRODUCT file, when parsed in CC5Dll.dll through Autodesk applications, can lead to a memory corruption vulnerability by write access violation. This vulnerability, in conjunction with other vulnerabilities, can lead to code execution in the context of the current process.	2024-06-25	not yet calculated
Autodesk--AutoCAD, Advance Steel and Civil 3D	A maliciously crafted SLDDRW file, when parsed in ODXSW_DLL.dll through Autodesk applications, can force an Out-of-Bound Read. A malicious actor can leverage this vulnerability to cause a crash, read sensitive data, or execute arbitrary code in the context of the current process.	2024-06-25	not yet calculated
Autodesk--AutoCAD, Advance Steel and Civil 3D	A maliciously crafted PRT file, when parsed in odxug_dll.dll through Autodesk applications, can force an Out-of-Bounds Write. A malicious actor can leverage this vulnerability to cause a crash, read sensitive data, or execute arbitrary code in the context of the current process.	2024-06-25	not yet calculated
Autodesk--AutoCAD, Advance Steel and Civil 3D	A maliciously crafted 3DM file, when parsed in ASMkern229A.dll through Autodesk applications, can force an Out-of-Bounds Write. A malicious actor can leverage this vulnerability to cause a crash, read sensitive data, or execute arbitrary code in the context of the current process.	2024-06-25	not yet calculated
Autodesk--AutoCAD, Advance Steel and Civil 3D	A maliciously crafted 3DM file, when parsed in opennurbs.dll through Autodesk applications, can force an Out-of-Bounds Read. A malicious actor can leverage this vulnerability to cause a crash, read sensitive data, or execute arbitrary code in the context of the current process.	2024-06-25	not yet calculated
Autodesk--AutoCAD, Advance Steel and Civil 3D	A maliciously crafted MODEL file, when parsed in libodx.dll through Autodesk applications, can force an Out-of-Bounds Read. A malicious actor can leverage this vulnerability to cause a crash, read sensitive data, or execute arbitrary code in the context of the current process.	2024-06-25	not yet calculated
Autodesk--AutoCAD, Advance Steel and Civil 3D	A maliciously crafted SLDPRT file, when parsed in ODXSW_DLL.dll through Autodesk applications, can be used to cause a Heap-based Overflow. A malicious actor can leverage this vulnerability to cause a crash, read sensitive data, or execute arbitrary code in the context of the current process.	2024-06-25	not yet calculated
Autodesk--AutoCAD, Advance Steel and Civil 3D	A maliciously crafted MODEL file, when parsed in atf_asm_interface.dll through Autodesk applications, can be used to cause a Heap-based Buffer Overflow. A malicious actor can leverage this vulnerability to cause a crash or execute arbitrary code in the context of the current process.	2024-06-25	not yet calculated
Autodesk--AutoCAD, Advance Steel and Civil 3D	A maliciously crafted 3DM file, when parsed in opennurbs.dll and ASMkern229A.dll through Autodesk applications, can lead to a memory corruption vulnerability by write access violation. This vulnerability, along with other vulnerabilities, can lead to code execution in the current process.	2024-06-25	not yet calculated
Autodesk--AutoCAD, Advance Steel and Civil 3D	A maliciously crafted SLDASM or SLDPRT file, when parsed in ODXSW_DLL.dll through Autodesk applications, can lead to a memory corruption vulnerability by write access violation. This vulnerability, along with other vulnerabilities, can lead to code execution in the current process.	2024-06-25	not yet calculated
Autodesk--AutoCAD, Advance Steel and Civil 3D	A maliciously crafted IGES file, when parsed in ASMImport229A.dll through Autodesk applications, can be used to cause a use-after-free vulnerability. A malicious actor can leverage this vulnerability to cause a crash or execute arbitrary code in the context of the current process.	2024-06-25	not yet calculated
Autodesk--AutoCAD, Advance Steel and Civil 3D	A maliciously crafted STP file, when parsed in stp_aim_x64_vc15d.dll through Autodesk applications, can be used to uninitialized variables. This vulnerability, along with other vulnerabilities, can lead to code execution in the current process.	2024-06-25	not yet calculated
Autodesk--AutoCAD, Advance Steel and Civil 3D	A maliciously crafted 3DM file, when parsed in opennurbs.dll through Autodesk applications, can force an Out-of-Bounds Write. A malicious actor can leverage this vulnerability to cause a crash, write sensitive data, or execute arbitrary code in the context of the current process.	2024-06-25	not yet calculated
Autodesk--AutoCAD, Advance Steel and Civil 3D	A maliciously crafted X_B file, when parsed in pskernel.DLL through Autodesk applications, can lead to a memory corruption vulnerability by write access violation. This vulnerability, in conjunction with other vulnerabilities, can lead to code execution in the context of the current process.	2024-06-25	not yet calculated
Autodesk--AutoCAD, Advance Steel and Civil 3D	[A maliciously crafted 3DM file, when parsed in opennurbs.dll through Autodesk applications, can be used to cause a Heap-based Overflow. A malicious actor can leverage this vulnerability to cause a crash, read sensitive data, or execute arbitrary code in the context of the current process.	2024-06-25	not yet calculated
Autodesk--AutoCAD, Advance Steel and Civil 3D	A maliciously crafted MODEL file, when parsed in ASMkern229A.dllthrough Autodesk applications, can be used to uninitialized variables. This vulnerability, along with other vulnerabilities, could lead to code execution in the current process.	2024-06-25	not yet calculated
Autodesk--AutoCAD, Advance Steel and Civil 3D	A maliciously crafted DWG and SLDPRT file, when parsed in opennurbs.dll and ODXSW_DLL.dll through Autodesk applications, can be used to cause a Stack-based Overflow. A malicious actor can leverage this vulnerability to cause a crash, read sensitive data, or execute arbitrary code in the context of the current process.	2024-06-25	not yet calculated
Autodesk--AutoCAD, Advance Steel and Civil 3D	A maliciously crafted SLDPRT file, when parsed in ASMKERN229A.dll through Autodesk applications, can cause a use-after-free vulnerability. This vulnerability, along with other vulnerabilities, could lead to code execution in the current process.	2024-06-25	not yet calculated
Autodesk--AutoCAD, Advance Steel and Civil 3D	A maliciously crafted X_B and X_T file, when parsed in pskernel.DLL through Autodesk applications, can force an Out-of-Bound Read. A malicious actor can leverage this vulnerability to cause a crash, read sensitive data, or execute arbitrary code in the context of the current process.	2024-06-25	not yet calculated
Autodesk--AutoCAD, Advance Steel and Civil 3D	A maliciously crafted CATPRODUCT file, when parsed in CC5Dll.dll through Autodesk applications, can lead to a memory corruption vulnerability by write access violation. This vulnerability, in conjunction with other vulnerabilities, can lead to code execution in the context of the current process.	2024-06-25	not yet calculated
Autodesk--AutoCAD, Advance Steel and Civil 3D	A maliciously crafted X_B and X_T file, when parsed in pskernel.DLL through Autodesk applications, can cause a use-after-free vulnerability. This vulnerability, along with other vulnerabilities, could lead to code execution in the current process.	2024-06-25	not yet calculated
Autodesk--Autodesk applications	A maliciously crafted 3DM and MODEL file, when parsed in opennurbs.dll and atf_api.dll through Autodesk applications, can force an Out-of-Bound Read. A malicious actor can leverage this vulnerability to cause a crash, read sensitive data, or execute arbitrary code in the context of the current process.	2024-06-25	not yet calculated
Autodesk--Autodesk applications	A maliciously crafted MODEL file, when parsed in libodxdll through Autodesk applications, can cause a double free. This vulnerability, along with other vulnerabilities, can lead to code execution in the current process.	2024-06-25	not yet calculated
Autodesk--Autodesk applications	A maliciously crafted CATPART, STP, and MODEL file, when parsed in atf_dwg_consumer.dll, rose_x64_vc15.dll and libodxdll through Autodesk applications, can cause a use-after-free vulnerability. This vulnerability, along with other vulnerabilities, can lead to code execution in the current process.	2024-06-25	not yet calculated
Autodesk--Autodesk applications	A maliciously crafted 3DM, MODEL and X_B file, when parsed in ASMkern229A.dll and ASMBASE229A.dll through Autodesk applications, can force an Out-of-Bound Read and/or Out-of-Bound Write. A malicious actor can leverage this vulnerability to cause a crash, read sensitive data, or execute arbitrary code in the context of the current process.	2024-06-25	not yet calculated
berriai--berriai/litellm	BerriAI/litellm version v1.35.8 contains a vulnerability where an attacker can achieve remote code execution. The vulnerability exists in the `add_deployment` function, which decodes and decrypts environment variables from base64 and assigns them to `os.environ`. An attacker can exploit this by sending a malicious payload to the `/config/update` endpoint, which is then processed and executed by the server when the `get_secret` function is triggered. This requires the server to use Google KMS and a database to store a model.	2024-06-27	not yet calculated
Bludit--Bludit	A security vulnerability has been identified in Bludit, allowing attackers with knowledge of the API token to upload arbitrary files through the File API which leads to arbitrary code execution on the server. This vulnerability arises from improper handling of file uploads, enabling malicious actors to upload and execute PHP files.	2024-06-24	not yet calculated
Bludit--Bludit	A security vulnerability has been identified in Bludit, allowing authenticated attackers to execute arbitrary code through the Image API. This vulnerability arises from improper handling of file uploads, enabling malicious actors to upload and execute PHP files.	2024-06-24	not yet calculated
Bludit--Bludit	A session fixation vulnerability in Bludit allows an attacker to bypass the server's authentication if they can trick an administrator or any other user into authorizing a session ID of their choosing.	2024-06-24	not yet calculated
Bludit--Bludit	Bludit uses the SHA-1 hashing algorithm to compute password hashes. Thus, attackers could determine cleartext passwords with brute-force attacks due to the inherent speed of SHA-1. In addition, the salt that is computed by Bludit is generated with a non-cryptographically secure function.	2024-06-24	not yet calculated
Bludit--Bludit	Bludit uses predictable methods in combination with the MD5 hashing algorithm to generate sensitive tokens such as the API token and the user token. This allows attackers to authenticate against the Bludit API.	2024-06-24	not yet calculated
Concept Intermedia--S@M CMS	Sites managed in S@M CMS (Concept Intermedia) might be vulnerable to Reflected XSS via including scripts in requested file names. Only a part of observed services is vulnerable, but since vendor has not investigated the root problem, it is hard to determine when the issue appears.	2024-06-28	not yet calculated
Concept Intermedia--S@M CMS	Sites managed in S@M CMS (Concept Intermedia) might be vulnerable to Reflected XSS via including scripts in one of GET header parameters. Only a part of observed services is vulnerable, but since vendor has not investigated the root problem, it is hard to determine when the issue appears.	2024-06-28	not yet calculated
Concept Intermedia--S@M CMS	Sites managed in S@M CMS (Concept Intermedia) might be vulnerable to a blind SQL Injection executed using the search bar. Only a part of observed services is vulnerable, but since vendor has not investigated the root problem, it is hard to determine when the issue appears.	2024-06-28	not yet calculated
Devolutions--Remote Desktop Manager	Improper access control in PAM dashboard in Devolutions Remote Desktop Manager 2024.2.11 and earlier on Windows allows an authenticated user to bypass the execute permission via the use of the PAM dashboard.	2024-06-26	not yet calculated
Devolutions--Server	Authentication bypass in the 2FA feature in Devolutions Server 2024.1.14.0 and earlier allows an authenticated attacker to authenticate to another user without being asked for the 2FA via another browser tab.	2024-06-25	not yet calculated
Faronics--WINSelect (Standard + Enterprise)	The application Faronics WINSelect (Standard + Enterprise) saves its configuration in an encrypted file on the file system which "Everyone" has read and write access to, path to file: C:\ProgramData\WINSelect\WINSelect.wsd The path for the affected WINSelect Enterprise configuration file is: C:\ProgramData\Faronics\StorageSpace\WS\WINSelect.wsd	2024-06-24	not yet calculated
Faronics--WINSelect (Standard + Enterprise)	The configuration file is encrypted with a static key derived from a static five-character password which allows an attacker to decrypt this file. The application hashes this five-character password with the outdated and broken MD5 algorithm (no salt) and uses the first five bytes as the key for RC4. The configuration file is then encrypted with these parameters.	2024-06-24	not yet calculated
Faronics--WINSelect (Standard + Enterprise)	The decrypted configuration file contains the password in cleartext which is used to configure WINSelect. It can be used to remove the existing restrictions and disable WINSelect entirely.	2024-06-24	not yet calculated
gaizhenbiao--gaizhenbiao/chuanhuchatgpt	A Server-Side Request Forgery (SSRF) vulnerability exists in the upload processing interface of gaizhenbiao/ChuanhuChatGPT versions <= ChuanhuChatGPT-20240410-git.zip. This vulnerability allows attackers to send crafted requests from the vulnerable server to internal or external resources, potentially bypassing security controls and accessing sensitive data.	2024-06-27	not yet calculated
gaizhenbiao--gaizhenbiao/chuanhuchatgpt	A Regular Expression Denial of Service (ReDoS) vulnerability exists in the latest version of gaizhenbiao/chuanhuchatgpt. The vulnerability is located in the filter_history function within the utils.py module. This function takes a user-provided keyword and attempts to match it against chat history filenames using a regular expression search. Due to the lack of sanitization or validation of the keyword parameter, an attacker can inject a specially crafted regular expression, leading to a denial of service condition. This can cause severe degradation of service performance and potential system unavailability.	2024-06-27	not yet calculated
gaizhenbiao--gaizhenbiao/chuanhuchatgpt	A path traversal vulnerability exists in gaizhenbiao/chuanhuchatgpt version 20240410, allowing any user to delete other users' chat histories. This vulnerability can also be exploited to delete any files ending in `.json` on the target system, leading to a denial of service as users are unable to authenticate.	2024-06-27	not yet calculated
golang.org/x/image--golang.org/x/image/tiff	Parsing a corrupt or malicious image with invalid color indices can cause a panic.	2024-06-27	not yet calculated
Google--Chrome	Use after free in Dawn in Google Chrome prior to 126.0.6478.126 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)	2024-06-24	not yet calculated
Google--Chrome	Use after free in Swiftshader in Google Chrome prior to 126.0.6478.126 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)	2024-06-24	not yet calculated
Google--Chrome	Use after free in Dawn in Google Chrome prior to 126.0.6478.126 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)	2024-06-24	not yet calculated
Google--Chrome	Use after free in Dawn in Google Chrome prior to 126.0.6478.126 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)	2024-06-24	not yet calculated
Google--Nearby	There exists a vulnerability in Quickshare/Nearby where an attacker can force the a victim to stay connected to a temporary hotspot created for the share. As part of the sequence of packets in a QuickShare connection over Bluetooth, the attacker forces the victim to connect to the attacker's WiFi network and then sends an OfflineFrame that crashes Quick Share. This makes the Wifi connection to the attacker's network last instead of returning to the old network when the Quick Share session is done allowing the attacker to be a MiTM. We recommend upgrading to version 1.0.1724.0 of Quickshare or above	2024-06-26	not yet calculated
Google--Nearby	There exists a vulnerability in Quickshare/Nearby where an attacker can bypass the accept file dialog on QuickShare Windows. Normally in QuickShare Windows app we can't send a file without the user accept from the receiving device if the visibility is set to everyone mode or contacts mode. We recommend upgrading to version 1.0.1724.0 of Quickshare or above	2024-06-26	not yet calculated
h2oai--h2oai/h2o-3	In h2oai/h2o-3 version 3.46.0, the `run_tool` command in the `rapids` component allows the `main` function of any class under the `water.tools` namespace to be called. One such class, `MojoConvertTool`, crashes the server when invoked with an invalid argument, causing a denial of service.	2024-06-27	not yet calculated
Hanwha Vision Co., Ltd.--A-Series, Q-Series, PNM-series Camera	badmonkey, a Security Researcher has found a flaw that allows for a unauthenticated DoS attack on the camera. An attacker runs a crafted URL, nobody can access the web management page of the camera. and must manually restart the device or re-power it. The manufacturer has released patch firmware for the flaw, please refer to the manufacturer's report for details and workarounds.	2024-06-25	not yet calculated
HP Inc.--HP PC BIOS	A potential Time-of-Check to Time-of Use (TOCTOU) vulnerability has been identified in the HP BIOS for certain HP PC products, which might allow arbitrary code execution, denial of service, and information disclosure. HP is releasing BIOS updates to mitigate the potential vulnerability.	2024-06-28	not yet calculated
imartinez--imartinez/privategpt	A Cross-Site Request Forgery (CSRF) vulnerability in version 0.5.0 of imartinez/privategpt allows an attacker to delete all uploaded files on the server. This can lead to data loss and service disruption for the application's users.	2024-06-27	not yet calculated
imartinez--imartinez/privategpt	An open redirect vulnerability exists in imartinez/privategpt version 0.5.0 due to improper handling of the 'file' parameter. This vulnerability allows attackers to redirect users to a URL specified by user-controlled input without proper validation or sanitization. The impact of this vulnerability includes potential phishing attacks, malware distribution, and credential theft.	2024-06-27	not yet calculated
JAMF--Jamf Compliance Editor	The XPC service within the audit functionality of Jamf Compliance Editor before version 1.3.1 on macOS can lead to local privilege escalation.	2024-06-27	not yet calculated
Jan Syski--MegaBIP	SQL Injection vulnerability in MegaBIP software allows attacker to disclose the contents of the database, obtain session cookies or modify the content of pages. This issue affects MegaBIP software versions through 5.12.1.	2024-06-24	not yet calculated
Jenkins Project--Jenkins Bitbucket Branch Source Plugin	Jenkins Bitbucket Branch Source Plugin 886.v44cf5e4ecec5 and earlier prints the Bitbucket OAuth access token as part of the Bitbucket URL in the build log in some cases.	2024-06-26	not yet calculated
Jenkins Project--Jenkins Plain Credentials Plugin	In rare cases Jenkins Plain Credentials Plugin 182.v468b_97b_9dcb_8 and earlier stores secret file credentials unencrypted (only Base64 encoded) on the Jenkins controller file system, where they can be viewed by users with access to the Jenkins controller file system (global credentials) or with Item/Extended Read permission (folder-scoped credentials).	2024-06-26	not yet calculated
Jenkins Project--Jenkins Structs Plugin	When Jenkins Structs Plugin 337.v1b_04ea_4df7c8 and earlier fails to configure a build step, it logs a warning message containing diagnostic information that may contain secrets passed as step parameters, potentially resulting in accidental exposure of secrets through the default system log.	2024-06-26	not yet calculated
lightning-ai--lightning-ai/pytorch-lightning	A vulnerability in the /v1/runs API endpoint of lightning-ai/pytorch-lightning v2.2.4 allows attackers to exploit path traversal when extracting tar.gz files. When the LightningApp is running with the plugin_server, attackers can deploy malicious tar.gz plugins that embed arbitrary files with path traversal vulnerabilities. This can result in arbitrary files being written to any directory in the victim's local file system, potentially leading to remote code execution.	2024-06-27	not yet calculated
Linux--Linux	In the Linux kernel, the following vulnerability has been resolved: x86/xen: Drop USERGS_SYSRET64 paravirt call commit afd30525a659ac0ae0904f0cb4a2ca75522c3123 upstream. USERGS_SYSRET64 is used to return from a syscall via SYSRET, but a Xen PV guest will nevertheless use the IRET hypercall, as there is no sysret PV hypercall defined. So instead of testing all the prerequisites for doing a sysret and then mangling the stack for Xen PV again for doing an iret just use the iret exit from the beginning. This can easily be done via an ALTERNATIVE like it is done for the sysenter compat case already. It should be noted that this drops the optimization in Xen for not restoring a few registers when returning to user mode, but it seems as if the saved instructions in the kernel more than compensate for this drop (a kernel build in a Xen PV guest was slightly faster with this patch applied). While at it remove the stale sysret32 remnants. [ pawan: Brad Spengler and Salvatore Bonaccorso <[email protected]> reported a problem with the 5.10 backport commit edc702b4a820 ("x86/entry_64: Add VERW just before userspace transition"). When CONFIG_PARAVIRT_XXL=y, CLEAR_CPU_BUFFERS is not executed in syscall_return_via_sysret path as USERGS_SYSRET64 is runtime patched to: .cpu_usergs_sysret64 = { 0x0f, 0x01, 0xf8, 0x48, 0x0f, 0x07 }, // swapgs; sysretq which is missing CLEAR_CPU_BUFFERS. It turns out dropping USERGS_SYSRET64 simplifies the code, allowing CLEAR_CPU_BUFFERS to be explicitly added to syscall_return_via_sysret path. Below is with CONFIG_PARAVIRT_XXL=y and this patch applied: syscall_return_via_sysret: ... <+342>: swapgs <+345>: xchg %ax,%ax <+347>: verw -0x1a2(%rip) <------ <+354>: sysretq ]	2024-06-25	not yet calculated
Linux--Linux	In the Linux kernel, the following vulnerability has been resolved: media: lgdt3306a: Add a check against null-pointer-def The driver should check whether the client provides the platform_data. The following log reveals it: [ 29.610324] BUG: KASAN: null-ptr-deref in kmemdup+0x30/0x40 [ 29.610730] Read of size 40 at addr 0000000000000000 by task bash/414 [ 29.612820] Call Trace: [ 29.613030] <TASK> [ 29.613201] dump_stack_lvl+0x56/0x6f [ 29.613496] ? kmemdup+0x30/0x40 [ 29.613754] print_report.cold+0x494/0x6b7 [ 29.614082] ? kmemdup+0x30/0x40 [ 29.614340] kasan_report+0x8a/0x190 [ 29.614628] ? kmemdup+0x30/0x40 [ 29.614888] kasan_check_range+0x14d/0x1d0 [ 29.615213] memcpy+0x20/0x60 [ 29.615454] kmemdup+0x30/0x40 [ 29.615700] lgdt3306a_probe+0x52/0x310 [ 29.616339] i2c_device_probe+0x951/0xa90	2024-06-25	not yet calculated
Linux--Linux	In the Linux kernel, the following vulnerability has been resolved: media: ti: j721e-csi2rx: Fix races while restarting DMA After the frame is submitted to DMA, it may happen that the submitted list is not updated soon enough, and the DMA callback is triggered before that. This can lead to kernel crashes, so move everything in a single lock/unlock section to prevent such races.	2024-06-24	not yet calculated
Linux--Linux	In the Linux kernel, the following vulnerability has been resolved: f2fs: compress: don't allow unaligned truncation on released compress inode f2fs image may be corrupted after below testcase: - mkfs.f2fs -O extra_attr,compression -f /dev/vdb - mount /dev/vdb /mnt/f2fs - touch /mnt/f2fs/file - f2fs_io setflags compression /mnt/f2fs/file - dd if=/dev/zero of=/mnt/f2fs/file bs=4k count=4 - f2fs_io release_cblocks /mnt/f2fs/file - truncate -s 8192 /mnt/f2fs/file - umount /mnt/f2fs - fsck.f2fs /dev/vdb [ASSERT] (fsck_chk_inode_blk:1256) --> ino: 0x5 has i_blocks: 0x00000002, but has 0x3 blocks [FSCK] valid_block_count matching with CP [Fail] [0x4, 0x5] [FSCK] other corrupted bugs [Fail] The reason is: partial truncation assume compressed inode has reserved blocks, after partial truncation, valid block count may change w/o .i_blocks and .total_valid_block_count update, result in corruption. This patch only allow cluster size aligned truncation on released compress inode for fixing.	2024-06-24	not yet calculated
Linux--Linux	In the Linux kernel, the following vulnerability has been resolved: f2fs: compress: fix to cover {reserve,release}_compress_blocks() w/ cp_rwsem lock It needs to cover {reserve,release}_compress_blocks() w/ cp_rwsem lock to avoid racing with checkpoint, otherwise, filesystem metadata including blkaddr in dnode, inode fields and .total_valid_block_count may be corrupted after SPO case.	2024-06-24	not yet calculated
Linux--Linux	In the Linux kernel, the following vulnerability has been resolved: PCI: of_property: Return error for int_map allocation failure Return -ENOMEM from of_pci_prop_intr_map() if kcalloc() fails to prevent a NULL pointer dereference in this case. [bhelgaas: commit log]	2024-06-24	not yet calculated
Linux--Linux	In the Linux kernel, the following vulnerability has been resolved: fpga: region: add owner module and take its refcount The current implementation of the fpga region assumes that the low-level module registers a driver for the parent device and uses its owner pointer to take the module's refcount. This approach is problematic since it can lead to a null pointer dereference while attempting to get the region during programming if the parent device does not have a driver. To address this problem, add a module owner pointer to the fpga_region struct and use it to take the module's refcount. Modify the functions for registering a region to take an additional owner module parameter and rename them to avoid conflicts. Use the old function names for helper macros that automatically set the module that registers the region as the owner. This ensures compatibility with existing low-level control modules and reduces the chances of registering a region without setting the owner. Also, update the documentation to keep it consistent with the new interface for registering an fpga region.	2024-06-24	not yet calculated
Linux--Linux	In the Linux kernel, the following vulnerability has been resolved: fpga: bridge: add owner module and take its refcount The current implementation of the fpga bridge assumes that the low-level module registers a driver for the parent device and uses its owner pointer to take the module's refcount. This approach is problematic since it can lead to a null pointer dereference while attempting to get the bridge if the parent device does not have a driver. To address this problem, add a module owner pointer to the fpga_bridge struct and use it to take the module's refcount. Modify the function for registering a bridge to take an additional owner module parameter and rename it to avoid conflicts. Use the old function name for a helper macro that automatically sets the module that registers the bridge as the owner. This ensures compatibility with existing low-level control modules and reduces the chances of registering a bridge without setting the owner. Also, update the documentation to keep it consistent with the new interface for registering an fpga bridge. Other changes: opportunistically move put_device() from __fpga_bridge_get() to fpga_bridge_get() and of_fpga_bridge_get() to improve code clarity since the bridge device is taken in these functions.	2024-06-24	not yet calculated
Linux--Linux	In the Linux kernel, the following vulnerability has been resolved: fpga: manager: add owner module and take its refcount The current implementation of the fpga manager assumes that the low-level module registers a driver for the parent device and uses its owner pointer to take the module's refcount. This approach is problematic since it can lead to a null pointer dereference while attempting to get the manager if the parent device does not have a driver. To address this problem, add a module owner pointer to the fpga_manager struct and use it to take the module's refcount. Modify the functions for registering the manager to take an additional owner module parameter and rename them to avoid conflicts. Use the old function names for helper macros that automatically set the module that registers the manager as the owner. This ensures compatibility with existing low-level control modules and reduces the chances of registering a manager without setting the owner. Also, update the documentation to keep it consistent with the new interface for registering an fpga manager. Other changes: opportunistically move put_device() from __fpga_mgr_get() to fpga_mgr_get() and of_fpga_mgr_get() to improve code clarity since the manager device is taken in these functions.	2024-06-24	not yet calculated
Linux--Linux	In the Linux kernel, the following vulnerability has been resolved: drm/xe: Only use reserved BCS instances for usm migrate exec queue The GuC context scheduling queue is 2 entires deep, thus it is possible for a migration job to be stuck behind a fault if migration exec queue shares engines with user jobs. This can deadlock as the migrate exec queue is required to service page faults. Avoid deadlock by only using reserved BCS instances for usm migrate exec queue. (cherry picked from commit 04f4a70a183a688a60fe3882d6e4236ea02cfc67)	2024-06-24	not yet calculated
Linux--Linux	In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix potential kernel bug due to lack of writeback flag waiting Destructive writes to a block device on which nilfs2 is mounted can cause a kernel bug in the folio/page writeback start routine or writeback end routine (__folio_start_writeback in the log below): kernel BUG at mm/page-writeback.c:3070! Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI ... RIP: 0010:__folio_start_writeback+0xbaa/0x10e0 Code: 25 ff 0f 00 00 0f 84 18 01 00 00 e8 40 ca c6 ff e9 17 f6 ff ff e8 36 ca c6 ff 4c 89 f7 48 c7 c6 80 c0 12 84 e8 e7 b3 0f 00 90 <0f> 0b e8 1f ca c6 ff 4c 89 f7 48 c7 c6 a0 c6 12 84 e8 d0 b3 0f 00 ... Call Trace: <TASK> nilfs_segctor_do_construct+0x4654/0x69d0 [nilfs2] nilfs_segctor_construct+0x181/0x6b0 [nilfs2] nilfs_segctor_thread+0x548/0x11c0 [nilfs2] kthread+0x2f0/0x390 ret_from_fork+0x4b/0x80 ret_from_fork_asm+0x1a/0x30 </TASK> This is because when the log writer starts a writeback for segment summary blocks or a super root block that use the backing device's page cache, it does not wait for the ongoing folio/page writeback, resulting in an inconsistent writeback state. Fix this issue by waiting for ongoing writebacks when putting folios/pages on the backing device into writeback state.	2024-06-25	not yet calculated
Linux--Linux	In the Linux kernel, the following vulnerability has been resolved: btrfs: fix crash on racing fsync and size-extending write into prealloc We have been seeing crashes on duplicate keys in btrfs_set_item_key_safe(): BTRFS critical (device vdb): slot 4 key (450 108 8192) new key (450 108 8192) ------------[ cut here ]------------ kernel BUG at fs/btrfs/ctree.c:2620! invalid opcode: 0000 [#1] PREEMPT SMP PTI CPU: 0 PID: 3139 Comm: xfs_io Kdump: loaded Not tainted 6.9.0 #6 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-2.fc40 04/01/2014 RIP: 0010:btrfs_set_item_key_safe+0x11f/0x290 [btrfs] With the following stack trace: #0 btrfs_set_item_key_safe (fs/btrfs/ctree.c:2620:4) #1 btrfs_drop_extents (fs/btrfs/file.c:411:4) #2 log_one_extent (fs/btrfs/tree-log.c:4732:9) #3 btrfs_log_changed_extents (fs/btrfs/tree-log.c:4955:9) #4 btrfs_log_inode (fs/btrfs/tree-log.c:6626:9) #5 btrfs_log_inode_parent (fs/btrfs/tree-log.c:7070:8) #6 btrfs_log_dentry_safe (fs/btrfs/tree-log.c:7171:8) #7 btrfs_sync_file (fs/btrfs/file.c:1933:8) #8 vfs_fsync_range (fs/sync.c:188:9) #9 vfs_fsync (fs/sync.c:202:9) #10 do_fsync (fs/sync.c:212:9) #11 __do_sys_fdatasync (fs/sync.c:225:9) #12 __se_sys_fdatasync (fs/sync.c:223:1) #13 __x64_sys_fdatasync (fs/sync.c:223:1) #14 do_syscall_x64 (arch/x86/entry/common.c:52:14) #15 do_syscall_64 (arch/x86/entry/common.c:83:7) #16 entry_SYSCALL_64+0xaf/0x14c (arch/x86/entry/entry_64.S:121) So we're logging a changed extent from fsync, which is splitting an extent in the log tree. But this split part already exists in the tree, triggering the BUG(). This is the state of the log tree at the time of the crash, dumped with drgn (https://github.com/osandov/drgn/blob/main/contrib/btrfs_tree.py) to get more details than btrfs_print_leaf() gives us: >>> print_extent_buffer(prog.crashed_thread().stack_trace()[0]["eb"]) leaf 33439744 level 0 items 72 generation 9 owner 18446744073709551610 leaf 33439744 flags 0x100000000000000 fs uuid e5bd3946-400c-4223-8923-190ef1f18677 chunk uuid d58cb17e-6d02-494a-829a-18b7d8a399da item 0 key (450 INODE_ITEM 0) itemoff 16123 itemsize 160 generation 7 transid 9 size 8192 nbytes 8473563889606862198 block group 0 mode 100600 links 1 uid 0 gid 0 rdev 0 sequence 204 flags 0x10(PREALLOC) atime 1716417703.220000000 (2024-05-22 15:41:43) ctime 1716417704.983333333 (2024-05-22 15:41:44) mtime 1716417704.983333333 (2024-05-22 15:41:44) otime 17592186044416.000000000 (559444-03-08 01:40:16) item 1 key (450 INODE_REF 256) itemoff 16110 itemsize 13 index 195 namelen 3 name: 193 item 2 key (450 XATTR_ITEM 1640047104) itemoff 16073 itemsize 37 location key (0 UNKNOWN.0 0) type XATTR transid 7 data_len 1 name_len 6 name: user.a data a item 3 key (450 EXTENT_DATA 0) itemoff 16020 itemsize 53 generation 9 type 1 (regular) extent data disk byte 303144960 nr 12288 extent data offset 0 nr 4096 ram 12288 extent compression 0 (none) item 4 key (450 EXTENT_DATA 4096) itemoff 15967 itemsize 53 generation 9 type 2 (prealloc) prealloc data disk byte 303144960 nr 12288 prealloc data offset 4096 nr 8192 item 5 key (450 EXTENT_DATA 8192) itemoff 15914 itemsize 53 generation 9 type 2 (prealloc) prealloc data disk byte 303144960 nr 12288 prealloc data offset 8192 nr 4096 ... So the real problem happened earlier: notice that items 4 (4k-12k) and 5 (8k-12k) overlap. Both are prealloc extents. Item 4 straddles i_size and item 5 starts at i_size. Here is the state of ---truncated---	2024-06-25	not yet calculated
Linux--Linux	In the Linux kernel, the following vulnerability has been resolved: btrfs: protect folio::private when attaching extent buffer folios [BUG] Since v6.8 there are rare kernel crashes reported by various people, the common factor is bad page status error messages like this: BUG: Bad page state in process kswapd0 pfn:d6e840 page: refcount:0 mapcount:0 mapping:000000007512f4f2 index:0x2796c2c7c pfn:0xd6e840 aops:btree_aops ino:1 flags: 0x17ffffe0000008(uptodate\|node=0\|zone=2\|lastcpupid=0x3fffff) page_type: 0xffffffff() raw: 0017ffffe0000008 dead000000000100 dead000000000122 ffff88826d0be4c0 raw: 00000002796c2c7c 0000000000000000 00000000ffffffff 0000000000000000 page dumped because: non-NULL mapping [CAUSE] Commit 09e6cef19c9f ("btrfs: refactor alloc_extent_buffer() to allocate-then-attach method") changes the sequence when allocating a new extent buffer. Previously we always called grab_extent_buffer() under mapping->i_private_lock, to ensure the safety on modification on folio::private (which is a pointer to extent buffer for regular sectorsize). This can lead to the following race: Thread A is trying to allocate an extent buffer at bytenr X, with 4 4K pages, meanwhile thread B is trying to release the page at X + 4K (the second page of the extent buffer at X). Thread A \| Thread B -----------------------------------+------------------------------------- \| btree_release_folio() \| \| This is for the page at X + 4K, \| \| Not page X. \| \| alloc_extent_buffer() \| \|- release_extent_buffer() \|- filemap_add_folio() for the \| \| \|- atomic_dec_and_test(eb->refs) \| page at bytenr X (the first \| \| \| \| page). \| \| \| \| Which returned -EEXIST. \| \| \| \| \| \| \| \|- filemap_lock_folio() \| \| \| \| Returned the first page locked. \| \| \| \| \| \| \| \|- grab_extent_buffer() \| \| \| \| \|- atomic_inc_not_zero() \| \| \| \| \| Returned false \| \| \| \| \|- folio_detach_private() \| \| \|- folio_detach_private() for X \| \|- folio_test_private() \| \| \|- folio_test_private() \| Returned true \| \| \| Returned true \|- folio_put() \| \|- folio_put() Now there are two puts on the same folio at folio X, leading to refcount underflow of the folio X, and eventually causing the BUG_ON() on the page->mapping. The condition is not that easy to hit: - The release must be triggered for the middle page of an eb If the release is on the same first page of an eb, page lock would kick in and prevent the race. - folio_detach_private() has a very small race window It's only between folio_test_private() and folio_clear_private(). That's exactly when mapping->i_private_lock is used to prevent such race, and commit 09e6cef19c9f ("btrfs: refactor alloc_extent_buffer() to allocate-then-attach method") screwed that up. At that time, I thought the page lock would kick in as filemap_release_folio() also requires the page to be locked, but forgot the filemap_release_folio() only locks one page, not all pages of an extent buffer. [FIX] Move all the code requiring i_private_lock into attach_eb_folio_to_filemap(), so that everything is done with proper lock protection. Furthermore to prevent future problems, add an extra lockdep_assert_locked() to ensure we're holding the proper lock. To reproducer that is able to hit the race (takes a few minutes with instrumented code inserting delays to alloc_extent_buffer()): #!/bin/sh drop_caches () { while(true); do echo 3 > /proc/sys/vm/drop_caches echo 1 > /proc/sys/vm/compact_memory done } run_tar () { while(true); do for x in `seq 1 80` ; do tar cf /dev/zero /mnt > /dev/null & done wait done } mkfs.btrfs -f -d single -m single ---truncated---	2024-06-25	not yet calculated
Linux--Linux	In the Linux kernel, the following vulnerability has been resolved: blk-cgroup: fix list corruption from reorder of WRITE ->lqueued __blkcg_rstat_flush() can be run anytime, especially when blk_cgroup_bio_start is being executed. If WRITE of `->lqueued` is re-ordered with READ of 'bisc->lnode.next' in the loop of __blkcg_rstat_flush(), `next_bisc` can be assigned with one stat instance being added in blk_cgroup_bio_start(), then the local list in __blkcg_rstat_flush() could be corrupted. Fix the issue by adding one barrier.	2024-06-24	not yet calculated
Linux--Linux	In the Linux kernel, the following vulnerability has been resolved: genirq/irqdesc: Prevent use-after-free in irq_find_at_or_after() irq_find_at_or_after() dereferences the interrupt descriptor which is returned by mt_find() while neither holding sparse_irq_lock nor RCU read lock, which means the descriptor can be freed between mt_find() and the dereference: CPU0 CPU1 desc = mt_find() delayed_free_desc(desc) irq_desc_get_irq(desc) The use-after-free is reported by KASAN: Call trace: irq_get_next_irq+0x58/0x84 show_stat+0x638/0x824 seq_read_iter+0x158/0x4ec proc_reg_read_iter+0x94/0x12c vfs_read+0x1e0/0x2c8 Freed by task 4471: slab_free_freelist_hook+0x174/0x1e0 __kmem_cache_free+0xa4/0x1dc kfree+0x64/0x128 irq_kobj_release+0x28/0x3c kobject_put+0xcc/0x1e0 delayed_free_desc+0x14/0x2c rcu_do_batch+0x214/0x720 Guard the access with a RCU read lock section.	2024-06-25	not yet calculated
Linux--Linux	In the Linux kernel, the following vulnerability has been resolved: s390/ap: Fix crash in AP internal function modify_bitmap() A system crash like this Failing address: 200000cb7df6f000 TEID: 200000cb7df6f403 Fault in home space mode while using kernel ASCE. AS:00000002d71bc007 R3:00000003fe5b8007 S:000000011a446000 P:000000015660c13d Oops: 0038 ilc:3 [#1] PREEMPT SMP Modules linked in: mlx5_ib ... CPU: 8 PID: 7556 Comm: bash Not tainted 6.9.0-rc7 #8 Hardware name: IBM 3931 A01 704 (LPAR) Krnl PSW : 0704e00180000000 0000014b75e7b606 (ap_parse_bitmap_str+0x10e/0x1f8) R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 RI:0 EA:3 Krnl GPRS: 0000000000000001 ffffffffffffffc0 0000000000000001 00000048f96b75d3 000000cb00000100 ffffffffffffffff ffffffffffffffff 000000cb7df6fce0 000000cb7df6fce0 00000000ffffffff 000000000000002b 00000048ffffffff 000003ff9b2dbc80 200000cb7df6fcd8 0000014bffffffc0 000000cb7df6fbc8 Krnl Code: 0000014b75e7b5fc: a7840047 brc 8,0000014b75e7b68a 0000014b75e7b600: 18b2 lr %r11,%r2 #0000014b75e7b602: a7f4000a brc 15,0000014b75e7b616 >0000014b75e7b606: eb22d00000e6 laog %r2,%r2,0(%r13) 0000014b75e7b60c: a7680001 lhi %r6,1 0000014b75e7b610: 187b lr %r7,%r11 0000014b75e7b612: 84960021 brxh %r9,%r6,0000014b75e7b654 0000014b75e7b616: 18e9 lr %r14,%r9 Call Trace: [<0000014b75e7b606>] ap_parse_bitmap_str+0x10e/0x1f8 ([<0000014b75e7b5dc>] ap_parse_bitmap_str+0xe4/0x1f8) [<0000014b75e7b758>] apmask_store+0x68/0x140 [<0000014b75679196>] kernfs_fop_write_iter+0x14e/0x1e8 [<0000014b75598524>] vfs_write+0x1b4/0x448 [<0000014b7559894c>] ksys_write+0x74/0x100 [<0000014b7618a440>] __do_syscall+0x268/0x328 [<0000014b761a3558>] system_call+0x70/0x98 INFO: lockdep is turned off. Last Breaking-Event-Address: [<0000014b75e7b636>] ap_parse_bitmap_str+0x13e/0x1f8 Kernel panic - not syncing: Fatal exception: panic_on_oops occured when /sys/bus/ap/a[pq]mask was updated with a relative mask value (like +0x10-0x12,+60,-90) with one of the numeric values exceeding INT_MAX. The fix is simple: use unsigned long values for the internal variables. The correct checks are already in place in the function but a simple int for the internal variables was used with the possibility to overflow.	2024-06-25	not yet calculated
Linux--Linux	In the Linux kernel, the following vulnerability has been resolved: blk-cgroup: fix list corruption from resetting io stat Since commit 3b8cc6298724 ("blk-cgroup: Optimize blkcg_rstat_flush()"), each iostat instance is added to blkcg percpu list, so blkcg_reset_stats() can't reset the stat instance by memset(), otherwise the llist may be corrupted. Fix the issue by only resetting the counter part.	2024-06-24	not yet calculated
Linux--Linux	In the Linux kernel, the following vulnerability has been resolved: ext4: fix mb_cache_entry's e_refcnt leak in ext4_xattr_block_cache_find() Syzbot reports a warning as follows: ============================================ WARNING: CPU: 0 PID: 5075 at fs/mbcache.c:419 mb_cache_destroy+0x224/0x290 Modules linked in: CPU: 0 PID: 5075 Comm: syz-executor199 Not tainted 6.9.0-rc6-gb947cc5bf6d7 RIP: 0010:mb_cache_destroy+0x224/0x290 fs/mbcache.c:419 Call Trace: <TASK> ext4_put_super+0x6d4/0xcd0 fs/ext4/super.c:1375 generic_shutdown_super+0x136/0x2d0 fs/super.c:641 kill_block_super+0x44/0x90 fs/super.c:1675 ext4_kill_sb+0x68/0xa0 fs/ext4/super.c:7327 [...] ============================================ This is because when finding an entry in ext4_xattr_block_cache_find(), if ext4_sb_bread() returns -ENOMEM, the ce's e_refcnt, which has already grown in the __entry_find(), won't be put away, and eventually trigger the above issue in mb_cache_destroy() due to reference count leakage. So call mb_cache_entry_put() on the -ENOMEM error branch as a quick fix.	2024-06-25	not yet calculated
Linux--Linux	In the Linux kernel, the following vulnerability has been resolved: Revert "xsk: Support redirect to any socket bound to the same umem" This reverts commit 2863d665ea41282379f108e4da6c8a2366ba66db. This patch introduced a potential kernel crash when multiple napi instances redirect to the same AF_XDP socket. By removing the queue_index check, it is possible for multiple napi instances to access the Rx ring at the same time, which will result in a corrupted ring state which can lead to a crash when flushing the rings in __xsk_flush(). This can happen when the linked list of sockets to flush gets corrupted by concurrent accesses. A quick and small fix is not possible, so let us revert this for now.	2024-06-25	not yet calculated
Linux--Linux	In the Linux kernel, the following vulnerability has been resolved: bonding: fix oops during rmmod "rmmod bonding" causes an oops ever since commit cc317ea3d927 ("bonding: remove redundant NULL check in debugfs function"). Here are the relevant functions being called: bonding_exit() bond_destroy_debugfs() debugfs_remove_recursive(bonding_debug_root); bonding_debug_root = NULL; <--------- SET TO NULL HERE bond_netlink_fini() rtnl_link_unregister() __rtnl_link_unregister() unregister_netdevice_many_notify() bond_uninit() bond_debug_unregister() (commit removed check for bonding_debug_root == NULL) debugfs_remove() simple_recursive_removal() down_write() -> OOPS However, reverting the bad commit does not solve the problem completely because the original code contains a race that could cause the same oops, although it was much less likely to be triggered unintentionally: CPU1 rmmod bonding bonding_exit() bond_destroy_debugfs() debugfs_remove_recursive(bonding_debug_root); CPU2 echo -bond0 > /sys/class/net/bonding_masters bond_uninit() bond_debug_unregister() if (!bonding_debug_root) CPU1 bonding_debug_root = NULL; So do NOT revert the bad commit (since the removed checks were racy anyway), and instead change the order of actions taken during module removal. The same oops can also happen if there is an error during module init, so apply the same fix there.	2024-06-25	not yet calculated
Linux--Linux	In the Linux kernel, the following vulnerability has been resolved: mm/memory-failure: fix handling of dissolved but not taken off from buddy pages When I did memory failure tests recently, below panic occurs: page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x8cee00 flags: 0x6fffe0000000000(node=1\|zone=2\|lastcpupid=0x7fff) raw: 06fffe0000000000 dead000000000100 dead000000000122 0000000000000000 raw: 0000000000000000 0000000000000009 00000000ffffffff 0000000000000000 page dumped because: VM_BUG_ON_PAGE(!PageBuddy(page)) ------------[ cut here ]------------ kernel BUG at include/linux/page-flags.h:1009! invalid opcode: 0000 [#1] PREEMPT SMP NOPTI RIP: 0010:__del_page_from_free_list+0x151/0x180 RSP: 0018:ffffa49c90437998 EFLAGS: 00000046 RAX: 0000000000000035 RBX: 0000000000000009 RCX: ffff8dd8dfd1c9c8 RDX: 0000000000000000 RSI: 0000000000000027 RDI: ffff8dd8dfd1c9c0 RBP: ffffd901233b8000 R08: ffffffffab5511f8 R09: 0000000000008c69 R10: 0000000000003c15 R11: ffffffffab5511f8 R12: ffff8dd8fffc0c80 R13: 0000000000000001 R14: ffff8dd8fffc0c80 R15: 0000000000000009 FS: 00007ff916304740(0000) GS:ffff8dd8dfd00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000055eae50124c8 CR3: 00000008479e0000 CR4: 00000000000006f0 Call Trace: <TASK> __rmqueue_pcplist+0x23b/0x520 get_page_from_freelist+0x26b/0xe40 __alloc_pages_noprof+0x113/0x1120 __folio_alloc_noprof+0x11/0xb0 alloc_buddy_hugetlb_folio.isra.0+0x5a/0x130 __alloc_fresh_hugetlb_folio+0xe7/0x140 alloc_pool_huge_folio+0x68/0x100 set_max_huge_pages+0x13d/0x340 hugetlb_sysctl_handler_common+0xe8/0x110 proc_sys_call_handler+0x194/0x280 vfs_write+0x387/0x550 ksys_write+0x64/0xe0 do_syscall_64+0xc2/0x1d0 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7ff916114887 RSP: 002b:00007ffec8a2fd78 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX: 000055eae500e350 RCX: 00007ff916114887 RDX: 0000000000000004 RSI: 000055eae500e390 RDI: 0000000000000003 RBP: 000055eae50104c0 R08: 0000000000000000 R09: 000055eae50104c0 R10: 0000000000000077 R11: 0000000000000246 R12: 0000000000000004 R13: 0000000000000004 R14: 00007ff916216b80 R15: 00007ff916216a00 </TASK> Modules linked in: mce_inject hwpoison_inject ---[ end trace 0000000000000000 ]--- And before the panic, there had an warning about bad page state: BUG: Bad page state in process page-types pfn:8cee00 page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x8cee00 flags: 0x6fffe0000000000(node=1\|zone=2\|lastcpupid=0x7fff) page_type: 0xffffff7f(buddy) raw: 06fffe0000000000 ffffd901241c0008 ffffd901240f8008 0000000000000000 raw: 0000000000000000 0000000000000009 00000000ffffff7f 0000000000000000 page dumped because: nonzero mapcount Modules linked in: mce_inject hwpoison_inject CPU: 8 PID: 154211 Comm: page-types Not tainted 6.9.0-rc4-00499-g5544ec3178e2-dirty #22 Call Trace: <TASK> dump_stack_lvl+0x83/0xa0 bad_page+0x63/0xf0 free_unref_page+0x36e/0x5c0 unpoison_memory+0x50b/0x630 simple_attr_write_xsigned.constprop.0.isra.0+0xb3/0x110 debugfs_attr_write+0x42/0x60 full_proxy_write+0x5b/0x80 vfs_write+0xcd/0x550 ksys_write+0x64/0xe0 do_syscall_64+0xc2/0x1d0 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f189a514887 RSP: 002b:00007ffdcd899718 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f189a514887 RDX: 0000000000000009 RSI: 00007ffdcd899730 RDI: 0000000000000003 RBP: 00007ffdcd8997a0 R08: 0000000000000000 R09: 00007ffdcd8994b2 R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffdcda199a8 R13: 0000000000404af1 R14: 000000000040ad78 R15: 00007f189a7a5040 </TASK> The root cause should be the below race: memory_failure try_memory_failure_hugetlb me_huge_page __page_handle_poison dissolve_free_hugetlb_folio drain_all_pages -- Buddy page can be isolated e.g. for compaction. take_page_off_buddy -- Failed as page is not in the ---truncated---	2024-06-25	not yet calculated
Linux--Linux	In the Linux kernel, the following vulnerability has been resolved: net/9p: fix uninit-value in p9_client_rpc() Syzbot with the help of KMSAN reported the following error: BUG: KMSAN: uninit-value in trace_9p_client_res include/trace/events/9p.h:146 [inline] BUG: KMSAN: uninit-value in p9_client_rpc+0x1314/0x1340 net/9p/client.c:754 trace_9p_client_res include/trace/events/9p.h:146 [inline] p9_client_rpc+0x1314/0x1340 net/9p/client.c:754 p9_client_create+0x1551/0x1ff0 net/9p/client.c:1031 v9fs_session_init+0x1b9/0x28e0 fs/9p/v9fs.c:410 v9fs_mount+0xe2/0x12b0 fs/9p/vfs_super.c:122 legacy_get_tree+0x114/0x290 fs/fs_context.c:662 vfs_get_tree+0xa7/0x570 fs/super.c:1797 do_new_mount+0x71f/0x15e0 fs/namespace.c:3352 path_mount+0x742/0x1f20 fs/namespace.c:3679 do_mount fs/namespace.c:3692 [inline] __do_sys_mount fs/namespace.c:3898 [inline] __se_sys_mount+0x725/0x810 fs/namespace.c:3875 __x64_sys_mount+0xe4/0x150 fs/namespace.c:3875 do_syscall_64+0xd5/0x1f0 entry_SYSCALL_64_after_hwframe+0x6d/0x75 Uninit was created at: __alloc_pages+0x9d6/0xe70 mm/page_alloc.c:4598 __alloc_pages_node include/linux/gfp.h:238 [inline] alloc_pages_node include/linux/gfp.h:261 [inline] alloc_slab_page mm/slub.c:2175 [inline] allocate_slab mm/slub.c:2338 [inline] new_slab+0x2de/0x1400 mm/slub.c:2391 ___slab_alloc+0x1184/0x33d0 mm/slub.c:3525 __slab_alloc mm/slub.c:3610 [inline] __slab_alloc_node mm/slub.c:3663 [inline] slab_alloc_node mm/slub.c:3835 [inline] kmem_cache_alloc+0x6d3/0xbe0 mm/slub.c:3852 p9_tag_alloc net/9p/client.c:278 [inline] p9_client_prepare_req+0x20a/0x1770 net/9p/client.c:641 p9_client_rpc+0x27e/0x1340 net/9p/client.c:688 p9_client_create+0x1551/0x1ff0 net/9p/client.c:1031 v9fs_session_init+0x1b9/0x28e0 fs/9p/v9fs.c:410 v9fs_mount+0xe2/0x12b0 fs/9p/vfs_super.c:122 legacy_get_tree+0x114/0x290 fs/fs_context.c:662 vfs_get_tree+0xa7/0x570 fs/super.c:1797 do_new_mount+0x71f/0x15e0 fs/namespace.c:3352 path_mount+0x742/0x1f20 fs/namespace.c:3679 do_mount fs/namespace.c:3692 [inline] __do_sys_mount fs/namespace.c:3898 [inline] __se_sys_mount+0x725/0x810 fs/namespace.c:3875 __x64_sys_mount+0xe4/0x150 fs/namespace.c:3875 do_syscall_64+0xd5/0x1f0 entry_SYSCALL_64_after_hwframe+0x6d/0x75 If p9_check_errors() fails early in p9_client_rpc(), req->rc.tag will not be properly initialized. However, trace_9p_client_res() ends up trying to print it out anyway before p9_client_rpc() finishes. Fix this issue by assigning default values to p9_fcall fields such as 'tag' and (just in case KMSAN unearths something new) 'id' during the tag allocation stage.	2024-06-25	not yet calculated
Linux--Linux	In the Linux kernel, the following vulnerability has been resolved: i2c: acpi: Unbind mux adapters before delete There is an issue with ACPI overlay table removal specifically related to I2C multiplexers. Consider an ACPI SSDT Overlay that defines a PCA9548 I2C mux on an existing I2C bus. When this table is loaded we see the creation of a device for the overall PCA9548 chip and 8 further devices - one i2c_adapter each for the mux channels. These are all bound to their ACPI equivalents via an eventual invocation of acpi_bind_one(). When we unload the SSDT overlay we run into the problem. The ACPI devices are deleted as normal via acpi_device_del_work_fn() and the acpi_device_del_list. However, the following warning and stack trace is output as the deletion does not go smoothly: ------------[ cut here ]------------ kernfs: can not remove 'physical_node', no directory WARNING: CPU: 1 PID: 11 at fs/kernfs/dir.c:1674 kernfs_remove_by_name_ns+0xb9/0xc0 Modules linked in: CPU: 1 PID: 11 Comm: kworker/u128:0 Not tainted 6.8.0-rc6+ #1 Hardware name: congatec AG conga-B7E3/conga-B7E3, BIOS 5.13 05/16/2023 Workqueue: kacpi_hotplug acpi_device_del_work_fn RIP: 0010:kernfs_remove_by_name_ns+0xb9/0xc0 Code: e4 00 48 89 ef e8 07 71 db ff 5b b8 fe ff ff ff 5d 41 5c 41 5d e9 a7 55 e4 00 0f 0b eb a6 48 c7 c7 f0 38 0d 9d e8 97 0a d5 ff <0f> 0b eb dc 0f 1f 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 RSP: 0018:ffff9f864008fb28 EFLAGS: 00010286 RAX: 0000000000000000 RBX: ffff8ef90a8d4940 RCX: 0000000000000000 RDX: ffff8f000e267d10 RSI: ffff8f000e25c780 RDI: ffff8f000e25c780 RBP: ffff8ef9186f9870 R08: 0000000000013ffb R09: 00000000ffffbfff R10: 00000000ffffbfff R11: ffff8f000e0a0000 R12: ffff9f864008fb50 R13: ffff8ef90c93dd60 R14: ffff8ef9010d0958 R15: ffff8ef9186f98c8 FS: 0000000000000000(0000) GS:ffff8f000e240000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f48f5253a08 CR3: 00000003cb82e000 CR4: 00000000003506f0 Call Trace: <TASK> ? kernfs_remove_by_name_ns+0xb9/0xc0 ? __warn+0x7c/0x130 ? kernfs_remove_by_name_ns+0xb9/0xc0 ? report_bug+0x171/0x1a0 ? handle_bug+0x3c/0x70 ? exc_invalid_op+0x17/0x70 ? asm_exc_invalid_op+0x1a/0x20 ? kernfs_remove_by_name_ns+0xb9/0xc0 ? kernfs_remove_by_name_ns+0xb9/0xc0 acpi_unbind_one+0x108/0x180 device_del+0x18b/0x490 ? srso_return_thunk+0x5/0x5f ? srso_return_thunk+0x5/0x5f device_unregister+0xd/0x30 i2c_del_adapter.part.0+0x1bf/0x250 i2c_mux_del_adapters+0xa1/0xe0 i2c_device_remove+0x1e/0x80 device_release_driver_internal+0x19a/0x200 bus_remove_device+0xbf/0x100 device_del+0x157/0x490 ? __pfx_device_match_fwnode+0x10/0x10 ? srso_return_thunk+0x5/0x5f device_unregister+0xd/0x30 i2c_acpi_notify+0x10f/0x140 notifier_call_chain+0x58/0xd0 blocking_notifier_call_chain+0x3a/0x60 acpi_device_del_work_fn+0x85/0x1d0 process_one_work+0x134/0x2f0 worker_thread+0x2f0/0x410 ? __pfx_worker_thread+0x10/0x10 kthread+0xe3/0x110 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x2f/0x50 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1b/0x30 </TASK> ---[ end trace 0000000000000000 ]--- ... repeated 7 more times, 1 for each channel of the mux ... The issue is that the binding of the ACPI devices to their peer I2C adapters is not correctly cleaned up. Digging deeper into the issue we see that the deletion order is such that the ACPI devices matching the mux channel i2c adapters are deleted first during the SSDT overlay removal. For each of the channels we see a call to i2c_acpi_notify() with ACPI_RECONFIG_DEVICE_REMOVE but, because these devices are not actually i2c_clients, nothing is done for them. Later on, after each of the mux channels has been dealt with, we come to delete the i2c_client representing the PCA9548 device. This is the call stack we see above, whereby the kernel cleans up the i2c_client including destruction of the mux and its channel adapters. At this point we do attempt to unbind from the ACPI peers but those peers ---truncated---	2024-06-25	not yet calculated
Linux--Linux	In the Linux kernel, the following vulnerability has been resolved: io_uring: check for non-NULL file pointer in io_file_can_poll() In earlier kernels, it was possible to trigger a NULL pointer dereference off the forced async preparation path, if no file had been assigned. The trace leading to that looks as follows: BUG: kernel NULL pointer dereference, address: 00000000000000b0 PGD 0 P4D 0 Oops: 0000 [#1] PREEMPT SMP CPU: 67 PID: 1633 Comm: buf-ring-invali Not tainted 6.8.0-rc3+ #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS unknown 2/2/2022 RIP: 0010:io_buffer_select+0xc3/0x210 Code: 00 00 48 39 d1 0f 82 ae 00 00 00 48 81 4b 48 00 00 01 00 48 89 73 70 0f b7 50 0c 66 89 53 42 85 ed 0f 85 d2 00 00 00 48 8b 13 <48> 8b 92 b0 00 00 00 48 83 7a 40 00 0f 84 21 01 00 00 4c 8b 20 5b RSP: 0018:ffffb7bec38c7d88 EFLAGS: 00010246 RAX: ffff97af2be61000 RBX: ffff97af234f1700 RCX: 0000000000000040 RDX: 0000000000000000 RSI: ffff97aecfb04820 RDI: ffff97af234f1700 RBP: 0000000000000000 R08: 0000000000200030 R09: 0000000000000020 R10: ffffb7bec38c7dc8 R11: 000000000000c000 R12: ffffb7bec38c7db8 R13: ffff97aecfb05800 R14: ffff97aecfb05800 R15: ffff97af2be5e000 FS: 00007f852f74b740(0000) GS:ffff97b1eeec0000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00000000000000b0 CR3: 000000016deab005 CR4: 0000000000370ef0 Call Trace: <TASK> ? __die+0x1f/0x60 ? page_fault_oops+0x14d/0x420 ? do_user_addr_fault+0x61/0x6a0 ? exc_page_fault+0x6c/0x150 ? asm_exc_page_fault+0x22/0x30 ? io_buffer_select+0xc3/0x210 __io_import_iovec+0xb5/0x120 io_readv_prep_async+0x36/0x70 io_queue_sqe_fallback+0x20/0x260 io_submit_sqes+0x314/0x630 __do_sys_io_uring_enter+0x339/0xbc0 ? __do_sys_io_uring_register+0x11b/0xc50 ? vm_mmap_pgoff+0xce/0x160 do_syscall_64+0x5f/0x180 entry_SYSCALL_64_after_hwframe+0x46/0x4e RIP: 0033:0x55e0a110a67e Code: ba cc 00 00 00 45 31 c0 44 0f b6 92 d0 00 00 00 31 d2 41 b9 08 00 00 00 41 83 e2 01 41 c1 e2 04 41 09 c2 b8 aa 01 00 00 0f 05 <c3> 90 89 30 eb a9 0f 1f 40 00 48 8b 42 20 8b 00 a8 06 75 af 85 f6 because the request is marked forced ASYNC and has a bad file fd, and hence takes the forced async prep path. Current kernels with the request async prep cleaned up can no longer hit this issue, but for ease of backporting, let's add this safety check in here too as it really doesn't hurt. For both cases, this will inevitably end with a CQE posted with -EBADF.	2024-06-25	not yet calculated
Linux--Linux	In the Linux kernel, the following vulnerability has been resolved: clk: bcm: rpi: Assign ->num before accessing ->hws Commit f316cdff8d67 ("clk: Annotate struct clk_hw_onecell_data with __counted_by") annotated the hws member of 'struct clk_hw_onecell_data' with __counted_by, which informs the bounds sanitizer about the number of elements in hws, so that it can warn when hws is accessed out of bounds. As noted in that change, the __counted_by member must be initialized with the number of elements before the first array access happens, otherwise there will be a warning from each access prior to the initialization because the number of elements is zero. This occurs in raspberrypi_discover_clocks() due to ->num being assigned after ->hws has been accessed: UBSAN: array-index-out-of-bounds in drivers/clk/bcm/clk-raspberrypi.c:374:4 index 3 is out of range for type 'struct clk_hw [] __counted_by(num)' (aka 'struct clk_hw []') Move the ->num initialization to before the first access of ->hws, which clears up the warning.	2024-06-25	not yet calculated
Linux--Linux	In the Linux kernel, the following vulnerability has been resolved: clk: bcm: dvp: Assign ->num before accessing ->hws Commit f316cdff8d67 ("clk: Annotate struct clk_hw_onecell_data with __counted_by") annotated the hws member of 'struct clk_hw_onecell_data' with __counted_by, which informs the bounds sanitizer about the number of elements in hws, so that it can warn when hws is accessed out of bounds. As noted in that change, the __counted_by member must be initialized with the number of elements before the first array access happens, otherwise there will be a warning from each access prior to the initialization because the number of elements is zero. This occurs in clk_dvp_probe() due to ->num being assigned after ->hws has been accessed: UBSAN: array-index-out-of-bounds in drivers/clk/bcm/clk-bcm2711-dvp.c:59:2 index 0 is out of range for type 'struct clk_hw [] __counted_by(num)' (aka 'struct clk_hw []') Move the ->num initialization to before the first access of ->hws, which clears up the warning.	2024-06-25	not yet calculated
Linux--Linux	In the Linux kernel, the following vulnerability has been resolved: 9p: add missing locking around taking dentry fid list Fix a use-after-free on dentry's d_fsdata fid list when a thread looks up a fid through dentry while another thread unlinks it: UAF thread: refcount_t: addition on 0; use-after-free. p9_fid_get linux/./include/net/9p/client.h:262 v9fs_fid_find+0x236/0x280 linux/fs/9p/fid.c:129 v9fs_fid_lookup_with_uid linux/fs/9p/fid.c:181 v9fs_fid_lookup+0xbf/0xc20 linux/fs/9p/fid.c:314 v9fs_vfs_getattr_dotl+0xf9/0x360 linux/fs/9p/vfs_inode_dotl.c:400 vfs_statx+0xdd/0x4d0 linux/fs/stat.c:248 Freed by: p9_fid_destroy (inlined) p9_client_clunk+0xb0/0xe0 linux/net/9p/client.c:1456 p9_fid_put linux/./include/net/9p/client.h:278 v9fs_dentry_release+0xb5/0x140 linux/fs/9p/vfs_dentry.c:55 v9fs_remove+0x38f/0x620 linux/fs/9p/vfs_inode.c:518 vfs_unlink+0x29a/0x810 linux/fs/namei.c:4335 The problem is that d_fsdata was not accessed under d_lock, because d_release() normally is only called once the dentry is otherwise no longer accessible but since we also call it explicitly in v9fs_remove that lock is required: move the hlist out of the dentry under lock then unref its fids once they are no longer accessible.	2024-06-25	not yet calculated
Linux--Linux	In the Linux kernel, the following vulnerability has been resolved: media: v4l: async: Fix notifier list entry init struct v4l2_async_notifier has several list_head members, but only waiting_list and done_list are initialized. notifier_entry was kept 'zeroed' leading to an uninitialized list_head. This results in a NULL-pointer dereference if csi2_async_register() fails, e.g. node for remote endpoint is disabled, and returns -ENOTCONN. The following calls to v4l2_async_nf_unregister() results in a NULL pointer dereference. Add the missing list head initializer.	2024-06-25	not yet calculated
Linux--Linux	In the Linux kernel, the following vulnerability has been resolved: media: mgb4: Fix double debugfs remove Fixes an error where debugfs_remove_recursive() is called first on a parent directory and then again on a child which causes a kernel panic. [hverkuil: added Fixes/Cc tags]	2024-06-25	not yet calculated
Linux--Linux	In the Linux kernel, the following vulnerability has been resolved: thermal/drivers/qcom/lmh: Check for SCM availability at probe Up until now, the necessary scm availability check has not been performed, leading to possible null pointer dereferences (which did happen for me on RB1). Fix that.	2024-06-25	not yet calculated
Linux--Linux	In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to do sanity check on i_xattr_nid in sanity_check_inode() syzbot reports a kernel bug as below: F2FS-fs (loop0): Mounted with checkpoint version = 48b305e4 ================================================================== BUG: KASAN: slab-out-of-bounds in f2fs_test_bit fs/f2fs/f2fs.h:2933 [inline] BUG: KASAN: slab-out-of-bounds in current_nat_addr fs/f2fs/node.h:213 [inline] BUG: KASAN: slab-out-of-bounds in f2fs_get_node_info+0xece/0x1200 fs/f2fs/node.c:600 Read of size 1 at addr ffff88807a58c76c by task syz-executor280/5076 CPU: 1 PID: 5076 Comm: syz-executor280 Not tainted 6.9.0-rc5-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024 Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114 print_address_description mm/kasan/report.c:377 [inline] print_report+0x169/0x550 mm/kasan/report.c:488 kasan_report+0x143/0x180 mm/kasan/report.c:601 f2fs_test_bit fs/f2fs/f2fs.h:2933 [inline] current_nat_addr fs/f2fs/node.h:213 [inline] f2fs_get_node_info+0xece/0x1200 fs/f2fs/node.c:600 f2fs_xattr_fiemap fs/f2fs/data.c:1848 [inline] f2fs_fiemap+0x55d/0x1ee0 fs/f2fs/data.c:1925 ioctl_fiemap fs/ioctl.c:220 [inline] do_vfs_ioctl+0x1c07/0x2e50 fs/ioctl.c:838 __do_sys_ioctl fs/ioctl.c:902 [inline] __se_sys_ioctl+0x81/0x170 fs/ioctl.c:890 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf5/0x240 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f The root cause is we missed to do sanity check on i_xattr_nid during f2fs_iget(), so that in fiemap() path, current_nat_addr() will access nat_bitmap w/ offset from invalid i_xattr_nid, result in triggering kasan bug report, fix it.	2024-06-25	not yet calculated
Linux--Linux	In the Linux kernel, the following vulnerability has been resolved: smb: client: fix deadlock in smb2_find_smb_tcon() Unlock cifs_tcp_ses_lock before calling cifs_put_smb_ses() to avoid such deadlock.	2024-06-25	not yet calculated
Linux--Linux	In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix nilfs_empty_dir() misjudgment and long loop on I/O errors The error handling in nilfs_empty_dir() when a directory folio/page read fails is incorrect, as in the old ext2 implementation, and if the folio/page cannot be read or nilfs_check_folio() fails, it will falsely determine the directory as empty and corrupt the file system. In addition, since nilfs_empty_dir() does not immediately return on a failed folio/page read, but continues to loop, this can cause a long loop with I/O if i_size of the directory's inode is also corrupted, causing the log writer thread to wait and hang, as reported by syzbot. Fix these issues by making nilfs_empty_dir() immediately return a false value (0) if it fails to get a directory folio/page.	2024-06-25	not yet calculated
Linux--Linux	In the Linux kernel, the following vulnerability has been resolved: eventfs: Fix a possible null pointer dereference in eventfs_find_events() In function eventfs_find_events,there is a potential null pointer that may be caused by calling update_events_attr which will perform some operations on the members of the ei struct when ei is NULL. Hence,When ei->is_freed is set,return NULL directly.	2024-06-25	not yet calculated
Linux--Linux	In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: add error handle to avoid out-of-bounds if the sdma_v4_0_irq_id_to_seq return -EINVAL, the process should be stop to avoid out-of-bounds read, so directly return -EINVAL.	2024-06-25	not yet calculated
lunary-ai--lunary-ai/lunary	In lunary-ai/lunary version 1.2.4, an improper access control vulnerability allows members with team management permissions to manipulate project identifiers in requests, enabling them to invite users to projects in other organizations, change members to projects in other organizations with escalated privileges, and change members from other organizations to their own or other projects, also with escalated privileges. This vulnerability is due to the backend's failure to validate project identifiers against the current user's organization ID and projects belonging to it, as well as a misconfiguration in attribute naming (`org_id` should be `orgId`) that prevents proper user organization validation. As a result, attackers can cause inconsistencies on the platform for affected users and organizations, including unauthorized privilege escalation. The issue is present in the backend API endpoints for user invitation and modification, specifically in the handling of project IDs in requests.	2024-06-27	not yet calculated
lunary-ai--lunary-ai/lunary	In lunary-ai/lunary versions <=v1.2.11, an attacker can bypass email validation by using a dot character ('.') in the email address. This allows the creation of multiple accounts with essentially the same email address (e.g., '[email protected]' and '[email protected]'), leading to incorrect synchronization and potential security issues.	2024-06-27	not yet calculated
lunary-ai--lunary-ai/lunary	In version 1.2.7 of lunary-ai/lunary, any authenticated user, regardless of their role, can change the name of an organization due to improper access control. The function checkAccess() is not implemented, allowing users with the lowest privileges, such as the 'Prompt Editor' role, to modify organization attributes without proper authorization.	2024-06-27	not yet calculated
marKoni--Markoni-D (Compact) FM Transmitters	TELSAT marKoni FM Transmitters are vulnerable to a command injection vulnerability through the manipulation of settings and could allow an attacker to gain unauthorized access to the system with administrative privileges.	2024-06-27	not yet calculated
marKoni--Markoni-D (Compact) FM Transmitters	TELSAT marKoni FM Transmitters are vulnerable to an attacker exploiting a hidden admin account that can be accessed through the use of hard-coded credentials.	2024-06-27	not yet calculated
marKoni--Markoni-D (Compact) FM Transmitters	TELSAT marKoni FM Transmitters are vulnerable to an attacker bypassing authentication and gaining administrator privileges.	2024-06-27	not yet calculated
marKoni--Markoni-D (Compact) FM Transmitters	TELSAT marKoni FM Transmitters are vulnerable to users gaining unauthorized access to sensitive information or performing actions beyond their designated permissions.	2024-06-27	not yet calculated
mintplex-labs--mintplex-labs/anything-llm	A vulnerability in mintplex-labs/anything-llm allows for a Denial of Service (DoS) condition due to uncontrolled resource consumption. Specifically, the issue arises from the application's failure to limit the size of usernames, enabling attackers to create users with excessively bulky texts in the username field. This exploit results in the user management panel becoming unresponsive, preventing administrators from performing critical user management actions such as editing, suspending, or deleting users. The impact of this vulnerability includes administrative paralysis, compromised security, and operational disruption, as it allows malicious users to perpetuate their presence within the system indefinitely, undermines the system's security posture, and degrades overall system performance.	2024-06-25	not yet calculated
mudler--mudler/localai	A command injection vulnerability exists in the mudler/localai version 2.14.0. The vulnerability arises from the application's handling of the backend parameter in the configuration file, which is used in the name of the initialized process. An attacker can exploit this vulnerability by manipulating the path of the vulnerable binary file specified in the backend parameter, allowing the execution of arbitrary code on the system. This issue is due to improper neutralization of special elements used in an OS command, leading to potential full control over the affected system.	2024-06-26	not yet calculated
n/a--n/a	In the Linux kernel before 4.8, usb_parse_endpoint in drivers/usb/core/config.c does not validate the wMaxPacketSize field of an endpoint descriptor. NOTE: This vulnerability only affects products that are no longer supported by the supplier.	2024-06-27	not yet calculated
n/a--n/a	parseWildcardRules in Gin-Gonic CORS middleware before 1.6.0 mishandles a wildcard at the end of an origin string, e.g., https://example.community/* is allowed when the intention is that only https://example.com/* should be allowed, and http://localhost.example.com/* is allowed when the intention is that only http://localhost/* should be allowed.	2024-06-29	not yet calculated
n/a--n/a	File upload vulnerability found in Softexpert Excellence Suite v.2.1 allows attackers to execute arbitrary code via a .php file upload to the form/efms_exec_html/file_upload_parser.php endpoint.	2024-06-26	not yet calculated
n/a--n/a	PHP Injection vulnerability in the module "M4 PDF Extensions" (m4pdf) up to version 3.3.2 from PrestaAddons for PrestaShop allows attackers to run arbitrary code via the M4PDF::saveTemplate() method.	2024-06-24	not yet calculated
n/a--n/a	In phpseclib before 1.0.22, 2.x before 2.0.46, and 3.x before 3.0.33, some characters in Subject Alternative Name fields in TLS certificates are incorrectly allowed to have a special meaning in regular expressions (such as a + wildcard), leading to name confusion in X.509 certificate host verification.	2024-06-27	not yet calculated
n/a--n/a	Geehy APM32F103CCT6, APM32F103RCT6, APM32F103RCT7, and APM32F103VCT6 devices have Incorrect Access Control.	2024-06-25	not yet calculated
n/a--n/a	Artery AT32F415CBT7 and AT32F421C8T7 devices have Incorrect Access Control.	2024-06-25	not yet calculated
n/a--n/a	GigaDevice GD32E103C8T6 devices have Incorrect Access Control.	2024-06-25	not yet calculated
n/a--n/a	An issue was discovered on HMS Anybus X-Gateway AB7832-F 3 devices. The gateway exposes an unidentified service on port 7412 on the network. All the network services of the gateway become unresponsive after sending 85 requests to this port. The content and length of the frame does not matter. The device needs to be restarted to resume operations.	2024-06-26	not yet calculated
n/a--n/a	An issue was discovered on HMS Anybus X-Gateway AB7832-F 3 devices. The gateway exposes a web interface on port 80. An unauthenticated GET request to a specific URL triggers the reboot of the Anybus gateway (or at least most of its modules). An attacker can use this feature to carry out a denial of service attack by continuously sending GET requests to that URL.	2024-06-26	not yet calculated
n/a--n/a	An issue was discovered on HMS Anybus X-Gateway AB7832-F firmware version 3. The HICP protocol allows unauthenticated changes to a device's network configurations.	2024-06-26	not yet calculated
n/a--n/a	Buffer Overflow vulnerability in DCMTK v.3.6.8 allows an attacker to execute arbitrary code via the EctEnhancedCT method component.	2024-06-28	not yet calculated
n/a--n/a	An issue in dc2niix before v.1.0.20240202 allows a local attacker to execute arbitrary code via the generated file name is not properly escaped and injected into a system call when certain types of compression are used.	2024-06-28	not yet calculated
n/a--n/a	Buffer overflow in the extract_openvpn_cr function in openvpn-cr.c in openvpn-auth-ldap (aka the Three Rings Auth-LDAP plugin for OpenVPN) 2.0.4 allows attackers with a valid LDAP username and who can control the challenge/response password field to pass a string with more than 14 colons into this field and cause a buffer overflow.	2024-06-27	not yet calculated
n/a--n/a	Stored Cross Site Scripting vulnerability in Emby Media Server Emby Media Server 4.8.3.0 allows a remote attacker to escalate privileges via the notifications.html component.	2024-06-25	not yet calculated
n/a--n/a	DESIGNA ABACUS v.18 and before allows an attacker to bypass the payment process via a crafted QR code.	2024-06-27	not yet calculated
n/a--n/a	Buffer Overflow vulnerability in ASUS router RT-AX88U with firmware versions v3.0.0.4.388_24198 allows a remote attacker to execute arbitrary code via the connection_state_machine due to improper length validation for the cookie field.	2024-06-24	not yet calculated
n/a--n/a	A cross-site scripting (XSS) vulnerability in the component XsltResultControllerHtml.jsp of Lumisxp v15.0.x to v16.1.x allows attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the lumPageID parameter.	2024-06-26	not yet calculated
n/a--n/a	A cross-site scripting (XSS) vulnerability in the component UrlAccessibilityEvaluation.jsp of Lumisxp v15.0.x to v16.1.x allows attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the contentHtml parameter.	2024-06-26	not yet calculated
n/a--n/a	A cross-site scripting (XSS) vulnerability in the component main.jsp of Lumisxp v15.0.x to v16.1.x allows attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the pageId parameter.	2024-06-26	not yet calculated
n/a--n/a	A hardcoded privileged ID within Lumisxp v15.0.x to v16.1.x allows attackers to bypass authentication and access internal pages and other sensitive information.	2024-06-26	not yet calculated
n/a--n/a	Axiros AXESS Auto Configuration Server (ACS) 4.x and 5.0.0 has Incorrect Access Control. An authorization bypass allows remote attackers to achieve unauthenticated remote code execution.	2024-06-24	not yet calculated
n/a--n/a	Virtual Programming Lab for Moodle up to v4.2.3 was discovered to contain a cross-site scripting (XSS) vulnerability via the component vplide.js.	2024-06-24	not yet calculated
n/a--n/a	An issue in VPL Jail System up to v4.0.2 allows attackers to execute a directory traversal via a crafted request to a public endpoint.	2024-06-24	not yet calculated
n/a--n/a	An issue was discovered in VirtoSoftware Virto Kanban Board Web Part before 5.3.5.1 for SharePoint 2019. There is /_layouts/15/Virto.KanbanTaskManager/api/KanbanData.ashx LinkTitle2 XSS.	2024-06-25	not yet calculated
n/a--n/a	Apache XML Security for C++ through 2.0.4 implements the XML Signature Syntax and Processing (XMLDsig) specification without protection against an SSRF payload in a KeyInfo element. NOTE: the supplier disputes this CVE Record on the grounds that they are implementing the specification "correctly" and are not "at fault."	2024-06-26	not yet calculated
n/a--n/a	The W3C XML Signature Syntax and Processing (XMLDsig) specification, starting with 1.0, was originally published with a "RetrievalMethod is a URI ... that may be used to obtain key and/or certificate information" statement and no accompanying information about SSRF risks, and this may have contributed to vulnerable implementations such as those discussed in CVE-2023-36661 and CVE-2024-21893. NOTE: this was mitigated in 1.1 and 2.0 via a directly referenced Best Practices document that calls on implementers to be wary of SSRF.	2024-06-26	not yet calculated
n/a--n/a	SQL injection vulnerability in the module "Complete for Create a Quote in Frontend + Backend Pro" (askforaquotemodul) <= 1.0.51 from Buy Addons for PrestaShop allows attackers to view sensitive information and cause other impacts via methods `AskforaquotemodulcustomernewquoteModuleFrontController::run()`, `AskforaquotemoduladdproductnewquoteModuleFrontController::run()`, `AskforaquotemodulCouponcodeModuleFrontController::run()`, `AskforaquotemodulgetshippingcostModuleFrontController::run()`, `AskforaquotemodulgetstateModuleFrontController::run().`	2024-06-24	not yet calculated
n/a--n/a	In the module "Axepta" (axepta) before 1.3.4 from Quadra Informatique for PrestaShop, a guest can download partial credit card information (expiry date) / postal address / email / etc. without restriction due to a lack of permissions control.	2024-06-24	not yet calculated
n/a--n/a	SQL Injection vulnerability in the module "Help Desk - Customer Support Management System" (helpdesk) up to version 2.4.0 from FME Modules for PrestaShop allows attackers to obtain sensitive information and cause other impacts via 'Tickets::getsearchedtickets()'	2024-06-24	not yet calculated
n/a--n/a	An issue in Daemon PTY Limited FarCry Core framework before 7.2.14 allows attackers to access sensitive information in the /facade directory.	2024-06-25	not yet calculated
n/a--n/a	An arbitrary file upload vulnerability in /fileupload/upload.cfm in Daemon PTY Limited FarCry Core framework before 7.2.14 allows attackers to execute arbitrary code via uploading a crafted .cfm file.	2024-06-25	not yet calculated
n/a--n/a	MAP-OS v4.45.0 and earlier was discovered to contain a cross-site scripting (XSS) vulnerability.	2024-06-26	not yet calculated
n/a--n/a	Directory Traversal vulnerability in Kalkitech ASE ASE61850 IEDSmart upto and including version 2.3.5 allows attackers to read/write arbitrary files via the IEC61850 File Transfer protocol.	2024-06-27	not yet calculated
n/a--n/a	Netwrix CoSoSys Endpoint Protector through 5.9.3 and CoSoSys Unify through 7.0.6 contain a remote code execution vulnerability in the logging component of the Endpoint Protector and Unify server application which allows an unauthenticated remote attacker to send a malicious request, resulting in the ability to execute system commands with root privileges.	2024-06-27	not yet calculated
n/a--n/a	Netwrix CoSoSys Endpoint Protector through 5.9.3 and CoSoSys Unify through 7.0.6 contain a remote code execution vulnerability in the shadowing component of the Endpoint Protector and Unify agent which allows an attacker with administrative access to the Endpoint Protector or Unify server to overwrite sensitive configuration and subsequently execute system commands with SYSTEM/root privileges on a chosen client endpoint.	2024-06-27	not yet calculated
n/a--n/a	Netwrix CoSoSys Endpoint Protector through 5.9.3 and CoSoSys Unify through 7.0.6 contain a remote code execution vulnerability in the Endpoint Protector and Unify agent in the way that the EasyLock dependency is acquired from the server. An attacker with administrative access to the Endpoint Protector or Unify server can cause a client to acquire and execute a malicious file resulting in remote code execution.	2024-06-27	not yet calculated
n/a--n/a	Netwrix CoSoSys Endpoint Protector through 5.9.3 and CoSoSys Unify through 7.0.6 contain a remote code execution vulnerability in the application configuration component of the Endpoint Protector and Unify agent which allows a remote, unauthenticated attacker to manipulate the configuration of either their own or another client endpoint resulting in the bypass of certain configuration options. Manipulation of the application configuration can result in local policy bypass and in some scenarios remote code execution.	2024-06-27	not yet calculated
n/a--n/a	SQL Injection vulnerability in the module "Isotope" (pk_isotope) <=1.7.3 from Promokit.eu for PrestaShop allows attackers to obtain sensitive information and cause other impacts via `pk_isotope::saveData` and `pk_isotope::removeData` methods.	2024-06-24	not yet calculated
n/a--n/a	In the module "Theme settings" (pk_themesettings) <= 1.8.8 from Promokit.eu for PrestaShop, a guest can download all email collected while SHOP is in maintenance mode. Due to a lack of permissions control, a guest can access the txt file which collect email when maintenance is enable which can lead to leak of personal information.	2024-06-24	not yet calculated
n/a--n/a	SQL injection vulnerability in the module "Products Alert" (productsalert) before 1.7.4 from Smart Modules for PrestaShop allows attackers to obtain sensitive information and cause other impacts via the ProductsAlertAjaxProcessModuleFrontController::initContent method.	2024-06-24	not yet calculated
n/a--n/a	D-Link DIR-1950 up to v1.11B03 does not validate SSL certificates when requesting the latest firmware version and downloading URL. This can allow attackers to downgrade the firmware version or change the downloading URL via a man-in-the-middle attack.	2024-06-27	not yet calculated
n/a--n/a	MAP-OS 4.45.0 and earlier is vulnerable to Cross-Site Scripting (XSS). This vulnerability allows malicious users to insert a malicious payload into the "Client Name" input. When a service order from this client is created, the malicious payload is displayed on the administrator and employee dashboards, resulting in unauthorized script execution whenever the dashboard is loaded.	2024-06-25	not yet calculated
n/a--n/a	Incorrect access control in Teldat M1 v11.00.05.50.01 allows attackers to obtain sensitive information via a crafted query string.	2024-06-26	not yet calculated
n/a--n/a	In MIT Kerberos 5 (aka krb5) before 1.21.3, an attacker can modify the plaintext Extra Count field of a confidential GSS krb5 wrap token, causing the unwrapped token to appear truncated to the application.	2024-06-28	not yet calculated
n/a--n/a	In MIT Kerberos 5 (aka krb5) before 1.21.3, an attacker can cause invalid memory reads during GSS message token handling by sending message tokens with invalid length fields.	2024-06-28	not yet calculated
n/a--n/a	Buffer Overflow vulnerability in SAS Broker 9.2 build 1495 allows attackers to cause denial of service or obtain sensitive information via crafted payload to the '_debug' parameter.	2024-06-26	not yet calculated
n/a--n/a	Cross Site Scripting vulnerability in Hangzhou Meisoft Information Technology Co., Ltd. Finesoft v.8.0 and before allows a remote attacker to execute arbitrary code via a crafted script.	2024-06-24	not yet calculated
n/a--n/a	An issue the background management system of Shanxi Internet Chuangxiang Technology Co., Ltd v1.0.1 allows a remote attacker to cause a denial of service via the index.html component.	2024-06-24	not yet calculated
n/a--n/a	An issue in OpenEMR 7.0.2 allows a remote attacker to escalate privileges viaa crafted POST request using the noteid parameter.	2024-06-26	not yet calculated
n/a--n/a	OpenPLC 3 through 9cd8f1b allows XSS via an SVG document as a profile picture.	2024-06-28	not yet calculated
n/a--n/a	Insecure Access Control in Safe Exam Browser (SEB) = 3.5.0 on Windows. The vulnerability allows an attacker to share clipboard data between the SEB kiosk mode and the underlying system, compromising exam integrity. By exploiting this flaw, an attacker can bypass exam controls and gain an unfair advantage during exams.	2024-06-25	not yet calculated
n/a--n/a	DataGear v5.0.0 and earlier was discovered to contain a SpEL (Spring Expression Language) expression injection vulnerability via the Data Viewing interface.	2024-06-24	not yet calculated
n/a--n/a	A nil pointer dereference in PingCAP TiDB v8.2.0-alpha-216-gfe5858b allows attackers to crash the application via expression.inferCollation.	2024-06-25	not yet calculated
n/a--n/a	An issue in EnvisionWare Computer Access & Reservation Control SelfCheck v1.0 (fixed in OneStop 3.2.0.27184 Hotfix May 2024) allows unauthenticated attackers on the same network to perform a directory traversal.	2024-06-24	not yet calculated
n/a--n/a	Craft CMS up to v3.7.31 was discovered to contain a SQL injection vulnerability via the GraphQL API endpoint.	2024-06-25	not yet calculated
n/a--n/a	An issue in Nepstech Wifi Router xpon (terminal) NTPL-Xpon1GFEVN, hardware verstion 1.0 firmware 2.0.1 allows a remote attacker to execute arbitrary code via the router's Telnet port 2345 without requiring authentication credentials.	2024-06-25	not yet calculated
n/a--n/a	An issue in Wavlink WN551K1 allows a remote attacker to obtain sensitive information via the ExportAllSettings.sh component.	2024-06-24	not yet calculated
n/a--n/a	WAVLINK WN551K1 found a command injection vulnerability through the IP parameter of /cgi-bin/touchlist_sync.cgi.	2024-06-24	not yet calculated
n/a--n/a	WAVLINK WN551K1'live_mfg.shtml enables attackers to obtain sensitive router information.	2024-06-24	not yet calculated
n/a--n/a	WAVLINK WN551K1 found a command injection vulnerability through the start_hour parameter of /cgi-bin/nightled.cgi.	2024-06-24	not yet calculated
n/a--n/a	WAVLINK WN551K1'live_check.shtml enables attackers to obtain sensitive router information.	2024-06-24	not yet calculated
n/a--n/a	H3C Magic R230 V100R002 was discovered to contain a hardcoded password vulnerability in /etc/shadow, which allows attackers to log in as root.	2024-06-24	not yet calculated
n/a--n/a	H3C Magic R230 V100R002's udpserver opens port 9034, allowing attackers to execute arbitrary commands.	2024-06-24	not yet calculated
n/a--n/a	Heap Buffer Overflow vulnerability in Libde265 v1.0.15 allows attackers to crash the application via crafted payload to display444as420 function at sdl.cc	2024-06-26	not yet calculated
n/a--n/a	Heap Buffer Overflow vulnerability in Libde265 v1.0.15 allows attackers to crash the application via crafted payload to __interceptor_memcpy function.	2024-06-26	not yet calculated
n/a--n/a	A buffer overflow in PX4-Autopilot v1.12.3 allows attackers to cause a Denial of Service (DoS) via a crafted MavLink message.	2024-06-25	not yet calculated
n/a--n/a	PX4-Autopilot v1.14.3 was discovered to contain a buffer overflow via the topic_name parameter at /logger/logged_topics.cpp.	2024-06-25	not yet calculated
n/a--n/a	Heap Buffer Overflow vulnerability in DumpTS v0.1.0-nightly allows attackers to cause a denial of service via the function PushTSBuf() at /src/PayloadBuf.cpp.	2024-06-27	not yet calculated
n/a--n/a	A NULL Pointer Dereference discovered in DumpTS v0.1.0-nightly allows attackers to cause a denial of service via the function DumpOneStream() at /src/DumpStream.cpp.	2024-06-27	not yet calculated
n/a--n/a	A NULL Pointer Dereference vulnerability in DumpTS v0.1.0-nightly allows attackers to cause a denial of service via the function VerifyCommandLine() at /src/DumpTS.cpp.	2024-06-27	not yet calculated
n/a--n/a	Heap Buffer Overflow vulnerability in zziplib v0.13.77 allows attackers to cause a denial of service via the __zzip_parse_root_directory() function at /zzip/zip.c.	2024-06-27	not yet calculated
n/a--n/a	A Stack Buffer Overflow vulnerability in zziplibv 0.13.77 allows attackers to cause a denial of service via the __zzip_fetch_disk_trailer() function at /zzip/zip.c.	2024-06-27	not yet calculated
n/a--n/a	idccms v1.35 was discovered to contain a Cross-Site Request Forgery (CSRF) via the component /admin/info_deal.php?mudi=del&dataType=news&dataTypeCN.	2024-06-27	not yet calculated
n/a--n/a	idccms v1.35 was discovered to contain a Cross-Site Request Forgery (CSRF) via the component /admin/keyWord_deal.php?mudi=del&dataType=word&dataTypeCN.	2024-06-27	not yet calculated
n/a--n/a	idccms v1.35 was discovered to contain a Cross-Site Request Forgery (CSRF) via the component /admin/ipRecord_deal.php?mudi=add.	2024-06-27	not yet calculated
n/a--n/a	idccms v1.35 was discovered to contain a Cross-Site Request Forgery (CSRF) via the component /admin/keyWord_deal.php?mudi=add.	2024-06-27	not yet calculated
n/a--n/a	idccms v1.35 was discovered to contain a Cross-Site Request Forgery (CSRF) via the component /admin/ipRecord_deal.php?mudi=del&dataType=&dataID=1.	2024-06-27	not yet calculated
n/a--n/a	idccms v1.35 was discovered to contain a Cross-Site Request Forgery (CSRF) via the component /admin/userSys_deal.php?mudi=infoSet.	2024-06-27	not yet calculated
n/a--n/a	lua-shmem v1.0-1 was discovered to contain a buffer overflow via the shmem_write function.	2024-06-27	not yet calculated
n/a--n/a	luci-app-lucky v2.8.3 was discovered to contain hardcoded credentials.	2024-06-27	not yet calculated
n/a--n/a	luci-app-sms-tool v1.9-6 was discovered to contain a command injection vulnerability via the score parameter.	2024-06-27	not yet calculated
n/a--n/a	Cross Site Scripting (XSS) vulnerability in skycaiji 2.8 allows attackers to run arbitrary code via /admin/tool/preview.	2024-06-26	not yet calculated
n/a--n/a	A cross-site scripting (XSS) vulnerability in skycaiji v2.8 allows attackers to execute arbitrary web scripts or HTML via a crafted payload using eval(String.fromCharCode()).	2024-06-26	not yet calculated
n/a--n/a	An issue discovered in skycaiji 2.8 allows attackers to run arbitrary code via crafted POST request to /index.php?s=/admin/develop/editor_save.	2024-06-26	not yet calculated
n/a--n/a	Click Studios Passwordstate Core before 9.8 build 9858 allows Authentication Bypass.	2024-06-24	not yet calculated
n/a--n/a	In the Console in Soffid IAM before 3.5.39, necessary checks were not applied to some Java objects. A malicious agent could possibly execute arbitrary code in the Sync Server and compromise security.	2024-06-27	not yet calculated
n/a--n/a	Soft Circle French-Bread Melty Blood: Actress Again: Current Code through 1.07 Rev. 1.4.0 allows a remote attacker to execute arbitrary code on a client's machine via a crafted packet on TCP port 46318.	2024-06-28	not yet calculated
n/a--n/a	NLTK through 3.8.1 allows remote code execution if untrusted packages have pickled Python code, and the integrated data package download functionality is used. This affects, for example, averaged_perceptron_tagger and punkt.	2024-06-27	not yet calculated
n/a--n/a	R74n Sandboxels 1.9 through 1.9.5 allows XSS via a message in a modified saved-game file. This was fixed in a hotfix to 1.9.5 on 2024-06-29.	2024-06-28	not yet calculated
n/a--n/a	Factorio before 1.1.101 allows a crafted server to execute arbitrary code on clients via a custom map that leverages the ability of certain Lua base module functions to execute bytecode and generate fake objects.	2024-06-29	not yet calculated
n/a--n/a	NewPass before 1.2.0 stores passwords (rather than password hashes) directly, which makes it easier to obtain unauthorized access to sensitive information. NOTE: in each case, data at rest is encrypted, but is decrypted within process memory during use.	2024-06-29	not yet calculated
n/a--n/a	Internet2 Grouper before 5.6 allows authentication bypass when LDAP authentication is used in certain ways. This is related to internet2.middleware.grouper.ws.security.WsGrouperLdapAuthentication and the use of the UyY29r password for the M3vwHr account. This also affects "Grouper for Web Services" before 4.13.1.	2024-06-29	not yet calculated
Nikola Vasilijevski--AdmirorFrames	Full Path Disclosure vulnerability in AdmirorFrames Joomla! extension in afHelper.php script allows an unauthorised attacker to retrieve location of web root folder. This issue affects AdmirorFrames: before 5.0.	2024-06-28	not yet calculated
Nikola Vasilijevski--AdmirorFrames	Server Side Request Forgery (SSRF) vulnerability in AdmirorFrames Joomla! extension in afGdStream.php script allows to access local files or server pages available only from localhost. This issue affects AdmirorFrames: before 5.0.	2024-06-28	not yet calculated
Nikola Vasilijevski--AdmirorFrames	Script afGdStream.php in AdmirorFrames Joomla! extension doesn't specify a content type and as a result default (text/html) is used. An attacker may embed HTML tags directly in image data which is rendered by a webpage as HTML. This issue affects AdmirorFrames: before 5.0.	2024-06-28	not yet calculated
OpenSSL--OpenSSL	Issue summary: Calling the OpenSSL API function SSL_select_next_proto with an empty supported client protocols buffer may cause a crash or memory contents to be sent to the peer. Impact summary: A buffer overread can have a range of potential consequences such as unexpected application beahviour or a crash. In particular this issue could result in up to 255 bytes of arbitrary private data from memory being sent to the peer leading to a loss of confidentiality. However, only applications that directly call the SSL_select_next_proto function with a 0 length list of supported client protocols are affected by this issue. This would normally never be a valid scenario and is typically not under attacker control but may occur by accident in the case of a configuration or programming error in the calling application. The OpenSSL API function SSL_select_next_proto is typically used by TLS applications that support ALPN (Application Layer Protocol Negotiation) or NPN (Next Protocol Negotiation). NPN is older, was never standardised and is deprecated in favour of ALPN. We believe that ALPN is significantly more widely deployed than NPN. The SSL_select_next_proto function accepts a list of protocols from the server and a list of protocols from the client and returns the first protocol that appears in the server list that also appears in the client list. In the case of no overlap between the two lists it returns the first item in the client list. In either case it will signal whether an overlap between the two lists was found. In the case where SSL_select_next_proto is called with a zero length client list it fails to notice this condition and returns the memory immediately following the client list pointer (and reports that there was no overlap in the lists). This function is typically called from a server side application callback for ALPN or a client side application callback for NPN. In the case of ALPN the list of protocols supplied by the client is guaranteed by libssl to never be zero in length. The list of server protocols comes from the application and should never normally be expected to be of zero length. In this case if the SSL_select_next_proto function has been called as expected (with the list supplied by the client passed in the client/client_len parameters), then the application will not be vulnerable to this issue. If the application has accidentally been configured with a zero length server list, and has accidentally passed that zero length server list in the client/client_len parameters, and has additionally failed to correctly handle a "no overlap" response (which would normally result in a handshake failure in ALPN) then it will be vulnerable to this problem. In the case of NPN, the protocol permits the client to opportunistically select a protocol when there is no overlap. OpenSSL returns the first client protocol in the no overlap case in support of this. The list of client protocols comes from the application and should never normally be expected to be of zero length. However if the SSL_select_next_proto function is accidentally called with a client_len of 0 then an invalid memory pointer will be returned instead. If the application uses this output as the opportunistic protocol then the loss of confidentiality will occur. This issue has been assessed as Low severity because applications are most likely to be vulnerable if they are using NPN instead of ALPN - but NPN is not widely used. It also requires an application configuration or programming error. Finally, this issue would not typically be under attacker control making active exploitation unlikely. The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue. Due to the low severity of this issue we are not issuing new releases of OpenSSL at this time. The fix will be included in the next releases when they become available.	2024-06-27	not yet calculated
parisneo--parisneo/lollms-webui	A Path Traversal and Remote File Inclusion (RFI) vulnerability exists in the parisneo/lollms-webui application, affecting versions v9.7 to the latest. The vulnerability arises from insufficient input validation in the `/apply_settings` function, allowing an attacker to manipulate the `discussion_db_name` parameter to traverse the file system and include arbitrary files. This issue is compounded by the bypass of input filtering in the `install_binding`, `reinstall_binding`, and `unInstall_binding` endpoints, despite the presence of a `sanitize_path_from_endpoint(data.name)` filter. Successful exploitation enables an attacker to upload and execute malicious code on the victim's system, leading to Remote Code Execution (RCE).	2024-06-25	not yet calculated
parisneo--parisneo/lollms-webui	A Cross-Site Request Forgery (CSRF) vulnerability exists in the 'Servers Configurations' function of the parisneo/lollms-webui, versions 9.6 to the latest. The affected functions include Elastic search Service (under construction), XTTS service, Petals service, vLLM service, and Motion Ctrl service, which lack CSRF protection. This vulnerability allows attackers to deceive users into unwittingly installing the XTTS service among other packages by submitting a malicious installation request. Successful exploitation results in attackers tricking users into performing actions without their consent.	2024-06-24	not yet calculated
parisneo--parisneo/lollms-webui	A Cross-site Scripting (XSS) vulnerability exists in the chat functionality of parisneo/lollms-webui in the latest version. This vulnerability allows an attacker to inject malicious scripts via chat messages, which are then executed in the context of the user's browser.	2024-06-27	not yet calculated
parisneo--parisneo/lollms-webui	An absolute path traversal vulnerability exists in parisneo/lollms-webui v9.6, specifically in the `open_file` endpoint of `lollms_advanced.py`. The `sanitize_path` function with `allow_absolute_path=True` allows an attacker to access arbitrary files and directories on a Windows system. This vulnerability can be exploited to read any file and list arbitrary directories on the affected system.	2024-06-27	not yet calculated
parisneo--parisneo/lollms	A remote code execution vulnerability exists in the create_conda_env function of the parisneo/lollms repository, version 5.9.0. The vulnerability arises from the use of shell=True in the subprocess.Popen function, which allows an attacker to inject arbitrary commands by manipulating the env_name and python_version parameters. This issue could lead to a serious security breach as demonstrated by the ability to execute the 'whoami' command among potentially other harmful commands.	2024-06-24	not yet calculated
parisneo--parisneo/lollms	A Cross-Site Request Forgery (CSRF) vulnerability exists in the XTTS server of parisneo/lollms version 9.6 due to a lax CORS policy. The vulnerability allows attackers to perform unauthorized actions by tricking a user into visiting a malicious webpage, which can then trigger arbitrary LoLLMS-XTTS API requests. This issue can lead to the reading and writing of audio files and, when combined with other vulnerabilities, could allow for the reading of arbitrary files on the system and writing files outside the permitted audio file location.	2024-06-24	not yet calculated
parisneo--parisneo/lollms	A path traversal vulnerability in the `/set_personality_config` endpoint of parisneo/lollms version 9.4.0 allows an attacker to overwrite the `configs/config.yaml` file. This can lead to remote code execution by changing server configuration properties such as `force_accept_remote_access` and `turn_on_code_validation`.	2024-06-27	not yet calculated
parisneo--parisneo/lollms	A path traversal vulnerability exists in the XTTS server included in the lollms package, version v9.6. This vulnerability arises from the ability to perform an unauthenticated root folder settings change. Although the read file endpoint is protected against path traversals, this protection can be bypassed by changing the root folder to '/'. This allows attackers to read arbitrary files on the system. Additionally, the output folders can be changed to write arbitrary audio files to any location on the system.	2024-06-27	not yet calculated
parisneo--parisneo/lollms	A path traversal vulnerability exists in the XTTS server of the parisneo/lollms package version v9.6. This vulnerability allows an attacker to write audio files to arbitrary locations on the system and enumerate file paths. The issue arises from improper validation of user-provided file paths in the `tts_to_file` endpoint.	2024-06-27	not yet calculated
Perforce--Helix ALM	In Helix ALM versions prior to 2024.2.0, a local command injection was identified. Reported by Bryan Riggins.	2024-06-28	not yet calculated
Phloc--Webscopes	An information disclosure vulnerability in Phloc Webscopes 7.0.0 allows local attackers with access to the log files to view logged HTTP requests that contain user passwords or other sensitive information.	2024-06-25	not yet calculated
Python Software Foundation--CPython	CPython 3.9 and earlier doesn't disallow configuring an empty list ("[]") for SSLContext.set_npn_protocols() which is an invalid value for the underlying OpenSSL API. This results in a buffer over-read when NPN is used (see CVE-2024-5535 for OpenSSL). This vulnerability is of low severity due to NPN being not widely used and specifying an empty list likely being uncommon in-practice (typically a protocol name would be configured).	2024-06-27	not yet calculated
Rockwell Automation--ThinManager ThinServer	Due to an improper input validation, an unauthenticated threat actor can send a malicious message to invoke a local or remote executable and cause a remote code execution condition on the Rockwell Automation ThinManagerÂ® ThinServerâ„¢.	2024-06-25	not yet calculated
Rockwell Automation--ThinManager ThinServer	Due to an improper input validation, an unauthenticated threat actor can send a malicious message to invoke SQL injection into the program and cause a remote code execution condition on the Rockwell Automation ThinManagerÂ® ThinServerâ„¢.	2024-06-25	not yet calculated
Rockwell Automation--ThinManager ThinServer	Due to an improper input validation, an unauthenticated threat actor can send a malicious message to a monitor thread within Rockwell Automation ThinServerâ„¢ and cause a denial-of-service condition on the affected device.	2024-06-25	not yet calculated
SDG Technologies--PnPSCADA	SDG Technologies PnPSCADA allows a remote attacker to attach various entities without requiring system authentication. This breach could potentially lead to unauthorized control, data manipulation, and access to sensitive information within the SCADA system.	2024-06-27	not yet calculated
SoftMaker Software GmbH--Office	An issue was discovered in SoftMaker Office 2024 / NX before revision 1214 and SoftMaker FreeOffice 2014 before revision 1215. FreeOffice 2021 is also affected, but won't be fixed. The SoftMaker Office and FreeOffice MSI installer files were found to produce a visible conhost.exe window running as the SYSTEM user when using the repair function of msiexec.exe. This allows a local, low-privileged attacker to use a chain of actions, to open a fully functional cmd.exe with the privileges of the SYSTEM user.	2024-06-27	not yet calculated
stangirard--stangirard/quivr	stangirard/quivr version 0.0.236 contains a Server-Side Request Forgery (SSRF) vulnerability. The application does not provide sufficient controls when crawling a website, allowing an attacker to access applications on the local network. This vulnerability could allow a malicious user to gain access to internal servers, the AWS metadata endpoint, and capture Supabase data.	2024-06-27	not yet calculated
stitionai--stitionai/devika	External Control of File Name or Path in GitHub repository stitionai/devika prior to -.	2024-06-27	not yet calculated
stitionai--stitionai/devika	Relative Path Traversal in GitHub repository stitionai/devika prior to -.	2024-06-27	not yet calculated
stitionai--stitionai/devika	Path Traversal in GitHub repository stitionai/devika prior to -.	2024-06-27	not yet calculated
stitionai--stitionai/devika	Cross-Site Request Forgery (CSRF) in stitionai/devika	2024-06-28	not yet calculated
stitionai--stitionai/devika	Missing Authorization in stitionai/devika	2024-06-27	not yet calculated
The Document Foundation--LibreOffice	Improper Certificate Validation vulnerability in LibreOffice "LibreOfficeKit" mode disables TLS certification verification LibreOfficeKit can be used for accessing LibreOffice functionality through C/C++. Typically this is used by third party components to reuse LibreOffice as a library to convert, view or otherwise interact with documents. LibreOffice internally makes use of "curl" to fetch remote resources such as images hosted on webservers. In affected versions of LibreOffice, when used in LibreOfficeKit mode only, then curl's TLS certification verification was disabled (CURLOPT_SSL_VERIFYPEER of false) In the fixed versions curl operates in LibreOfficeKit mode the same as in standard mode with CURLOPT_SSL_VERIFYPEER of true. This issue affects LibreOffice before version 24.2.4.	2024-06-25	not yet calculated
Unknown--Animated AL List	The Animated AL List WordPress plugin through 1.0.6 does not sanitise and escape a parameter before outputting it back in the page, leading to a Reflected Cross-Site Scripting which could be used against high privilege users such as admin	2024-06-28	not yet calculated
Unknown--Bookster	The Bookster WordPress plugin through 1.1.0 allows adding sensitive parameters when validating appointments allowing attackers to manipulate the data sent when booking an appointment (the request body) to change its status from pending to approved.	2024-06-26	not yet calculated
Unknown--Easy Table of Contents	The Easy Table of Contents WordPress plugin before 2.0.66 does not sanitise and escape some of its settings, which could allow high privilege users such as editors to perform Cross-Site Scripting attacks even when unfiltered_html is disallowed	2024-06-26	not yet calculated
Unknown--Frontend Checklist	The Frontend Checklist WordPress plugin through 2.3.2 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup)	2024-06-26	not yet calculated
Unknown--Frontend Checklist	The Frontend Checklist WordPress plugin through 2.3.2 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup)	2024-06-26	not yet calculated
Unknown--Logo Manager For Enamad	The Logo Manager For Enamad WordPress plugin through 0.7.0 does not have CSRF check in some places, and is missing sanitisation as well as escaping, which could allow attackers to make logged in admin add Stored XSS payloads via a CSRF attack	2024-06-25	not yet calculated
Unknown--Mime Types Extended	The Mime Types Extended WordPress plugin through 0.11 does not sanitise uploaded SVG files, which could allow users with a role as low as Author to upload a malicious SVG containing XSS payloads.	2024-06-25	not yet calculated
Unknown--Muslim Prayer Time BD	The Muslim Prayer Time BD WordPress plugin through 2.4 does not have CSRF check in place when reseting its settings, which could allow attackers to make a logged in admin reset them via a CSRF attack	2024-06-26	not yet calculated
Unknown--Pagerank tools	The Pagerank tools WordPress plugin through 1.1.5 does not sanitise and escape a parameter before outputting it back in the page, leading to a Reflected Cross-Site Scripting which could be used against high privilege users such as admin	2024-06-28	not yet calculated
Unknown--SEOPress	The SEOPress WordPress plugin before 7.8 does not sanitise and escape some of its Post settings, which could allow high privilege users such as contributor to perform Stored Cross-Site Scripting attacks.	2024-06-24	not yet calculated
Unknown--SEOPress	The SEOPress WordPress plugin before 7.8 does not validate and escape one of its Post settings, which could allow contributor and above role to perform Open redirect attacks against any user viewing a malicious post	2024-06-24	not yet calculated
Unknown--Simple AL Slider	The Simple AL Slider WordPress plugin through 1.2.10 does not sanitise and escape a parameter before outputting it back in the page, leading to a Reflected Cross-Site Scripting which could be used against high privilege users such as admin	2024-06-28	not yet calculated
Unknown--Simple Photoswipe	The Simple Photoswipe WordPress plugin through 0.1 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup).	2024-06-26	not yet calculated
Unknown--Simple Photoswipe	The Simple Photoswipe WordPress plugin through 0.1 does not have authorisation check when updating its settings, which could allow any authenticated users, such as subscriber to update them	2024-06-28	not yet calculated
Unknown--Spotify Play Button	The Spotify Play Button WordPress plugin through 1.0 does not validate and escape some of its shortcode attributes before outputting them back in a page/post where the shortcode is embed, which could allow users with the contributor role and above to perform Stored Cross-Site Scripting attacks.	2024-06-26	not yet calculated
Unknown--Video Widget	The Video Widget WordPress plugin through 1.2.3 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup)	2024-06-26	not yet calculated
Unknown--WebP & SVG Support	The WebP & SVG Support WordPress plugin through 1.4.0 does not sanitise uploaded SVG files, which could allow users with a role as low as Author to upload a malicious SVG containing XSS payloads.	2024-06-26	not yet calculated
Unknown--Widget4Call	The Widget4Call WordPress plugin through 1.0.7 does not sanitise and escape a parameter before outputting it back in the page, leading to a Reflected Cross-Site Scripting which could be used against high privilege users such as admin	2024-06-28	not yet calculated
vanna-ai--vanna-ai/vanna	In the latest version of vanna-ai/vanna, the `vanna.ask` function is vulnerable to remote code execution due to prompt injection. The root cause is the lack of a sandbox when executing LLM-generated code, allowing an attacker to manipulate the code executed by the `exec` function in `src/vanna/base/base.py`. This vulnerability can be exploited by an attacker to achieve remote code execution on the app backend server, potentially gaining full control of the server.	2024-06-27	not yet calculated
vanna-ai--vanna-ai/vanna	Vanna v0.3.4 is vulnerable to SQL injection in its DuckDB integration exposed to its Flask Web APIs. Attackers can inject malicious SQL training data and generate corresponding queries to write arbitrary files on the victim's file system, such as backdoor.php with contents `<?php system($_GET[0]); ?>`. This can lead to command execution or the creation of backdoors.	2024-06-28	not yet calculated
Western Digital--My Cloud Home web app	A Cross-Site Scripting (XSS) vulnerability on the My Cloud, My Cloud Home, SanDisk ibi, and WD Cloud web apps was found which could allow an attacker to redirect the user to a crafted domain and reset their credentials, or to execute arbitrary client-side code in the user's browser session to carry out malicious activities.The web apps for these devices have been automatically updated to resolve this vulnerability and improve the security of your devices and data.	2024-06-24	not yet calculated
zenml-io--zenml-io/zenml	A denial of service (DoS) vulnerability exists in zenml-io/zenml version 0.56.3 due to improper handling of line feed (`\n`) characters in component names. When a low-privileged user adds a component through the API endpoint `api/v1/workspaces/default/components` with a name containing a `\n` character, it leads to uncontrolled resource consumption. This vulnerability results in the inability of users to add new components in certain categories (e.g., 'Image Builder') and to register new stacks through the UI, thereby degrading the user experience and potentially rendering the ZenML Dashboard unusable. The issue does not affect component addition through the Web UI, as `\n` characters are properly escaped in that context. The vulnerability was tested on ZenML running in Docker, and it was observed in both Firefox and Chrome browsers.	2024-06-24	not yet calculated

Please share your thoughts

We recently updated our anonymous product survey ; we’d welcome your feedback.

IMAGES

How to Set Static IP Address on Ubuntu 22.04
Assign Static Ip Ubuntu How To Configure On 18 04 Network Address In
How To Assign Static Ip Address On Ubuntu 20 04 Lts
Linux Basics: Configuring A Static IP In Ubuntu
How To Configure Static IP Address On Ubuntu 22.04 » TechnologyRSS
Set a Static IP on Ubuntu

VIDEO

แก้ Static IP ubuntu server
Assign static IP address to a VM in Google Cloud
How to assign Static IP Address in Ubuntu 17.04
How to Set Static IP in Ubuntu Server 20.04 & Create New User |Hindi|
Howto Setting IP in UBUNTU 18
Setting a Netplan in Ubuntu Server 22.04

COMMENTS

How to Configure Static IP Address on Ubuntu 18.04
In the Activities screen, search for "network" and click on the Network icon. This will open the GNOME Network configuration settings. Click on the cog icon. In "IPV4" Method" section, select "Manual" and enter your static IP address, Netmask and Gateway. Once done, click on the "Apply" button.
How to configure a static IP address in Ubuntu Server 18.04
The new method. Open up a terminal window on your Ubuntu 18.04 server (or log in via secure shell). Change into the /etc/netplan directory with the command cd /etc/netplan. Issue the command ls ...
Set static IP in Ubuntu using Command Line
Below is the output of running the ip command on my computer: $ ip route default via 192.168.122.1 dev enp1s0 proto static 192.168.122./24 dev enp1s0 proto kernel scope link src 192.168.122.69. On the line that starts with "default via", I can see that my gateway address '192.168.122.1' Make a note of your gateway address. Step 4: Set static ...
Netplan static IP on Ubuntu configuration
Netplan network configuration had been first introduced starting from Ubuntu 18.04, hence Netplan is available to all new Ubuntu from this version and higher. Ubuntu uses Netplan to configure static IP addesses, which utilizes a YAML syntax. This makes it easy to configure a static IP and change minute details in the future if necessary.
Ubuntu Static IP configuration
Open network settings Ubuntu Desktop. Click on the settings icon to start IP address configuration. Start network configuration to set static IP address. Select IPv4 tab. Static IPv4 IP address Ubuntu Desktop. Select manual and enter your desired IP address, netmask, gateway and DNS settings. Once ready click Apply button.
How to Assign Static IP Address on Ubuntu Linux
Method 2: Switch to static IP address in Ubuntu graphically. If you are on desktop, using the graphical method is easier and faster. Go to the settings and look for network settings. Click the gear symbol adjacent to your network connection. Next, you should go to the IPv4 tab.
How to configure static IP address on Ubuntu 18.04
Some explains: ens33 - interface name dhcp4, dhcp6 - this sections are respective to the dhcp-properties for 4th and 6th IP-protocol versions. addresses - static addresses "pointed" to the interface. (in CIDR format) gateway4 - IPv4 address for default hope. nameservers - IP addresses for servers which resolves DNS-queries.. NOTE: You must use spaces only, no tabs.
How to Set a Static IP Address in Ubuntu
Set a Static IP in Ubuntu with the GUI. Click the icons at the far-right end of the system bar to show the system menu, then click on the "Wired Connected" menu option. If you're using a wireless connection, instead click the name of your Wi-Fi network. The available connections are displayed.
How to Configure static IP address in Ubuntu Server 18.04 LTS
Next, we start the interface configuration: ethernets: enp0s3: Here, enp0s3 is the name of the interface, you can run ip link show command to list network interfaces on your Ubuntu server. Next, we set the static IP to 192.168.1.100 with the netmask of 24: addresses: - 192.168.1.100/24.
Setting a Static IP in Ubuntu
Static IP applied How to Set a Static IP Using the GUI. It is very easy to set a static IP through the Ubuntu GUI/ Desktop. Here are the steps: Search for settings. Click on either Network or Wi-Fi tab, depending on the interface you would like to modify. To open the interface settings, click on the gear icon next to the interface name. Select ...
Configure Static IP Address on Ubuntu 22.04|20.04|18.04
Method 2: Use Netplan YAML network configuration. On Ubuntu 22.04|20.04|18.04, you can use Netplan which is a YAML network configuration tool to set static IP address. This configuration assumes your network interface is called eth0. This may vary depending on your working environment. Create a network configuration file.
Setting a Static IP Address in Ubuntu 18.04
Finally, we are in the right menu on Ubuntu 18.04 to set a static IP address. There are several things you will need to do on this screen. First, you need to change the DHCP mode from automatic to manual ( 1. ). Once in manual mode, you will need to define the address ( 2. ), netmask ( 3. ), and gateway ( 4. ).
How To Configure Static IP Address in Ubuntu 18.04 using Netplan
If you want to assign static, click on the gear icon in WiFi settings page. Configure Static IP Address in Ubuntu 18.04 - Configure WIFI. Go to IPv4 tab and enter the IP address details shown like below. Finally, click Apply. Configure Static IP Address in Ubuntu 18.04 - Manual IP Address to WiFi.
How to setup a static IP on Ubuntu Server 18.04
Why oh why is every guide to setting a static IP on 18.04 telling me to edit a yaml file that says it is a dynamically created file that will not persist? Another cruel joke from the Ubuntu developers that think it is ok to just break things by default...
Configure Ubuntu Server 18.04 to use a static IP address
Configure Ubuntu Server 18.04 to use a static IP address. 0 Comments ... How to change the IP address from DHCP to static on Ubuntu Server 18.04. Open the netplan config file: ... First we want to change dhcp4 to false and then add the static IP config below this. Here's an example below: network: version: 2 renderer: networkd ethernets ...
Configuring networks
To configure a default gateway, you can use the ip command in the following manner. Modify the default gateway address to match your network requirements. sudo ip route add default via 10.102.66.1. You can also use the ip command to verify your default gateway configuration, as follows: ip route show.
How to Configure Static IP Address on Ubuntu 18.04
1.In the Activities screen, search for "network" and click on the Network icon. This will open the GNOME Network configuration settings. Click on the cog icon. 2. This will open the Network interface settings dialog box. 3. In the "IPV4" Method" section select "Manual", and enter your static IP address, Netmask and Gateway.
How to Configure Static IP Address on Ubuntu 18.04
Click on the cog icon. Select Network icon. 2. This will open the Network interface settings dialog box. Network interface settings dialog box. 3. In "IPV4" Method" section select "Manual", and enter your static IP address, Netmask and Gateway. Click on the "Apply" button once completed.
How to Configure Network Static IP Address in Ubuntu 18.04
Set Static IP Address in Ubuntu 18.04. In this example, we will configure a static IP for the enp0s8 ethernet network interface. Open the netplan configuration file using your text editor as shown. ... Configure Static IP in Ubuntu. Save the file and exit. Then apply the recent network changes using following netplan command. $ sudo netplan apply
How to configure static IP on ubuntu 18.04 server
We know the configuration of IP on Ubuntu 18.04 is different from other. Ubuntu versions like Ubuntu 14, Ubuntu 16 etc. The manner by which Ubuntu oversees organize interfaces has totally changed. We use NetPlan as the new network configuration tool to manage network settings in Ubuntu 18. NetPlan replaces the static interfaces "/etc/network ...
How to Configure Static IP Address on Ubuntu 18.04 (Desktop)
Step 2 - Setup Static IP on Ubuntu 18.04. Under the IPv4 Method select the "Manual" option. Now go to the Addresses section and set your IP Address, Netmask, and Gateway. You can also set remote DNS IP addresses. If you don't know what to set here use 8.8.8.8 and 8.8.4.4 as shown in below screenshot.
How to Configure Network Static IP Address in Ubuntu 18.04?
How to Configure Network Static IP Address in Ubuntu 18 04 - Introduction The Internet Protocol (IP) address is a crucial component of computer networking as it uniquely identifies each device connected to a network. By default, most network interfaces are configured to obtain an IP address dynamically from a router or DHCP server. However, in some cases, it
How to assign static IP address on Ubuntu Linux
To assign a static IP address on Ubuntu (server or client) through the Settings app, use these steps: Open Settings. Click on Network. Click the Settings button for the "Wired" network interface. Click the IPv4 tab. Select the Manual option for the "IPv4 Method" setting. Under the "Addresses" section, confirm the static IP address ...
Tutorial
Errors or typos? Topics missing? Hard to read? Let us know or open an issue on GitHub. Multipass is a flexible and powerful tool that can be used for many purposes. In its simplest form, it can be used to quickly create and destroy Ubuntu VMs (instances) on any host machine. When used maximally, Multipass is a local mini-cloud on your laptop, ensuring that you can test and develop multi ...
Vulnerability Summary for the Week of June 24, 2024
Avaya--IP Office : An improper input validation vulnerability was discovered in Avaya IP Office that could allow remote command or code execution via a specially crafted web request to the Web Control component. Affected versions include all versions prior to 11.1.3.1. 2024-06-25: 10: CVE-2024-4196 [email protected]: Avaya--IP Office

How to Configure Static IP Address on Ubuntu 18.04

Configuring Static IP address using DHCP #

Configuring Static IP address on Ubuntu Server #

Configuring Static IP address on Ubuntu Desktop #

Conclusion #

How to Configure Static IP Address on Ubuntu 20.04

Related Articles

TechRepublic

Share with Your Friends

The new method

Restarting/testing networking

That’s all there is to it

Subscribe to the Developer Insider Newsletter

Create a TechRepublic Account

Sign in to TechRepublic

Reset Password

Welcome. Tell us a little bit about you.

Want to receive more TechRepublic news?

Set static IP in Ubuntu using Terminal

Step 1: Identify the correct network interface

Ubuntu Server

Ubuntu Desktop

Step 2: See current IP address

Step 3: See the gateway

Step 4: Set static IP address

Step 4-A: Disable cloud-init if present

Back to Step 4

On this page

Ubuntu Static IP configuration

Software Requirements and Conventions Used

Ubuntu Static IP configuration step by step

Ubuntu Server

Closing Thoughts

Related Linux Tutorials:

How to Assign Static IP Address on Ubuntu Linux

Method 1: Assign static IP in Ubuntu using command line

Step 1: Get the name of network interface and the default gateway

Step 2: Locate Netplan configuration

Step 3: Edit Netplan configuration for assigning static IP

Method 2: Switch to static IP address in Ubuntu graphically

Exploring the Default Tiling Windows Feature in Ubuntu 24.04 (and Enhancing it)

How to configure static IP address on Ubuntu 18.04

How-To Geek

Quick Links

How to Configure static IP address in Ubuntu Server 18.04 LTS

Identify available network interface with ip command

Netplan and YAML format interface configuration file

Assigning static IP addresses (IPv4)

How it works..

Configure static IPv6 Addresses on Ubuntu Server

Assign multiple IP addresses to a single network interface

Configure Multiple network interfaces

Setting a Static IP in Ubuntu – Linux IP Address Tutorial

How to Set a Static IP Using the Command Line

Step 1: Launch the terminal

Step 2: Note information about the current network

Step 3: Make configuration changes

Step 4: Apply and test the changes

How to Set a Static IP Using the GUI

Configure Static IP Address on Ubuntu 22.04|20.04|18.04

Method 1: Manually edit Network Configuration files

Method 2: Use Netplan YAML network configuration

YOU CAN SUPPORT OUR WORK WITH A CUP OF COFFEE

RELATED ARTICLES MORE FROM AUTHOR

Setting a Static IP Address in Ubuntu 18.04

Table of Contents

Setting a Static IP Address on Ubuntu Server 18.04

Recommended

Leave a Reply Cancel reply

Netplan – How To Configure Static IP Address in Ubuntu 18.04 using Netplan

Prerequisites

Find the available network cards on your system

Choose the desired network interface

Configure Static IP Address using Netplan

Verify Static IP Address

Configure Static IP Address using ifupdown / Network Manager

Stack Exchange Network

How to setup a static IP on Ubuntu Server 18.04

11 Answers 11

This is set a static IP instruction in Ubuntu-Server 18.04 and 20.04