Renderer crash via premature material property assignment
Published Jun 25, 2025 · Updated Jun 25, 2025
Null pointer dereference in vkoskiv c-ray 1.1 allows remote attackers to crash the renderer via a crafted Wavefront material file. The parse_mtllib function leaves current as NULL until a material is created, then writes current->IOR when an Ni directive appears first. Processing an attacker-controlled material file is required, and the resulting dereference terminates the rendering process.
Summary
What happened
Null pointer dereference in vkoskiv c-ray 1.1 allows remote attackers to crash the renderer via a crafted Wavefront material file. The parse_mtllib function leaves current as NULL until a material is created, then writes current->IOR when an Ni directive appears first. Processing an attacker-controlled material file is required, and the resulting dereference terminates the rendering process.
The record
- CVE
- CVE-2025-45332
- Published
- Jun 25, 2025
- Updated
- Jun 25, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 25, 2025CVE publishedPublication date reported by the CVE source.
- Jun 25, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo