# CVE-2023-2737: Improper securing of log directory may allow a denial of service

> An authenticated local attacker can cause denial of service and escalate privileges due to improper log directory permissions in SafeNet Authentication Service.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Aug 2023
- **Updated:** 1 Oct 2024
- **Also known as:** GHSA-348r-gpc5-cffx

## What is CVE-2023-2737?

CVE-2023-2737 is a medium-severity vulnerability in Thales SafeNet Authtentication Service Agent, published on 16 Aug 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper log permissions in SafeNet Authentication Service Version 3.4.0 on Windows allows an authenticated attacker to cause a denial of service via local privilege escalation.

Weakness: CWE-276 (Incorrect Default Permissions)

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

It affects 1 product.


Products: Thalesgroup Safenet Authentication Service.

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

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

## Is CVE-2023-2737 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-2737 is a medium-severity vulnerability in Thales SafeNet Authtentication Service Agent, published on 16 Aug 2023. 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-2737 in the wild and no public exploit code.

Affected product: Thales SafeNet Authtentication Service Agent. 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-2737/ (Markdown: https://insights.sbomify.com/CVE-2023-2737/index.md)
```

## Sources

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

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