CVE-2023-6764 Vulnerability Analysis & Exploit Details

CVE-2023-6764
Vulnerability Scoring

8.1
/10
Severe Risk

Cybersecurity professionals consider CVE-2023-6764 an immediate threat requiring urgent mitigation.

Attack Complexity Details

  • Attack Complexity: High
    Exploits require significant effort and special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2023-6764 Details

Status: Analyzed

Last updated: 🕡 21 Jan 2025, 18:35 UTC
Originally published on: 🕒 20 Feb 2024, 03:15 UTC

Time between publication and last update: 336 days

CVSS Release: version 3

CVSS3 Source

security@zyxel.com.tw

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

CVE-2023-6764 Vulnerability Summary

CVE-2023-6764: A format string vulnerability in a function of the IPSec VPN feature in Zyxel ATP series firmware versions from 4.32 through 5.37 Patch 1, USG FLEX series firmware versions from 4.50 through 5.37 Patch 1, USG FLEX 50(W) series firmware versions from 4.16 through 5.37 Patch 1, and USG20(W)-VPN series firmware versions from 4.16 through 5.37 Patch 1 could allow an attacker to achieve unauthorized remote code execution by sending a sequence of specially crafted payloads containing an invalid pointer; however, such an attack would require detailed knowledge of an affected device’s memory layout and configuration.

Assessing the Risk of CVE-2023-6764

Access Complexity Graph

The exploitability of CVE-2023-6764 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2023-6764

CVE-2023-6764 presents a challenge to exploit due to its high attack complexity, but the absence of privilege requirements still makes it a viable target for skilled attackers. A thorough security review is advised.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2023-6764, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2023-6764, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2023-6764 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2023-6764 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2023-6764 can disrupt system operations, potentially causing complete denial of service (DoS).

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.043% (probability of exploit)

EPSS Percentile: 11.87% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 88.13% of others.

CVE-2023-6764 References

External References

CWE Common Weakness Enumeration

CWE-134

CAPEC Common Attack Pattern Enumeration and Classification

  • Format String Injection CAPEC-135 An adversary includes formatting characters in a string input field on the target application. Most applications assume that users will provide static text and may respond unpredictably to the presence of formatting character. For example, in certain functions of the C programming languages such as printf, the formatting character %s will print the contents of a memory location expecting this location to identify a string and the formatting character %n prints the number of DWORD written in the memory. An adversary can use this to read or write to memory locations or files, or simply to manipulate the value of the resulting text in unexpected ways. Reading or writing memory may result in program crashes and writing memory could result in the execution of arbitrary code if the adversary can write to the program stack.
  • String Format Overflow in syslog() CAPEC-67 This attack targets applications and software that uses the syslog() function insecurely. If an application does not explicitely use a format string parameter in a call to syslog(), user input can be placed in the format string parameter leading to a format string injection attack. Adversaries can then inject malicious format string commands into the function call leading to a buffer overflow. There are many reported software vulnerabilities with the root cause being a misuse of the syslog() function.

