Proficy Machine EditionApplication · Emerson

CVE-2021-29297

MEDIUM · 5.3 CVSS v3.1 Published 2021-07-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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
Buffer Overflow in Emerson GE Automation Proficy Machine Edition v8.0 allows an attacker to cause a denial of service and application crash via crafted traffic from a Man-in-the-Middle (MITM) attack to the component "FrameworX.exe" in the module "MSVCR100.dll".

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

Buffer overflow vulnerability in Emerson GE Automation Proficy Machine Edition v8.0 allows an attacker positioned as a Man-in-the-Middle to send crafted network traffic to the FrameworX.exe component (which uses MSVCR100.dll), causing a denial of service and application crash.

MitigationApply vendor-supplied patches or upgrade to a patched version of Proficy Machine Edition; implement network segmentation to reduce MITM attack surface.

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
Proficy Machine EditionApplication
Affected:= 8.0

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
Network
Complexity
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/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. Confirm Proficy Machine Edition installation
    Locate the Proficy Machine Edition installation directory. Common paths include C:\Program Files\GE Automation\Proficy Machine Edition or C:\Program Files (x86)\GE Automation\Proficy Machine Edition. Check for the presence of the main application folder.
    Affected if The software is not installed or the installation directory cannot be found.
  2. Identify installed version
    Locate the version information for the installation. Check the executable properties of any .exe in the Proficy Machine Edition folder, or look for a version file or registry entry under HKEY_LOCAL_MACHINE\SOFTWARE\GE Automation\Proficy Machine Edition (or similar). The affected version is specifically 8.0.
    Affected if The installed version is exactly 8.0. Versions other than 8.0 are not affected by this specific CVE.
  3. Verify FrameworX.exe component presence
    Navigate to the Proficy Machine Edition installation directory and search for FrameworX.exe. This is the specific component identified as vulnerable in the CVE.
    Affected if FrameworX.exe is present on the system.
  4. Confirm MSVCR100.dll dependency
    Check for the presence of MSVCR100.dll in the FrameworX.exe directory or in system PATH. This DLL is used by the vulnerable component.
    Affected if MSVCR100.dll is loaded by FrameworX.exe.
  5. Assess network exposure
    Since the attack vector requires a Man-in-the-Middle position, evaluate whether the machine running Proficy Machine Edition is on a network segment where an attacker could intercept traffic. Check for exposed network interfaces or listening ports related to the application.
    Affected if The application is accessible on a network where untrusted parties could potentially intercept communications.

A system is affected only if Proficy Machine Edition version 8.0 is installed with the FrameworX.exe component present and accessible on a network where MITM attacks are possible.

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

Apply vendor-supplied patches or upgrade to a patched version of Proficy Machine Edition; implement network segmentation to reduce MITM attack surface.

Fix this in Proficy Machine Edition Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-29297 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-29297 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