Yuto Iso

**Name of the Vulnerable Software and Affected Versions** PhishWall Client Internet Explorer edition versions 3.7.15 and earlier **Description** The issue concerns an untrusted search path vulnerability in the installer. This vulnerability allows an attacker to gain privileges by using a Trojan horse DLL in an unspecified directory. **Recommendations** For versions 3.7.15 and earlier, update to a version later than 3.7.15 to resolve the issue.

**Name of the Vulnerable Software and Affected Versions** PhishWall Client Firefox and Chrome edition for Windows version 5.1.26 and earlier **Description** The issue concerns an untrusted search path vulnerability in the installer. This vulnerability allows an attacker to gain privileges via a Trojan horse DLL in an unspecified directory. **Recommendations** For versions 5.1.26 and earlier, update to a version later than 5.1.26 to resolve the issue.

**Name of the Vulnerable Software and Affected Versions** HYPER SBI versions 2.2 and earlier **Description** The issue allows an attacker to gain privileges via a Trojan horse DLL in an unspecified directory. **Recommendations** For HYPER SBI versions 2.2 and earlier, at the moment, there is no information about a newer version that contains a fix for this issue.

**Name of the Vulnerable Software and Affected Versions** TVer App for Android versions 3.2.7 and earlier **Description** The issue allows man-in-the-middle attackers to spoof servers and obtain sensitive information via a crafted certificate because the TVer App for Android does not verify X.509 certificates from SSL servers. **Recommendations** For versions 3.2.7 and earlier, at the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Photopt for Android versions prior to 2.0.1 **Description** The issue is related to the failure of the application to verify SSL certificates. This could potentially allow for man-in-the-middle attacks. **Recommendations** For versions prior to 2.0.1, update to version 2.0.1 or later to resolve the issue.