The attacker would have to send a packet with a malicious format string that would cause the vulnerable NAS to execute commands on the device. In most cases, customers do not manually configure the device to accept unauthenticated incoming traffic. This scenario can be especially dangerous when the device is configured to accept “DNS-like” remote configuration traffic. The attacker could then send a packet with a malicious format string that would cause the vulnerable NAS to execute commands on the device. In most cases, customers do not manually configure the device to accept unauthenticated incoming traffic. This scenario can be especially dangerous when the device is configured to accept “DNS-like” remote configuration traffic. Mitigation The vendor has released firmware version V5.21(AAZF.12)C0, which resolves this issue. In order to update the device, users should contact their vendors or distributors. —
OSVDB-CVE-2016-10275
The vulnerability is caused by the release of the FreeNAS-9.3-1.0_A1029, which was released on April 29th, 2016
FreeNAS-9.2.1-1 and earlier versions are not affected
The vulnerability allows an attacker to execute commands on a vulnerable NAS device without authenticating themselves.
Mitigation The vendor has released firmware version V5.21(AAZF.12)C0, which resolves this issue. In order to update the device, users should contact their vendors or distributors.
CVE-2023-34748
The attacker would have to send a packet with a malicious format string that would cause the vulnerable NAS to execute commands on the device. In most cases, customers do not manually configure the device to accept unauthenticated incoming traffic. This scenario can be especially dangerous when the device is configured to accept “DNS-like” remote configuration traffic. The attacker could then send a packet with a malicious format string that would cause the vulnerable NAS to execute commands on the device. In most cases, customers do not manually configure the device to accept unauthenticated incoming traffic. This scenario can be especially dangerous when the device is configured to accept “DNS-like” remote configuration traffic. Mitigation The vendor has released firmware version V5.21(AAZF.12)C0, which resolves this issue. In order to update the device, users should contact their vendors or distributors.
Remotely Manageable Device (RMD)
The Remote Manageable Device (RMD) is a device that provides an alternative network connectivity option for customers who do not have a traditional network. These devices can be configured to support local, remote, or web-based management. They support configuration of the device through a variety of protocols, including HTTP, SNMP, and SSH.
In some cases, NAS devices that are deployed in Remote Manageable Devices could be vulnerable to attacks if they receive unsolicited requests from remote hosts. This vulnerability is present when the Remote Manageable Device receives unsolicited requests from remote hosts and processes them without authenticating the source. Mitigation The vendor has released firmware version V5.21(AAZF.12)C0 which resolves this issue: https://support-openstack-redhat-openness/discussions/76941/?source=default
Vendor Response:
Affected products:
* All models of the Cisco UCS C220 M2 Rack Server (UCS-C220-M2-1X40B) that have an affected release of firmware
The Cisco Security Team is aware of this vulnerability, and has provided a fix for it. Customers are advised to contact their local Cisco Technical Assistance Center (TAC) or Cisco Service Provider Operations (SPO) team as soon as possible to ensure they receive the latest update.
Timeline
Published on: 09/06/2022 02:15:00 UTC
Last modified on: 09/08/2022 14:50:00 UTC