dbcve.org
Echo Curve ViewerApplication · Endress

CVE-2024-6596

CRITICAL · 9.8 CVSS v3.1 Published 2024-09-10
Fix available
A fix is available. Upgrade to 1.40.1 / 6.0.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
An unauthenticated remote attacker can run malicious c# code included in curve files and execute commands in the users context.

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

An unauthenticated remote attacker can execute arbitrary C# code embedded in malicious curve files, achieving command execution within the context of the user who opens the affected file. This represents a critical code injection or deserialization vulnerability in software that processes curve files.

MitigationApply available vendor patches immediately; until patched, avoid opening curve files from untrusted sources and consider restricting file associations or implementing endpoint protection to block malicious curve file execution.

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
Echo Curve ViewerApplication
Affected:< 6.0.0
Fieldcare Sfe500 PackageApplication
Affected:< 1.40.1
Field Xpert Smt79 FirmwareOperating system
Affected:all versions
Field Xpert Smt77 FirmwareOperating system
Affected:all versions
Field Xpert Smt70 FirmwareOperating system
Affected:all versions
Field Xpert Smt50 FirmwareOperating system
Affected:all versions

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 Endress Echo Curve Viewer installation and version
    Check for Echo Curve Viewer installation in typical locations such as C:\Program Files\Endress+Hauser\Echo Curve Viewer\ or C:\Program Files (x86)\Endress+Hauser\Echo Curve Viewer\. Locate the application executable or check Windows Registry under HKEY_LOCAL_MACHINE\SOFTWARE\Endress+Hauser\EchoCurveViewer for version information.
    Affected if Version is found to be lower than 6.0.0 or version cannot be determined (implies vulnerable)
  2. Identify Endress Fieldcare Sfe500 Package installation and version
    Check for Fieldcare installation with Sfe500 package. Look in C:\Program Files\Endress+Hauser\Fieldcare\ or C:\Program Files (x86)\Endress+Hauser\Fieldcare\. Locate version information in the application directory or check Windows Registry under HKEY_LOCAL_MACHINE\SOFTWARE\Endress+Hauser\Fieldcare for the Sfe500 component version.
    Affected if Sfe500 Package version is lower than 1.40.1 or version cannot be determined (implies vulnerable)
  3. Identify Field Xpert device models and firmware versions
    Access the Field Xpert devices (SMT50, SMT70, SMT77, SMT79) via their web interface or console. Check the device firmware version information typically found in the device settings, about page, or via SNMP/sysinfo queries. Document the model number and firmware version for each device.
    Affected if Device model is SMT50, SMT70, SMT77, or SMT79 with any firmware version (all versions affected)
  4. Detect presence of curve file processing functionality
    Search for file associations or file handlers related to curve files on systems with the software installed. Look for .curve, .ecurve, or vendor-specific curve file extensions in the application configuration or Windows file type associations. Check if the software is configured to auto-process or preview curve files.
    Affected if Curve file handling is enabled and the software versions in steps 1-2 are vulnerable, or any Field Xpert device is in use

You are affected if any Endress Echo Curve Viewer below 6.0.0, Fieldcare Sfe500 Package below 1.40.1, or any Field Xpert SMT50/SMT70/SMT77/SMT79 device is present in your environment with curve file processing enabled.

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
Upgrade available Upgrade to 1.40.1 / 6.0.0 or later
Fixed in 1.40.16.0.0
Interim mitigation

Apply available vendor patches immediately; until patched, avoid opening curve files from untrusted sources and consider restricting file associations or implementing endpoint protection to block malicious curve file execution.

Fix this in Echo Curve Viewer Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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