# CVE-2023-7234: Integration Objects OPC UA Server Toolkit Improper Output Neutralization for Logs

> An attacker can inject malicious content into logs via the client description field, potentially affecting log integrity or downstream log processing systems.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jan 2024
- **Updated:** 2 Jun 2025
- **Also known as:** GHSA-j8f3-4cqg-mhw4

## What is CVE-2023-7234?

CVE-2023-7234 is a medium-severity vulnerability in Integration Objects OPC UA Server Toolkit, published on 16 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OPCUAServerToolkit will write a log message once an OPC UA client has successfully connected containing the client's self-defined description field.

Weakness: CWE-116 (Improper Encoding or Escaping of Output), CWE-117 (Improper Output Neutralization for Logs)

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

It affects 1 product.


Products: Integrationobjects Opc Ua Server Toolkit.

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

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

## Is CVE-2023-7234 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-7234 is a medium-severity vulnerability in Integration Objects OPC UA Server Toolkit, published on 16 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-7234 in the wild and no public exploit code.

Affected product: Integration Objects OPC UA Server Toolkit. 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-7234/ (Markdown: https://insights.sbomify.com/CVE-2023-7234/index.md)
```

## Sources

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

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