Skip to main content
CVE-2022-23767VulnerabilityPublished Updated

CVE-2022-23767: HANSSAK SecureGate · Authentication Bypass Using an Alternate Path or Channel

Affects HANSSAK SecureGateSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.9% chance of exploitation in 30 days – higher than 61% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Sep 2022

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
HANSSAK Co.,Ltd SecureGateAffected
  • =3.5
Fixed in–

AI-suggested

Organizations should immediately verify if they are running SecureGate version 3.5 and prioritize upgrading to a patched version once available from HANSSAK Co., Ltd. In the absence of an official patch, network-level mitigations should be implemented, such as restricting access to SecureGate management interfaces to trusted IP addresses and deploying web application firewalls (WAFs) with rules to detect and block SQL injection and path traversal attempts. Conduct thorough input validation and sanitization on any user-supplied data if custom integrations exist. Regularly audit logs for suspicious authentication attempts or unusual file access patterns. Employ network segmentation to limit the exposure of SecureGate devices. Additionally, implement strict monitoring and incident response procedures to quickly detect and respond to exploitation attempts. Engage with the vendor for updates and consider temporary compensating controls such as multi-factor authentication on related systems to reduce risk.

Description

This vulnerability of SecureGate is SQL-Injection using login without password. A path traversal vulnerability is also identified during file transfer. An attacker can take advantage of these vulnerabilities to perform various attacks such as obtaining privileges and executing remote code, thereby taking over the victim’s system.

References

Community reviews

Loading reviews…