☠️
EXFILTRATING
DATA...
01010111 10110010 00101001 11000110 01101100 10011011 00010001 11100101 01000010 10101111
[ <-- BACK_TO_SEARCH ]
[ VENDOR STATS ]
CVSS: 7.8 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H 🐛 CWE-843
👁️
Common Weakness Enumeration - Identifies the specific category of software weakness or flaw.

CVE-2025-8002

CVE-2025-8002 Remote Code Execution in Ashlar-vellum
📅 PUBLISHED: 2025-09-17 20:53 UTC 🔄 UPDATED: 2026-09-26 06:30 UTC
[ ZERO-DAY / UNPATCHED ] [ DEFENSE PATCH ↓ ]
💣 PoC: Public
👁️
Proof of Concept - Indicates if functional exploit code is publicly available, drastically increasing the risk of immediate attacks.
🎯 EPSS: 0.05%
👁️
0.05% probability
1.2× above the median CVE
Tier: LOW
30-day exploitation window · FIRST.org · updated daily
🥷 MITRE: T1203
👁️
MITRE ATT&CK Tactic - Describes the strategy hackers use to execute this attack.
VULNERABLE: UNKNOWN / CHECK VENDOR
CVSS VECTOR BREAKDOWN 7.8
AV: L Attack Vector Local
AC: L Attack Complexity Low
PR: N Privileges Required None
UI: R User Interaction Required
S: U Scope Unchanged
C: H Confidentiality High
I: H Integrity High
A: H Availability High
7.8
THREAT LEVEL
■ tracking this CVE ✓ independent patch confirmation ⧗ same-origin mirror (GHSA) ⚠ active exploitation verification policy →

Executive Summary

CVE-2025-8002 is a critical type confusion vulnerability in Ashlar-Vellum Cobalt, a CAD/CAM software application. The flaw resides in the parsing of CO files, where improper validation of user-supplied data can lead to a type confusion condition. An attacker can exploit this by convincing a user to open a malicious CO file or visit a malicious page, resulting in remote code execution in the context of the current process. With a CVSS score of 7.8, this vulnerability poses a significant risk to users of Ashlar-Vellum Cobalt, especially in environments where untrusted files are processed. No public exploit or patch is currently available, making detection and mitigation critical.

⚡ AUTOMATE YOUR CVE INTELLIGENCE

This record — and 170,000+ others — are available via the ValtersIT API. One endpoint replaces five: NVD + GitHub CVE + CISA KEV + EPSS + Nuclei + Exploit-DB, unified.

›Patch confidence — UNVERIFIED to CONFIRMED, cross-referenced NVD + RHSA + Debian
›Exploit & PoC — poc_status, poc_url, has_exploit. Not in NVD.
›Shodan dorks — ready-made queries to find exposed vulnerable systems
›Detection rules — YARA · Wazuh · Elastic (all plans) · Sigma (Pro)
›pending_fields — know exactly which of 7 fields NVD hasn't processed yet
›Free backfill — data incomplete when you paid? Re-check within 30 days = 0 credits
PAYG €0.08/lookup Standard €19/mo (was €29) · 5k credits Pro €65/mo (was €99) · 20k credits FOUNDING PRICE · LOCKED FOR LIFE · ENDS 31 DEC 2026
[ FROM €19/MO ]
Free sandbox key available
No signup required

CVSS Breakdown & Threat Level

  • CVSS Score: 7.8 (High)
  • Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
  • Attack Vector: Local (requires user interaction)
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: Required (victim must open a malicious file or page)
  • Scope: Unchanged
  • Confidentiality Impact: High
  • Integrity Impact: High
  • Availability Impact: High

Threat Level: High. Exploitation leads to full compromise of the affected system, with no privileges required and low attack complexity.

Deep Dive & Mechanics

The vulnerability is a type confusion error in the CO file parser of Ashlar-Vellum Cobalt. Type confusion occurs when a program uses a variable or object as a different type than intended, often due to insufficient validation of input data. In this case, the parser fails to properly validate the type of data within a CO file, allowing an attacker to craft a file that causes the parser to misinterpret data as a different type. This can lead to memory corruption and, ultimately, arbitrary code execution.

The specific flaw is triggered during the parsing of CO files, which are native to Ashlar-Vellum Cobalt. The lack of proper validation allows an attacker to supply data that causes the parser to treat a pointer or object as a different type, leading to out-of-bounds memory access or function pointer overwriting. This can be leveraged to execute arbitrary code in the context of the current process, typically with the same privileges as the user running the application.

Vulnerable vs. Patched Code

No patched version is available, and the vendor has not released a fix. The vulnerable code is in the CO file parsing routine, where type validation is missing. A hypothetical patch would involve adding strict type checks before processing data from the file, ensuring that each data structure is validated against expected types and sizes.

Vulnerable Code (Conceptual):

void parse_co_file(FILE *file) {
    COHeader header;
    fread(&header, sizeof(header), 1, file);
    // No type validation
    process_data(header.data_type, header.data);
}

