CVE-2025-11277

Description

A flaw was found in the assimp library. Processing a specially crafted input file can trigger a heap-based buffer overflow due to an integer overflow when reading texture data, causing a crash to the application linked to the library and resulting in a denial of service.

Statement

To exploit this issue, an attacker needs to be able to process a specially crafted input file with the application linked to the assimp library. Additionally, this issue can cause an out-of-bounds write of only 1 byte, limiting the impact of this vulnerability, potentially resulting only in a denial of service. Due to these reasons, this flaw has been rated with a moderate severity.

Mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert: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 HatNVDcve.org
Base Score6.17.85.3
Attack VectorLocalLocalLocal
Attack ComplexityLowLowLow
Privileges RequiredLowLowLow
User InteractionNoneNoneNone
ScopeUnchangedUnchangedUnchanged
ConfidentialityNoneHighLow
Integrity ImpactLowHighLow
Availability ImpactHighHighLow

Vector

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

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

cve.org: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RC:R

Red Hat CVSS v3 Score Explanation

This issue can cause an out-of-bounds write of only 1 byte, limiting the security impact of this vulnerability to a denial of service. To reflect this condition, the confidentiality metric is set to none and the integrity metric is set to low.

Understanding the Weakness (CWE)

Integrity

Technical Impact: Modify Memory; Execute Unauthorized Code or Commands

Write operations could cause memory corruption. In some cases, an adversary can modify control data such as return addresses in order to execute unexpected code.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

Attempting to access out-of-range, invalid, or unauthorized memory could cause the product to crash.

Other

Technical Impact: Unexpected State

Subsequent write operations can produce undefined or unexpected results.

Frequently Asked Questions

Want to get errata notifications? Sign up here.