dbcve.org
MultiprogApplication · Phoenixcontact

CVE-2023-5592

HIGH · 7.5 CVSS v3.1 Published 2023-12-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
Download of Code Without Integrity Check vulnerability in PHOENIX CONTACT MULTIPROG, PHOENIX CONTACT ProConOS eCLR (SDK) allows an unauthenticated remote attacker to download and execute applications without integrity checks on the device which may result in a complete loss of integrity.

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 vulnerability in PHOENIX CONTACT MULTIPROG and ProConOS eCLR SDK allows unauthenticated remote attackers to download and execute arbitrary applications on affected devices without any integrity verification. The lack of cryptographic signatures or checksums before execution enables complete compromise of device integrity.

MitigationImplement code signing and integrity verification (e.g., cryptographic signatures, HMAC, or checksum validation) for all downloaded applications. Additionally, require authentication for download operations and apply any vendor-provided patches or firmware updates.

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
MultiprogApplication
Affected:all versions
Proconos EclrApplication
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
None
Integrity
High
Availability
None

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

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 affected Phoenix Contact products are installed
    Check system inventory or installed programs for 'Phoenix Contact Multiprog' or 'ProConOS eCLR' or 'eCLR' software packages. Look in Program Files, Program Files (x86), or use system inventory tools.
    Affected if Either Phoenix Contact Multiprog or ProConOS eCLR SDK is installed on the system, regardless of version.
  2. Locate the ProConOS eCLR runtime or download service
    Search for ProConOS or eCLR executable files, services, or runtime components on the system. Check installation directories, services list, and running processes for eCLR-related components.
    Affected if ProConOS eCLR runtime or associated download service is present on the system.
  3. Check for code signing or integrity verification configuration
    Examine the ProConOS eCLR configuration files, settings, or control panel options for any code signing, checksum validation, or integrity verification settings. Look for options related to 'signature verification', 'checksum validation', or 'integrity check' in the product configuration.
    Affected if No cryptographic signature, HMAC, or checksum validation is enforced for downloaded applications, or such features are disabled or absent.
  4. Verify if authentication is required for application downloads
    Review the product security settings, user authentication configuration, or access control settings to determine whether unauthenticated or anonymous download operations are permitted.
    Affected if Download operations can be performed without authentication, or no access controls are enforced on the download interface.
  5. Identify network-exposed download interfaces
    Check network configuration, firewall rules, and open ports to determine if the product's download functionality is exposed to the network. Review any HTTP, FTP, or proprietary download endpoints.
    Affected if The application download interface is accessible from the network without requiring prior authentication.

The environment is affected if Phoenix Contact Multiprog or ProConOS eCLR is installed and the system allows unauthenticated application downloads without cryptographic signature or integrity verification.

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

Implement code signing and integrity verification (e.g., cryptographic signatures, HMAC, or checksum validation) for all downloaded applications. Additionally, require authentication for download operations and apply any vendor-provided patches or firmware updates.

Fix this in Multiprog Scoped from the published advisory
  • Consultation8.0 h
  • Implementation40.0 h
  • Testing16.0 h
  • Review / QA8.0 h
72.0 hours of engineering $12,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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