Patched Code (Conceptual):

void parse_co_file(FILE *file) {
    COHeader header;
    if (fread(&header, sizeof(header), 1, file) != 1) {
        return; // Error handling
    }
    // Validate data type
    if (header.data_type != EXPECTED_TYPE) {
        return; // Reject invalid type
    }
    process_data(header.data_type, header.data);
}

Exploitation & Lab Setup

Red Team (Exploitation)

Lab Setup:

  • Target: Windows 10/11 with Ashlar-Vellum Cobalt installed (any version).
  • Attacker: Kali Linux or any system with a Python environment.
  • Tools: Python 3, Metasploit (optional), custom exploit script.

Exploitation Steps:

  1. Craft Malicious CO File: Create a CO file that triggers the type confusion. This involves manipulating the file header to specify an invalid data type, causing the parser to misinterpret memory.
  2. Deliver Payload: Use social engineering to deliver the file (e.g., email attachment, download link).
  3. Execute: When the victim opens the file in Cobalt, the type confusion leads to arbitrary code execution.

Example Exploit Script (Conceptual):

import struct

def create_malicious_co():
    # Craft a CO file with type confusion
    header = b'\x00' * 16  # Placeholder header
    # Overwrite data type field to cause confusion
    data_type = struct.pack('<I', 0xFFFFFFFF)  # Invalid type
    payload = b'\x90' * 1000  # NOP sled + shellcode
    with open('malicious.co', 'wb') as f:
        f.write(header + data_type + payload)

create_malicious_co()

Blue Team (Detection & Defense)

Detection:

  • Monitor for unusual CO file downloads or attachments.
  • Use endpoint detection and response (EDR) to detect memory corruption or code injection.
  • Implement file reputation checks for CO files.

Defense:

  • Restrict execution of Ashlar-Vellum Cobalt in sandboxed environments.
  • Use application whitelisting to prevent untrusted files from being opened.
  • Educate users about the risks of opening unsolicited files.

Indicators of Compromise (IOCs)

  • File Hashes: (None available publicly; generate upon discovery)
  • Network Indicators: Connections to unknown IPs or domains after exploitation.
  • Process Behavior: Cobalt.exe spawning child processes (e.g., cmd.exe, powershell.exe).
  • Registry Changes: Modifications to startup keys or COM objects.
  • File Artifacts: Malicious CO files with unusual headers or large sizes.

Detection Engineering

YARA Rule

rule CVE_2025_8002_Type_Confusion {
    meta:
        description = "Detects malicious CO files exploiting CVE-2025-8002"
        author = "Valters IT"
        date = "2025-04-10"
    strings:
        $co_magic = { 43 4F 46 46 } // "COFF" magic bytes (example)
        $suspicious_type = { FF FF FF FF } // Invalid type field
    condition:
        $co_magic at 0 and $suspicious_type
}

Sigma Rule

title: CVE-2025-8002 Ashlar-Vellum Cobalt CO File Type Confusion
id: 12345678-1234-1234-1234-123456789012
status: experimental
description: Detects attempts to exploit CVE-2025-8002 via malicious CO files
author: Valters IT
date: 2025-04-10
logsource:
    category: file_event
    product: windows
detection:
    selection:
        Image|endswith: '\Cobalt.exe'
        TargetFilename|endswith: '.co'
    condition: selection
falsepositives:
    - Legitimate CO files from trusted sources
level: high

Suricata Rule

alert tcp $HOME_NET any -> $EXTERNAL_NET any (msg:"CVE-2025-8002 Ashlar-Vellum Cobalt CO File Download"; flow:to_server,established; content:"|43 4F 46 46|"; depth:4; classtype:attempted-user; sid:1000001; rev:1;)

Remediation & Mitigation

  • Immediate: Disable or restrict the use of Ashlar-Vellum Cobalt until a patch is available.
  • Workaround: Use file scanning tools to inspect CO files before opening.
  • Long-term: Monitor vendor channels for an official patch and apply it promptly.
  • Compensating Controls: Implement application sandboxing, endpoint protection, and user awareness training.

Valters IT
DevSecOps & Cyber Threat Intelligence

👁️ SHODAN DORKS (THREAT HUNTING)

What is this? Security researchers use these exact search queries on Shodan.io (a search engine for internet-connected devices) to find vulnerable systems globally. You can copy these dorks to see if your organization's IP space is exposed.

Ashlar-Vellum Cobalt
Cobalt CO file parser

💣 PoC CODE AVAILABLE

Exploit code for this CVE is tracked in our database. Access poc_code via API Pro.

[ API_PRO ] →
◈ SOURCE Analysis & enrichment: valtersit.com/cve/CVE-2025-8002/ · CVE data: NVD/MITRE (public domain) · © 2026 ValtersIT Hub
>_ SYSTEM_CORE: INTEL_ACTIVE
90% TEAM-CURATED // 10% AUTOMATED INGESTION.
ALL PATCH REFERENCES AND VERSION DATA SOURCED FROM NVD + OSV OFFICIAL REGISTRIES.