The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers). An example of a network attack is an attacker causing a denial of service by sending a specially crafted TCP packet across a wide area network (e.g., CVE-2004-0230).
Attack Complexity
Low
AC
The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Privileges Required
High
PR
The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
User Interaction
None
UI
The vulnerable system can be exploited without interaction from any human user, other than the attacker. Examples include: a remote attacker is able to send packets to a target system a locally authenticated attacker executes code to elevate privileges
Scope
Unchanged
S
An exploited vulnerability can only affect resources managed by the same security authority. In the case of a vulnerability in a virtualized environment, an exploited vulnerability in one guest instance would not affect neighboring guest instances.
Confidentiality
High
C
There is total information disclosure, resulting in all data on the system being revealed to the attacker, or there is a possibility of the attacker gaining control over confidential data.
Integrity
High
I
There is a total compromise of system integrity. There is a complete loss of system protection, resulting in the attacker being able to modify any file on the target system.
Availability
None
A
There is no impact on the availability of the system; the attacker does not have the ability to disrupt access to or use of the system.
Below is a copy: Delta Electronics DX-2100-L1-CN 1.5.0.10 Command Injection / XSS
CyberDanube Security Research 20221130-0
-------------------------------------------------------------------------------
title| Multiple Vulnerabilities
product| Delta Electronics DX-2100-L1-CN
vulnerable version| V1.5.0.10
fixed version| V1.5.0.12
CVE number| -
impact| High
homepage| https://www.deltaww.com
found| 2022-08-01
by| T. Weber (Office Vienna)
| CyberDanube Security Research
| Vienna | St. Plten
|
| https://www.cyberdanube.com
-------------------------------------------------------------------------------
Vendor description
-------------------------------------------------------------------------------
"Delta, founded in 1971, is a global provider of power and thermal
management
solutions. Its mission statement, "To provide innovative, clean and energy
-efficient solutions for a better tomorrow," focuses on addressing key
environmental issues such as global climate change. As an energy-saving
solutions provider with core competencies in power electronics and
automation,
Delta's business categories include Power Electronics, Automation, and
Infrastructure."
Source: https://www.deltaww.com/en-US/about/aboutProfile
Vulnerable versions
-------------------------------------------------------------------------------
DX-2100-L1-CN / V1.5.0.10
Vulnerability overview
-------------------------------------------------------------------------------
1) Authenticated Command Injection
An authenticated command injection has been identified in the web
configuration
service of the device. It can be used to execute system commands on the
OS from
the device in the context of the user "root". Therefore, a full
compromization
of the device is possible by having credentials for the web service only.
2) Stored Cross-Site Scripting
A stored cross-site scripting vulnerability has been identified in the
function
"net diagnosis" on the device's web configuration service. This can be
exploited in the context of a victim's session.
Proof of Concept
-------------------------------------------------------------------------------
1) Authenticated Command Injection
The parameter "diagnose_address" contains the payload ";ls /;", which
basically
prints the content of the root directory to the serial terminal of the
device.
http://192.168.3.150/lform/net_diagnose?action=diagnose&diagnose_type=0&diagnose_address=;ls%20/;
The output can be seen in the context of a virtualized firmware clone,
as used
to find this vulnerability, but is usually invisible to a customer.
Therefore,
a more visible payload may be commands that interact via the network, like
";ping 192.168.0.10;". This command will ping a device on the
corresponding IP
address within the local network.
2) Stored Cross-Site Scripting
The following code prints the current cached cookies of a user's session
to the
screen. The JavaScript code will be stored on the device permanently.
===============================================================================
POST /lform/urlfilter?action=save HTTP/1.1
Host: 192.168.3.150
Accept: */*
Accept-Language: de,en-US;q=0.7,en;q=0.3
Accept-Encoding: gzip, deflate
Content-Type: application/x-www-form-urlencoded
Content-Length: 190
Connection: keep-alive
Cookie: language=en_US; userindex=1; loginexpire=1648630746607; session=30
lan_ipaddr=192.168.5.5&lan_netmask=255.255.255.0&src_addr_start=&src_addr_end=&editnum=0&bfilter_urllist=0&url_addr=<script>alert(document.cookie)</script>&src_addr_type=0&filter_state=1
===============================================================================
The vulnerabilities were manually verified on an emulated device by
using the
MEDUSA scalable firmware runtime (https://medusa.cyberdanube.com).
Solution
-------------------------------------------------------------------------------
Update to firmware version V1.5.0.12.
Workaround
-------------------------------------------------------------------------------
None
Recommendation
-------------------------------------------------------------------------------
CyberDanube recommends Delta Electronics customers to upgrade the
firmware to
the latest version available.
Contact Timeline
-------------------------------------------------------------------------------
2022-08-02: Contacting Delta Electronics.
2022-08-10: Vendor requested the advisory without encryption; Sent
advisory to
Delta Electronics.
2022-08-16: Security contact asked few questions regarding responsible
disclosure; Sent answers.
2022-08-30: Asked for an update.
2022-09-01: Vendor responded, that they will need more time to resolve the
issues; Provided additional 30 days (until 2022-11-02) for
patching.
2022-10-11: Asked for an update.
2022-10-12: Vendor responded, that fixing will be done 2022-11-15; Shifted
release date to this date.
2022-10-16: Vendor shifted release date again to 2022-11-18. Shifted
advisory
release date to the same day.
2022-10-17: Asked for an update regarding the release; No answer.
2022-10-18: Asked for an update and shifted release date to 2022-10-22.
2022-10-19: Vendor responded, that there were problems at releasing the
patch.
Contact stated, that the patch will delay until end of
November.
2022-10-21: Asked vendor for a concrete release date; No answer.
2022-10-28: Announced advisory release date for 2022-10-30 to vendor.
2022-10-29: Found firmware patches with issue date 2022-11-25 on vendors
website.
2022-10-30: Vendor confirmed fixes. Coordinated release of security
advisory.
Web: https://www.cyberdanube.com
Twitter: https://twitter.com/cyberdanube
Mail: research at cyberdanube dot com
EOF T. Weber / @2022
This information is provided for TESTING and LEGAL RESEARCH purposes only. All trademarks used are properties of their respective owners. By visiting this website you agree to Terms of Use and Privacy Policy and Impressum