dbcve.org
EdgeaggregatorWeb browser · Softing

CVE-2023-27336

HIGH · 7.5 CVSS v3.0 Published 2024-05-03
Fix available
A fix is available. Upgrade to 1.30 / 3.70 or later.
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
Softing edgeConnector Siemens OPC UA Server Null Pointer Dereference Denial-of-Service Vulnerability. This vulnerability allows remote attackers to create a denial-of-service condition on affected installations of Softing edgeConnector Siemens. Authentication is not required to exploit this vulnerability. The specific flaw exists within the handling of OPC client certificates. The issue results from dereferencing a NULL pointer. An attacker can leverage this vulnerability to create a denial-of-service condition on the system. Was ZDI-CAN-20508.

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 NULL pointer dereference vulnerability exists in Softing edgeConnector Siemens OPC UA Server's handling of OPC client certificates. An unauthenticated remote attacker can send specially crafted client certificate data that causes the server to dereference a NULL pointer, resulting in a denial-of-service condition.

MitigationApply the vendor patch when released. In the interim, restrict network access to the OPC UA server via firewall rules and network segmentation to limit exposure to untrusted clients.

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
EdgeaggregatorWeb browser
Affected:< 3.70
EdgeconnectorWeb browser
Affected:< 3.70
Secure Integration ServerApplication
Affected:< 1.30

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
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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. Identify the installed Softing product and version
    Run 'docker ps' to list running Softing containers, then 'docker inspect <container_id>' to retrieve the image version tag, or check the service version via the management interface at port 8080
    Affected if The displayed version is lower than 3.70 for Edgeaggregator/Edgeconnector, or lower than 1.30 for Secure Integration Server
  2. Verify the OPC UA server component is enabled
    Check the configuration file (typically located in /opt/softing/ or the mounted config volume) for the OPC UA server settings, or inspect the running container's environment variables for 'OPCUASERVER_ENABLED' or similar
    Affected if The OPC UA server module is actively running and accepting connections
  3. Confirm network exposure of the OPC UA server port
    Run 'netstat -tlnp | grep 4840' (default OPC UA port) or check firewall rules with 'iptables -L' or 'ufw status' to list open ports and their source restrictions
    Affected if Port 4840 (or configured OPC UA port) is open to untrusted network segments or the internet without network segmentation or firewall filters
  4. Check for recent crashes or service restarts
    Review system logs with 'journalctl -u softing-edgeconnector' or container logs with 'docker logs <container_id>' for NULL pointer dereference errors or unexpected server restarts around the time of potential exploitation
    Affected if Logs show frequent crashes or restart cycles of the OPC UA server process that cannot be explained by normal operations

You are affected if the installed Softing product version is below 3.70 (Edgeaggregator/Edgeconnector) or below 1.30 (Secure Integration Server) AND the OPC UA server component is exposed to network access from untrusted clients.

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 1.30 / 3.70 or later
Fixed in 1.303.70
Interim mitigation

Apply the vendor patch when released. In the interim, restrict network access to the OPC UA server via firewall rules and network segmentation to limit exposure to untrusted clients.

Recommended fix High confidence

Edgeaggregator >= 3.70; Edgeconnector >= 3.70; Secure Integration Server >= 1.30

  1. Identify the currently installed Softing product (Edgeaggregator, Edgeconnector, or Secure Integration Server) using the system's package manager or application documentation
  2. For Edgeaggregator or Edgeconnector: Upgrade to version 3.70 or later
  3. For Secure Integration Server: Upgrade to version 1.30 or later
  4. After upgrading, verify the new version is running by checking the application version via its management interface or command line
  5. Restart the OPC UA service if required by the upgrade process to ensure the new version is fully active
Caveat Ensure compatibility with existing OPC UA client configurations after upgrade, as certificate handling behavior may have changed

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

Fix this in Edgeaggregator Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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