# CVE-2023-43081: Misconfiguration in PowerProtect Agent for File System

> A local attacker can overwrite log files due to incorrect default permissions in the Dell PowerProtect Agent for File System.

- **Severity:** Medium 4.0 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Nov 2023
- **Updated:** 1 Oct 2024
- **Also known as:** GHSA-6598-w327-pmxr

## What is CVE-2023-43081?

CVE-2023-43081 is a medium-severity vulnerability in Dell PowerProtect Agent for File System, published on 22 Nov 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

PowerProtect Agent for File System Version 19.14 and prior, contains an incorrect default permissions vulnerability in ddfscon component. A low Privileged local attacker could potentially exploit this vulnerability, leading to overwriting of log files.

Weakness: CWE-276 (Incorrect Default Permissions)

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

It affects 1 product.


Products: Dell Powerprotect Agent for File System.

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

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

## Is CVE-2023-43081 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-43081 is a medium-severity vulnerability in Dell PowerProtect Agent for File System, published on 22 Nov 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-43081 in the wild and no public exploit code.

Affected product: Dell PowerProtect Agent for File System. 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-43081/ (Markdown: https://insights.sbomify.com/CVE-2023-43081/index.md)
```

## Sources

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

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