Luci Stanescu

**Name of the Vulnerable Software and Affected Versions** provd versions prior to 0.1.5 **Description** An issue was discovered in provd with a setuid binary, which allows a local attacker to escalate their privilege. **Recommendations** For versions prior to 0.1.5, update to version 0.1.5 or later to resolve the issue. As a temporary workaround, consider restricting access to the setuid binary to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** OpenSSH versions 8.9 through 9.2 **Description** The issue is related to the use of memory after it has been freed in the ssh-agent of OpenSSH, which can allow a remote attacker to impact the confidentiality, integrity, and availability of protected information. The problem specifically involves the ssh-add feature adding smartcard keys to ssh-agent without the intended per-hop destination constraints. **Recommendations** For OpenSSH versions 8.9 through 9.2, update to version 9.3 or later to resolve the issue. As a temporary workaround, consider restricting access to the ssh-add feature until a patch is available. Avoid using smartcard keys with ssh-agent until the issue is resolved.

**Name of the Vulnerable Software and Affected Versions** Zyxel NWA110AX versions prior to 6.50(ABTG.0)C0 **Description** The issue is related to an improper check for unusual conditions in the firmware, which could allow a LAN attacker to cause a temporary denial-of-service (DoS) by sending crafted VLAN frames if the MAC address of the vulnerable AP were intercepted by the attacker. Additionally, there is a vulnerability in the implementation of the command-line interface (CLI) of Zyxel network device firmware, related to the failure to neutralize special elements used in the command of the operating system, which could allow a remote attacker to execute arbitrary commands. **Recommendations** For versions prior to 6.50(ABTG.0)C0, update to version 6.50(ABTG.0)C0 or later to resolve the issue. As a temporary workaround, consider restricting access to the vulnerable AP to minimize the risk of exploitation. Avoid using the vulnerable CLI interface until the issue is resolved.