CVE-2019-12583 Vulnerability Analysis & Exploit Details

CVE-2019-12583
Vulnerability Scoring

9.1
/10
Critical Risk

As a catastrophic security flaw, CVE-2019-12583 has severe implications, demanding immediate intervention.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or 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-2019-12583 Details

Status: Modified

Last updated: 🕓 21 Nov 2024, 04:23 UTC
Originally published on: 🕑 27 Jun 2019, 14:15 UTC

Time between publication and last update: 1973 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

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

CVE-2019-12583 Vulnerability Summary

CVE-2019-12583: Missing Access Control in the "Free Time" component of several Zyxel UAG, USG, and ZyWall devices allows a remote attacker to generate guest accounts by directly accessing the account generator. This can lead to unauthorised network access or Denial of Service.

Assessing the Risk of CVE-2019-12583

Access Complexity Graph

The exploitability of CVE-2019-12583 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-2019-12583

With low attack complexity and no required privileges, CVE-2019-12583 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

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-2019-12583, 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-2019-12583, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2019-12583 has no significant impact on data confidentiality.
  • Integrity: High
    CVE-2019-12583 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2019-12583 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.342% (probability of exploit)

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

CVE-2019-12583 References

External References

CWE Common Weakness Enumeration

CWE-425

CAPEC Common Attack Pattern Enumeration and Classification

  • Directory Indexing CAPEC-127 An adversary crafts a request to a target that results in the target listing/indexing the content of a directory as output. One common method of triggering directory contents as output is to construct a request containing a path that terminates in a directory name rather than a file name since many applications are configured to provide a list of the directory's contents when such a request is received. An adversary can use this to explore the directory tree on a target as well as learn the names of files. This can often end up revealing test files, backup files, temporary files, hidden files, configuration files, user accounts, script contents, as well as naming conventions, all of which can be used by an attacker to mount additional attacks.
  • Detect Unpublicized Web Pages CAPEC-143 An adversary searches a targeted web site for web pages that have not been publicized. In doing this, the adversary may be able to gain access to information that the targeted site did not intend to make public.
  • Detect Unpublicized Web Services CAPEC-144 An adversary searches a targeted web site for web services that have not been publicized. This attack can be especially dangerous since unpublished but available services may not have adequate security controls placed upon them given that an administrator may believe they are unreachable.
  • Key Negotiation of Bluetooth Attack (KNOB) CAPEC-668 An adversary can exploit a flaw in Bluetooth key negotiation allowing them to decrypt information sent between two devices communicating via Bluetooth. The adversary uses an Adversary in the Middle setup to modify packets sent between the two devices during the authentication process, specifically the entropy bits. Knowledge of the number of entropy bits will allow the attacker to easily decrypt information passing over the line of communication.
  • Forceful Browsing CAPEC-87 An attacker employs forceful browsing (direct URL entry) to access portions of a website that are otherwise unreachable. Usually, a front controller or similar design pattern is employed to protect access to portions of a web application. Forceful browsing enables an attacker to access information, perform privileged operations and otherwise reach sections of the web application that have been improperly protected.

