dbcve.org
EdgeaggregatorWeb browser · Softing

CVE-2023-38125

HIGH · 8.8 CVSS v3.1 Published 2024-05-03
Fix available
A fix is available. Upgrade to 1.30 / 3.50 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 edgeAggregator Permissive Cross-domain Policy with Untrusted Domains Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Softing edgeAggregator. Authentication is required to exploit this vulnerability. The specific flaw exists within the configuration of the web server. The issue results from the lack of appropriate Content Security Policy headers. An attacker can leverage this in conjunction with other vulnerabilities to execute code in the context of root. Was ZDI-CAN-20542.

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

This vulnerability in Softing edgeAggregator stems from the web server's lack of proper Content Security Policy (CSP) headers, resulting in a permissive cross-domain policy that allows untrusted domains. While authentication is required, an attacker can chain this CSP weakness with other vulnerabilities to achieve arbitrary code execution in the root context.

MitigationImplement strict Content Security Policy headers on the edgeAggreg web server to restrict cross-domain requests and define trusted content sources, eliminating the permissive policy that enables exploitation.

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.50
EdgeconnectorWeb browser
Affected:< 3.50
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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 the installed Softing product and version
    Access the product's web interface or check system information to determine whether you are running Softing edgeAggregator, edgeConnector, or Secure Integration Server, and note the exact version number installed.
    Affected if The installed version is edgeAggregator or edgeConnector below 3.50, or Secure Integration Server below 1.30.
  2. Retrieve the HTTP response headers from the web interface
    Use a browser developer tool, curl command, or similar HTTP client to request the main page of the product's web interface (typically port 443 or 8080) and capture the response headers.
    Affected if The response does not contain a Content-Security-Policy header or contains a CSP header that allows wildcard or untrusted domains in directives like script-src, style-src, or connect-src.
  3. Inspect the CSP header configuration
    Examine the Content-Security-Policy header value specifically for permissive settings such as 'unsafe-inline', 'unsafe-eval', wildcard sources (*.example.com), or missing restrictions on cross-origin requests.
    Affected if The CSP header is missing entirely, or is configured with overly permissive directives that allow untrusted domains to load resources or make cross-domain requests.

Your environment is affected if the product version is below 3.50 (edgeAggregator/edgeConnector) or below 1.30 (Secure Integration Server) AND the web server response lacks strict CSP headers or permits untrusted cross-domain requests.

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.50 or later
Fixed in 1.303.50
Interim mitigation

Implement strict Content Security Policy headers on the edgeAggreg web server to restrict cross-domain requests and define trusted content sources, eliminating the permissive policy that enables exploitation.

Recommended fix High confidence

Edgeaggregator 3.50+, Edgeconnector 3.50+, Secure Integration Server 1.30+

  1. Upgrade edgeAggregator to version 3.50 or later
  2. Upgrade edgeConnector to version 3.50 or later
  3. Upgrade Secure Integration Server to version 1.30 or later
  4. After upgrading, verify that Content Security Policy headers are properly configured in the web server configuration
  5. Confirm that the vulnerability is remediated by reviewing the HTTP response headers for appropriate CSP headers

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-38125 — 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-38125 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