CVE-2023-41570 Vulnerability Analysis & Exploit Details

CVE-2023-41570
Vulnerability Scoring

5.3
/10
Significant Risk

Security assessments indicate that CVE-2023-41570 presents a notable risk, potentially requiring prompt 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: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2023-41570 Details

Status: Modified

Last updated: 🕗 21 Nov 2024, 08:21 UTC
Originally published on: 🕚 14 Nov 2023, 23:15 UTC

Time between publication and last update: 372 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

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

CVE-2023-41570 Vulnerability Summary

CVE-2023-41570: MikroTik RouterOS v7.1 to 7.11 was discovered to contain incorrect access control mechanisms in place for the Rest API.

Assessing the Risk of CVE-2023-41570

Access Complexity Graph

The exploitability of CVE-2023-41570 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-41570

This vulnerability, CVE-2023-41570, requires a high level of attack complexity and low privileges, making it difficult but not impossible to exploit. Organizations should ensure robust security configurations to mitigate risks.

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-41570, 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-41570, 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-41570 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: None
    CVE-2023-41570 poses no threat to data integrity.
  • Availability: None
    CVE-2023-41570 does not impact system availability.

Exploit Prediction Scoring System (EPSS)

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

EPSS Score: 0.066% (probability of exploit)

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

CVE-2023-41570 References

External References

CWE Common Weakness Enumeration

CWE-284

