LiveActive security incident?Get immediate response
CVE Record

CVE-2017-12104: An exploitable integer overflow exists in the way that the Blender open-source 3d creation suite v2.78c dra...

An exploitable integer overflow exists in the way that the Blender open-source 3d creation suite v2.78c draws a Particle object. A specially crafted .blend file can cause an integer overflow resulting in a buffer overflow which can allow for code execution under the context of the application. An attacker can convince a user to open the file or use the file as a library in order to trigger this vulnerability.

HighCVSS 8.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2017-12104 is a high-severity Blender file-handling flaw. A malicious .blend file can crash or potentially run code when opened in affected Blender 2.78c 32-bit, giving the attacker the same privileges as the application user.

Executive priority

Treat this as urgent where Blender processes external assets. The business risk is user-assisted code execution on creative workstations or render infrastructure, especially where downloaded or customer-supplied .blend files are opened.

Technical view

The issue is an integer overflow in how Blender 2.78c 32-bit draws a Particle object. A specially crafted .blend file can trigger integer overflow leading to buffer overflow and possible code execution in the application context. The bundle lists no CWE.

Likely exposure

Exposure is most likely on workstations or render workflows using Blender v2.78c 32-bit and opening untrusted .blend files or libraries. Other versions and 64-bit builds are not established by the provided sources.

Exploitation context

The vulnerability requires user interaction: opening a malicious .blend file or using it as a library. The CVSS vector indicates network deliverability, low attack complexity, no privileges required, and high confidentiality, integrity, and availability impact. KEV is false and the bundle gives no active exploitation evidence.

Researcher notes

Focus validation on affected version and architecture, not Blender generally. The provided evidence names Blender v2.78c 32-bit and Particle object drawing. Do not assume active exploitation, affected later versions, or exact fixed versions without vendor advisory confirmation.

Mitigation direction

  • Identify and retire Blender v2.78c 32-bit installations.
  • Apply Blender or distribution security updates using vendor guidance.
  • Prioritize systems that open third-party .blend assets.
  • Quarantine untrusted .blend files until affected systems are updated.
  • Use isolation for third-party assets in render or design workflows.

Validation and detection

  • Inventory Blender versions and architecture across endpoints and render nodes.
  • Confirm whether Blender v2.78c 32-bit is present.
  • Review asset ingestion workflows for untrusted .blend files.
  • Verify Debian or vendor security updates are installed where applicable.
  • Check endpoint controls for recent suspicious Blender crashes or child processes.
Prepared
Confidence
high
Sources
5

Public sources used

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.

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-2017-12104 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
High
CVSS
8.8 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:N/AC:L/PR:N/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
4Source 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
8.8CVSS 3.0HighCVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

8.8High
CVSS 3.0 vector shape for CVE-2017-12104Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:N/AC:L/PR:N/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
BlenderBlenderv2.78c (32-bit)Listed
Weakness

CWE details

No CWE listed

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