LiveActive security incident?Get immediate response
CVE Record

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

An exploitable integer overflow exists in the way that the Blender open-source 3d creation suite v2.78c applies a particular object modifier to a Mesh. 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

A malicious Blender project file can make affected 32-bit Blender 2.78c run attacker-controlled code when a user opens it or uses it as a library. The main business risk is compromise of workstations that handle externally supplied 3D assets.

Executive priority

Prioritize remediation where Blender handles third-party assets or email/downloaded project files. This is high impact but requires user interaction, so urgency depends on asset-ingestion exposure.

Technical view

CVE-2017-12105 is an integer overflow in Blender 2.78c 32-bit when applying a specific object modifier to a Mesh. A crafted .blend file can turn this into a buffer overflow and code execution in the Blender application context.

Likely exposure

Exposure is most likely on workstations, render nodes, or asset-review systems still running Blender v2.78c 32-bit and opening untrusted .blend files. The bundle does not identify other affected versions.

Exploitation context

The source bundle describes user-assisted exploitation through opening a crafted .blend file or using it as a library. KEV is false, and the provided sources do not state active exploitation in the wild.

Researcher notes

The bundle attributes the issue to Talos and Debian advisories but does not include CWE, detailed modifier name, exploit maturity, or a universal upstream fixed version. Do not broaden affected versions beyond Blender v2.78c 32-bit without additional vendor evidence.

Mitigation direction

  • Inventory Blender installations and identify Blender v2.78c 32-bit.
  • Apply Debian Blender security updates where Debian packages are used.
  • For non-Debian deployments, check Blender or vendor guidance for fixed builds.
  • Avoid opening untrusted .blend files on production workstations.
  • Use sandboxed or isolated environments for external asset review.

Validation and detection

  • Confirm Blender version and 32-bit versus 64-bit architecture on endpoints.
  • Verify Debian DSA-4248 or DLA-1465-1 updates are applied where relevant.
  • Review pipelines that import .blend files from external parties.
  • Confirm endpoint controls quarantine unexpected .blend attachments or downloads.
  • Check whether render nodes process user-supplied Blender libraries.
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-12105 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-12105Attack 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.