dbcve.org
Pro Face Gp Pro ExApplication · Schneider Electric

CVE-2023-3953

MEDIUM · 5.3 CVSS v3.1 Published 2023-08-09
Fix available
A fix is available. Upgrade to 4.09.500 or later.
See remediation →
56/100
Remediation priority · Elevated
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
A CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerability exists that could cause memory corruption when an authenticated user opens a tampered log file from GP-Pro EX.

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 · moderate confidence

A memory buffer restriction vulnerability (CWE-119) in GP-Pro EX allows authenticated users to cause memory corruption by opening a specially crafted (tampered) log file. The vulnerability stems from improper bounds checking during log file parsing, leading to potential heap or stack buffer overflows when processing malformed file content.

MitigationUsers should avoid opening log files from untrusted sources. Organizations should apply any available vendor patches for GP-Pro EX and implement file integrity verification before processing log files.

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
Pro Face Gp Pro ExApplication
Affected:< 4.09.500

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
Low
Integrity
Low
Availability
Low

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

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 GP-Pro EX installation
    Check if Schneider Electric Pro Face GP-Pro EX is installed on the system by looking in standard installation directories (e.g., Program Files, Program Files (x86)) or checking Windows Registry for installed software under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
    Affected if GP-Pro EX software is present on the system
  2. Identify installed version
    Locate the GP-Pro EX executable (typically named GP-Pro EX.exe or similar) and check its file properties, or look for version information in the Windows Registry under the GP-Pro EX uninstall entry
    Affected if The version number cannot be determined or is lower than 4.09.500
  3. Compare version to vulnerable range
    Compare the identified version against the affected range: any version lower than 4.09.500 is vulnerable
    Affected if Installed version is below 4.09.500 (e.g., 4.09.400, 4.08.000, etc.)
  4. Confirm log file processing capability
    GP-Pro EX processes log files during normal operation - verify the software has been used to create or open project files that may contain or reference log data
    Affected if The software is used and can open log files, making the vulnerability exploitable if a tampered log file is opened

You are affected if GP-Pro EX is installed and the installed version is lower than 4.09.500, and an authenticated user could open a specially crafted log file through the application.

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

Users should avoid opening log files from untrusted sources. Organizations should apply any available vendor patches for GP-Pro EX and implement file integrity verification before processing log files.

Recommended fix Moderate confidence

GP-Pro EX version 4.09.500

  1. 1. Obtain GP-Pro EX version 4.09.500 or later from the official Schneider Electric download portal (download.schneider-electric.com)
  2. 2. Back up all existing GP-Pro EX project files, configurations, and log files before proceeding
  3. 3. Uninstall the current (vulnerable) version of GP-Pro EX from the system
  4. 4. Install the new version 4.09.500 or later of GP-Pro EX
  5. 5. After installation, verify the version by checking 'Help' > 'About GP-Pro EX' to confirm version 4.09.500 or higher is installed
  6. 6. Test your existing projects to ensure they function correctly with the updated software
Caveat Review release notes for any changes in behavior with log file handling; test projects in a non-production environment first

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

Fix this in Pro Face Gp Pro Ex Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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