dbcve.org
FvdesignerApplication · Fatek

CVE-2023-34268

HIGH · 7.8 CVSS v3.1 Published 2024-05-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Fatek Automation FvDesigner FPJ File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Fatek Automation FvDesigner. 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 FPJ files. The issue results from the lack of proper validation of user-supplied data, which can result in a write past the end of an allocated data structure. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-18172.

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 write vulnerability in Fatek Automation FvDesigner's FPJ file parser. The application fails to properly validate user-supplied data when parsing FPJ project files, allowing an attacker to write data past the end of an allocated buffer. This memory corruption can be leveraged to achieve arbitrary code execution in the context of the current process.

MitigationRestrict opening of untrusted FPJ files and implement file sanitization/validation before parsing. Apply vendor patches when available. Consider network isolation and endpoint protection to limit exposure.

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
FvdesignerApplication
Affected:= 1.6.24

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

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

  1. Identify if Fatek FvDesigner is installed
    Check for FvDesigner in installed programs on Windows (Control Panel > Programs and Features) or look for the executable in common installation paths such as C:\Program Files\Fatek\FvDesigner or C:\Program Files (x86)\Fatek\FvDesigner
    Affected if FvDesigner is present on the system
  2. Determine the installed version of FvDesigner
    Right-click the FvDesigner executable, select Properties, and check the File Version tab, or launch FvDesigner and go to Help > About to view the version information
    Affected if The installed version is exactly 1.6.24
  3. Check for FPJ project files on the system
    Search for files with the .fpj extension on the system using File Explorer search (type: *.fpj) or PowerShell command: Get-ChildItem -Path C:\ -Recurse -Filter *.fpj -ErrorAction SilentlyContinue
    Affected if FPJ files exist and the system processes them with the vulnerable version of FvDesigner
  4. Verify if FvDesigner is configured to automatically open FPJ files
    Check file association settings for .fpj files by right-clicking an FPJ file, selecting Properties, and viewing the 'Opens with' field, or check browser/download settings if FPJ files are received via email or web downloads
    Affected if FPJ files are set to open automatically with FvDesigner 1.6.24

A user is affected if Fatek FvDesigner version 1.6.24 is installed and the system processes or is configured to open FPJ project files with this vulnerable version.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict opening of untrusted FPJ files and implement file sanitization/validation before parsing. Apply vendor patches when available. Consider network isolation and endpoint protection to limit exposure.

Fix this in Fvdesigner 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 help mitigating

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-34268 — 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-34268 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