LiveActive security incident?Get immediate response
CVE Record

CVE-2015-5297: An integer overflow issue has been reported in the general_composite_rect() function in pixman prior to ver...

An integer overflow issue has been reported in the general_composite_rect() function in pixman prior to version 0.32.8. An attacker could exploit this issue to cause an application using pixman to crash or, potentially, execute arbitrary code.

MediumCVSS 6.7Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Pixman, a graphics library used by applications for image compositing, had an integer overflow before version 0.32.8. A local attacker with some privileges and user interaction might crash an affected application or potentially run code. The source bundle does not show active exploitation.

Executive priority

Treat this as moderate priority unless pixman is present in high-risk user-facing workflows. The risk is constrained by local access, high complexity, and user interaction, but the potential impact includes code execution.

Technical view

CVE-2015-5297 is a CWE-190 integer overflow in pixman's general_composite_rect() before 0.32.8. The CVSS 3.0 vector is local, high complexity, low privileges, user interaction required, unchanged scope, with high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely on systems running applications linked against pixman versions before 0.32.8. Prioritize endpoints, workstations, or servers with graphical rendering components where untrusted or user-supplied content can reach pixman-backed compositing paths.

Exploitation context

The provided CVE data says exploitation could crash an application or potentially execute arbitrary code. KEV is false, and the source bundle does not cite active exploitation, public exploit maturity, or a reliable attack chain.

Researcher notes

The bundle identifies the vulnerable function and integer overflow class but provides limited implementation detail. Validate exposure through package versions and linkage rather than assuming every graphical application is reachable. Do not claim exploitation without new evidence.

Mitigation direction

  • Inventory installed pixman versions across managed systems.
  • Update pixman to 0.32.8 or a vendor-patched package.
  • Check Red Hat and upstream freedesktop guidance for package-specific fixes.
  • Prioritize systems processing untrusted graphical or document content.
  • Restart dependent applications after updating shared libraries.

Validation and detection

  • Confirm pixman package versions are not earlier than 0.32.8.
  • Verify vendor advisory status for each affected operating system build.
  • Identify applications dynamically linked to pixman on critical systems.
  • Review crash telemetry for pixman-related rendering failures.
  • Record exceptions where vendor guidance is unavailable or packages are unsupported.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-190: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2015-5297 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.7 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.7CVSS 3.0MediumCVSS:3.0/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H0.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

6.7Medium
CVSS 3.0 vector shape for CVE-2015-5297Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
The pixman Projectpixman0.32.8Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-190 · source CWE mapping

Integer Overflow or Wraparound

Integer Overflow or Wraparound represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.