CVE-2019-20659 Vulnerability Analysis & Exploit Details

CVE-2019-20659
Vulnerability Scoring

7.2
/10
Very High Risk

Highly exploitable, CVE-2019-20659 poses a critical security risk that could lead to severe breaches.

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: High
    High-level 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-20659 Details

Status: Analyzed

Last updated: 🕠 24 Aug 2020, 17:37 UTC
Originally published on: 🕖 15 Apr 2020, 19:15 UTC

Time between publication and last update: 130 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

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

CVE-2019-20659 Vulnerability Summary

CVE-2019-20659: Certain NETGEAR devices are affected by command injection by an authenticated user. This affects R6400v2 before 1.0.4.84, R6700 before 1.0.2.8, R6700v3 before 1.0.4.84, R6900 before 1.0.2.8, and R7900 before 1.0.3.10.

Assessing the Risk of CVE-2019-20659

Access Complexity Graph

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

The exploitability of CVE-2019-20659 is influenced by multiple factors. Security teams should analyze system configurations and apply appropriate countermeasures to mitigate threats.

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-20659, 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-20659, 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-2019-20659 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2019-20659 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2019-20659 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.177% (probability of exploit)

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

CVE-2019-20659 References

External References

CWE Common Weakness Enumeration

CWE-77

CAPEC Common Attack Pattern Enumeration and Classification

  • LDAP Injection CAPEC-136 An attacker manipulates or crafts an LDAP query for the purpose of undermining the security of the target. Some applications use user input to create LDAP queries that are processed by an LDAP server. For example, a user might provide their username during authentication and the username might be inserted in an LDAP query during the authentication process. An attacker could use this input to inject additional commands into an LDAP query that could disclose sensitive information. For example, entering a * in the aforementioned query might return information about all users on the system. This attack is very similar to an SQL injection attack in that it manipulates a query to gather additional information or coerce a particular return value.
  • Command Delimiters CAPEC-15 An attack of this type exploits a programs' vulnerabilities that allows an attacker's commands to be concatenated onto a legitimate command with the intent of targeting other resources such as the file system or database. The system that uses a filter or denylist input validation, as opposed to allowlist validation is vulnerable to an attacker who predicts delimiters (or combinations of delimiters) not present in the filter or denylist. As with other injection attacks, the attacker uses the command delimiter payload as an entry point to tunnel through the application and activate additional attacks through SQL queries, shell commands, network scanning, and so on.
  • IMAP/SMTP Command Injection CAPEC-183 An adversary exploits weaknesses in input validation on web-mail servers to execute commands on the IMAP/SMTP server. Web-mail servers often sit between the Internet and the IMAP or SMTP mail server. User requests are received by the web-mail servers which then query the back-end mail server for the requested information and return this response to the user. In an IMAP/SMTP command injection attack, mail-server commands are embedded in parts of the request sent to the web-mail server. If the web-mail server fails to adequately sanitize these requests, these commands are then sent to the back-end mail server when it is queried by the web-mail server, where the commands are then executed. This attack can be especially dangerous since administrators may assume that the back-end server is protected against direct Internet access and therefore may not secure it adequately against the execution of malicious commands.
  • Command Injection CAPEC-248 An adversary looking to execute a command of their choosing, injects new items into an existing command thus modifying interpretation away from what was intended. Commands in this context are often standalone strings that are interpreted by a downstream component and cause specific responses. This type of attack is possible when untrusted values are used to build these command strings. Weaknesses in input validation or command construction can enable the attack and lead to successful exploitation.
  • Manipulating Writeable Terminal Devices CAPEC-40 This attack exploits terminal devices that allow themselves to be written to by other users. The attacker sends command strings to the target terminal device hoping that the target user will hit enter and thereby execute the malicious command with their privileges. The attacker can send the results (such as copying /etc/passwd) to a known directory and collect once the attack has succeeded.
  • Exploiting Multiple Input Interpretation Layers CAPEC-43 An attacker supplies the target software with input data that contains sequences of special characters designed to bypass input validation logic. This exploit relies on the target making multiples passes over the input data and processing a "layer" of special characters with each pass. In this manner, the attacker can disguise input that would otherwise be rejected as invalid by concealing it with layers of special/escape characters that are stripped off by subsequent processing steps. The goal is to first discover cases where the input validation layer executes before one or more parsing layers. That is, user input may go through the following logic in an application: <parser1> --> <input validator> --> <parser2>. In such cases, the attacker will need to provide input that will pass through the input validator, but after passing through parser2, will be converted into something that the input validator was supposed to stop.
  • Manipulating Writeable Configuration Files CAPEC-75 Generally these are manually edited files that are not in the preview of the system administrators, any ability on the attackers' behalf to modify these files, for example in a CVS repository, gives unauthorized access directly to the application, the same as authorized users.
  • Manipulating Web Input to File System Calls CAPEC-76 An attacker manipulates inputs to the target software which the target software passes to file system calls in the OS. The goal is to gain access to, and perhaps modify, areas of the file system that the target software did not intend to be accessible.

