CVE-2023-34288
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 · uneditedAshlar-Vellum Cobalt XE File Parsing Uninitialized Pointer 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 XE files. The issue results from the lack of proper initialization of a pointer prior to accessing it. An attacker can leverage this vulnerability to execute code in the context of the current process. . Was ZDI-CAN-17966.
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 confidenceA pointer is not properly initialized before being accessed during XE file parsing in Ashlar-Vellum Cobalt XE, leading to arbitrary code execution in the context of the current process when a user opens a malicious XE file.
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< 12.0.1204.54CVSS 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.1/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 checksWork through these to decide whether this CVE applies to you.
-
Locate Ashlar Cobalt installationCheck Program Files or Program Files (x86) for an Ashlar folder, or look in the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named Ashlar CobaltAffected if Ashlar Cobalt is installed on the system
-
Identify installed versionRight-click the executable (typically Cobalt.exe or similar in the Ashlar installation folder), select Properties, and check the Details tab for the File Version; alternatively, check the version listed in Add/Remove ProgramsAffected if version number cannot be determined or the software appears to be an unpatched release
-
Compare version to affected rangeCompare the identified version number to 12.0.1204.54 using numeric version comparison (for example, 12.0.1204.53 or 11.x.x.x would be less than the patched version)Affected if the installed version is less than 12.0.1204.54
-
Assess XE file handling exposureCheck if .xe file associations are configured to automatically open with Ashlar Cobalt, or if users commonly double-click XE files to launch the applicationAffected if XE files are associated with Ashlar Cobalt and users may open untrusted XE files
The environment is affected if Ashlar Cobalt version is present and is less than 12.0.1204.54, and users process XE files with the software.
Generated from the published advisory. Verify against your own configuration.
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 · scoped12.0.1204.54
Avoid opening untrusted or unverified XE files. Apply vendor patches when available and restrict file type associations to trusted sources.
Cobalt version 12.0.1204.54 or later
- Obtain Cobalt version 12.0.1204.54 or later from the official Ashlar-Vellum vendor website or authorized distribution channel
- Back up all existing Cobalt project files (.cobalt, .xe, and related files) before upgrading
- Uninstall the current version of Cobalt
- Install the fixed version (12.0.1204.54 or newer)
- Verify the installation completed successfully
- Open a test XE file to confirm the software functions correctly with the fixed version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-34288 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-34288 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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