dbcve.org
CobaltApplication · Ashlar

CVE-2023-34292

HIGH · 7.8 CVSS v3.0 Published 2024-05-03
Fix available
A fix is available. Upgrade to 12.0.1204.54 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 Write 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 X_B or X_T files. The issue results from the lack of proper validation of user-supplied data, which can result in a write before the start of an allocated buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. . Was ZDI-CAN-18552.

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

An out-of-bounds write vulnerability exists in Ashlar-Vellum Cobalt during parsing of X_B or X_T CAD files. The lack of proper validation of user-supplied data allows writing before the start of an allocated buffer, enabling remote code execution in the context of the current process. User interaction is required (opening malicious file).

MitigationAvoid opening untrusted X_B or X_T files from unknown sources. Apply vendor patches when available. Consider endpoint detection solutions to monitor for suspicious file parsing behavior.

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.0.1204.54

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. Verify Ashlar Cobalt is installed
    Locate the Ashlar Cobalt application on the system, typically found in Program Files or Program Files (x86) directories, or check Add/Remove Programs for the software.
    Affected if The software is present on the system.
  2. Determine installed version of Ashlar Cobalt
    Open Ashlar Cobalt and navigate to Help > About, or right-click the application executable and select Properties > Details to view the version number.
    Affected if The displayed version is lower than 12.0.1204.54.
  3. Identify if X_B or X_T file parsing is in use
    Check if the application has recent activity or file associations for .X_B or .X_T CAD file extensions, or search for these file types in recent documents or downloads.
    Affected if The application is configured to handle or has recently processed X_B or X_T files.
  4. Confirm file parsing functionality is enabled
    Review the application's file handling settings or preferences to verify that CAD file import functionality is active, which enables parsing of X_B and X_T formats.
    Affected if CAD file parsing features are enabled and accessible to users.

A user is affected if Ashlar Cobalt version 12.0.1204.54 or higher is NOT installed AND the application can parse X_B or X_T CAD files, combined with the risk of opening untrusted files from unknown sources.

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.0.1204.54 or later
Fixed in 12.0.1204.54
Interim mitigation

Avoid opening untrusted X_B or X_T files from unknown sources. Apply vendor patches when available. Consider endpoint detection solutions to monitor for suspicious file parsing behavior.

Recommended fix High confidence

12.0.1204.54 or later

  1. 1. Open Ashlar-Vellum Cobalt application
  2. 2. Navigate to Help > About to check the current version number
  3. 3. If the version is below 12.0.1204.54, download the latest version from the official Ashlar-Vellum website or your licensed distribution channel
  4. 4. Run the installer and follow the prompts to upgrade the software
  5. 5. After installation, verify the version by checking Help > About again

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

Fix this in Cobalt Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-34292 — 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-34292 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