DENIAL OF SERVICE FOR CONCURRENT CONNECTIONS ON TELNET
An attacker with access to the system's internal network can cause a denial of service on the system by making two concurrent connections through the Telnet service.
No EFACEC vulnerabilities are listed in CISA KEV.
15 records
An attacker with access to the system's internal network can cause a denial of service on the system by making two concurrent connections through the Telnet service.
The massive sending of ARP requests causes a denial of service on one board of the charger that allows control of the EV interfaces.
An attacker with a network connection could detect credentials in clear text.
Through the exploitation of active user sessions, an attacker could send custom requests to cause a denial-of-service condition on the device.
The massive sending of ICMP requests causes a denial of service on one of the boards from the EVCharger that allows control the EV interfaces.
An attacker with the ability to interact through the network and with access credentials, could, thanks to the unsecured (unencrypted) MQTT communications protocol, write on the server topics of the board that controls t…
The absence of permissions control for the user XXX allows the current configuration in the sudoers file to escalate privileges without any restrictions
A successful CSRF attack could force the user to perform state changing requests on the application.
The credentials required to access the device's web server are sent in base64 within the HTTP headers.
An attacker with network access could perform a man-in-the-middle (MitM) attack and capture sensitive information to gain unauthorized access to the application.
The lack of hardening of the system allows the user used to manage and maintain the charger to consult different files containing clear-text credentials or valuable information for an attacker.
An attacker could construct a URL within the application that causes a redirection to an arbitrary external domain and could be leveraged to facilitate phishing attacks against application users.
An attacker could create malicious requests to obtain sensitive information about the web server.
As the service interaction is performed without authentication, an attacker with some knowledge of the protocol could obtain information about the charger via OCPP v1.6.
A user without administrator permissions with access to the UC500 windows system could perform a memory dump of the running processes and extract clear credentials or valid session tokens.