CAPEC Common Attack Pattern Enumeration and Classification

  • Embedding Scripts within Scripts CAPEC-19 An adversary leverages the capability to execute their own script by embedding it within other scripts that the target software is likely to execute due to programs' vulnerabilities that are brought on by allowing remote hosts to execute scripts.
  • Malicious Logic Insertion CAPEC-441 An adversary installs or adds malicious logic (also known as malware) into a seemingly benign component of a fielded system. This logic is often hidden from the user of the system and works behind the scenes to achieve negative impacts. With the proliferation of mass digital storage and inexpensive multimedia devices, Bluetooth and 802.11 support, new attack vectors for spreading malware are emerging for things we once thought of as innocuous greeting cards, picture frames, or digital projectors. This pattern of attack focuses on systems already fielded and used in operation as opposed to systems and their components that are still under development and part of the supply chain.
  • Modification of Windows Service Configuration CAPEC-478 An adversary exploits a weakness in access control to modify the execution parameters of a Windows service. The goal of this attack is to execute a malicious binary in place of an existing service.
  • Malicious Root Certificate CAPEC-479 An adversary exploits a weakness in authorization and installs a new root certificate on a compromised system. Certificates are commonly used for establishing secure TLS/SSL communications within a web browser. When a user attempts to browse a website that presents a certificate that is not trusted an error message will be displayed to warn the user of the security risk. Depending on the security settings, the browser may not allow the user to establish a connection to the website. Adversaries have used this technique to avoid security warnings prompting users when compromised systems connect over HTTPS to adversary controlled web servers that spoof legitimate websites in order to collect login credentials.
  • Intent Spoof CAPEC-502 An adversary, through a previously installed malicious application, issues an intent directed toward a specific trusted application's component in an attempt to achieve a variety of different objectives including modification of data, information disclosure, and data injection. Components that have been unintentionally exported and made public are subject to this type of an attack. If the component trusts the intent's action without verififcation, then the target application performs the functionality at the adversary's request, helping the adversary achieve the desired negative technical impact.
  • WebView Exposure CAPEC-503 An adversary, through a malicious web page, accesses application specific functionality by leveraging interfaces registered through WebView's addJavascriptInterface API. Once an interface is registered to WebView through addJavascriptInterface, it becomes global and all pages loaded in the WebView can call this interface.
  • Data Injected During Configuration CAPEC-536 An attacker with access to data files and processes on a victim's system injects malicious data into critical operational data during configuration or recalibration, causing the victim's system to perform in a suboptimal manner that benefits the adversary.
  • Incomplete Data Deletion in a Multi-Tenant Environment CAPEC-546 An adversary obtains unauthorized information due to insecure or incomplete data deletion in a multi-tenant environment. If a cloud provider fails to completely delete storage and data from former cloud tenants' systems/resources, once these resources are allocated to new, potentially malicious tenants, the latter can probe the provided resources for sensitive information still there.
  • Install New Service CAPEC-550 When an operating system starts, it also starts programs called services or daemons. Adversaries may install a new service which will be executed at startup (on a Windows system, by modifying the registry). The service name may be disguised by using a name from a related operating system or benign software. Services are usually run with elevated privileges.
  • Modify Existing Service CAPEC-551 When an operating system starts, it also starts programs called services or daemons. Modifying existing services may break existing services or may enable services that are disabled/not commonly used.
  • Install Rootkit CAPEC-552 An adversary exploits a weakness in authentication to install malware that alters the functionality and information provide by targeted operating system API calls. Often referred to as rootkits, it is often used to hide the presence of programs, files, network connections, services, drivers, and other system components.
  • Replace File Extension Handlers CAPEC-556 When a file is opened, its file handler is checked to determine which program opens the file. File handlers are configuration properties of many operating systems. Applications can modify the file handler for a given file extension to call an arbitrary program when a file with the given extension is opened.
  • Replace Trusted Executable CAPEC-558 An adversary exploits weaknesses in privilege management or access control to replace a trusted executable with a malicious version and enable the execution of malware when that trusted executable is called.
  • Modify Shared File CAPEC-562 An adversary manipulates the files in a shared location by adding malicious programs, scripts, or exploit code to valid content. Once a user opens the shared content, the tainted content is executed.
  • Add Malicious File to Shared Webroot CAPEC-563 An adversaries may add malicious content to a website through the open file share and then browse to that content with a web browser to cause the server to execute the content. The malicious content will typically run under the context and permissions of the web server process, often resulting in local system or administrative privileges depending on how the web server is configured.
  • Run Software at Logon CAPEC-564 Operating system allows logon scripts to be run whenever a specific user or users logon to a system. If adversaries can access these scripts, they may insert additional code into the logon script. This code can allow them to maintain persistence or move laterally within an enclave because it is executed every time the affected user or users logon to a computer. Modifying logon scripts can effectively bypass workstation and enclave firewalls. Depending on the access configuration of the logon scripts, either local credentials or a remote administrative account may be necessary.
  • Disable Security Software CAPEC-578 An adversary exploits a weakness in access control to disable security tools so that detection does not occur. This can take the form of killing processes, deleting registry keys so that tools do not start at run time, deleting log files, or other methods.

