# CVE-2023-39482: Softing Secure Integration Server Hardcoded Cryptographic Key Information Disclosure Vulnerability

> Remote attackers can bypass authentication and disclose stored credentials due to hardcoded cryptographic keys in Softing Secure Integration Server.

- **Severity:** Medium 4.9 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 May 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-4g38-9x5c-pq58

## What is CVE-2023-39482?

CVE-2023-39482 is a medium-severity vulnerability in Softing Secure Integration Server, published on 3 May 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Softing Secure Integration Server Hardcoded Cryptographic Key Information Disclosure Vulnerability. This vulnerability allows remote attackers to disclose sensitive information on affected installations of Softing Secure Integration Server. Although authentication is required to exploit this vulnerability, the existing authentication mechanism can be bypassed.

The specific flaw exists within libopcuaclient.so. The issue results from hardcoding crytographic keys within the product. An attacker can leverage this vulnerability to disclose stored credentials, leading to further compromise. Was ZDI-CAN-20610.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-321 (Use of Hard-coded Cryptographic Key)

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

It affects 3 products.


Products: Softing Edgeaggregator, Softing Edgeconnector, Softing Secure Integration Server.

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

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

## Is CVE-2023-39482 being exploited?

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

## Other vulnerabilities in Softing Secure Integration Server

- [CVE-2022-2336](https://insights.sbomify.com/CVE-2022-2336/): Softing Secure Integration Server Improper Authentication (critical 9.8)
- [CVE-2023-27335](https://insights.sbomify.com/CVE-2023-27335/): Softing edgeAggregator Client Cross-Site Scripting Remote Code Execution Vulnerability (high 8.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)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-39482 is a medium-severity vulnerability in Softing Secure Integration Server, published on 3 May 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-39482 in the wild and no public exploit code.

Affected product: Softing Secure Integration Server. 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-39482/ (Markdown: https://insights.sbomify.com/CVE-2023-39482/index.md)
```

## Sources

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

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