dbcve.org
CobaltApplication · Ashlar

CVE-2023-34304

HIGH · 7.8 CVSS v3.0 Published 2024-05-03
Fix available
A fix is available. Upgrade to 12.4.1204.200 or later.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Ashlar-Vellum Cobalt Out-Of-Bounds Access Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Ashlar-Vellum Cobalt. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the parsing of IGS files. The issue results from the lack of proper validation of user-supplied data, which can result in a memory access past the end of an allocated buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. . Was ZDI-CAN-18006.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is an out-of-bounds access vulnerability in Ashlar-Vellum Cobalt's IGS (IGES) file parser. The flaw results from insufficient validation of user-supplied data during IGS file parsing, allowing memory access beyond allocated buffer boundaries. Successful exploitation enables arbitrary code execution in the context of the current process when a user opens a malicious IGS file.

MitigationUsers should avoid opening IGS files from untrusted sources. The vendor should implement proper bounds checking and input validation in the IGS file parsing routines to prevent buffer overread conditions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CobaltApplication
Affected:< 12.4.1204.200

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Ashlar-Vellum Cobalt installation
    Locate the Ashlar Cobalt application on the system. Check Program Files for 'Ashlar' or 'Cobalt' folders, or search for cobalt.exe in the installation directory.
    Affected if The software is installed and is Ashlar Cobalt version 12.4.1204.200 or lower.
  2. Determine installed Cobalt version
    Open Cobalt and navigate to Help > About, or right-click on the executable and view Properties > Details to see the File Version.
    Affected if The version number is less than 12.4.1204.200.
  3. Check for IGS file handler registration
    Search the system for .igs or .iges file associations. Look in Windows Registry under HKCR\.igs or examine file associations in Control Panel > Default Programs.
    Affected if IGS/IGES file types are registered to open with Ashlar Cobalt.
  4. Inspect recent IGS file activity
    Review Windows Event Viewer, Cobalt's recent files list, or search the file system for .igs files that have been recently opened with Cobalt.
    Affected if A user has opened an IGS file with the affected Cobalt version.

A user is affected if Ashlar Cobalt version 12.4.1204.200 or lower is installed and configured to open IGS/IGES files, and a malicious IGS file has been opened.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 12.4.1204.200 or later
Fixed in 12.4.1204.200
Interim mitigation

Users should avoid opening IGS files from untrusted sources. The vendor should implement proper bounds checking and input validation in the IGS file parsing routines to prevent buffer overread conditions.

Recommended fix Moderate confidence

Ashlar-Vellum Cobalt version 12.4.1204.200 or later

  1. 1. Identify the current version of Ashlar-Vellum Cobalt installed on the system
  2. 2. Obtain Ashlar-Vellum Cobalt version 12.4.1204.200 or later from the official Ashlar-Vellum vendor
  3. 3. Follow standard software upgrade procedures to apply the updated version
  4. 4. Verify the installation completed successfully and the new version is running

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cobalt Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-34304 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-34304 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data