No Image

USN-4734-1: wpa_supplicant and hostapd vulnerabilities

2021-02-12 KENNETH 0

USN-4734-1: wpa_supplicant and hostapd vulnerabilities It was discovered that wpa_supplicant did not properly handle P2P (Wi-Fi Direct) group information in some situations, leading to a heap overflow. A physically proximate attacker could use this to cause a denial of service or possibly execute arbitrary code. (CVE-2021-0326) It was discovered that hostapd did not properly handle UPnP subscribe messages in some circumstances. An attacker could use this to cause a denial of service. (CVE-2020-12695) Source: USN-4734-1: wpa_supplicant and hostapd vulnerabilities

No Image

USN-4733-1: GNOME Autoar vulnerability

2021-02-11 KENNETH 0

USN-4733-1: GNOME Autoar vulnerability Yiğit Can Yılmaz discovered that GNOME Autoar could extract files outside of the intended directory. If a user were tricked into extracting a specially crafted archive, a remote attacker could create files in arbitrary locations, possibly leading to code execution. Source: USN-4733-1: GNOME Autoar vulnerability

No Image

USN-4732-1: SQLite vulnerability

2021-02-11 KENNETH 0

USN-4732-1: SQLite vulnerability It was discovered that SQLite incorrectly handled certain sub-queries. An attacker could use this issue to cause SQLite to crash, resulting in a denial of service, or possibly execute arbitrary code. Source: USN-4732-1: SQLite vulnerability

No Image

USN-4730-1: PostSRSd vulnerability

2021-02-11 KENNETH 0

USN-4730-1: PostSRSd vulnerability It was discovered that PostSRSd mishandled certain input. A remote attacker could use this vulnerability to cause a denial of service via a long timestamp tag in an SRS address. Source: USN-4730-1: PostSRSd vulnerability

No Image

Securing gRPC APIs with NGINX App Protect

2021-02-11 KENNETH 0

Securing gRPC APIs with NGINX App Protect In the beginning was the monolith. It served software developers well for a long time, and still does for some use cases. But as applications grew, monoliths became unwieldy to develop, secure, and maintain. Microservices came on the scene as an alternative – the monolith is broken into small and autonomous services that perform a single business function and communicate over a network to provide the full functionality of the application. Initially, web developers used SOAP as the communication protocol and XML to encode data, but many found the combination cumbersome and slow. That inspired a switch to REST‑based architectures and the widespread adoption of HTTP and JSON as the protocol and data‑serialization method, respectively. But as is often the case with technology, developers continued to look for even better ways to design applications, [ more… ]