# CVE-2023-27335: Softing edgeAggregator Client Cross-Site Scripting Remote Code Execution Vulnerability

> Remote attackers can execute arbitrary code with root privileges via cross-site scripting in Softing edgeAggregator Client.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 May 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-jgg3-hp8q-5678

## What is CVE-2023-27335?

CVE-2023-27335 is a high-severity cross-site scripting vulnerability in Softing edgeAggregator, published on 3 May 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2023-27335?

It affects 2 products.


Products: Softing Edgeaggregator, Softing Secure Integration Server.

## How do I fix CVE-2023-27335?

No fix has been published for CVE-2023-27335 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-27335 being exploited?

There is no known exploitation of CVE-2023-27335 in the wild and no public exploit code.

## Other vulnerabilities in Softing edgeAggregator

- [CVE-2022-2336](https://insights.sbomify.com/CVE-2022-2336/): Softing Secure Integration Server Improper Authentication (critical 9.8)
- [CVE-2024-0860](https://insights.sbomify.com/CVE-2024-0860/): Cleartext Transmission of Sensitive Information in Softing edgeConnector and edgeAggregator (high 8.0)
- [CVE-2023-27334](https://insights.sbomify.com/CVE-2023-27334/): Softing edgeConnector Siemens ConditionRefresh Resource Exhaustion Denial-of-Service Vulnerability (high 7.5)
- [CVE-2023-27336](https://insights.sbomify.com/CVE-2023-27336/): Softing edgeConnector Siemens OPC UA Server Null Pointer Dereference Denial-of-Service Vulnerability (high 7.5)
- [CVE-2023-38125](https://insights.sbomify.com/CVE-2023-38125/): Softing edgeAggregator Permissive Cross-domain Policy with Untrusted Domains Remote Code Execution Vulnerability (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-27335 and fix it if it is affected.

What it is: CVE-2023-27335 is a high-severity cross-site scripting vulnerability in Softing edgeAggregator, published on 3 May 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-27335 in the wild and no public exploit code.

Affected product: Softing edgeAggregator. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-27335/ (Markdown: https://insights.sbomify.com/CVE-2023-27335/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-27335
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-27335
- OSV: https://osv.dev/vulnerability/CVE-2023-27335

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-27335/
Summaries are generated and may contain mistakes; the official description above is the record.