# CVE-2023-5937: Sensitive data exfiltration via unsafe permissions on Windows systems in Arc before v1.6.0

> Local attackers can read sensitive data from Arc configuration files on Windows due to unsafe world-readable permissions.

- **Severity:** Medium 5.2 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:H/SI:H/SA: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:** 15 May 2024
- **Updated:** 20 Sep 2024
- **Also known as:** GHSA-jwfg-733h-8pc5

## What is CVE-2023-5937?

CVE-2023-5937 is a medium-severity vulnerability in Nozomi Networks Arc, published on 15 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

On Windows systems, the Arc configuration files resulted to be world-readable.

This can lead to information disclosure by local attackers, via exfiltration of sensitive data from configuration files.

Weakness: CWE-538 (Insertion of Sensitive Information into Externally-Accessible File or Directory)

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


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

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

## Is CVE-2023-5937 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-5937 is a medium-severity vulnerability in Nozomi Networks Arc, published on 15 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-5937 in the wild and no public exploit code.

Affected product: Nozomi Networks Arc. 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-5937/ (Markdown: https://insights.sbomify.com/CVE-2023-5937/index.md)
```

## Sources

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

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