Vulnerable Configurations

  • cpe:2.3:o:mikrotik:routeros:7.1:-:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.1:-:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.1.1:*:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.1.1:*:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.1.2:*:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.1.2:*:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.1.3:*:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.1.3:*:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.1.4:*:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.1.4:*:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.1.5:*:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.1.5:*:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.1:beta1:*:*:*:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.1:beta1:*:*:*:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.1:beta2:*:*:*:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.1:beta2:*:*:*:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.2:-:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.2:-:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.2.1:*:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.2.1:*:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.2.2:*:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.2.2:*:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.2.3:*:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.2.3:*:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.2:rc1:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.2:rc1:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.2:rc2:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.2:rc2:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.2:rc3:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.2:rc3:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.2:rc4:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.2:rc4:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.2:rc5:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.2:rc5:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.2:rc6:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.2:rc6:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.2:rc7:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.2:rc7:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.3:-:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.3:-:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.3.1:*:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.3.1:*:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.3:rc1:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.3:rc1:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.3:rc2:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.3:rc2:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.3:beta33:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.3:beta33:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.3:beta34:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.3:beta34:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.3:beta37:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.3:beta37:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.3:beta40:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.3:beta40:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.4:-:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.4:-:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.4.1:*:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.4.1:*:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.4:rc1:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.4:rc1:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.4:rc2:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.4:rc2:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.4:beta4:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.4:beta4:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.4:beta5:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.4:beta5:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.5:*:*:*:*:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.5:*:*:*:*:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.5:-:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.5:-:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.5:rc1:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.5:rc1:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.5:rc2:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.5:rc2:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.5:beta4:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.5:beta4:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.5:beta5:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.5:beta5:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.5:beta8:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.5:beta8:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.5:beta11:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.5:beta11:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.6:-:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.6:-:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.6:rc1:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.6:rc1:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.6:rc2:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.6:rc2:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.6:rc3:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.6:rc3:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.6:beta4:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.6:beta4:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.6:beta6:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.6:beta6:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.6:beta7:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.6:beta7:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.6:beta8:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.6:beta8:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.6:beta10:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.6:beta10:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.7:-:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.7:-:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.7:rc1:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.7:rc1:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.7:rc2:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.7:rc2:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.7:rc3:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.7:rc3:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.7:rc4:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.7:rc4:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.7:rc5:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.7:rc5:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.7:beta3:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.7:beta3:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.7:beta4:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.7:beta4:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.7:beta6:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.7:beta6:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.7:beta8:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.7:beta8:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.7:beta9:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.7:beta9:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.8:-:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.8:-:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.8:rc1:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.8:rc1:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.8:rc2:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.8:rc2:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.8:rc3:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.8:rc3:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.8:beta2:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.8:beta2:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.8:beta3:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.8:beta3:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.9:-:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.9:-:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.9.1:*:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.9.1:*:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.9.2:*:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.9.2:*:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.9:rc1:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.9:rc1:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.9:rc2:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.9:rc2:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.9:rc3:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.9:rc3:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.9:rc4:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.9:rc4:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.9:rc5:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.9:rc5:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.9:beta4:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.9:beta4:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.10:-:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.10:-:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.10.1:*:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.10.1:*:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.10.2:*:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.10.2:*:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.10:rc1:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.10:rc1:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.10:rc3:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.10:rc3:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.10:rc4:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.10:rc4:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.10:rc5:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.10:rc5:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.10:rc6:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.10:rc6:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.10:beta5:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.10:beta5:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.10:beta8:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.10:beta8:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.11:-:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.11:-:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.11.1:*:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.11.1:*:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.11.2:*:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.11.2:*:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.11:rc1:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.11:rc1:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.11:rc2:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.11:rc2:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.11:rc3:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.11:rc3:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.11:rc4:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.11:rc4:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.11:beta2:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.11:beta2:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.11:beta4:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.11:beta4:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.11:beta5:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.11:beta5:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.11:beta6:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.11:beta6:*:*:-:*:*:*
  • cpe:2.3:o:mikrotik:routeros:7.11:beta7:*:*:-:*:*:*
    cpe:2.3:o:mikrotik:routeros:7.11:beta7:*:*:-:*:*:*

Protect Your Infrastructure against CVE-2023-41570: 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-2122 – A vulnerability classified as problematic was found in Thinkware Car Dashcam F800 Pro up to 20250226. Affected by this vulnerability is an unknown ...
  • CVE-2025-27636 – Bypass/Injection vulnerability in Apache Camel. This issue affects Apache Camel: from 4.10.0 through <= 4.10.1, from 4.8.0 through <= 4.8.4, from ...
  • CVE-2025-2121 – A vulnerability classified as critical has been found in Thinkware Car Dashcam F800 Pro up to 20250226. Affected is an unknown function of the comp...
  • CVE-2025-2120 – A vulnerability was found in Thinkware Car Dashcam F800 Pro up to 20250226. It has been rated as problematic. This issue affects some unknown proce...
  • CVE-2025-2119 – A vulnerability was found in Thinkware Car Dashcam F800 Pro up to 20250226. It has been declared as problematic. This vulnerability affects unknown...