CVE-2018-21232

VEX

Public on

Last modified: UTC

CVE-2018-21232 does not affect Red Hat software

Description

From CVE.org

re2c before 2.0 has uncontrolled recursion that causes stack consumption in find_fixed_tags.

Statement

This vulnerability does not affect any version of re2c shipped with any version of Red Hat Enterprise Linux.

This vulnerability does not affect any version of re2c shipped with any version of Red Hat Enterprise Linux.

Additional information

  • Bugzilla 1837650: re2c: uncontrolled recursion that causes stack consumption in find_fixed_tags
  • CWE-674: Uncontrolled Recursion
  • FAQ: Frequently asked questions about CVE-2018-21232

Common Vulnerability Scoring System (CVSS) Score Details

Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown
Red HatNVD

CVSS v3 Base Score

5.5

5.5

Attack Vector

Local

Local

Attack Complexity

Low

Low

Privileges Required

None

None

User Interaction

Required

Required

Scope

Unchanged

Unchanged

Confidentiality Impact

None

None

Integrity Impact

None

None

Availability Impact

High

High

CVSS v3 Vector

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

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

Understanding the Weakness (CWE)

CWE-674

Availability

Technical Impact:DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory)

Resources including CPU, memory, and stack memory could be rapidly consumed or exhausted, eventually leading to an exit or crash.

Confidentiality

Technical Impact:Read Application Data

In some cases, an application's interpreter might kill a process or thread that appears to be consuming too much resources, such as with PHP's memory_limit setting. When the interpreter kills the process/thread, it might report an error containing detailed information such as the application's installation path.

Frequently Asked Questions

Why is Red Hat's CVSS v3 score or Impact different from other vendors?

My product is listed as "Under investigation" or "Affected", when will Red Hat release a fix for this vulnerability?

What can I do if my product is listed as "Will not fix"?

What can I do if my product is listed as "Fix deferred"?

What is a mitigation?

I have a Red Hat product but it is not in the above list, is it affected?

Why is my security scanner reporting my product as vulnerable to this vulnerability even though my product version is fixed or not affected?

Want to get errata notifications? Sign up here.