Vulnerable Configurations

  • cpe:2.3:o:zyxel:atp100_firmware:4.32:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp100_firmware:4.32:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp100_firmware:4.35:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp100_firmware:4.35:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp100_firmware:4.35\(abps.2\)c0:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp100_firmware:4.35\(abps.2\)c0:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp100_firmware:4.35\(abps.3\)c0:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp100_firmware:4.35\(abps.3\)c0:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp100_firmware:4.60:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp100_firmware:4.60:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp100_firmware:5.10:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp100_firmware:5.10:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp100_firmware:5.20:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp100_firmware:5.20:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp100_firmware:5.30:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp100_firmware:5.30:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp100_firmware:5.31:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp100_firmware:5.31:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp100_firmware:5.35:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp100_firmware:5.35:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp100_firmware:5.36:-:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp100_firmware:5.36:-:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp100_firmware:5.36:patch1:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp100_firmware:5.36:patch1:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp100_firmware:5.36:patch2:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp100_firmware:5.36:patch2:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp100_firmware:5.37:-:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp100_firmware:5.37:-:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp100_firmware:5.37:patch1:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp100_firmware:5.37:patch1:*:*:*:*:*:*
  • cpe:2.3:h:zyxel:atp100:-:*:*:*:*:*:*:*
    cpe:2.3:h:zyxel:atp100:-:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp100w_firmware:4.32:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp100w_firmware:4.32:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp100w_firmware:4.60:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp100w_firmware:4.60:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp100w_firmware:5.10:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp100w_firmware:5.10:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp100w_firmware:5.20:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp100w_firmware:5.20:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp100w_firmware:5.30:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp100w_firmware:5.30:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp100w_firmware:5.35:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp100w_firmware:5.35:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp100w_firmware:5.36:-:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp100w_firmware:5.36:-:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp100w_firmware:5.36:patch1:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp100w_firmware:5.36:patch1:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp100w_firmware:5.36:patch2:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp100w_firmware:5.36:patch2:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp100w_firmware:5.37:-:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp100w_firmware:5.37:-:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp100w_firmware:5.37:patch1:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp100w_firmware:5.37:patch1:*:*:*:*:*:*
  • cpe:2.3:h:zyxel:atp100w:-:*:*:*:*:*:*:*
    cpe:2.3:h:zyxel:atp100w:-:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp200_firmware:4.32:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp200_firmware:4.32:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp200_firmware:4.35:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp200_firmware:4.35:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp200_firmware:4.35\(abfw.3\)c0:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp200_firmware:4.35\(abfw.3\)c0:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp200_firmware:4.60:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp200_firmware:4.60:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp200_firmware:5.10:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp200_firmware:5.10:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp200_firmware:5.20:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp200_firmware:5.20:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp200_firmware:5.30:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp200_firmware:5.30:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp200_firmware:5.35:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp200_firmware:5.35:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp200_firmware:5.36:-:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp200_firmware:5.36:-:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp200_firmware:5.36:patch1:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp200_firmware:5.36:patch1:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp200_firmware:5.36:patch2:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp200_firmware:5.36:patch2:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp200_firmware:5.37:-:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp200_firmware:5.37:-:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp200_firmware:5.37:patch1:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp200_firmware:5.37:patch1:*:*:*:*:*:*
  • cpe:2.3:h:zyxel:atp200:-:*:*:*:*:*:*:*
    cpe:2.3:h:zyxel:atp200:-:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp500_firmware:4.32:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp500_firmware:4.32:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp500_firmware:4.35:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp500_firmware:4.35:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp500_firmware:4.35\(abfu.3\)c0:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp500_firmware:4.35\(abfu.3\)c0:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp500_firmware:4.60:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp500_firmware:4.60:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp500_firmware:5.10:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp500_firmware:5.10:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp500_firmware:5.20:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp500_firmware:5.20:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp500_firmware:5.30:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp500_firmware:5.30:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp500_firmware:5.35:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp500_firmware:5.35:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp500_firmware:5.36:-:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp500_firmware:5.36:-:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp500_firmware:5.36:patch1:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp500_firmware:5.36:patch1:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp500_firmware:5.36:patch2:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp500_firmware:5.36:patch2:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp500_firmware:5.37:-:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp500_firmware:5.37:-:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp500_firmware:5.37:patch1:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp500_firmware:5.37:patch1:*:*:*:*:*:*
  • cpe:2.3:h:zyxel:atp500:-:*:*:*:*:*:*:*
    cpe:2.3:h:zyxel:atp500:-:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp700_firmware:4.32:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp700_firmware:4.32:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp700_firmware:4.60:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp700_firmware:4.60:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp700_firmware:5.10:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp700_firmware:5.10:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp700_firmware:5.20:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp700_firmware:5.20:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp700_firmware:5.30:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp700_firmware:5.30:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp700_firmware:5.35:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp700_firmware:5.35:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp700_firmware:5.36:-:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp700_firmware:5.36:-:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp700_firmware:5.36:patch1:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp700_firmware:5.36:patch1:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp700_firmware:5.36:patch2:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp700_firmware:5.36:patch2:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp700_firmware:5.37:-:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp700_firmware:5.37:-:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp700_firmware:5.37:patch1:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp700_firmware:5.37:patch1:*:*:*:*:*:*
  • cpe:2.3:h:zyxel:atp700:-:*:*:*:*:*:*:*
    cpe:2.3:h:zyxel:atp700:-:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp800_firmware:4.32:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp800_firmware:4.32:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp800_firmware:4.35:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp800_firmware:4.35:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp800_firmware:4.35\(abiq.3\)c0:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp800_firmware:4.35\(abiq.3\)c0:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp800_firmware:4.60:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp800_firmware:4.60:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp800_firmware:5.10:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp800_firmware:5.10:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp800_firmware:5.20:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp800_firmware:5.20:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp800_firmware:5.30:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp800_firmware:5.30:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp800_firmware:5.35:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp800_firmware:5.35:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp800_firmware:5.36:-:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp800_firmware:5.36:-:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp800_firmware:5.36:patch1:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp800_firmware:5.36:patch1:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp800_firmware:5.36:patch2:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp800_firmware:5.36:patch2:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp800_firmware:5.37:-:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp800_firmware:5.37:-:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:atp800_firmware:5.37:patch1:*:*:*:*:*:*
    cpe:2.3:o:zyxel:atp800_firmware:5.37:patch1:*:*:*:*:*:*
  • cpe:2.3:h:zyxel:atp800:-:*:*:*:*:*:*:*
    cpe:2.3:h:zyxel:atp800:-:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_100_firmware:4.50:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_100_firmware:4.50:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_100_firmware:4.60:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_100_firmware:4.60:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_100_firmware:5.00:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_100_firmware:5.00:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_100_firmware:5.01:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_100_firmware:5.01:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_100_firmware:5.20:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_100_firmware:5.20:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_100_firmware:5.35:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_100_firmware:5.35:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_100_firmware:5.36:-:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_100_firmware:5.36:-:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_100_firmware:5.36:patch1:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_100_firmware:5.36:patch1:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_100_firmware:5.36:patch2:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_100_firmware:5.36:patch2:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_100_firmware:5.37:-:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_100_firmware:5.37:-:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_100_firmware:5.37:patch1:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_100_firmware:5.37:patch1:*:*:*:*:*:*
  • cpe:2.3:h:zyxel:usg_flex_100:-:*:*:*:*:*:*:*
    cpe:2.3:h:zyxel:usg_flex_100:-:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_100ax_firmware:5.37:-:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_100ax_firmware:5.37:-:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_100ax_firmware:5.37:patch1:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_100ax_firmware:5.37:patch1:*:*:*:*:*:*
  • cpe:2.3:h:zyxel:usg_flex_100ax:-:*:*:*:*:*:*:*
    cpe:2.3:h:zyxel:usg_flex_100ax:-:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_100h_firmware:5.37:-:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_100h_firmware:5.37:-:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_100h_firmware:5.37:patch1:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_100h_firmware:5.37:patch1:*:*:*:*:*:*
  • cpe:2.3:h:zyxel:usg_flex_100h:-:*:*:*:*:*:*:*
    cpe:2.3:h:zyxel:usg_flex_100h:-:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_100w_firmware:4.50:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_100w_firmware:4.50:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_100w_firmware:4.60:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_100w_firmware:4.60:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_100w_firmware:5.00:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_100w_firmware:5.00:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_100w_firmware:5.01:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_100w_firmware:5.01:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_100w_firmware:5.30:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_100w_firmware:5.30:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_100w_firmware:5.35:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_100w_firmware:5.35:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_100w_firmware:5.36:-:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_100w_firmware:5.36:-:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_100w_firmware:5.36:patch1:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_100w_firmware:5.36:patch1:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_100w_firmware:5.36:patch2:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_100w_firmware:5.36:patch2:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_100w_firmware:5.37:-:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_100w_firmware:5.37:-:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_100w_firmware:5.37:patch1:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_100w_firmware:5.37:patch1:*:*:*:*:*:*
  • cpe:2.3:h:zyxel:usg_flex_100w:-:*:*:*:*:*:*:*
    cpe:2.3:h:zyxel:usg_flex_100w:-:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_200_firmware:4.50:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_200_firmware:4.50:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_200_firmware:4.60:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_200_firmware:4.60:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_200_firmware:5.00:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_200_firmware:5.00:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_200_firmware:5.01:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_200_firmware:5.01:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_200_firmware:5.20:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_200_firmware:5.20:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_200_firmware:5.30:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_200_firmware:5.30:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_200_firmware:5.35:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_200_firmware:5.35:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_200_firmware:5.36:-:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_200_firmware:5.36:-:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_200_firmware:5.36:patch1:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_200_firmware:5.36:patch1:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_200_firmware:5.36:patch2:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_200_firmware:5.36:patch2:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_200_firmware:5.37:-:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_200_firmware:5.37:-:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_200_firmware:5.37:patch1:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_200_firmware:5.37:patch1:*:*:*:*:*:*
  • cpe:2.3:h:zyxel:usg_flex_200:-:*:*:*:*:*:*:*
    cpe:2.3:h:zyxel:usg_flex_200:-:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_200h_firmware:5.37:-:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_200h_firmware:5.37:-:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_200h_firmware:5.37:patch1:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_200h_firmware:5.37:patch1:*:*:*:*:*:*
  • cpe:2.3:h:zyxel:usg_flex_200h:-:*:*:*:*:*:*:*
    cpe:2.3:h:zyxel:usg_flex_200h:-:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_200hp_firmware:5.37:-:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_200hp_firmware:5.37:-:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_200hp_firmware:5.37:patch1:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_200hp_firmware:5.37:patch1:*:*:*:*:*:*
  • cpe:2.3:h:zyxel:usg_flex_200hp:-:*:*:*:*:*:*:*
    cpe:2.3:h:zyxel:usg_flex_200hp:-:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_500_firmware:4.50:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_500_firmware:4.50:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_500_firmware:4.60:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_500_firmware:4.60:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_500_firmware:5.00:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_500_firmware:5.00:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_500_firmware:5.01:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_500_firmware:5.01:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_500_firmware:5.20:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_500_firmware:5.20:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_500_firmware:5.30:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_500_firmware:5.30:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_500_firmware:5.35:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_500_firmware:5.35:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_500_firmware:5.36:-:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_500_firmware:5.36:-:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_500_firmware:5.36:patch1:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_500_firmware:5.36:patch1:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_500_firmware:5.36:patch2:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_500_firmware:5.36:patch2:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_500_firmware:5.37:-:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_500_firmware:5.37:-:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_500_firmware:5.37:patch1:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_500_firmware:5.37:patch1:*:*:*:*:*:*
  • cpe:2.3:h:zyxel:usg_flex_500:-:*:*:*:*:*:*:*
    cpe:2.3:h:zyxel:usg_flex_500:-:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_500h_firmware:5.37:-:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_500h_firmware:5.37:-:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_500h_firmware:5.37:patch1:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_500h_firmware:5.37:patch1:*:*:*:*:*:*
  • cpe:2.3:h:zyxel:usg_flex_500h:-:*:*:*:*:*:*:*
    cpe:2.3:h:zyxel:usg_flex_500h:-:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_700_firmware:4.50:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_700_firmware:4.50:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_700_firmware:4.60:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_700_firmware:4.60:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_700_firmware:5.00:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_700_firmware:5.00:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_700_firmware:5.20:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_700_firmware:5.20:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_700_firmware:5.30:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_700_firmware:5.30:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_700_firmware:5.35:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_700_firmware:5.35:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_700_firmware:5.36:-:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_700_firmware:5.36:-:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_700_firmware:5.36:patch1:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_700_firmware:5.36:patch1:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_700_firmware:5.36:patch2:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_700_firmware:5.36:patch2:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_700_firmware:5.37:-:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_700_firmware:5.37:-:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_700_firmware:5.37:patch1:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_700_firmware:5.37:patch1:*:*:*:*:*:*
  • cpe:2.3:h:zyxel:usg_flex_700:-:*:*:*:*:*:*:*
    cpe:2.3:h:zyxel:usg_flex_700:-:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_700h_firmware:5.37:-:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_700h_firmware:5.37:-:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_700h_firmware:5.37:patch1:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_700h_firmware:5.37:patch1:*:*:*:*:*:*
  • cpe:2.3:h:zyxel:usg_flex_700h:-:*:*:*:*:*:*:*
    cpe:2.3:h:zyxel:usg_flex_700h:-:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_50_firmware:4.50:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_50_firmware:4.50:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_50_firmware:4.60:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_50_firmware:4.60:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_50_firmware:5.00:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_50_firmware:5.00:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_50_firmware:5.35:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_50_firmware:5.35:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_50_firmware:5.36:-:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_50_firmware:5.36:-:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_50_firmware:5.36:patch1:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_50_firmware:5.36:patch1:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_50_firmware:5.36:patch2:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_50_firmware:5.36:patch2:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_50_firmware:5.37:-:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_50_firmware:5.37:-:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_50_firmware:5.37:patch1:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_50_firmware:5.37:patch1:*:*:*:*:*:*
  • cpe:2.3:h:zyxel:usg_flex_50:-:*:*:*:*:*:*:*
    cpe:2.3:h:zyxel:usg_flex_50:-:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_50w_firmware:4.50:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_50w_firmware:4.50:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_50w_firmware:4.60:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_50w_firmware:4.60:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_50w_firmware:5.00:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_50w_firmware:5.00:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_50w_firmware:5.10:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_50w_firmware:5.10:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_50w_firmware:5.30:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_50w_firmware:5.30:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_50w_firmware:5.35:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_50w_firmware:5.35:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_50w_firmware:5.36:-:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_50w_firmware:5.36:-:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_50w_firmware:5.36:patch1:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_50w_firmware:5.36:patch1:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_50w_firmware:5.36:patch2:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_50w_firmware:5.36:patch2:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_50w_firmware:5.37:-:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_50w_firmware:5.37:-:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg_flex_50w_firmware:5.37:patch1:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg_flex_50w_firmware:5.37:patch1:*:*:*:*:*:*
  • cpe:2.3:h:zyxel:usg_flex_50w:-:*:*:*:*:*:*:*
    cpe:2.3:h:zyxel:usg_flex_50w:-:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg20-vpn_firmware:4.31:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg20-vpn_firmware:4.31:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg20-vpn_firmware:4.35:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg20-vpn_firmware:4.35:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg20-vpn_firmware:4.35\(abaq.3\)c0:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg20-vpn_firmware:4.35\(abaq.3\)c0:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg20-vpn_firmware:4.60:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg20-vpn_firmware:4.60:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg20-vpn_firmware:5.01:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg20-vpn_firmware:5.01:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg20-vpn_firmware:5.36:-:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg20-vpn_firmware:5.36:-:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg20-vpn_firmware:5.36:patch1:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg20-vpn_firmware:5.36:patch1:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg20-vpn_firmware:5.36:patch2:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg20-vpn_firmware:5.36:patch2:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg20-vpn_firmware:5.37:-:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg20-vpn_firmware:5.37:-:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg20-vpn_firmware:5.37:patch1:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg20-vpn_firmware:5.37:patch1:*:*:*:*:*:*
  • cpe:2.3:h:zyxel:usg20-vpn:-:*:*:*:*:*:*:*
    cpe:2.3:h:zyxel:usg20-vpn:-:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg20w-vpn_firmware:4.31:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg20w-vpn_firmware:4.31:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg20w-vpn_firmware:4.35:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg20w-vpn_firmware:4.35:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg20w-vpn_firmware:4.35\(abar.3\)c0:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg20w-vpn_firmware:4.35\(abar.3\)c0:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg20w-vpn_firmware:4.60:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg20w-vpn_firmware:4.60:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg20w-vpn_firmware:5.01:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg20w-vpn_firmware:5.01:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg20w-vpn_firmware:5.10:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg20w-vpn_firmware:5.10:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg20w-vpn_firmware:5.30:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg20w-vpn_firmware:5.30:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg20w-vpn_firmware:5.37:-:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg20w-vpn_firmware:5.37:-:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg20w-vpn_firmware:5.37:patch1:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg20w-vpn_firmware:5.37:patch1:*:*:*:*:*:*
  • cpe:2.3:h:zyxel:usg20w-vpn:-:*:*:*:*:*:*:*
    cpe:2.3:h:zyxel:usg20w-vpn:-:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2023-6764: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-2130 – A vulnerability was found in OpenXE up to 1.12. It has been declared as problematic. This vulnerability affects unknown code of the component Ticke...
  • CVE-2025-26205 – Lua 5.4.7, when the debug library is used, has a out-of-bounds read and segmentation violation in mainpositionTV in ltable.c. NOTE: this is dispute...
  • CVE-2025-26204 – Lua 5.4.7, when the debug library is used, has a out-of-bounds read and segmentation violation in equalkey in ltable.c. NOTE: this is disputed beca...
  • CVE-2025-2129 – A vulnerability was found in Mage AI 0.9.75. It has been classified as problematic. This affects an unknown part. The manipulation leads to insecur...
  • CVE-2025-2127 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla. It has been classified as problematic. Affected is an unknown function of th...