CVE-2023-25360

Public on

Last Modified: UTC

Description

The CVE Program describes this issue as:

A use-after-free vulnerability in WebCore::RenderLayer::renderer in WebKitGTK before 2.36.8 allows attackers to execute code remotely.

Additional information

  • Bugzilla 2175101: webkitgtk: heap-use-after-free in WebCore::RenderLayer::renderer()
  • CWE-94->CWE-416: Improper Control of Generation of Code ('Code Injection') leads to Use After Free
  • FAQ: Frequently asked questions about CVE-2023-25360

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).

CVSS v3 Score Breakdown
Red HatNVD

CVSS v3 Base Score

7.5

8.8

Attack Vector

Network

Network

Attack Complexity

High

Low

Privileges Required

None

None

User Interaction

Required

Required

Scope

Unchanged

Unchanged

Confidentiality Impact

High

High

Integrity Impact

High

High

Availability Impact

High

High

CVSS v3 Vector

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

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

Red Hat CVSS v3 Score Explanation

We consider the attack complexity is High instead of Low is due to a website needs to be created which adds an additional complexity. Also it would require a specific configuration such as javascript enabled in order to perform the attack. Different browsers and js dependency versions might be used, which could contribute to the complexity of the attack. It would also be needed to write a particular code which knows exactly where and how to write in order to exploit and run the arbitrary code successfully.

We consider the attack complexity is High instead of Low is due to a website needs to be created which adds an additional complexity. Also it would require a specific configuration such as javascript enabled in order to perform the attack. Different browsers and js dependency versions might be used, which could contribute to the complexity of the attack. It would also be needed to write a particular code which knows exactly where and how to write in order to exploit and run the arbitrary code successfully.

Understanding the Weakness (CWE)

CWE-94

Access Control

Technical Impact: Bypass Protection Mechanism

In some cases, injectable code controls authentication; this may lead to a remote vulnerability.

Access Control

Technical Impact: Gain Privileges or Assume Identity

Injected code can access resources that the attacker is directly prevented from accessing.

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

Code injection attacks can lead to loss of data integrity in nearly all cases as the control-plane data injected is always incidental to data recall or writing. Additionally, code injection can often result in the execution of arbitrary code.

Non-Repudiation

Technical Impact: Hide Activities

Often the actions performed by injected control code are unlogged.

CWE-416

Integrity

Technical Impact: Modify Memory

The use of previously freed memory may corrupt valid data, if the memory area in question has been allocated and used properly elsewhere.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If chunk consolidation occurs after the use of previously freed data, the process may crash when invalid data is used as chunk information.

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

If malicious data is entered before chunk consolidation can take place, it may be possible to take advantage of a write-what-where primitive to execute arbitrary code. If the newly allocated data happens to hold a class, in C++ for example, various function pointers may be scattered within the heap data. If one of these function pointers is overwritten with an address to valid shellcode, execution of arbitrary code can be achieved.

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.