# CVE-2022-38583: Missing authorization in n/a

> Low-privileged users can access shared folders to steal credentials, leading to SQL database admin access and potential code execution.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Apr 2023
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-vc8j-g69q-pqfg

## What is CVE-2022-38583?

CVE-2022-38583 is a high-severity missing authorization vulnerability in n/a, published on 28 Apr 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

On versions of Sage 300 2017 - 2022 (6.4.x - 6.9.x) which are setup in a "Windows Peer-to-Peer Network" or "Client Server Network" configuration, a low-privileged Sage 300 workstation user could abuse their access to the "SharedData" folder on the connected Sage 300 server to view and/or modify the credentials associated with Sage 300 users and SQL accounts to impersonate users and/or access the SQL database as a system administrator. With system administrator-level access to the Sage 300 MS SQL database it would be possible to create, update, and delete all records associated with the program and, depending on the configuration, execute code on the underlying database server.

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2022-38583?

It affects 1 product.


Products: Sage Sage 300.

## How do I fix CVE-2022-38583?

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

## Is CVE-2022-38583 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-38583 exists.

## Other vulnerabilities in n/a

- [CVE-2022-41397](https://insights.sbomify.com/CVE-2022-41397/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2022-41400](https://insights.sbomify.com/CVE-2022-41400/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2021-45492](https://insights.sbomify.com/CVE-2021-45492/): Privilege escalation in n/a (high 7.8)
- [CVE-2022-41398](https://insights.sbomify.com/CVE-2022-41398/): Hardcoded credentials in n/a (high 7.5)
- [CVE-2022-41399](https://insights.sbomify.com/CVE-2022-41399/): Hardcoded credentials in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-38583 and fix it if it is affected.

What it is: CVE-2022-38583 is a high-severity missing authorization vulnerability in n/a, published on 28 Apr 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-38583 exists.

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-2022-38583/ (Markdown: https://insights.sbomify.com/CVE-2022-38583/index.md)
```

## Sources

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

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