CVE-2017-18347 Vulnerability Analysis & Exploit Details

CVE-2017-18347
Vulnerability Scoring

4.6
/10
Medium Risk

The vulnerability CVE-2017-18347 could compromise system integrity but typically requires user interaction to be exploited.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Physical
    Physical access is required to exploit this vulnerability.
  • 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-2017-18347 Details

Status: Modified

Last updated: 🕒 21 Nov 2024, 03:19 UTC
Originally published on: 🕒 12 Sep 2018, 15:29 UTC

Time between publication and last update: 2261 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

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

CVE-2017-18347 Vulnerability Summary

CVE-2017-18347: Incorrect access control in RDP Level 1 on STMicroelectronics STM32F0 series devices allows physically present attackers to extract the device's protected firmware via a special sequence of Serial Wire Debug (SWD) commands because there is a race condition between full initialization of the SWD interface and the setup of flash protection.

Assessing the Risk of CVE-2017-18347

Access Complexity Graph

The exploitability of CVE-2017-18347 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-2017-18347

With low attack complexity and no required privileges, CVE-2017-18347 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-2017-18347, 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-2017-18347, 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-2017-18347 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: None
    CVE-2017-18347 poses no threat to data integrity.
  • Availability: None
    CVE-2017-18347 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.139% (probability of exploit)

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

CVE-2017-18347 References

External References

CWE Common Weakness Enumeration

CWE-362

CAPEC Common Attack Pattern Enumeration and Classification

  • Leveraging Race Conditions CAPEC-26 The adversary targets a race condition occurring when multiple processes access and manipulate the same resource concurrently, and the outcome of the execution depends on the particular order in which the access takes place. The adversary can leverage a race condition by "running the race", modifying the resource and modifying the normal execution flow. For instance, a race condition can occur while accessing a file: the adversary can trick the system by replacing the original file with their version and cause the system to read the malicious file.
  • Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions CAPEC-29 This attack targets a race condition occurring between the time of check (state) for a resource and the time of use of a resource. A typical example is file access. The adversary can leverage a file access race condition by "running the race", meaning that they would modify the resource between the first time the target program accesses the file and the time the target program uses the file. During that period of time, the adversary could replace or modify the file, causing the application to behave unexpectedly.

Vulnerable Configurations

  • cpe:2.3:o:st:stm32f071rb_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f071rb_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f071rb:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f071rb:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f071v8_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f071v8_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f071v8:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f071v8:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f071vb_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f071vb_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f071vb:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f071vb:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f072c8_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f072c8_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f072c8:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f072c8:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f072cb_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f072cb_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f072cb:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f072cb:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f072r8_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f072r8_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f072r8:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f072r8:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f072rb_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f072rb_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f072rb:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f072rb:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f072v8_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f072v8_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f072v8:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f072v8:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f072vb_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f072vb_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f072vb:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f072vb:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f078cb_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f078cb_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f078cb:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f078cb:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f078rb_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f078rb_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f078rb:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f078rb:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f078vb_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f078vb_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f078vb:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f078vb:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f091cb_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f091cb_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f091cb:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f091cb:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f091cc_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f091cc_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f091cc:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f091cc:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f091rb_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f091rb_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f091rb:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f091rb:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f091rc_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f091rc_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f091rc:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f091rc:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f091vb_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f091vb_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f091vb:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f091vb:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f091vc_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f091vc_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f091vc:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f091vc:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f098cc_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f098cc_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f098cc:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f098cc:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f098rc_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f098rc_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f098rc:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f098rc:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f098vc_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f098vc_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f098vc:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f098vc:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f070c6_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f070c6_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f070c6:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f070c6:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f070cb_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f070cb_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f070cb:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f070cb:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f070f6_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f070f6_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f070f6:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f070f6:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f070rb_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f070rb_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f070rb:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f070rb:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f071c8_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f071c8_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f071c8:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f071c8:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f071cb_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f071cb_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f071cb:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f071cb:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f051t8_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f051t8_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f051t8:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f051t8:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f058c8_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f058c8_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f058c8:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f058c8:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f058r8_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f058r8_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f058r8:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f058r8:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f058t8_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f058t8_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f058t8:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f058t8:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f051k4_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f051k4_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f051k4:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f051k4:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f051k6_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f051k6_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f051k6:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f051k6:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f051k8_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f051k8_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f051k8:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f051k8:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f051r4_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f051r4_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f051r4:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f051r4:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f051r6_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f051r6_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f051r6:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f051r6:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f051r8_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f051r8_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f051r8:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f051r8:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f042t6_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f042t6_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f042t6:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f042t6:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f048c6_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f048c6_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f048c6:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f048c6:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f048g6_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f048g6_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f048g6:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f048g6:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f048t6_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f048t6_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f048t6:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f048t6:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f051c4_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f051c4_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f051c4:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f051c4:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f051c6_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f051c6_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f051c6:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f051c6:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f051c8_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f051c8_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f051c8:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f051c8:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f042f4_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f042f4_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f042f4:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f042f4:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f042f6_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f042f6_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f042f6:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f042f6:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f042g4_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f042g4_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f042g4:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f042g4:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f042g6_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f042g6_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f042g6:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f042g6:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f042k4_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f042k4_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f042k4:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f042k4:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f042k6_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f042k6_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f042k6:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f042k6:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f038c6_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f038c6_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f038c6:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f038c6:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f038e6_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f038e6_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f038e6:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f038e6:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f038f6_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f038f6_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f038f6:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f038f6:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f038g6_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f038g6_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f038g6:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f038g6:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f038k6_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f038k6_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f038k6:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f038k6:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f042c4_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f042c4_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f042c4:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f042c4:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f042c6_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f042c6_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f042c6:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f042c6:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f031e6_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f031e6_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f031e6:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f031e6:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f031f4_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f031f4_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f031f4:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f031f4:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f031f6_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f031f6_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f031f6:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f031f6:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f031g4_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f031g4_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f031g4:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f031g4:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f031g6_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f031g6_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f031g6:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f031g6:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f031k4_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f031k4_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f031k4:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f031k4:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f030f4_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f030f4_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f030f4:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f030f4:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f030k6_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f030k6_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f030k6:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f030k6:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f030r8_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f030r8_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f030r8:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f030r8:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f030rc_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f030rc_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f030rc:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f030rc:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f031c4_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f031c4_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f031c4:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f031c4:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f031c6_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f031c6_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f031c6:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f031c6:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f030c6_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f030c6_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f030c6:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f030c6:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f030c8_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f030c8_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f030c8:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f030c8:-:*:*:*:*:*:*:*
  • cpe:2.3:o:st:stm32f030cc_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:st:stm32f030cc_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:st:stm32f030cc:-:*:*:*:*:*:*:*
    cpe:2.3:h:st:stm32f030cc:-:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2017-18347: 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...