Vulnerable Configurations

  • cpe:2.3:o:zyxel:uag2100_firmware:4.18\(aaiz.1\)c0:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:uag2100_firmware:4.18\(aaiz.1\)c0:*:*:*:*:*:*:*
  • cpe:2.3:h:zyxel:uag2100:-:*:*:*:*:*:*:*
    cpe:2.3:h:zyxel:uag2100:-:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:uag4100_firmware:4.18\(aatd.1\)c0:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:uag4100_firmware:4.18\(aatd.1\)c0:*:*:*:*:*:*:*
  • cpe:2.3:h:zyxel:uag4100:-:*:*:*:*:*:*:*
    cpe:2.3:h:zyxel:uag4100:-:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:uag5100_firmware:4.18\(aapn.1\)c0:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:uag5100_firmware:4.18\(aapn.1\)c0:*:*:*:*:*:*:*
  • cpe:2.3:h:zyxel:uag5100:-:*:*:*:*:*:*:*
    cpe:2.3:h:zyxel:uag5100:-:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg110_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg110_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg110_firmware:4.30:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg110_firmware:4.30:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg110_firmware:4.31:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg110_firmware:4.31:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg110_firmware:4.33\(aaph.0\)c0:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg110_firmware:4.33\(aaph.0\)c0:*:*:*:*:*:*:*
  • cpe:2.3:h:zyxel:usg110:-:*:*:*:*:*:*:*
    cpe:2.3:h:zyxel:usg110:-:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg210_firmware:4.30:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg210_firmware:4.30:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg210_firmware:4.31:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg210_firmware:4.31:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg210_firmware:4.33\(aapi.0\)c0:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg210_firmware:4.33\(aapi.0\)c0:*:*:*:*:*:*:*
  • cpe:2.3:h:zyxel:usg210:-:*:*:*:*:*:*:*
    cpe:2.3:h:zyxel:usg210:-:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg310_firmware:4.30:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg310_firmware:4.30:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg310_firmware:4.31:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg310_firmware:4.31:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg310_firmware:4.33\(aapj.0\)c0:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg310_firmware:4.33\(aapj.0\)c0:*:*:*:*:*:*:*
  • cpe:2.3:h:zyxel:usg310:-:*:*:*:*:*:*:*
    cpe:2.3:h:zyxel:usg310:-:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg1100_firmware:4.30:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg1100_firmware:4.30:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg1100_firmware:4.31:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg1100_firmware:4.31:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg1100_firmware:4.33\(aapk.0\)c0:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg1100_firmware:4.33\(aapk.0\)c0:*:*:*:*:*:*:*
  • cpe:2.3:h:zyxel:usg1100:-:*:*:*:*:*:*:*
    cpe:2.3:h:zyxel:usg1100:-:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg1900_firmware:4.30:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg1900_firmware:4.30:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg1900_firmware:4.31:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg1900_firmware:4.31:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg1900_firmware:4.33\(aapl.0\)c0:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg1900_firmware:4.33\(aapl.0\)c0:*:*:*:*:*:*:*
  • cpe:2.3:h:zyxel:usg1900:-:*:*:*:*:*:*:*
    cpe:2.3:h:zyxel:usg1900:-:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg2200-vpn_firmware:4.25:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg2200-vpn_firmware:4.25:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg2200-vpn_firmware:4.30:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg2200-vpn_firmware:4.30:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg2200-vpn_firmware:4.31:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg2200-vpn_firmware:4.31:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:usg2200-vpn_firmware:4.33\(abae.0\)c0:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:usg2200-vpn_firmware:4.33\(abae.0\)c0:*:*:*:*:*:*:*
  • cpe:2.3:h:zyxel:usg2200-vpn:-:*:*:*:*:*:*:*
    cpe:2.3:h:zyxel:usg2200-vpn:-:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:zywall_vpn100_firmware:4.20:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:zywall_vpn100_firmware:4.20:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:zywall_vpn100_firmware:4.30:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:zywall_vpn100_firmware:4.30:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:zywall_vpn100_firmware:4.35:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:zywall_vpn100_firmware:4.35:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:zywall_vpn100_firmware:5.00:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:zywall_vpn100_firmware:5.00:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:zywall_vpn100_firmware:5.01:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:zywall_vpn100_firmware:5.01:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:zywall_vpn100_firmware:5.37:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:zywall_vpn100_firmware:5.37:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:zywall_vpn100_firmware:10.02\(abfv.0\)c0:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:zywall_vpn100_firmware:10.02\(abfv.0\)c0:*:*:*:*:*:*:*
  • cpe:2.3:h:zyxel:zywall_vpn100:-:*:*:*:*:*:*:*
    cpe:2.3:h:zyxel:zywall_vpn100:-:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:zywall_vpn300_firmware:4.20:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:zywall_vpn300_firmware:4.20:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:zywall_vpn300_firmware:4.30:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:zywall_vpn300_firmware:4.30:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:zywall_vpn300_firmware:4.35:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:zywall_vpn300_firmware:4.35:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:zywall_vpn300_firmware:5.00:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:zywall_vpn300_firmware:5.00:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:zywall_vpn300_firmware:5.01:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:zywall_vpn300_firmware:5.01:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:zywall_vpn300_firmware:5.37:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:zywall_vpn300_firmware:5.37:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:zywall_vpn300_firmware:10.02\(abfc.0\)c0:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:zywall_vpn300_firmware:10.02\(abfc.0\)c0:*:*:*:*:*:*:*
  • cpe:2.3:h:zyxel:zywall_vpn300:-:*:*:*:*:*:*:*
    cpe:2.3:h:zyxel:zywall_vpn300:-:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:zywall_110_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:zywall_110_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:zywall_110_firmware:4.20:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:zywall_110_firmware:4.20:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:zywall_110_firmware:4.31:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:zywall_110_firmware:4.31:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:zywall_110_firmware:4.33\(aaaa.0\)c0:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:zywall_110_firmware:4.33\(aaaa.0\)c0:*:*:*:*:*:*:*
  • cpe:2.3:h:zyxel:zywall_110:-:*:*:*:*:*:*:*
    cpe:2.3:h:zyxel:zywall_110:-:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:zywall_310_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:zywall_310_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:zywall_310_firmware:4.20:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:zywall_310_firmware:4.20:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:zywall_310_firmware:4.31:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:zywall_310_firmware:4.31:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:zywall_310_firmware:4.33\(aaab.0\)c0:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:zywall_310_firmware:4.33\(aaab.0\)c0:*:*:*:*:*:*:*
  • cpe:2.3:h:zyxel:zywall_310:-:*:*:*:*:*:*:*
    cpe:2.3:h:zyxel:zywall_310:-:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:zywall_1100_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:zywall_1100_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:zywall_1100_firmware:4.20:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:zywall_1100_firmware:4.20:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:zywall_1100_firmware:4.31:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:zywall_1100_firmware:4.31:*:*:*:*:*:*:*
  • cpe:2.3:o:zyxel:zywall_1100_firmware:4.33\(aaac.0\)c0:*:*:*:*:*:*:*
    cpe:2.3:o:zyxel:zywall_1100_firmware:4.33\(aaac.0\)c0:*:*:*:*:*:*:*
  • cpe:2.3:h:zyxel:zywall_1100:-:*:*:*:*:*:*:*
    cpe:2.3:h:zyxel:zywall_1100:-:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2019-12583: 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-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...
  • CVE-2025-2126 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla and classified as critical. This issue affects some unknown processing of the...