dbcve.org
Screen Creator Advance 2Application · Jtekt

CVE-2023-25755

HIGH · 7.8 CVSS v3.1 Published 2023-04-11
Fix available
A fix is available. Upgrade to 0.1.1.4 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
Screen Creator Advance 2 Ver.0.1.1.4 Build01A and earlier is vulnerable to improper restriction of operations within the bounds of a memory buffer (CWE-119) due to improper check of its data size when processing a project file. If a user of Screen Creator Advance 2 opens a specially crafted project file, information may be disclosed and/or arbitrary code may be executed.

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

Buffer overflow vulnerability (CWE-119) in Screen Creator Advance 2's project file parsing function due to improper size validation. Opening a specially crafted project file triggers out-of-bounds memory access, enabling information disclosure and potentially arbitrary code execution.

MitigationDo not open untrusted or unverified project files in Screen Creator Advance 2. Monitor vendor for patch releases and update to version beyond 0.1.1.4 Build01A when available.

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
Screen Creator Advance 2Application
Affected:< 0.1.1.4= 0.1.1.4

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. Locate the Screen Creator Advance 2 installation directory
    Search for 'Screen Creator Advance 2' in Program Files (x86) or Program Files, or use the search feature in Windows Explorer
    Affected if The application is installed on the system
  2. Identify the installed version number
    Right-click the executable (commonly named ScreenCreatorAdvance2.exe or similar) and select Properties, then check the Details tab for the File Version or Product Version
    Affected if The version is displayed as a value less than 0.1.1.4 or exactly 0.1.1.4
  3. Check if project files exist or have been opened
    Search for files with common project extensions such as .scp, .sca, or .project in user directories or recent file locations; also check the application's recent projects list if accessible
    Affected if The application has been used to create or open project files on this machine
  4. Verify the application can parse project files
    Open the application and attempt to locate a project file opening function or verify the File menu contains options to open or import project files
    Affected if The application includes project file parsing functionality

The environment is affected if Screen Creator Advance 2 is installed with a version lower than 0.1.1.4 or exactly 0.1.1.4 and the application is capable of opening project files.

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 0.1.1.4 or later
Fixed in 0.1.1.4
Interim mitigation

Do not open untrusted or unverified project files in Screen Creator Advance 2. Monitor vendor for patch releases and update to version beyond 0.1.1.4 Build01A when available.

Recommended fix Moderate confidence

Screen Creator Advance 2 version > 0.1.1.4 (contact vendor for exact fixed release)

  1. 1. Close Screen Creator Advance 2 completely before proceeding with the update
  2. 2. Navigate to the official vendor website at www.electronics.jtekt.co.jp
  3. 3. Locate the downloads or support section for Screen Creator Advance 2
  4. 4. Download the latest version of Screen Creator Advance 2 (version higher than 0.1.1.4)
  5. 5. Verify the downloaded file integrity if hash verification is provided
  6. 6. Install the new version following the vendor's installation instructions
  7. 7. After installation, verify the installed version matches the expected fixed release
  8. 8. Do not open any untrusted or specially crafted project files with the updated software
Caveat Minor - review release notes for any project file format changes or feature modifications

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

Fix this in Screen Creator Advance 2 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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 locally
dbcve dependency scanner

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