dbcve.org
EdgeaggregatorWeb browser · Softing

CVE-2023-27335

CRITICAL · 9.6 CVSS v3.1 Published 2024-05-03
Fix available
A fix is available. Upgrade to 1.30 / 3.70 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Softing edgeAggregator Client Cross-Site Scripting Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Softing edgeAggregator. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the handling of the input parameters provided to the edgeAggregetor client. The issue results from the lack of proper validation of user-supplied data, which can lead to the injection of an arbitrary script. An attacker can leverage this in conjunction with other vulnerabilities to execute arbitrary code in the context of root. Was ZDI-CAN-20504.

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

A cross-site scripting vulnerability exists in Softing edgeAggregator client due to improper validation of user-supplied input parameters. An attacker can inject arbitrary script that executes in the context of the user's session, and when combined with other vulnerabilities, can achieve remote code execution with root privileges.

MitigationImplement strict input validation and output encoding for all user-supplied parameters in the edgeAggregator client. Additionally, apply the principle of least privilege and ensure that any chained vulnerabilities are also patched to prevent root-level code 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
EdgeaggregatorWeb 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
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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 installed Softing Edgeaggregator version
    Locate the installation directory or use system package manager to query the installed version of edgeAggregator. Common locations include /opt/softing/ or program files on Windows. Check version file or run: edgeaggregator --version
    Affected if Installed version is lower than 3.70
  2. Identify installed Softing Secure Integration Server version
    Locate the installation directory or use system package manager to query the installed version of Secure Integration Server. Check version file or run: sis --version
    Affected if Installed version is lower than 1.30
  3. Verify web client interface is accessible
    Check if the edgeAggregator or Secure Integration Server web interface is exposed and accessible. Test by attempting to reach the client portal URL or checking listening network services on ports 80/443 or configured web service ports
    Affected if Web interface is exposed without proper input validation controls in place
  4. Confirm user input handling in client configuration
    Review the client configuration files for edgeAggregator to identify any parameters that accept user-supplied input. Look for configuration files in the installation directory that control input validation or sanitization settings
    Affected if Input validation is disabled or not configured for web client parameters

Environment is affected if either Softing Edgeaggregator version is below 3.70 or Softing Secure Integration Server version is below 1.30, and the web client interface is accessible to users.

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

Implement strict input validation and output encoding for all user-supplied parameters in the edgeAggregator client. Additionally, apply the principle of least privilege and ensure that any chained vulnerabilities are also patched to prevent root-level code execution.

Recommended fix Moderate confidence

edgeAggregator version 3.70 or later; Secure Integration Server version 1.30 or later

  1. Identify which Softing product is in use: edgeAggregator or Secure Integration Server
  2. Check the current installed version of the product
  3. For edgeAggregator: Upgrade to version 3.70 or later
  4. For Secure Integration Server: Upgrade to version 1.30 or later
  5. After upgrade, verify the new version is installed correctly
  6. Test that the application functions normally post-upgrade

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

Fix this in Edgeaggregator Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
34.0 hours of engineering $6,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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