Vulnerable Configurations

  • cpe:2.3:o:netgear:r6400_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6400_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6400_firmware:1.0.1.12:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6400_firmware:1.0.1.12:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6400_firmware:1.0.1.14:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6400_firmware:1.0.1.14:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6400_firmware:1.0.1.18:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6400_firmware:1.0.1.18:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6400_firmware:1.0.1.20:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6400_firmware:1.0.1.20:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6400_firmware:1.0.1.24:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6400_firmware:1.0.1.24:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6400_firmware:1.0.1.32:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6400_firmware:1.0.1.32:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6400_firmware:1.0.1.36:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6400_firmware:1.0.1.36:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6400_firmware:1.0.1.42:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6400_firmware:1.0.1.42:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6400_firmware:1.0.1.44:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6400_firmware:1.0.1.44:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6400_firmware:1.0.1.46:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6400_firmware:1.0.1.46:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6400_firmware:1.0.1.50:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6400_firmware:1.0.1.50:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6400_firmware:1.0.1.52:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6400_firmware:1.0.1.52:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6400_firmware:1.0.1.62:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6400_firmware:1.0.1.62:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6400_firmware:1.0.1.68:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6400_firmware:1.0.1.68:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6400_firmware:1.0.1.70:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6400_firmware:1.0.1.70:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6400_firmware:1.0.1.74:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6400_firmware:1.0.1.74:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6400_firmware:1.0.1.76:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6400_firmware:1.0.1.76:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6400_firmware:1.0.1.78:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6400_firmware:1.0.1.78:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6400_firmware:1.0.1.62_1.0.41:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6400_firmware:1.0.1.62_1.0.41:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6400_firmware:1.0.2.18:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6400_firmware:1.0.2.18:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6400_firmware:1.0.2.30:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6400_firmware:1.0.2.30:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6400_firmware:1.0.2.32:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6400_firmware:1.0.2.32:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6400_firmware:1.0.2.34:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6400_firmware:1.0.2.34:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6400_firmware:1.0.2.44:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6400_firmware:1.0.2.44:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6400_firmware:1.0.2.46:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6400_firmware:1.0.2.46:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6400_firmware:1.0.2.52:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6400_firmware:1.0.2.52:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6400_firmware:1.0.2.56:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6400_firmware:1.0.2.56:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6400_firmware:1.0.2.60:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6400_firmware:1.0.2.60:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6400_firmware:1.0.2.62:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6400_firmware:1.0.2.62:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6400_firmware:1.0.2.66:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6400_firmware:1.0.2.66:*:*:*:*:*:*:*
  • cpe:2.3:h:netgear:r6400:v2:*:*:*:*:*:*:*
    cpe:2.3:h:netgear:r6400:v2:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6700_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6700_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6700_firmware:1.0.0.26:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6700_firmware:1.0.0.26:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6700_firmware:1.0.1.14:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6700_firmware:1.0.1.14:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6700_firmware:1.0.1.16:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6700_firmware:1.0.1.16:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6700_firmware:1.0.1.20:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6700_firmware:1.0.1.20:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6700_firmware:1.0.1.22:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6700_firmware:1.0.1.22:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6700_firmware:1.0.1.26:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6700_firmware:1.0.1.26:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6700_firmware:1.0.1.30:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6700_firmware:1.0.1.30:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6700_firmware:1.0.1.36:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6700_firmware:1.0.1.36:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6700_firmware:1.0.1.44:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6700_firmware:1.0.1.44:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6700_firmware:1.0.1.46:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6700_firmware:1.0.1.46:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6700_firmware:1.0.1.48:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6700_firmware:1.0.1.48:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6700_firmware:1.0.2.6:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6700_firmware:1.0.2.6:*:*:*:*:*:*:*
  • cpe:2.3:h:netgear:r6700:-:*:*:*:*:*:*:*
    cpe:2.3:h:netgear:r6700:-:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6700_firmware:1.0.2.8:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6700_firmware:1.0.2.8:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6700_firmware:1.0.2.16:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6700_firmware:1.0.2.16:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6700_firmware:1.0.2.26:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6700_firmware:1.0.2.26:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6700_firmware:1.0.2.32:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6700_firmware:1.0.2.32:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6700_firmware:1.0.2.52:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6700_firmware:1.0.2.52:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6700_firmware:1.0.2.62:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6700_firmware:1.0.2.62:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6700_firmware:1.0.2.66:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6700_firmware:1.0.2.66:*:*:*:*:*:*:*
  • cpe:2.3:h:netgear:r6700:v3:*:*:*:*:*:*:*
    cpe:2.3:h:netgear:r6700:v3:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6900_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6900_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6900_firmware:1.0.1.14:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6900_firmware:1.0.1.14:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6900_firmware:1.0.1.16:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6900_firmware:1.0.1.16:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6900_firmware:1.0.1.20:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6900_firmware:1.0.1.20:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6900_firmware:1.0.1.22:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6900_firmware:1.0.1.22:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6900_firmware:1.0.1.26:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6900_firmware:1.0.1.26:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6900_firmware:1.0.1.28:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6900_firmware:1.0.1.28:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6900_firmware:1.0.1.30:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6900_firmware:1.0.1.30:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6900_firmware:1.0.1.34:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6900_firmware:1.0.1.34:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6900_firmware:1.0.1.44:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6900_firmware:1.0.1.44:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6900_firmware:1.0.1.46:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6900_firmware:1.0.1.46:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6900_firmware:1.0.1.48:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6900_firmware:1.0.1.48:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r6900_firmware:1.0.2.4:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r6900_firmware:1.0.2.4:*:*:*:*:*:*:*
  • cpe:2.3:h:netgear:r6900:-:*:*:*:*:*:*:*
    cpe:2.3:h:netgear:r6900:-:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r7900_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r7900_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r7900_firmware:1.0.1.8:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r7900_firmware:1.0.1.8:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r7900_firmware:1.0.1.12:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r7900_firmware:1.0.1.12:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r7900_firmware:1.0.1.14:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r7900_firmware:1.0.1.14:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r7900_firmware:1.0.1.16:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r7900_firmware:1.0.1.16:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r7900_firmware:1.0.1.18:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r7900_firmware:1.0.1.18:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r7900_firmware:1.0.1.26:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r7900_firmware:1.0.1.26:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r7900_firmware:1.0.2.4:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r7900_firmware:1.0.2.4:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r7900_firmware:1.0.2.10:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r7900_firmware:1.0.2.10:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r7900_firmware:1.0.2.16:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r7900_firmware:1.0.2.16:*:*:*:*:*:*:*
  • cpe:2.3:o:netgear:r7900_firmware:1.0.3.8:*:*:*:*:*:*:*
    cpe:2.3:o:netgear:r7900_firmware:1.0.3.8:*:*:*:*:*:*:*
  • cpe:2.3:h:netgear:r7900:-:*:*:*:*:*:*:*
    cpe:2.3:h:netgear:r7900:-:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2019-20659: 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...