# CVE-2023-30223: Auth bypass in n/a

> Attackers can bypass authentication in 4D Server to perform arbitrary actions via crafted TCP packets, requiring immediate upgrades.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 Jun 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-w8fw-c2w3-8j49

## What is CVE-2023-30223?

CVE-2023-30223 is a high-severity authentication bypass vulnerability in n/a, published on 16 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A broken authentication vulnerability in 4D SAS 4D Server software v17, v18, v19 R7, and earlier allows attackers to send crafted TCP packets containing requests to perform arbitrary actions.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: 4d Server.

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

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

## Is CVE-2023-30223 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-39847](https://insights.sbomify.com/CVE-2024-39847/): Arbitrary File Read and Server Side Request Forgery via XML External Entities in 4D Server SOAP (high 8.7)
- [CVE-2023-30222](https://insights.sbomify.com/CVE-2023-30222/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-30223 is a high-severity authentication bypass vulnerability in n/a, published on 16 Jun 2023. 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-30223 in the wild and no public exploit code.

Affected product: n/a. 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-30223/ (Markdown: https://insights.sbomify.com/CVE-2023-30223/index.md)
```

## Sources

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

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