Dr. Faruk Kazi

A flaw in the gst-plugins-bad package occurs when processing a specially crafted H.264 video file containing malformed Multiview Video Coding (MVC) or Scalable Video Coding (SVC) extension slice Network Abstraction Layer (NAL) units. A 1-byte heap out-of-bounds read can happen during parsing because the parser checks slice boundary information without verifying if the NAL unit contains sufficient data beyond the extension header. This could lead to an application crash or the leakage of a single byte of heap memory if a user opens a malicious file.

The issue is related to an insufficient session expiration, which could allow an attacker to transmit passwords over unencrypted connections, resulting in the product becoming vulnerable to interception. This could permit attackers to intercept passwords.

The issue concerns the transmission of user credentials in clear text without encryption when a user is added or user credentials are changed via the device's webpage. This affects the security of user credentials.

Name of the Vulnerable Software and Affected Versions: TP-Link Archer C50 (affected versions not specified) Description: The issue is related to the improper signature verification mechanism in the firmware upgrade process at the web interface of the TP-Link Archer C50. This allows an attacker with administrative privileges within the router's Wi-Fi range to exploit the vulnerability by uploading and executing malicious firmware, potentially leading to the complete compromise of the targeted device. The exploitation can result in the execution of arbitrary code and may cause a denial of service. Recommendations: At the moment, there is no information about a newer version that contains a fix for this vulnerability.

This issue is related to the storage of Wi-Fi credentials in plain text within the device firmware of Philips lighting devices. An attacker with physical access could exploit this by extracting the firmware and analyzing the binary data to obtain the plaintext Wi-Fi credentials stored on the vulnerable device. Successful exploitation could allow an attacker to gain unauthorized access to the Wi-Fi network to which the vulnerable device is connected.

The issue concerns the transmission of credentials using a weak encoding method, specifically base64. An attacker present in the network can intercept the traffic and decode the credentials.

This issue exists due to insufficient validation of user-supplied input for the `DDNS Username` parameter at the web interface. A remote attacker could exploit this by supplying specially crafted input to the parameter, potentially allowing them to perform stored XSS attacks on the targeted system.

This issue is due to insufficient validation of user-supplied input for the `Identity` parameter under Local endpoint settings at the web interface. A remote attacker could exploit this by supplying specially crafted input to the parameter at the web interface of the targeted system. Successful exploitation could allow the attacker to perform stored XSS attacks on the targeted system.

This issue exists due to insufficient validation of user-supplied input for the `Pre-shared key` parameter at the web interface. A remote attacker could exploit this by supplying specially crafted input to the parameter, potentially allowing them to perform stored XSS attacks on the targeted system.

The issue exists due to insufficient validation of user-supplied input for the `L2TP/PPTP Username` parameter at the web interface. A remote attacker could exploit this by supplying specially crafted input to the parameter, potentially allowing them to perform stored XSS attacks on the targeted system.

The issue exists due to insufficient validation of user-supplied input for the `Preshared Phrase` parameter at the web interface. A remote attacker could exploit this by supplying specially crafted input to the parameter, potentially allowing stored XSS attacks on the targeted system.

This issue exists due to insufficient validation of user-supplied input for the `Network Name (SSID)` parameter at the web interface. A remote attacker could exploit this by supplying specially crafted input to the parameter, allowing them to perform stored XSS attacks on the targeted system.

This issue exists due to insufficient validation of user-supplied input for the `Device Name` parameter at the web interface. A remote attacker could exploit this by supplying specially crafted input to the parameter, allowing them to perform stored XSS attacks on the targeted system.

This issue exists due to the transmission of authentication credentials in plaintext over the network. A remote attacker could exploit this by eavesdropping on the victim’s network traffic to extract the `username` and `password` from the web interface (Login Page) of the targeted system.

This issue exists due to the transmission of authentication credentials in plaintext over the network. A remote attacker could exploit this by eavesdropping on the victim’s network traffic to extract the `username` and `password` from the web interface, specifically the Password Reset Page, of the targeted system.

This issue is due to insufficient validation of user-supplied input for the `Add Downstream Frequency` parameter at the web interface. A remote attacker could exploit this by supplying specially crafted input to the parameter, potentially allowing a Denial of Service (DoS) attack on the targeted system.

This issue is due to insufficient validation of user-supplied input for the `Set Upstream Channel ID (UCID)` parameter at the web interface. A remote attacker could exploit this by supplying specially crafted input to the parameter, potentially allowing them to perform a Denial of Service (DoS) attack on the targeted system.

This issue is due to insufficient validation of user-supplied input for the `Traceroute` parameter at the web interface. A remote attacker could exploit this by supplying specially crafted input to the parameter, allowing them to perform stored XSS attacks on the targeted system.

This issue exists due to insufficient validation of user-supplied input for the `Time Server 1` parameter at the web interface. A remote attacker could exploit this by supplying specially crafted input to the parameter, allowing them to perform stored XSS attacks on the targeted system.

The issue exists due to insufficient validation of user-supplied input for the `Time Server 2` parameter at the web interface. A remote attacker could exploit this by supplying specially crafted input to the parameter, allowing them to perform stored XSS attacks on the targeted system.